Relay go offline

Hi Jason,
yea i am requesting my reseller to provide the customer number or agreement number, if i got the number where to create the ID and open a PMR (or TS i already confused)?

many thanks.

Tony

Hi Jason,
I got a 10 digit oem software agreement number from my reseller but i cant fit in the 7-digit page, any suggestion?

Tony

wrong pic, should be as below

I am having the same issue on a relay also. It was reporting fine until Jun29 and now i see this winsock error 4294967288 error in the logs and the relay went offline.

HI TVN,
My env is 9.5.6, whats ur can you share?

Tony

Technically now they are called “TS” (Tech Support requests) but by convention a lot of us still refer to the former term “PMR”

Click that link for support resource help to send them an email and they should help you.

Hi tonyjar, same version here. 9.5.6.63 to be more precise. I have tried a new relay install. Without the relay installed, the client started reporting back to the console. When i installed the relay, it stopped to post reports after about 20min.

Hi TVN,
somewhat the symptom is very similar to my env.
i just checked with network team, they set a bandwidth control at the outbound data, i am guessing if it limited the data out and resulting disconnection from client. see if it could be any hints for u too, cheers

Tony

Hi tonyjar,

In my case it was a little bit different.

The netstat command showed me that there was something holding the 52311 port, i got that by the logs:
Wed, 11 Jul 2018 10:55:14 -0400 - 1669719840 - Unable to start http server: socket may already be in use on port 52311, next retry in 30 seconds
Wed, 11 Jul 2018 10:50:16 -0400 - PeriodicTasks (650106624) - Error running task UpdateAndSendRelayStatus: HTTP Error 28: Timeout was reached: Connection timed out after 10010 milliseconds
Wed, 11 Jul 2018 10:50:44 -0400 - 1669719840 - Can’t listen on address [0.0.0.0]: 15SocketAddrInUse

And the command:
[root@ ~]# netstat -apn |grep 52311
tcp 0 78661 <ip_number>:52311 <ip_number>:56829 FIN_WAIT1 -
udp 0 0 0.0.0.0:52311 0.0.0.0:* 9332/BESClient

The FIN_WAIT1 - was an orphan process, that i could kill using the tcp orphan file tcp_max_orphans:
cat /proc/sys/net/ipv4/tcp_max_orphans

This makes me think that at some point, the TLR of this relay sent a message but it did not got a response back, which caused the orphan process.

I added the value 0 to the file:
echo 0 > /proc/sys/net/ipv4/tcp_max_orphans

The process FIN_WAIT1 - died.

So i added the original value to the file again:
echo 262144 > /proc/sys/net/ipv4/tcp_max_orphans

After that, i restarted the client and relay and it is up for about 10 hours.

1 Like

Hi TVN,
It really not similar with my case then…
whatever thanks for the sharing,

cheers,
Tony