-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
SSL error monero v0.14.1.0 #5717
Comments
|
Here you are. But i do not think i did the "gdb monerod core*" part correct, right!?:~$ gdb monerod core* |
You need to give the path to monerod, so: gdb /home/monero/monero-arm-linux-gnueabihf/monerod core* |
$ gdb /home/monero/monero-arm-linux-gnueabihf/monerod core* |
output should be ok now i think?! |
Can you also |
Sure! I hope i understood the backtics the right way ;)' |
Almost there :) Please provide the full output of Thanks /Edit: (like this)
|
I hope i got it right(gdb) disas |
Good enough :) @moneromooo-monero: Looks like the issue is confirmed on ARMv7. It only seems to happen after v4. |
Ok, glad i could help. And i hope you find a solution soon to fix this. |
I'm a little embarrassed to admit that, but unfortunately I do not know how to get that inserted the right way. |
Is the actual download for ARMv7 devices patched already? |
No. |
Oh, but you can get a build bot binary from the bottom of the #5726 PR when the link for ARM pops up, they're slow to build and I just updated the patch after review. |
i am sorry but i do not seem to get it done |
But if it worked for you it might be fine. So if you add the patch to the ARMv7 download, i can go the standart way to set everything up and run the sync |
For what it's worth this issue is not limited to ARM, I get it on x86 when starting the daemon via the GUI General system specs FWIW:
|
So this is not solved/ patched till now? I am using v14.0.0.0 at the moment till this is done but the last v is much slower and sometimes too slow to broadcast sucessfull on arm v7 devices |
@blacksheepicu - Have you tried CLI v0.14.1.2 (which got released a few days ago)? |
Yes i tested v0.14.1.2 now. This version seems to work flawles! |
I found a bug in the new monero command line version (the official download) for ARMv7 devices.
Download link: https://downloads.getmonero.org/cli/linuxarm7
First thing to say, i had the old version of Monerod running flawles in the same environment.
After seting up a fresh system (Cubietruck /Cubieboard3 with Armbian OS) for v0.14.1.0 and building monerod up as i should it seems to start good and syncs fast.
When the process reaches 66% sync, this appears in monerods logs and he stops working:
"
2019-06-27 03:24:22.495 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1390 �[1;33mSynced 1237971/1865802 (66%, 627831 left)�[0m
2019-06-27 15:49:30.527 b6f14210 INFO logging contrib/epee/src/mlog.cpp:273 New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,serialization:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2019-06-27 15:49:30.529 b6f14210 INFO global src/daemon/main.cpp:281 Monero 'Boron Butterfly' (v0.14.1.0-release)
2019-06-27 15:49:30.532 b6f14210 INFO global contrib/epee/src/net_ssl.cpp:124 Generating SSL certificate
2019-06-27 15:49:46.772 b6f14210 ERROR msgwriter src/common/scoped_message_writer.h:102 Error: Couldn't connect to daemon: 192.168.0.171:18081
"
When i start monerod again and watch syncing i see this popping up before he shuts down:
"2019-07-01 12:42:18.241 I Synced 1246238/1868959 (66%, 622721 left)
Segmentation fault"
I set three new instances up with a clean system-> same result!
Then i used another device (BananaPi Pro+ Armbian)-> same problem!
Some SSL bugs makes going farer impossible.
And after the error in the first run monerod also stops to update his log data.
The text was updated successfully, but these errors were encountered: