| View previous topic :: View next topic |
| Author |
Message |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sat Oct 23, 2010 8:00 pm Post subject: |
|
|
as you can plainly see, no icecast is running so naturally it won't be able to respond to a browser request or an ices attempt to stream..
| Quote: |
| Now this signal termination is due to no signal from streamer Ices-0.4 OR refering to something else? |
As you mentioned previously, the log entry is from the icecast log file so it refers to the termination of the icecast process. ices uses a separate log file so any reports about ices will be in that one.
karl.
. |
|
| Back to top |
|
 |
mkido
Joined: 22 Jan 2010 Posts: 63 Location: Los Angeles, California
|
Posted: Sat Oct 23, 2010 10:15 pm Post subject: IceCast got running now. |
|
|
Great! Wonderful karl, now I got running IceCast like a daemon. The problem was in the command line I used to start IceCast. I remotely login to the FC7 server, then became superuser, and issued command line as below,
~
biwa$su - root
Mot de passe :
[root@biwa ~]# icecast -c /etc/icecast.xml
Changed groupid to 495.
Changed userid to 496.
By this command, the computer didn't returned sharp prompt (#), therfore, so to see what was going on, I always typed <Ctrl>+C, to get the prompt (#) back, and this <Ctrl>+C became the,
[2010-10-22 20:36:45] INFO sighandler/_sig_die Caught signal 2, shutting down...
I tested by 5 minutes of interval before issuing <Ctrl>+C, then looked at error.log. I saw about 5 minutes delay of
[2010-10-22 20:36:45] INFO sighandler/_sig_die Caught signal 2, shutting down...
So, now, I just did,
[root@biwa ~]# icecast -c /etc/icecast.xml
Changed groupid to 495.
Changed userid to 496.
And by another remote login by another [Terminal], and I looked at # netstat -tnlp. Wonderful, icecast keeps running.
| Code: |
[root@biwa icecast]# netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN 24014/icecast
tcp 0 0 127.0.0.1:2208 0.0.0.0:* LISTEN 2032/hpiod
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 2167/mysqld
tcp 0 0 0.0.0.0:750 0.0.0.0:* LISTEN 1840/rpc.statd
tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 2504/dnsmasq
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 2076/vsftpd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2049/cupsd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2211/sendmail: acce
tcp 0 0 127.0.0.1:2207 0.0.0.0:* LISTEN 2037/python
tcp 0 0 :::111 :::* LISTEN 1811/rpcbind
tcp 0 0 :::80 :::* LISTEN 2232/httpd
tcp 0 0 :::22 :::* LISTEN 2063/sshd
tcp 0 0 :::443 :::* LISTEN 2232/httpd
[root@biwa icecast]#
|
Now, is there any modification to the following command line to start running IceCast and I can get back command prompt (#) normally.
[root@biwa ~]# icecast -c /etc/icecast.xml
mkido |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Oct 24, 2010 12:01 am Post subject: |
|
|
yes the -b option, you can also use & at the end of the command line.
karl. |
|
| Back to top |
|
 |
mkido
Joined: 22 Jan 2010 Posts: 63 Location: Los Angeles, California
|
Posted: Sun Oct 24, 2010 1:10 am Post subject: Thanks, great karl! |
|
|
| Thanks, great karl! |
|
| Back to top |
|
 |
mkido
Joined: 22 Jan 2010 Posts: 63 Location: Los Angeles, California
|
Posted: Sun Oct 24, 2010 1:27 am Post subject: How to stop icecast by a command line. |
|
|
Now, IceCast is ruuning like a daemon, great! Here comes one more question,
Now, then if I want to stop it, for example to change the icecast.xml configuration, which command is the most proper to issue?
mkido |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Oct 24, 2010 1:52 am Post subject: |
|
|
kill can be used to send a signal for icecast shutdown, Many changes can actually be reloaded (kill -HUP ...).
karl |
|
| Back to top |
|
 |
DJ-Zath

Joined: 11 Feb 2009 Posts: 155 Location: Western Illinois - USA
|
Posted: Mon Oct 25, 2010 9:36 am Post subject: |
|
|
I have a suggestion:
You really shouldn't run Icecast (or Ices) as "root"..
What I do, is create an seperate account/user for Icecast.. and then start Icecast under that user's credentials.. I do this for security reasons- but also, so that I can load "check scripts" in cron to check and test Icecast to make sure its running (and stays running) the other reason I do this is to isolate it from other processes on the server- this way its own "start" and "stop" scripts can easily modify cron (and other elements of the server) which are related to Icecast without effecting anything else. _________________ -DjZ-
 |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Mon Oct 25, 2010 12:59 pm Post subject: |
|
|
just to clarify, starting as root may be required (low port numbers for example) but icecast forces the use of change owner is run as root initially.
karl. |
|
| Back to top |
|
 |
|