~30 second client disconnect

[sllywhtboy]

hi all,

I set up a relay of a popular public shoutcast stream on my routerbox at home because ~4 people in this place tune into the same stream. i did this to save bandwidth. it's set up with "RIP-Only" because I don't want people on the internet tuning into this server. it's on slackware linux 8.0 w/ kernel 2.4.19 with an AMD k62-450 & 192mb ram. shoutcast/linux 1.9.2

it appears that after ~12 hrs, the clients get disconnected from the server. there's no indication of any 'source-server' issues in the log files. here's a snippet from the logs after the problem starts.

<12/24/02@04:40:25> [dest: 192.168.7.12] starting stream (UID: 323)[L: 2]{A: WinampMPEG/2.8}(P: 1)
<12/24/02@04:40:57> [dest: 192.168.5.12] connection closed (33 seconds) (UID: 322)[L: 1]{Bytes: 256000}(P: 0)
<12/24/02@04:40:57> [dest: 192.168.5.12] starting stream (UID: 324)[L: 2]{A: WinampMPEG/2.8}(P: 0)
<12/24/02@04:40:58> [dest: 192.168.7.12] connection closed (34 seconds) (UID: 323)[L: 1]{Bytes: 256000}(P: 1)
<12/24/02@04:40:59> [dest: 192.168.7.12] starting stream (UID: 325)[L: 2]{A: WinampMPEG/2.8}(P: 1)
<12/24/02@04:41:30> [dest: 192.168.5.12] connection closed (33 seconds) (UID: 324)[L: 1]{Bytes: 256000}(P: 0)
<12/24/02@04:41:31> [dest: 192.168.5.12] starting stream (UID: 326)[L: 2]{A: WinampMPEG/2.8}(P: 0)
<12/24/02@04:41:33> [dest: 192.168.7.12] connection closed (34 seconds) (UID: 325)[L: 1]{Bytes: 256000}(P: 1)
<12/24/02@04:41:35> [dest: 192.168.7.12] starting stream (UID: 327)[L: 2]{A: WinampMPEG/2.8}(P: 1)
<12/24/02@04:42:03> [dest: 192.168.5.12] connection closed (33 seconds) (UID: 326)[L: 1]{Bytes: 256000}(P: 0)
<12/24/02@04:42:03> [dest: 192.168.5.12] starting stream (UID: 328)[L: 2]{A: WinampMPEG/2.8}(P: 0)
<12/24/02@04:42:08> [dest: 192.168.7.12] connection closed (34 seconds) (UID: 327)[L: 1]{Bytes: 256000}(P: 1)
<12/24/02@04:42:10> [dest: 192.168.7.12] starting stream (UID: 329)[L: 2]{A: WinampMPEG/2.8}(P: 1)
<12/24/02@04:42:36> [dest: 192.168.5.12] connection closed (33 seconds) (UID: 328)[L: 1]{Bytes: 256000}(P: 0)
<12/24/02@04:42:37> [dest: 192.168.5.12] starting stream (UID: 330)[L: 2]{A: WinampMPEG/2.8}(P: 0)
<12/24/02@04:42:43> [dest: 192.168.7.12] connection closed (34 seconds) (UID: 329)[L: 1]{Bytes: 256000}(P: 1)
<12/24/02@04:42:45> [dest: 192.168.7.12] starting stream (UID: 331)[L: 2]{A: WinampMPEG/2.8}(P: 1)
<12/24/02@04:43:09> [dest: 192.168.5.12] connection closed (33 seconds) (UID: 330)[L: 1]{Bytes: 256000}(P: 0)
<12/24/02@04:43:10> [dest: 192.168.5.12] starting stream (UID: 332)[L: 2]{A: WinampMPEG/2.8}(P: 0)
<12/24/02@04:43:17> [main] SIGTERM; exiting!

it works fine for a while if i HUP the server.

i've not had any problems like this in the past with relaying servers. any suggestions?

thanks,
--slly

[sllywhtboy]

does it make a difference on the number of interfaces that shoutcast can broadcast through? i know it shouldn't, however i thought i'd ask..

--slly

[sllywhtboy]

is there command switches to invoke a debug mode? this problem is really annoying.

thanks for your help,
--slly

[DJ AmPs]

what happens if you listen on that same server? note that I've ran shoutcast on two net cards under linux - incoming stream on one and outgoing on another. no problems there. looks like a client problem not server.

[sllywhtboy]

i don't/can't tune into this machine, there's no sound card. i do everything with this box through telnet/ssh.

all the clients do is connect to the shoutcast stream as they would connect to any other shoutcast stream. http://sllywhtboy.myftp.org:8002/ and its listen.pls or winamp's play | location | sllywhtboy.myftp.org:8002 (these won't work for any of you, since you're not on the "reserve" list.

--slly

[sllywhtboy]

i noticed something else today that may help you help me!

after a while, the clients connect for 15-35 seconds. however the only data/music being sent to the client is what's stored in the buffer.

when i restart the relay, it's on a totally different song.

this routerbox is linux 2.4.19 w/ iptables packet filtering/NAT software. i've never had any problem with it and keeping sockets open for 12+ hrs. i used to run this relay on a linux box behind my firewall but i had to use it for other things; no problems there.

suggestions?

--slly

[sllywhtboy]

i checked the timing in the logs: the server i'm relaying from restarts itself every day. thanks everyone!

--slly