Shoutcast

[Sekka]

Hi there,

I am new to servers and SSH so bear with me.

I have download and placed Shoutcast on my dedicated server running plesk.

I have configured it to run on the port 8500 and when I type "./sc_serv sc_serv.conf" it starts running. I get the following,

<08/08/06@17:03:45> [SHOUTcast] DNAS/Linux v1.9.7 (Jun 23 2006) starting up...
<08/08/06@17:03:45> [main] pid: 12161
<08/08/06@17:03:45> [main] loaded config from sc_serv.conf
<08/08/06@17:03:45> [main] initializing (usermax:20 portbase:8500)...
<08/08/06@17:03:45> [main] No ban file found (sc_serv.ban)
<08/08/06@17:03:45> [main] No rip file found (sc_serv.rip)
<08/08/06@17:03:45> [main] opening source socket
<08/08/06@17:03:45> [main] source thread starting
<08/08/06@17:03:45> [main] opening client socket
<08/08/06@17:03:45> [source] listening for connection on port 8501
<08/08/06@17:03:45> [main] Client Stream thread [0] starting
<08/08/06@17:03:45> [main] client main thread starting

So, when I try going to 000.000.000.000:8500, I can't connect or anything. (000.000.000.000 being my IP address)

Am I right in assuming the port may be blocked? How do I get it working?

For the record, I have installed shoutcast in "/shoutcast/".

 

[Who-m3]

Utilizing FireFox, IE, or any web browser, go to http://000.000.000.000:8500/ to access the Shoutcast Server Site for your radio. To listen to the stream, go to http://000.000.000.000:8500/listen.pls (that'll open in WinAMP automatically, if you're a WinAMP user...)

Fair warning, though, I highly discourage you from running anything as root that doesn't HAVE to be run as root. By installing shoutcast in /shoutcast, that indicates you're running at root (at this time). This is a bad idea. Shoutcast is a precompiled binary, and it does occasionally have problems (i.e. they recently updated from .6 to .7 because of a problem they were unaware of). Running as root with anything that doesn't HAVE to be run as root opens the system to more vulnerabilities, which are serious enough at a user-level, much less at the superuser-level.

Add a new user, such as "shoutcast", move your shoutcast files to that directory, and change the ownership to the new user. Then run the server as the user (su to the account or login as the account) instead of running it as root.

Also, be aware that Shoutcast has a configuration setting to show the log to console or to keep the output straight to the log. This will prevent your console from being flooded. However, you also have an option of running this process in the background (instead of having to keep your window active while running the process). To do this, run the server as.. "./sc_serv sc_serv.conf &" (forcing to the background).

 

[DCNet_James]

You also need to be broadcasting to the server from your source. W/O this you won't hear anything when you goto listen

Also you might want to run it as ./sc_serv sc_serv.conf & so it daemonizes. Otherwise it will quit as soon as you log off the ssh session.

As above, I wouldn't run this as root, create a user called shoutcast to run it as, or something along those lines.

Thx
James

 

[Basch]

Also be sure to open the port 8500 in iptables.

Add the following lines to /etc/sysconfig/iptables

-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 8500 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 8500 -j ACCEPT

Assuming you are using Fedora. (Do not forget to restart iptables: /etc/init.d/iptables restart)

 

[Sekka]

I worked it out. Our server provider has the server behind another firewall that's blocking the port. I just need to ask them unblock it.

Thank you for all the help though! I will do the user and run it in the background.