Fix startup issues of Tor #1798
Comments
HenrikJannsen
added
network
HenrikJannsen
changed the title
|
Hi Guys, it is my first time running the application and I think i get the issue you are presenting here. Looking at the logs, I get this:
Another thing that I notice, every time that I run the application it goes a bit further in the Bootstrap %. first stoped with 3%, then 6%, 12.50%, 12.75% Hope that it helps. |
Consumers can asynchronously subscribe to directory events with the Flow components. Ref: bisq-network#1798
Presently, we parse Tor's log file to detect when the control port is ready. This is unstable and could break with any Tor update. A better approach is to use Tor's 'ControlPortWriteToFile' config option and parse the control port from that file. Ref: bisq-network#1798
Use the flow-component-based DirectoryWatcher to wait for the control port file and parse the control port file with the ControlPortFileParser afterward. Ref: bisq-network#1798
To select the Tor control port, we bind to a random port, close it and pass the port number to Tor. It can happen that Tor tries to bind to the port before it is closed. In this case, the Tor startup will fail because Tor will never print a line containing "[notice] Opened Control listener connection (ready) on ". Up until now, Bisq monitored the Tor log file to know when the control port is ready. Now Tor writes the control port to a file and Bisq reads that file. Ref: bisq-network#1798
To select the Tor control port, we bind to a random port, close it and pass the port number to Tor. It can happen that Tor tries to bind to the port before it is closed. In this case, the Tor startup will fail because Tor will never print a line containing "[notice] Opened Control listener connection (ready) on ". Up until now, Bisq monitored the Tor log file to know when the control port is ready. Now Tor writes the control port to a file and Bisq reads that file. Ref: bisq-network#1798
To select the Tor control port, we bind to a random port, close it and pass the port number to Tor. It can happen that Tor tries to bind to the port before it is closed. In this case, the Tor startup will fail because Tor will never print a line containing "[notice] Opened Control listener connection (ready) on ". Up until now, Bisq monitored the Tor log file to know when the control port is ready. Now Tor writes the control port to a file and Bisq reads that file. Ref: bisq-network#1798
To select the Tor control port, we bind to a random port, close it and pass the port number to Tor. It can happen that Tor tries to bind to the port before it is closed. In this case, the Tor startup will fail because Tor will never print a line containing "[notice] Opened Control listener connection (ready) on ". Up until now, Bisq monitored the Tor log file to know when the control port is ready. Now Tor writes the control port to a file and Bisq reads that file. Ref: bisq-network#1798
To select the Tor control port, we bind to a random port, close it and pass the port number to Tor. It can happen that Tor tries to bind to the port before it is closed. In this case, the Tor startup will fail because Tor will never print a line containing "[notice] Opened Control listener connection (ready) on ". Up until now, Bisq monitored the Tor log file to know when the control port is ready. Now Tor writes the control port to a file and Bisq reads that file. Ref: bisq-network#1798
When the Tor network is under load, the bootstrap process takes multiple minutes. Tor informs us about the progress with BootstrapEvent's until Tor is ready. Fixes bisq-network#1798
To select the Tor SOCKS5 port, we bind to a random port, close it and pass the port number to Tor. It can happen that Tor tries to bind to the port before it is closed. In this case, the Tor startup will fail. Ref: bisq-network#1798
To select the Tor SOCKS5 port, we bind to a random port, close it and pass the port number to Tor. It can happen that Tor tries to bind to the port before it is closed. In this case, the Tor startup will fail. Ref: bisq-network#1798
|
Actually issue is not solved, I'm using v2.0.4 on Linux, It keeps bootstraping Tor 7% or 11% then "Itializing applicationService failed" and shutdown. |
|
Hi @Raviu56, Could try v2.1.0 and report back? Thank you! |
Tor setup sometimes hangs specially at first time using Bisq2.
The text was updated successfully, but these errors were encountered: