Koozali.org: home of the SME Server
Obsolete Releases => SME Server 8.x => Topic started by: cbacani on February 12, 2015, 05:43:45 AM
-
Hey, My server has died and i am trying to rebuild it but I think I might be using the wrong syntax. Does this look right or is this still the way to open a port with::
config set shoutcast service access public status enabled TCPPorts 8000:8001
It has been a long time since I installed this in the SME Server. Running version 8x
Thank You
Carl
P.S. Shows how GREAT the SME server is.
-
That looks right to me.
You would need to follow that with signal-event remoteaccess-update
...and, you might want to confirm your settings by examining /etc/init.d/masq
-
First, thank you for responding. I tried that and the port still will not open.Any other ideas? I tried the masq command and it does nothing. I also looked to see what ports were open and 3 other ports were opened by what I do not know. I might have to reinstall the server just to make sure that I have a clean install. Maybe I should also use the control panel to open the ports?
CHARLIE BRADY! Can you chime in on this one?
Carl
-
I tried that and the port still will not open.
How can you tell it is not open? Why are you talking about a port while you define 2 TCP ports?
Do they show up in 'iptables -L' ?
-
is shoutcast service running? because if it isn't, no one is listening on those ports...
-
This what it reads.
ACCEPT tcp -- anywhere wsip-70-169-35-XXX.tu.ph.cox.net tcp dpt:8001
ACCEPT tcp -- anywhere wsip-70-169-35-XXX.tu.ph.cox.net tcp dpt:https
ACCEPT tcp -- anywhere wsip-70-169-35-XXX.tu.ph.cox.net tcp dpt:8000
you would think it would work
Carl
-
is shoutcast service running? because if it isn't, no one is listening on those ports...
That is a great point what is the process to check for that? Please forgive me but Iam 65 years old and I forget a lot of stuff these days.
-
ok guys it came back to me:
ps aux | grep shoutcast
root 1804 0.0 0.0 120 32 ? Ss 10:42 0:00 runsv shoutcast
smelog 1840 0.0 0.0 3692 364 ? S 10:42 0:00 /usr/local/bin/multilog t s5000000 /var/log/shoutcast
root 7585 0.0 0.0 61196 736 pts/0 S+ 11:36 0:00 grep shoutcast
I think it is running
-
well, I'd try with
service shoutcast status
and
netstat -napt | grep ':800'
-
down: /service/shoutcast: 1s, want up; run: log: (pid 1840) 4495s
Installing Shoutcast on the SME server as follows.
mkdir -p /opt/shoutcast
cd /opt/shoutcast
wget ftp://ftp.tw.freebsd.org/pub/ports/distfiles/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
nano -w run (SEE NOTE #1)
cd log
nano -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
signal-event remoteaccess-update
verify the change with : /etc/init.d/masq restart
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
NOTE: The system will go down for a reboot *****************************
ln -s /etc/rc.d/init.d/shoutcast S92shoutcast
cd /opt/shoutcast
nano sc_serv.conf to set password and other options.
Password=XXXXXXX (replace XXXX with your password)
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_basic.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
---------------------------------------
-
wget ftp://ftp.tw.freebsd.org/pub/ports/distfiles/sc_serv_1.9.8_Linux.tar.gz (ftp://ftp.tw.freebsd.org/pub/ports/distfiles/sc_serv_1.9.8_Linux.tar.gz)
There is no longer any code in the directory ftp://ftp.tw.freebsd.org/pub/ports/distfiles/
-
odd, when i tried it at 12:52pm my time it just worked It isn't listed anywhere i can see but it does download.
-
well, I'd try with
service shoutcast status
and
netstat -napt | grep ':800'
service shoutcast status : down: /service/shoutcast: 0s, want up; run: log: (pid 1845) 277s
When I run service shoutcast start it comes back with
Starting shoutcast: [ OK ]
When I check status it comes back with down: /service/shoutcast: 0s, want up; run: log: (pid 1845) 277s
Any suggestions?
Carl
-
Carl,
my best guess would be that nothing has been installed and no service will be started.
SME Server responds to db entries, but there is n real service running.
-
Download link is working for me..
-
something new has happened. While trying to start the service i get this error code.
-bash: ./sc_serv: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
How can this be. The file is sitting in the directory but is cannot see it, anybody have any ideas.
-
bad elf. I took the time to read a lot of information on this web site and found out what was wrong. my code will only run on a i386 based server. After I figured that out re-installed the i386 SME server the system started and ran and it was the elf error that gave me a clue.
Thanks to all that helped me to read the web, and keep up the good work. It is nice to see people helping each other.
Carl
-
this is closed thanks again guys and gals
-
When I check status it comes back with down: /service/shoutcast: 0s, want up; run: log: (pid 1845) 277s
That shows that your shoutcast 'run' script is failing immediately. The log file may tell you the reason.
Alternatively, do:
cd /service/shoutcast
sv d .
./run
You will see an error message.