Koozali.org: home of the SME Server
Obsolete Releases => SME 7.x Contribs => Topic started by: cbacani on March 27, 2009, 03:12:02 PM
-
William, if you are out there? It would seem that something has changed in the install of Shoutcast. Here is what I am using (please see below). After the install completes, I am unable to connect to the stream - it almost seems like the firewall isn't allowing any stream through.
Installing Shoutcast on the SME server as follows.
mkdir -p /opt/shoutcast
cd /opt/shoutcast
wget http://yp.shoutcast.com/downloads/sc1-9-8/sc_serv_1.9.8_Linux.tar.gz
tar -zxvf sc_serv_1.9.8_Linux.tar.gz
mkdir -p /var/service/shoutcast
mkdir -p /var/service/shoutcast/log
cd /var/service/shoutcast
pico -w run (SEE NOTE #1)
cd log
pico -w run (SEE NOTE #2)
touch /var/service/shoutcast/down
mkdir -p /var/log/shoutcast
config set shoutcast1 service access public status enabled TCPPort 8000
config set shoutcast2 service access public status enabled TCPPort 8001
config set shoutcast service access public status enabled TCPPorts 8000:8001
ln -s /var/service/shoutcast /service/shoutcast
ln -s /etc/rc.d/init.d/daemontools /etc/rc.d/init.d/supervise/shoutcast
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S92shoutcast
chmod 755 /var/service/shoutcast/run
chmod 755 /var/service/shoutcast/log/run
chown smelog:smelog /var/log/shoutcast
/sbin/e-smith/signal-event console-save
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot
******* SYSTEM WILL HAVE TO BE REBOOTED AT THIS POINT *******
ln -s /etc/rc.d/init.d/shoutcast S92shoutcast
cd /opt/shoutcast
pico sc_serv.conf to set password and other options.
NOTICE: You have to reboot the server in order for the
new password to take effect.
NOTE #1 Place the 3 lines of code below into run #1
-------------------------------------
#!/bin/sh
exec 2>&1
exec /opt/shoutcast/sc_serv /opt/shoutcast/sc_serv.conf
NOTE #2 Place the 5 lines of code below into run #2
-------------------------------------
#!/bin/sh
exec \
/usr/local/bin/setuidgid smelog \
/usr/local/bin/multilog t s5000000 \
/var/log/shoutcast
----------------------------------------------------------------
config set shoutcast service access public status enabled TCPPorts 8000:8001
Is this still a valid method or is there a YUM method hiding in the ether?
Carl
-
FOLLOW UP
After last nights update I have noticed a few other things.
1. /etc/cron.daily/01-rkhunter:
Warning: Groups have been added to the group file:
otir:x:5000:admin,www,operations
Warning: Groups have been removed from the group file:
otir:x:5000:admin,www,operations,otr
One or more warnings have been found while checking the system.
Please check the log file (/var/log/rkhunter.log)
/etc/cron.daily/freshclam:
/usr/bin/freshclam: unrecognized option `--log-verbose'
ERROR: Unknown option passed
ERROR: Can't parse command line options
What changed?
-
cbacani
Did you get Shoutcast running ?
I have it running internally ... but nothing external with ports forwarded.
I am trying to set Shoutcast up on a server only machine.
Regards,
Tib
-
After last nights update I have noticed a few other things.
1. /etc/cron.daily/01-rkhunter:
Warning: Groups have been added to the group file:
otir:x:5000:admin,www,operations
Warning: Groups have been removed from the group file:
otir:x:5000:admin,www,operations,otr
Normal warning after updates or user addition, see SME Server 7.4 release notes at the bottom: http://wiki.contribs.org/SME_Server_7.4#After_installing_for_the_very_first_time
One or more warnings have been found while checking the system.
Please check the log file (/var/log/rkhunter.log)
/etc/cron.daily/freshclam:
/usr/bin/freshclam: unrecognized option `--log-verbose'
ERROR: Unknown option passed
ERROR: Can't parse command line options
See http://bugs.contribs.org/show_bug.cgi?id=5114 , next time please do a search first, you could have easily found this by searching the bugtracker on "unrecognized option `--log-verbose'", the only result is quoted bug.
-
cbacani
Did you get Shoutcast running ?
I have it running internally ... but nothing external with ports forwarded.
I am trying to set Shoutcast up on a server only machine.
Regards,
I got it working after the second set of updates came dome the stream. It's no wonder why people don't post here. Help comes from the heart and not from comments like the one's posted. 'Why don't you read this or that? Please read before you post. Did you ever think that this
forum has gotten so big and so full of junk that it is too hard to find anything within a reasonable length of time?
Some websites need to be "weeded" for both content and people. Being mean to people sucks I am so glad that I do not try to make people feel bad so I can make myself feel better, There needs to be a change in the way we handle people and answer the questions. long time coming.
And, if you cannot see what is really needed in the change of attitude, maybe it is time that I to leave this forum like so many have.
A change is needed. Tib, Yes it is working and thank you for your concern
Carl
-
cbacani
Can you give me a bit of a guide on what you did to get it working.
I followed one of your posts on the installation of shoutcast ... but I can only seem to listen to it from internally.
It seems as if the db command doesn't open up the port to the outside.
modified
what one of the following commands do I use?
config set shoutcast1 service access public status enabled TCPPort 8000
config set shoutcast2 service access public status enabled TCPPort 8001
config set shoutcast service access public status enabled TCPPorts 8000:8001
Regards,
Tib
-
It's ok ... I have it working now
I didn't realize I required all 3 lines
Thanks
Tib
-
You had the same issue that I had. For some people this command works.
config set shoutcast service access public status enabled TCPPorts 8000:8001
on 7.4 it seems that this version works.
config set shoutcast service TCPPort 8000,8001 access public status enabled
I wanted to ask the people here like William as to which version would be proper but I do not see him log on anymore. Ya, I know -bugzilla ya right! It is because of good people like you that we little people find the answers. Ya know what? When good people help it makes me feel good and then I want to find answers and share them. Also, here is what Iam using that works for me (see below) Ever wonder why the same code works for some and not others?
Installing Shoutcast on the SME server as follows.
mkdir -p /opt/shoutcast
cd /opt/shoutcast
wget http://yp.shoutcast.com/downloads/sc1-9-8/sc_serv_1.9.8_Linux.tar.gz
tar -zxvf sc_serv_1.9.8_Linux.tar.gz
mkdir -p /var/service/shoutcast
mkdir -p /var/service/shoutcast/log
cd /var/service/shoutcast
pico -w run (SEE NOTE #1)
cd log
pico -w run (SEE NOTE #2)
touch /var/service/shoutcast/down
mkdir -p /var/log/shoutcast
config set shoutcast service access public status enabled TCPPorts 8000:8001
config set shoutcast service TCPPort 8000,8001 access public status enabled
signal-event remoteaccess-update
ln -s /var/service/shoutcast /service/shoutcast
ln -s /etc/rc.d/init.d/daemontools /etc/rc.d/init.d/supervise/shoutcast
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S92shoutcast
chmod 755 /var/service/shoutcast/run
chmod 755 /var/service/shoutcast/log/run
chown smelog:smelog /var/log/shoutcast
/sbin/e-smith/signal-event console-save
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot
******* SYSTEM WILL HAVE TO BE REBOOTED AT THIS POINT *******
ln -s /etc/rc.d/init.d/shoutcast S92shoutcast
cd /opt/shoutcast
pico sc_serv.conf to set password and other options.
NOTICE: You have to reboot the server in order for the
new password to take effect.
NOTE #1 Place the 3 lines of code below into run #1
-------------------------------------
#!/bin/sh
exec 2>&1
exec /opt/shoutcast/sc_serv /opt/shoutcast/sc_serv.conf
NOTE #2 Place the 5 lines of code below into run #2
-------------------------------------
#!/bin/sh
exec \
/usr/local/bin/setuidgid smelog \
/usr/local/bin/multilog t s5000000 \
/var/log/shoutcast
----------------------------------------------------------------
config set shoutcast service access public status enabled TCPPorts 8000:8001
On Your Webpage
On your webpage add something like this
<p> <a href="http://98.190.159.162:8000/listen.pls" title="Listen Live"><br />LISTEN LIVE</a></p>
------------------------------------------------------------------
Raw dump of configuration database for all services:
Code: db configuration print | grep "=service"
List of service names for all services that have "access=public" and "status=enabled":
Code: db configuration print |awk -F"[=|]" '/\=service.*public.*enabled/ {print $1}'
Raw dump of configuration database for public, enabled services:
Code: db configuration print |awk -F"[=|]" '/\=service.*public.*enabled/ {print $_}'
signal-event reboot
Carl
-
Forgot to tell you that it is not supposed to require all three lines but for some people it works.
Carl
-
cbacani
Thanks for your help ... very much appreciated.
I love shoutcast :grin:
Regards,
Tib
-
Tib,
For the record - What are you using it for?
Iam using it for canyonoaksradio.com in conjunction with Sam Broadcaster running a automated FM and internet radio station that plays old radio shows ie: Burns and Allen etc.
Carl
-
carl
We are just testing this out for our selves on linux at the moment but who knows what the future brings :)
My business partner has setup shoutcast for a singer in Romania for an online radio http://getaarghius.com ... but it's on xp .... so we are trying to get more familiar with the linux side of it.
Regards,
Tib