SupportSages » shoutcast hosting http://www.supportsages.com/blog Technical Support and Server Management : Musings in the fox hole. Thu, 05 Jan 2012 03:05:11 +0000 en hourly 1 http://wordpress.org/?v=3.1.3 Cast Control installation on a suPHP installed server fails http://www.supportsages.com/blog/2009/05/cast-control-installation-on-a-suphp-installed-server-fails/ http://www.supportsages.com/blog/2009/05/cast-control-installation-on-a-suphp-installed-server-fails/#comments Thu, 21 May 2009 13:27:18 +0000 George http://www.supportsages.com/blog/?p=380 CastControl folder, files/1-9-8-linux-glibc6/sc_serv and files/1-9-8-linux-glibc6/sc_trans should have permissions 777 even if your server is running under suPHP. If installation fails after setting it to 777, with an error message as below,
There was a problem with the tested shoutcast server While the SHOUTcast server ...]]> Shoutcast hosting is one of the niche market for the hosting industry. But sometimes, issues like this creep in. So here is the solution for the issue. Even if you are offering unmanaged VPS web hosting, clients may not be able to easily solve this themselves. Please help them :)

Make sure that the files inside the CastControl folder, files/1-9-8-linux-glibc6/sc_serv and files/1-9-8-linux-glibc6/sc_trans should have permissions 777 even if your server is running under suPHP. If installation fails after setting it to 777, with an error message as below,

There was a problem with the tested shoutcast server
While the SHOUTcast server seems to have started, it was terminated unexpectantly

Click here to view the shoutcast log

It’s time to check the apache error logs. Because shoutcast logs are empty or even the logs folder inside cast control. And the apache error log has tons of errors like below,

[Thu May 21 03:11:37 2009] [error] [client xxx.xxx.xxx.xxx] sh: whoami: command not found, referer: http://www.shoutcastsage.net/shoutcast/install/install.php
[Thu May 21 03:11:40 2009] [error] [client xxx.xxx.xxx.xxx] sh: whoami: command not found, referer: http://www.shoutcastsage.net/shoutcast/install/install.php
[Thu May 21 03:11:40 2009] [error] [client xxx.xxx.xxx.xxx] Warning: bad syntax, perhaps a bogus ‘-’? See /usr/share/doc/procps-3.2.7/FAQ, referer: http://www.shoutcastsage.net/shoutcast/install/install.php
[Thu May 21 03:11:40 2009] [error] [client xxx.xxx.xxx.xxx] sh: pgrep: command not found, referer: http://www.shoutcastsage.net/shoutcast/install/install.php
[Thu May 21 03:11:40 2009] [error] [client xxx.xxx.xxx.xxx] ../temp/installation.conf.sh: line 3: nohup: command not found, referer: http://www.shoutcastsage.net/shoutcast/install/install.php

But pgrep and whoami are there in the server. What to do next ?

Time to edit suphp.conf. The culprit is the env_path setting in the conf file.

Current setting would be env_path=/bin:/usr/bin . Add double quotes there for the path setting and restart apache, like below

;PATH environment variable
env_path="/bin:/usr/bin"

Post to Twitter Tweet This Post

]]> http://www.supportsages.com/blog/2009/05/cast-control-installation-on-a-suphp-installed-server-fails/feed/ 0