It fell over earlier in the day and I found it d.o.a. The logs--access and error--were clean. I booted the system, which came back nicely, but without Icecast running. I ran it manually with /usr/bin/icecast -c /etc/icecast.xml & and everything was fine. Of course I had to start streaming services manually, but that was OK, considering there was nothing for them to talk to without Icecast running. So I thought I'd see if either the access or error logs showed anything. They didn't. In fact, I can find no place on the system where what happened was logged. Thinking I'd maybe find a clue by looking at the system console during the boot sequence, I enabled that, and watched as the system rebooted a second time. Still nothing. Without a traceback or stack dump or *anything* to look at, I'm rather at a loss. What really gets me is not knowing what could have happened during the day to cause Icecast to fall over of its own accord, which could mean I may have done something without even knowing I did anything. But it's a new system, nobody's losing millions of anything over this, and I'm still learning.
On 03/26/2015 02:29 AM, Steve Matzura wrote:> It fell over earlier in the day and I found it d.o.a. The logs--access > and error--were clean.Did the error.log show any signs of it shutting down or did it just end abruptly?> I booted the system, which came back nicely, > but without Icecast running. I ran it manually with > > /usr/bin/icecast -c /etc/icecast.xml & > > and everything was fine. Of course I had to start streaming services > manually, but that was OK, considering there was nothing for them to > talk to without Icecast running. > > So I thought I'd see if either the access or error logs showed > anything. They didn't. In fact, I can find no place on the system > where what happened was logged. Thinking I'd maybe find a clue by > looking at the system console during the boot sequence, I enabled > that, and watched as the system rebooted a second time. Still nothing.Fedora 20 uses systemd. Have you checked the journal for the output when Icecast start up failed?> Without a traceback or stack dump or *anything* to look at, I'm rather > at a loss. What really gets me is not knowing what could have happened > during the day to cause Icecast to fall over of its own accord, which > could mean I may have done something without even knowing I did > anything.Depending on your system configuration there might be at least some vague note in the journal about a process segfaulting or such. I know at least Ubuntu logs segfaults, not sure about Fedora. If this happens again, you could set up coredumps. That would get us something to debug.> But it's a new system, nobody's losing millions of anything > over this, and I'm still learning.Hehe, I'm sure we'll all learn something from this. Cheers Thomas
On Thu, 26 Mar 2015 06:58:17 +0000, you wrote:>Fedora 20 uses systemd. Have you checked the journal for the output when >Icecast start up failed?Unless I'm doing something very wrong, which is probably the case, the messages files have no strings containing `icecast'.>Depending on your system configuration there might be at least some >vague note in the journal about a process segfaulting or such. I know at >least Ubuntu logs segfaults, not sure about Fedora.Well, here's something that's telling--the output from running the startup script /etc/init.d/icecast2 in a subshell: + PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin + DAEMON=/usr/bin/icecast2 + NAME=icecast2 + DESC=icecast2 + test -x /usr/bin/icecast2 + exit 0 Failed the test for existence? How's that? + PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin + DAEMON=/usr/bin/icecast2 + NAME=icecast2 + DESC=icecast2 + test -x /usr/bin/icecast2 + exit 0 # ls -al /usr/bin/icecast -rwxr-xr-x 1 root root 237424 Dec 4 21:28 /usr/bin/icecast # file /usr/bin/icecast /usr/bin/icecast: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=050419accf8c5dcf4eb3daf92729f4e48271ca6b, stripped
Hi, I don't know about Fedora, but the Debian package won't run until you edit/etc/default/icecast2 to say "ENABLE=true". This is to prevent an unconfigured Icecast from running with default passwords, etc. Maybe the Fedora package has a similar mechanism. Geoff.