Health Checks Spinning

On seven
Screenshot_2024-08-18_14-49-17
of my installed services, the ‘Health Checks’ keep spinning, and it says ‘Awaiting result…’ The services all seem to be working okay. Is there something I should check? I am running Start9 on a plain old desktop with an i5 Intel chip.

Hey! If they are all working fine, try restaring the whole server.

1 Like

And if after a restart it’s doing the same… the next place to look is always the logs, the source of truth for all services.

Every service exposes its logs at Service Name → Logs

1 Like

The log say it is sending a handshake but there is a problem connecting to the onion peer…

Actually seeing the logs rather than a description of them might help. You might be having issues with Tor inside this service (yes it uses it’s own instance of Tor that can’t be reset in the typical way as with the StartOS system Tor instance).

You could restart the service after a period of being off (you should get a new circuit), or if you have SSH set up…

Reset Tor and wipe state in the Jam container, first SSH in:

  sudo podman exec -it jam.embassy bash

Then issue the command:

  dinitctl stop jmwalletd && dinitctl stop ob-watcher && dinitctl stop tor && rm /home/tor/.tor/state && dinitctl start tor && dinitctl start ob-watcher && dinitctl start jmwalletd
1 Like

2024-08-22T16:33:01-04:00 2024-08-22 20:33:00,526 [INFO] Sending this handshake: {“app-name”: “joinmarket”, “directory”: false, “location-string”: “NOT-SERVING-ONION”, “proto-ver”: 5, “features”: {}, “nick”: “J54rXsU9TwcRDPDb”, “network”: “mainnet”} to peer 3kxw6lf5vf6y26emzwgibzhrzhmhqiw6ekrek3nqfjjmhwznb2moonad.onion:5222
2024-08-22T16:33:01-04:00 2024-08-22 20:33:00,978 [INFO] Going to reattempt connection to 3kxw6lf5vf6y26emzwgibzhrzhmhqiw6ekrek3nqfjjmhwznb2moonad.onion:5222 in 13304.026920318604 seconds.
2024-08-22T17:20:07-04:00 2024-08-22 21:20:06,699 [INFO] Failed to connect to peer wkd3kd73ze62sqhlj2ebwe6fxqvshw5sya6nkvrgcweegt7ljhuspaid.onion:5222
2024-08-22T17:20:07-04:00 2024-08-22 21:20:06,699 [INFO] Going to reattempt connection to wkd3kd73ze62sqhlj2ebwe6fxqvshw5sya6nkvrgcweegt7ljhuspaid.onion:5222 in 13306.026920318604 seconds.
2024-08-22T17:22:56-04:00 2024-08-22 21:22:56,293 [INFO] Failed to connect to peer ylegp63psfqh3zk2huckf2xth6dxvh2z364ykjfmvsoze6tkfjceq7qd.onion:5222
2024-08-22T17:22:56-04:00 2024-08-22 21:22:56,293 [INFO] Going to reattempt connection to ylegp63psfqh3zk2huckf2xth6dxvh2z364ykjfmvsoze6tkfjceq7qd.onion:5222 in 13302.026920318604 seconds.
2024-08-22T17:23:50-04:00 2024-08-22 21:23:50,081 [INFO] Failed to connect to peer g3hv4uynnmynqqq2mchf3fcm3yd46kfzmcdogejuckgwknwyq5ya6iad.onion:5222
2024-08-22T17:23:50-04:00 2024-08-22 21:23:50,081 [INFO] Going to reattempt connection to g3hv4uynnmynqqq2mchf3fcm3yd46kfzmcdogejuckgwknwyq5ya6iad.onion:5222 in 13306.026920318604 seconds.
2024-08-22T20:15:27-04:00 2024-08-23 00:15:27,078 [INFO] Updating status to connected for peer 3kxw6lf5vf6y26emzwgibzhrzhmhqiw6ekrek3nqfjjmhwznb2moonad.onion:5222.

Continued Tor connectivity issues. But is this the only thing in the logs? I assume the health checks are still spinning?

Yes, still spinning. Here is some more of the log:

2024-08-23T07:20:51-04:00 2024-08-23 11:20:50,554 [INFO] We, NOT-SERVING-ONION, are calling the handshake callback as client.
2024-08-23T07:20:51-04:00 2024-08-23 11:20:50,554 [INFO] Sending this handshake: {“app-name”: “joinmarket”, “directory”: false, “location-string”: “NOT-SERVING-ONION”, “proto-ver”: 5, “features”: {}, “nick”: “J54rXsU9TwcRDPDb”, “network”: “mainnet”} to peer 3kxw6lf5vf6y26emzwgibzhrzhmhqiw6ekrek3nqfjjmhwznb2moonad.onion:5222
2024-08-23T08:08:29-04:00 2024-08-23 12:08:29,250 [INFO] Failed to connect to peer wkd3kd73ze62sqhlj2ebwe6fxqvshw5sya6nkvrgcweegt7ljhuspaid.onion:5222
2024-08-23T08:08:29-04:00 2024-08-23 12:08:29,253 [INFO] Going to reattempt connection to wkd3kd73ze62sqhlj2ebwe6fxqvshw5sya6nkvrgcweegt7ljhuspaid.onion:5222 in 13300.026920318604 seconds.
2024-08-23T08:11:06-04:00 2024-08-23 12:11:06,425 [INFO] Failed to connect to peer g3hv4uynnmynqqq2mchf3fcm3yd46kfzmcdogejuckgwknwyq5ya6iad.onion:5222
2024-08-23T08:11:06-04:00 2024-08-23 12:11:06,425 [INFO] Going to reattempt connection to g3hv4uynnmynqqq2mchf3fcm3yd46kfzmcdogejuckgwknwyq5ya6iad.onion:5222 in 13302.026920318604 seconds.
2024-08-23T08:11:41-04:00 2024-08-23 12:11:40,645 [INFO] Failed to connect to peer ylegp63psfqh3zk2huckf2xth6dxvh2z364ykjfmvsoze6tkfjceq7qd.onion:5222
2024-08-23T08:11:41-04:00 2024-08-23 12:11:40,645 [INFO] Going to reattempt connection to ylegp63psfqh3zk2huckf2xth6dxvh2z364ykjfmvsoze6tkfjceq7qd.onion:5222 in 13302.026920318604 seconds.
2024-08-23T11:50:55-04:00 2024-08-23 15:50:55,519 [INFO] Failed to connect to peer wkd3kd73ze62sqhlj2ebwe6fxqvshw5sya6nkvrgcweegt7ljhuspaid.onion:5222
2024-08-23T11:50:55-04:00 2024-08-23 15:50:55,520 [INFO] Going to reattempt connection to wkd3kd73ze62sqhlj2ebwe6fxqvshw5sya6nkvrgcweegt7ljhuspaid.onion:5222 in 13303.026920318604 seconds.
2024-08-23T11:53:27-04:00 2024-08-23 15:53:27,830 [INFO] Failed to connect to peer ylegp63psfqh3zk2huckf2xth6dxvh2z364ykjfmvsoze6tkfjceq7qd.onion:5222
2024-08-23T11:53:27-04:00 2024-08-23 15:53:27,830 [INFO] Going to reattempt connection to ylegp63psfqh3zk2huckf2xth6dxvh2z364ykjfmvsoze6tkfjceq7qd.onion:5222 in 13303.026920318604 seconds.
2024-08-23T11:54:20-04:00 2024-08-23 15:54:20,240 [INFO] Failed to connect to peer g3hv4uynnmynqqq2mchf3fcm3yd46kfzmcdogejuckgwknwyq5ya6iad.onion:5222
2024-08-23T11:54:20-04:00 2024-08-23 15:54:20,240 [INFO] Going to reattempt connection to g3hv4uynnmynqqq2mchf3fcm3yd46kfzmcdogejuckgwknwyq5ya6iad.onion:5222 in 13304.026920318604 seconds.
2024-08-23T14:41:28-04:00 2024-08-23 18:41:28,474 [INFO] Going to reattempt connection to bqlpq6ak24mwvuixixitift4yu42nxchlilrcqwk2ugn45tdclg42qid.onion:5222 in 1167.717041015625 seconds.
2024-08-23T15:01:08-04:00 2024-08-23 19:01:08,218 [INFO] Updating status to connected for peer bqlpq6ak24mwvuixixitift4yu42nxchlilrcqwk2ugn45tdclg42qid.onion:5222.
2024-08-23T15:01:08-04:00 2024-08-23 19:01:08,220 [INFO] We, NOT-SERVING-ONION, are calling the handshake callback as client.
2024-08-23T15:01:08-04:00 2024-08-23 19:01:08,220 [INFO] Sending this handshake: {“app-name”: “joinmarket”, “directory”: false, “location-string”: “NOT-SERVING-ONION”, “proto-ver”: 5, “features”: {}, “nick”: “J54rXsU9TwcRDPDb”, “network”: “mainnet”} to peer bqlpq6ak24mwvuixixitift4yu42nxchlilrcqwk2ugn45tdclg42qid.onion:5222
2024-08-23T15:32:44-04:00 2024-08-23 19:32:43,736 [INFO] Failed to connect to peer wkd3kd73ze62sqhlj2ebwe6fxqvshw5sya6nkvrgcweegt7ljhuspaid.onion:5222
2024-08-23T15:32:44-04:00 2024-08-23 19:32:43,737 [INFO] Going to reattempt connection to wkd3kd73ze62sqhlj2ebwe6fxqvshw5sya6nkvrgcweegt7ljhuspaid.onion:5222 in 13304.026920318604 seconds.
2024-08-23T15:35:17-04:00 2024-08-23 19:35:16,531 [INFO] Failed to connect to peer ylegp63psfqh3zk2huckf2xth6dxvh2z364ykjfmvsoze6tkfjceq7qd.onion:5222
2024-08-23T15:35:17-04:00 2024-08-23 19:35:16,532 [INFO] Going to reattempt connection to ylegp63psfqh3zk2huckf2xth6dxvh2z364ykjfmvsoze6tkfjceq7qd.onion:5222 in 13305.026920318604 seconds.
2024-08-23T15:36:10-04:00 2024-08-23 19:36:09,785 [INFO] Failed to connect to peer g3hv4uynnmynqqq2mchf3fcm3yd46kfzmcdogejuckgwknwyq5ya6iad.onion:5222
2024-08-23T15:36:10-04:00 2024-08-23 19:36:09,786 [INFO] Going to reattempt connection to g3hv4uynnmynqqq2mchf3fcm3yd46kfzmcdogejuckgwknwyq5ya6iad.onion:5222 in 13303.026920318604 seconds.
2024-08-23T17:59:01-04:00 2024-08-23 21:59:01,692 [INFO] Going to reattempt connection to bqlpq6ak24mwvuixixitift4yu42nxchlilrcqwk2ugn45tdclg42qid.onion:5222 in 1750.5755615234375 seconds.
2024-08-23T18:28:20-04:00 2024-08-23 22:28:20,131 [INFO] Updating status to connected for peer bqlpq6ak24mwvuixixitift4yu42nxchlilrcqwk2ugn45tdclg42qid.onion:5222.
2024-08-23T18:28:20-04:00 2024-08-23 22:28:20,133 [INFO] We, NOT-SERVING-ONION, are calling the handshake callback as client.
2024-08-23T18:28:20-04:00 2024-08-23 22:28:20,133 [INFO] Sending this handshake: {“app-name”: “joinmarket”, “directory”: false, “location-string”: “NOT-SERVING-ONION”, “proto-ver”: 5, “features”: {}, “nick”: “J54rXsU9TwcRDPDb”, “network”: “mainnet”} to peer bqlpq6ak24mwvuixixitift4yu42nxchlilrcqwk2ugn45tdclg42qid.onion:5222
2024-08-23T18:28:20-04:00 2024-08-23 22:28:20,134 [INFO] Going to reattempt connection to bqlpq6ak24mwvuixixitift4yu42nxchlilrcqwk2ugn45tdclg42qid.onion:5222 in 2628.3633422851562 seconds.
2024-08-23T19:12:17-04:00 2024-08-23 23:12:16,611 [INFO] Updating status to connected for peer bqlpq6ak24mwvuixixitift4yu42nxchlilrcqwk2ugn45tdclg42qid.onion:5222.
2024-08-23T19:12:17-04:00 2024-08-23 23:12:16,613 [INFO] We, NOT-SERVING-ONION, are calling the handshake callback as client.
2024-08-23T19:12:17-04:00 2024-08-23 23:12:16,613 [INFO] Sending this handshake: {“app-name”: “joinmarket”, “directory”: false, “location-string”: “NOT-SERVING-ONION”, “proto-ver”: 5, “features”: {}, “nick”: “J54rXsU9TwcRDPDb”, “network”: “mainnet”} to peer bqlpq6ak24mwvuixixitift4yu42nxchlilrcqwk2ugn45tdclg42qid.onion:5222
2024-08-23T19:12:17-04:00 2024-08-23 23:12:16,950 [INFO] Going to reattempt connection to bqlpq6ak24mwvuixixitift4yu42nxchlilrcqwk2ugn45tdclg42qid.onion:5222 in 3942.0450134277344 seconds.
2024-08-23T19:14:34-04:00 2024-08-23 23:14:33,591 [INFO] Failed to connect to peer wkd3kd73ze62sqhlj2ebwe6fxqvshw5sya6nkvrgcweegt7ljhuspaid.onion:5222
2024-08-23T19:14:34-04:00 2024-08-23 23:14:33,592 [INFO] Going to reattempt connection to wkd3kd73ze62sqhlj2ebwe6fxqvshw5sya6nkvrgcweegt7ljhuspaid.onion:5222 in 13305.026920318604 seconds.
2024-08-23T19:17:06-04:00 2024-08-23 23:17:06,428 [INFO] Failed to connect to peer ylegp63psfqh3zk2huckf2xth6dxvh2z364ykjfmvsoze6tkfjceq7qd.onion:5222
2024-08-23T19:17:06-04:00 2024-08-23 23:17:06,428 [INFO] Going to reattempt connection to ylegp63psfqh3zk2huckf2xth6dxvh2z364ykjfmvsoze6tkfjceq7qd.onion:5222 in 13306.026920318604 seconds.

I’ve had occasions where I needed to reset TOR more than once to get a good circuit that was reliable. That may be the case here too.

How do i reset TOR? Do i need to shut the whole system down? Does each service have its own TOR circuit or do they all use the same one? Only 7 of my health checks keep spinning. Most of them do not.

System → Manage → Experimental Features → Reset TOR

The above does not shut the whole system down. Just resets TOR

You can also look at the TOR logs: System ->Insights->TOR Logs

1 Like

Thank you. I had not looked into the experimental tab.

That’s for the system Tor. Most services use that but Jam uses it’s own Tor instance and it must be reset like this:

2 Likes

I restarted and now they are fine. :slight_smile:

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.