Possible bug? I think so
 

Okay the following i see with some stations i sometimes help:

In this case the dsp sends it's data to an server on the internal network, which is connected to the outside world. A relay gets it's source from the local shoutcast on the server where is streamed to.

When the connection drops locally and it after a few secs come up again, the relay doesn't connect anymore to the source. It just keeps playing it's buffer over and over again. I saw this with 1.8.3 and 1.8.9

The only solution is to kick the source at the relay and then it connects again to the source and all is just fine. I noticed that this only happens when there are still listeners on the relay.. On a relay with 0 listeners... then there is no problem with a dropout. the server is going offline normally and gets online as soon as the source is back.

This is all linux based streaming. So my question is, why does this happen, why doesn't shoutcast go down if there is no source anymore? I tried many things, but nothing helps.. so i guess it's a bug?

Hoping to get this problem clear,

With kind regards,

Freddy
PureDJ.com Webradio

I just realized that this is also happening to me. I've have a few server problems in the last few days and when my relay server doesnt reccontect to my shoutcast sever the track goes in a 30 second loop. I also noticed that the IP reserve doesnt work and if someone connects to my mp3 source server the relay server just doesnt reconect untill I kick off who the logged in IP.

This seems to be happening with the newest Shoutcast server as I havent seen this happen before.