ShoutCast Error - Centova Cast

Read 18635 times
i have a unix dedicated Server from LeaseWeb with control panel centova cast.
 
one of my client got this error :

<02/09/11@08:08:36> [dest: 91.138.149.136] connection closed (0 seconds) (UID: 0)[L: 0]{Bytes: 41990}(P: 0)
<02/09/11@08:08:36> [dest: 91.138.149.136] starting stream (UID: 1)[L: 1]{A: NSPlayer/12.00.7600.16597 WMFSDK/12.00.7600.16597}(P: 0)
<02/09/11@08:08:36> [dest: 91.138.149.136] connection closed (0 seconds) (UID: 1)[L: 0]{Bytes: 36182}(P: 0)
<02/09/11@08:08:36> [dest: 91.138.149.136] starting stream (UID: 2)[L: 1]{A: NSPlayer/12.00.7600.16597 WMFSDK/12.00.7600.16597}(P: 0)
<02/09/11@08:13:18> [dest: 91.138.149.136] connection closed (282 seconds) (UID: 2)[L: 0]{Bytes: 3750121}(P: 0)
<02/09/11@08:56:53> [dest: 79.166.144.30] starting stream (UID: 3)[L: 1]{A: Windows-Media-Player/12.0.7600.16667}(P: 0)
<02/09/11@08:56:53> [dest: 79.166.144.30] connection closed (0 seconds) (UID: 3)[L: 0]{Bytes: 40960}(P: 0)
<02/09/11@08:56:56> [dest: 79.166.144.30] starting stream (UID: 4)[L: 1]{A: NSPlayer/12.00.7600.16597 WMFSDK/12.00.7600.16597}(P: 0)
<02/09/11@08:56:56> [dest: 79.166.144.30] connection closed (0 seconds) (UID: 4)[L: 0]{Bytes: 40960}(P: 0)
<02/09/11@08:57:00> [dest: 79.166.144.30] starting stream (UID: 5)[L: 1]{A: NSPlayer/12.00.7600.16597 WMFSDK/12.00.7600.16597}(P: 0)
<02/09/11@08:57:32> [dest: 79.166.144.30] connection closed (33 seconds) (UID: 5)[L: 0]{Bytes: 256000}(P: 0)
<02/09/11@08:57:48> [dest: 79.166.144.30] starting stream (UID: 6)[L: 1]{A: Windows-Media-Player/12.0.7600.16667}(P: 0)
<02/09/11@08:57:48> [dest: 79.166.144.30] connection closed (1 seconds) (UID: 6)[L: 0]{Bytes: 40960}(P: 0)
<02/09/11@08:57:51> [dest: 79.166.144.30] starting stream (UID: 7)[L: 1]{A: NSPlayer/12.00.7600.16597 WMFSDK/12.00.7600.16597}(P: 0)
<02/09/11@08:57:51> [dest: 79.166.144.30] connection closed (0 seconds) (UID: 7)[L: 0]{Bytes: 37634}(P: 0)
<02/09/11@08:57:54> [dest: 79.166.144.30] starting stream (UID: 8)[L: 1]{A: NSPlayer/12.00.7600.16597 WMFSDK/12.00.7600.16597}(P: 0)
<02/09/11@08:58:27> [dest: 79.166.144.30] connection closed (33 seconds) (UID: 8)[L: 0]{Bytes: 256000}(P: 0)
<02/09/11@09:01:38> [SHOUTcast] DNAS/Linux v1.9.8 (Feb 28 2007) starting up...
<02/09/11@09:01:38> [main] pid: 29016
<02/09/11@09:01:38> [main] loaded config from /home/centovacast/vhosts/radiosakis/etc/server.conf
<02/09/11@09:01:38> [main] initializing (usermax:50 portbase:8016)...
<02/09/11@09:01:38> [main] No ban file found (etc/sc_serv.ban)
<02/09/11@09:01:38> [main] No rip file found (etc/sc_serv.rip)
<02/09/11@09:01:38> [main] opening source socket
<02/09/11@09:01:38> [main] error opening source socket! FATAL ERROR! Some other process is using this port!

--Some other process is using this port --

Try changing the clients port #
My Auto DJ
Orlando, FL USA
Quality SHOUTcast Hosting http://myautodj.com
SHOUTcast Widgets http://shoutcastwidgets.com
i tried this configuration twice ! i change the port 2 times but nothing changed !
1- Find out what process is using the port:
       netstat -anp|grep xxxx  .... (where xxxx is the port #)
2- Abort the process(s) using that port:
      kill yyyy  ... (where yyyy is the process number)
3- Restart the server

>>>>>>>>>>>>>>>

If this doesn't work, make sure that Host Name and IP address match on the Configure Server page
It can also be caused by specifying a bad IP address.  FYI the best way to diagnose errors like this is simply to punch the error message, verbatim, into our KB search box.  Searching for "FATAL ERROR! Some other process is using this port!" yields the answer to your question.