Removing Noise with AI - RM Noise

Posted: **Wed Jan 10, 2024 4:23 pm**

Maybe this is known, or maybe problem on my end, or maybe just expected behaior. It appears that 84.73.217.148 is down however I can ping 84.73.217.148 ok. The "socket CONNECT exception" message repeats
---
2024-01-10 08:18:18.485894 84.73.217.148 : attempting to connect on port: 11109
2024-01-10 08:18:39.509029 84.73.217.148 : error: cannot connect to: 84.73.217.148 socket CONNECT exception - retrying [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2024-01-10 08:18:47.510184 84.73.217.148 : attempting to connect on port: 11109
2024-01-10 08:19:08.535835 84.73.217.148 : error: cannot connect to: 84.73.217.148 socket CONNECT exception - retrying [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2024-01-10 08:19:16.536923 84.73.217.148 : attempting to connect on port: 11109
2024-01-10 08:19:37.556529 84.73.217.148 : error: cannot connect to: 84.73.217.148 socket CONNECT exception - retrying [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2024-01-10 08:19:44.815597 Stats report

Posted: **Wed Jan 10, 2024 4:33 pm**

That's a good catch

Very well observed. Rmnoise3 is currently undergoing maintenance, everybody connected to rmnoise3 has been moved to one of the remaining RM Noise servers. Still, the client software polls rmnoise3, once up it will be ready to connect to. RMNoise3 is the Server in Switzerland and does not play a vital role for users in the US.

Posted: **Wed Jan 10, 2024 4:39 pm**

OK, as expected then.. while the frequency seems high, the performance for my US station seems unaffected.

Posted: **Wed Jan 10, 2024 4:40 pm**

The frequency has to be high, to guarantee a quick failover and failback

Posted: **Wed Jan 10, 2024 5:51 pm**

That frequency was changed on later versions. I suspect you are using pre9. The latest public version - pre15c - tries twice with 8 seconds between tries, then slows to 60 seconds between tries.

Pre15c:
https://ournetplace.com/rm-noise/new-se ... rs-wanted/

System Status:
https://ournetplace.com/rm-noise/system-status/

Posted: **Fri Jan 12, 2024 5:20 pm**

Upgraded to pre15c
Now all i see in the terminal window is this:

Code: Select all

started...
loading config.
started waterfall process
started stats process

Nothing more after about ten minutes.
IDK if this is intentional, but I did enjoying watch the behind the scenes activity.

Posted: **Fri Jan 12, 2024 5:31 pm**

Works as designed check the "full log" in the "info" window

Posted: **Sat Jan 13, 2024 3:49 pm**

Works as designed check the "full log" in the "info" window

Ahh I see.. suggest an addition to:
https://ournetplace.com/rm-noise/documentation/
as time permits. 73

Posted: **Wed Jan 17, 2024 5:33 am**

W4ZD wrote: ↑Sat Jan 13, 2024 3:49 pm
Works as designed check the "full log" in the "info" window
Ahh I see.. suggest an addition to:
https://ournetplace.com/rm-noise/documentation/
as time permits. 73

Done.

Removing Noise with AI - RM Noise

Server down? Multiple reconnect attempts

Server down? Multiple reconnect attempts

Re: Server down? Multiple reconnect attempts

Re: Server down? Multiple reconnect attempts

Re: Server down? Multiple reconnect attempts

Re: Server down? Multiple reconnect attempts

Re: Server down? Multiple reconnect attempts

Re: Server down? Multiple reconnect attempts

Re: Server down? Multiple reconnect attempts

Re: Server down? Multiple reconnect attempts