Opened 4 years ago

Last modified 9 months ago

#119 new defect

Pull relays do not reconnect, recover on 2.0.36

Reported by: mark@… Owned by: stoecker
Priority: major Component: Professional Caster
Version: Keywords:


We have run into an issue with relays reconnecting to sources that go away and then come back. Our relevant configuration is:

relay pull -i u:p -m /RTCM3EPH

max_clients 10000
max_clients_per_source 1000
max_sources 40
max_admins 2
throttle 0

max_ip_connections 1000

I'm going through the code trying to understand how timeouts to read connections like this would be applied. Is there some configuration we're missing that could help us recover quickly?

We had a recent outage where our BKG relay did not recover after a relay source went down for 15 minutes - the BKG relay stayed down for 2 hours, while our other caster (a SNIP) recovered the stream after 15 minutes.

Any advice in debugging this would be very appreciated. I'm thinking about adding a setsockopt call with SOL_TCP and TCP_USER_TIMEOUT on the sockets to improve timeouts.

Attachments (0)

Change History (0)

Modify Ticket

Change Properties
as new The owner will remain stoecker.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from stoecker to the selected user. Next status will be 'assigned'.
Next status will be 'needinfo'. The owner will be changed from stoecker to mark@….
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from stoecker to anonymous. Next status will be 'accepted'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.