[Qt Warning] QSslSocket lines at the beginning #132
Comments
|
Missing There seems to be an issue on the Qt bug tracker: |
|
Can confirm warning message...same versions as OP |
|
@chuegel is your server able to connect to other Electrum protocol server peers? E.g. does |
|
Hmm ok, I reproduced the error on a newer Ubuntu system. Yes I can conclude that while the message is super-annoying, it is safe to ignore. My server accepts SSL connections ok, and is able to peer ok with other SSL peers. Sorry about the error -- I'll try and think of a way to fix this. I observed that if I built Fulcrum locally the error disappears (presumably the locally installed Qt5 knows how to find the symbols it needs, etc). This is an artifact of the fact that the static Qt linked into the static binary does dynamic lookup of openssl. A fix would be to install opernssl1.1 and see about adding it to LD_LIBRARY_PATH somehow but that may interfere with your system. I'll try and come up with a fix for this but it's a bit of an onion -- the current build system builds a very compatible binary (supports older openssl1.1 systems, etc). If I force Qt to use newer openssl it may break on older systems.. :/ Of course.. I could always statically-link-in an OpenSSL into the Fulcrum binary I release but I hesitate to do that on account of the fact that system openssl is more likely to contain latest bugfixes. Hmm. A bit of a catch-22. Alternatively I could release a binary that filters these messages out intentionally... Hmm. |
|
Ok, I added a commit to suppress these messages for now. I will issue a Fulcrum release later today (v1.8.0) that will contain this fix. Closing issue as resolved ... |
|
@cculianu Still me appearing these logs in the new release 1.8.0 after the update: Are you sure this issue was fixed? |
|
Hey guys thanks for the feedback. @twofaktor Yeah the "cannot resolve" message was left in there intentionally -- it only happens once at startup. The reason I left it in is so that I don't forget about this and so that I am reminded there is an issue with older Qt and newer openssl. I hope to resolve this -- my current plan is just to offer a a separate linux static build -- one for newer Ubuntu. Alternatively I could actually see about just statically linking OpenSSL into the app directly. tl;dr: I hope to actually solve this. For now I am just "suppressing" the messages that would have appeared with every new SSL connection (which would have filled the log with noise) -- but the initial "cannot resolve X" I am leaving in... until I have a "real" solution. |
|
PS: Just to be clear the symbols that Qt's openssl engine cannot find are not actually used by Fulcrum -- so it's safe to ignore the message at startup... just to be clear. |
Hello,
After starting Fulcrum at the 2 first lines, logs shows me the next 2 warnings lines
[Qt Warning] QSslSocket:At this moment I show this status in logs of Fulcrum, so I think everything is fine for now.:
But, this warning, could affect the proper functioning of the service in the future as SSL connections to wallets for example? do you know the reason and how to fix it?
PD: I have installed:
Ubuntu 22.04.1 LTS amd64 / binaries: Fulcrum-1.7.0-x86_64-linux.tar.gz
openssl 3.0.2-0ubuntu1.6
Thanks!
Edit:
The initial sync has finished, now I show only these logs when I connect a wallet to Fulcrum or BTC RPC Explorer:
Despite these logs, I have not experienced connection or scanning errors, or any kind of failure to connect the wallets.
The text was updated successfully, but these errors were encountered: