RadioBOSS continues attempting connections after moving on to next track (still)

eddr

Member
eddr said:
2017-07-21 18:07:56  INFO  [SRC X.X.X.X sid=1] SHOUTcast 1 source disconnected.
2017-07-21 18:07:58  ERROR  [DST 127.0.0.1 sid=1] SHOUTcast 1 client connection rejected. Stream not available as there is no source connected. Agent: `RadioBOSS'
2017-07-21 18:07:58  ERROR  [DST 127.0.0.1 sid=1] SHOUTcast 1 client connection rejected. Stream not available as there is no source connected. Agent: `NSPlayer/12.0.10011.16384 WMFSDK/12.0'
2017-07-21 18:07:58  ERROR  [DST 127.0.0.1 sid=1] SHOUTcast 1 client connection rejected. Stream not available as there is no source connected. Agent: `RadioBOSS'
2017-07-21 18:07:58  ERROR  [DST 127.0.0.1 sid=1] SHOUTcast 1 client connection rejected. Stream not available as there is no source connected. Agent: `NSPlayer/12.0.10011.16384 WMFSDK/12.0'
2017-07-21 18:07:59  INFO  [SRC X.X.X.X sid=1] SHOUTcast 1 source connection starting.

As per the quote above and original post it's quoted from, this still seems to be happening in the latest RadioBOSS whereby it continues to connect to the stream even after RadioBOSS has moved on to the next track and continues to do so for some time - you stated before that this could be down to connection attempts not being completed which may still be queued - but before a connection is attempted a check should be made to see if it even needs to connect no?
 

djsoft

Well-known member
Staff member
eddr said:
but before a connection is attempted a check should be made to see if it even needs to connect no?
It does check it and of course if a track should not be playing, it will not try to connect. I'll add it to the list of bugs to check, just in case.
 

eddr

Member
Ok please if you can that would be great, as it fills up our shoutcast server logs whenever the source disconnects.

Note that we set the network connect attempts to a high number 10000 and duration of the stream really high (many hours).
 

eddr

Member
Also in the previous thread I mentioned the error 40 (timeout) - was a way implemented to stop radioboss moving on to next track?
 

djsoft

Well-known member
Staff member
eddr said:
Note that we set the network connect attempts to a high number 10000 and duration of the stream really high (many hours).
It should not matter as when a track is set to stop, it should also stop anyt pending connection attempts. It's in the queue and we'll check it soon.

eddr said:
Also in the previous thread I mentioned the error 40 (timeout) - was a way implemented to stop radioboss moving on to next track?
Error 40 means that connection is not possible because of network timeout, it should not cause any side effects.
 
Top