-
Notifications
You must be signed in to change notification settings - Fork 418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
segfault at 0 ip 00005602580ea423 sp 00007ffbbd7f9910 error 4 in i2pd[560257fe3000+2eb000] #1738
Comments
Please enable coredump saving and install i2pd-dbgsym package. sudo apt-get install gdb i2pd-dbgsym
sudo mkdir /etc/systemd/system/i2pd.service.d
sudo echo -e "[Service]\nLimitCORE=infinity" > /etc/systemd/system/i2pd.service.d/override.conf
sudo systemctl daemon-reload
sudo systemctl restart i2pd Wait for crash, then go to |
-> E: Unable to locate package i2pd-dbgsym $ sudo apt search i2pd* My Linux experience is low and my /etc/apt/sources.list like this. i do not see any dbgsym deb package or such downloadable. |
Where you got package? |
Please use our repository: https://repo.i2pd.xyz/.help/readme.html |
it was .deb from github.com/PurpleI2P/i2pd/.
In repository is:
so i have installed it: and coredumps are created using command: so i will inform if crash happen again.. |
I got a similar segfault right out of the blues, after updating i2pd using your repo seemed to solve the issue. |
I don't know if same crash but: |
Looks like old version. Update to 2.41.0. |
Maybe same issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008087 |
2.41.0 from https://repo.i2pd.xyz/.help/readme.html fixed the issue for me |
Getting similar kind of segfault on Ubuntu 22.04 and I2PD 2.41 from the repo
Backtrace here: https://pastebin.com/jTs1ZtT9 |
Rolled back to version 2.29.0 and the problem seems to be gone (UPD: see my comment below). Must be some kind of regression. |
Try package from i2pd-git PPA: https://launchpad.net/~purplei2p/+archive/ubuntu/i2pd-git |
What can I confirm so far:
Haven't tried version from |
In that case build i2pd yourself and run it using gdb to check what happens.
Maybe also here can be problem with AES-NI on Ubuntu 22.04, can you try to disable it in config file in section
After a time it will crash when router meet some of SSU2-enabled peers. |
Tested with release package and i2pd-git (https://launchpad.net/~purplei2p/+archive/ubuntu/i2pd-git/+sourcepub/13492589/+listing-archive-extra): release crashes with malloc - seems like launchpad builds shit like always, for trunk package - crashing too. But local build using trunk works (not tested for long) with OpenSSL 3.0.2 and without any issues with OpenSSL 1.1.1. |
So, it's been two weeks on i2pd 2.35.0. No problems or crashes whatsoever. I guess I'm stuck with it until some incompatible changes in the protocol will be introduced. Thanks @r4sas , but I don't have much freedom of experiment on this machine. It should work and be accessible 24/7/365, and with 2.35.0 it does. |
In any case, we do not recommend using older versions. We are currently unable to update the code to use the new OpenSSL API due to breaking changes in some parts of its code (some things just broken...).
You can build the binary and run it in parallel with 2.35 to make checks. |
I've made some changes in package building process, please test package |
Linux Debian "systemctl status i2pd" shown:
https://www.quora.com/What-is-a-SEGV-in-Linux
checking "sudo journalctl -xg SEGV"
and then the lines around the time using "sudo journalctl -x --since today" i have found:
Last minute of the /var/log/i2pd/i2pd.log
is here
currently SWAP is 0 bytes free and normal memory is 9.4Gi free
If i should try something, let me know please.
The text was updated successfully, but these errors were encountered: