Shoutcast Servers just stop running.

marcm · 18th April 2012, 19:16

OK, so I have a Centos server and I'm trying to run multiple Shoutcast Servers., ( running V1 servers ) For some reason, all but one seem to be stopping every night/day. I was thinking, at first, that the server was restarting, but one of the servers remains active. So I'm thinking there must be another reason they are stopping.

I have a command that I run from php to see if a certain stream is up, but it isn't proving to be consistent.

My server does run ConfigServer, but it is not sending me any alerts about long running shoutcast processes.

Does anyone have any thoughts on why these could be stopping?
Is there an easy way to have a server start when someone attempts to connect to it?
I also need a reliable way to test if a server is running via php.

Any help is greatly appreciated.

marcm · 20th April 2012, 04:17

I've discovered that the one stream that keeps running was started as "root", while the others were started as the user the domain is setup with.

The server is not restarting, so something is making these server processes stop. All I can think atm is that the configServer might be stopping them.

marcm · 21st April 2012, 21:50

Well, I've solve it by simply restarting them every x minutes. I was worried that restarting an already running stream would disrupt it, but thankfully it does not. Therefore, no need to check if they are not running first.

I hope this will help someone else down the line.

Thanks to all that replied

/end sarcasm

DrO · 22nd April 2012, 21:03

it sounds like the account being used to run them times out which would explain what you're seeing. depending on how things are setup, you may or may not be able to amend the timeout in the shell's permissions to allow it to keep going once created.

-daz

18th April 2012, 19:16	#1
marcm Junior Member Join Date: Apr 2011 Posts: 20	Shoutcast Servers just stop running. OK, so I have a Centos server and I'm trying to run multiple Shoutcast Servers., ( running V1 servers ) For some reason, all but one seem to be stopping every night/day. I was thinking, at first, that the server was restarting, but one of the servers remains active. So I'm thinking there must be another reason they are stopping. I have a command that I run from php to see if a certain stream is up, but it isn't proving to be consistent. My server does run ConfigServer, but it is not sending me any alerts about long running shoutcast processes. Does anyone have any thoughts on why these could be stopping? Is there an easy way to have a server start when someone attempts to connect to it? I also need a reliable way to test if a server is running via php. Any help is greatly appreciated.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

20th April 2012, 04:17	#2
marcm Junior Member Join Date: Apr 2011 Posts: 20	I've discovered that the one stream that keeps running was started as "root", while the others were started as the user the domain is setup with. The server is not restarting, so something is making these server processes stop. All I can think atm is that the configServer might be stopping them.

21st April 2012, 21:50	#3
marcm Junior Member Join Date: Apr 2011 Posts: 20	Well, I've solve it by simply restarting them every x minutes. I was worried that restarting an already running stream would disrupt it, but thankfully it does not. Therefore, no need to check if they are not running first. I hope this will help someone else down the line. Thanks to all that replied /end sarcasm

22nd April 2012, 21:03	#4
DrO - Join Date: Sep 2003 Location: UK Posts: 22,204	it sounds like the account being used to run them times out which would explain what you're seeing. depending on how things are setup, you may or may not be able to amend the timeout in the shell's permissions to allow it to keep going once created. -daz