Go Back   Winamp Forums > SHOUTcast > SHOUTcast Technical Support
Reload this Page ShoutCAST Stagnant Ports?

Reply
Thread Tools Search this Thread Display Modes
Old 17th March 2004, 16:53   #1
Jasio
Junior Member
 
Join Date: Mar 2004
Location: BC, CANADA
Posts: 10
ShoutCAST Stagnant Ports?
Hello,

I installed and ran shoutCAST without any problems for the first time. The stream worked perfectly, but I had about 4 hours of music placed in the playlist (I was broadcasting from home to the server). I went away for about 6 hours. I come back and see the servers timed out because there is no content being sent to it. I put something on the playlist again, but it failed to stream. The plug suddenly counldnt connect to the server. So I shutdown ./sc_serv , the server was running fine, and I simply restarted ./sc_serv (I run the shoutcast on redhat linux enterprise 3.0 es) and now I suddenly started getting this message:

<03/17/04@09:36:00> [dest: 66.188.230.69] server unavailable, disconnecting
<03/17/04@09:36:00> [dest: 82.38.57.39] server unavailable, disconnecting
<03/17/04@09:36:00> [dest: 68.91.108.68] server unavailable, disconnecting
<03/17/04@09:36:00> [dest: 66.188.230.69] server unavailable, disconnecting
<03/17/04@09:36:00> [dest: 82.38.57.39] server unavailable, disconnecting
<03/17/04@09:36:01> [dest: 68.91.108.68] server unavailable, disconnecting
<03/17/04@09:36:01> [dest: 66.188.230.69] server unavailable, disconnecting
<03/17/04@09:36:01> [dest: 68.91.108.68] server unavailable, disconnecting
<03/17/04@09:36:01> [dest: 82.38.57.39] server unavailable, disconnecting
<03/17/04@09:36:01> [dest: 66.188.230.69] server unavailable, disconnecting
<03/17/04@09:36:02> [dest: 68.91.108.68] server unavailable, disconnecting
<03/17/04@09:36:02> [dest: 82.38.57.39] server unavailable, disconnecting
<03/17/04@09:36:02> [dest: 66.188.230.69] server unavailable, disconnecting
<03/17/04@09:36:02> [dest: 68.91.108.68] server unavailable, disconnecting
<03/17/04@09:36:02> [dest: 66.188.230.69] server unavailable, disconnecting

I think there were previous connections to the stream, that seem to have been left open.

I ran netstat -an|grep :8000 (8000 is the port of course)

And this is what I got:

tcp 0 0 69.93.213.18:8000 0.0.0.0:* LISTEN
tcp 0 0 69.93.213.18:8000 68.91.108.68:4641 SYN_RECV
tcp 0 0 69.93.213.18:8000 68.91.108.68:4642 SYN_RECV
tcp 0 0 69.93.213.18:8000 66.188.230.69:4498 SYN_RECV
tcp 0 0 69.93.213.18:8000 66.188.230.69:4499 SYN_RECV
tcp 0 0 69.93.213.18:8000 82.38.57.39:4254 SYN_RECV
tcp 0 0 69.93.213.18:8000 82.38.57.39:4285 SYN_RECV
tcp 0 0 69.93.213.18:8000 66.188.230.69:4500 SYN_RECV
tcp 0 0 69.93.213.18:8000 68.91.108.68:4643 SYN_RECV
tcp 0 0 69.93.213.18:8000 82.38.57.39:4319 SYN_RECV
tcp 115 0 69.93.213.18:8000 82.38.57.39:3004 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3321 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4446 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4447 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3451 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4445 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3383 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3313 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3248 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 24.26.227.161:2487 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3179 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3493 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3107 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3042 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3421 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3484 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:2972 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3035 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4466 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4464 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3351 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4465 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3280 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3411 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3218 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4458 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4459 CLOSE_WAIT
tcp 380 0 69.93.213.18:8000 69.139.124.71:3204 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4456 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4457 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4462 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4463 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3211 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4460 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3147 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4461 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4450 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3140 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4451 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4448 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4449 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4454 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4455 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4452 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 66.188.230.69:4453 CLOSE_WAIT
tcp 115 0 69.93.213.18:8000 82.38.57.39:3074 CLOSE_WAIT

I'm a bit lost as to why it would suddenly up and decided to stop and not work properly.

Any ideas ? As a final note, the conf file is set correctly to the appropriate IPs because it streamed just fine before.
Jasio is offline   Reply With Quote
Old 17th March 2004, 17:03   #2
FesterHead
Alumni
 
FesterHead's Avatar
 
Join Date: Sep 2001
Location: Maui, Hawaii
Posts: 14,109
What's the stream bitrate?

I use 56kbps and noticed the same disconnection behavior if the source drops from the DNAS.
The listener is dangling until the source reconnects.
I don't think it's harmful.

As to why the source wouldn't connect, can't help there.
I don't use sc_trans, sorry.
FesterHead is offline   Reply With Quote
Old 17th March 2004, 17:11   #3
Jasio
Junior Member
 
Join Date: Mar 2004
Location: BC, CANADA
Posts: 10
I use a 128kbps stream, the dangling listeners are annoying because I cannot start the service again. And I am using ./sc_serv not sc_trans just for reference.
Jasio is offline   Reply With Quote
Old 17th March 2004, 17:19   #4
FesterHead
Alumni
 
FesterHead's Avatar
 
Join Date: Sep 2001
Location: Maui, Hawaii
Posts: 14,109
The DNAS shouldn't need a restart if the source drops.

What are you using?
I assumed sc_trans.
FesterHead is offline   Reply With Quote
Old 17th March 2004, 17:36   #5
Jasio
Junior Member
 
Join Date: Mar 2004
Location: BC, CANADA
Posts: 10
What exactly is sc_trans ?

Shouldnt there be a simple command to kill all connections to a port ? I mean if I have connections to it, as root I should be able to boot everyone off... any ideas as to what the command is ?
Last edited by Jasio; 17th March 2004 at 18:56.
Jasio is offline   Reply With Quote
Old 17th March 2004, 21:52   #6
FesterHead
Alumni
 
FesterHead's Avatar
 
Join Date: Sep 2001
Location: Maui, Hawaii
Posts: 14,109
sc_trans = SHOUTcast Broadcasting Tools for Mac OS X, Linux, and FreeBSD

Sorry, my knowledge of *nix is limited to speeling
FesterHead is offline   Reply With Quote
Old 17th March 2004, 21:56   #7
Jasio
Junior Member
 
Join Date: Mar 2004
Location: BC, CANADA
Posts: 10
I am using the DSP plugin for Winamp 2.x on my home windows xp machine and broadcasting it to my linux server which is relaying it to the web.

All the songs are on my comp, not on the server, so I shouldnt need sc_trans installed.
Jasio is offline   Reply With Quote
Old 17th March 2004, 22:23   #8
FesterHead
Alumni
 
FesterHead's Avatar
 
Join Date: Sep 2001
Location: Maui, Hawaii
Posts: 14,109
Is "repeat" toggled?
FesterHead is offline   Reply With Quote
Old 17th March 2004, 23:43   #9
Jasio
Junior Member
 
Join Date: Mar 2004
Location: BC, CANADA
Posts: 10
Repeat is toggled off.

I solved the problem by binding the server to another IP (have about 8 free IPs) but if this happens again, I will uninstall shoutcast and go for Icecast if I had to change ports everytime the server decides to crap out.

For now its ok, but as I posted in a new thread, once one thing works, another thing breaks...
Jasio is offline   Reply With Quote
Old 18th March 2004, 01:09   #10
peppert
UID 0
 
peppert's Avatar
 
Join Date: May 2000
Location: a tent outside forums.winamp.com
Posts: 230
shutting down any unix process with sockets open with anything but a SIGTERM (kill -TERM, ctrl-C from the display) will result in hung sockets until your tcp finwait timeout is reached. SHOUTcast will gracefully shutdown all sockets and disconnect them if you use kill -TERM instead of kill -9.
peppert is offline   Reply With Quote
Old 18th March 2004, 01:42   #11
Jasio
Junior Member
 
Join Date: Mar 2004
Location: BC, CANADA
Posts: 10
Ahh excellent. Thank you very much.
Jasio is offline   Reply With Quote
Reply
Go Back   Winamp Forums > SHOUTcast > SHOUTcast Technical Support
Reload this Page ShoutCAST Stagnant Ports?

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Winamp.com - Archive - Top
Send Feedback

Android is a trademark of Google Inc. Use of this trademark is subject to Google Permissions.

The free customizable Winamp media player that plays mp3 + other audio files,

syncs your iPod, subscribes to Podcasts and more.

Copyright © 1999 - 2013 Nullsoft. All Rights Reserved.

Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.