Process icecast often dies unexpectedly

[Smana]

Hello,

We have several icecast servers, and we noticed recently that some of them died for an unknown reason. Nothing in the log files, even in debug mode. Therefore we decide to generate a core dump to see what happened but it didn't helped either.

GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/icecast-kh...(no debugging symbols found)...done.
[New LWP 3097]
[New LWP 3098]
[New LWP 57181]
[New LWP 3096]
[New LWP 35889]

warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/icecast-kh -b -c /etc/icecast-kh/icecast.xml'.
Program terminated with signal 6, Aborted.
#0  0x00007f4c28f96475 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) 

Could you please guide us in a way to identify the root cause of the issue ?

version 2.3.3-kh7 os : debian wheezy kernel : 3.2.0-4-amd64

Regards, Smana

[karlheyes]

Hard to say, the raise usually occurs from an abort call or a detected memory allocation problem. There was an abort that was got rid of after kh7 which occurred on a reload type of event. This is not an issue in kh9 or later.

karl.

[Smana]

Hello Karl,

I'll try tu upgrade and let you know if it fixes our issue. Thanks for your reply,

Smana,

[mr-deamon]

Hi Karl I have the same problems. After upgrading to kh9, it still hapens. Here are my details:

icecast -v

Icecast 2.3.3-kh9-0-g5abf46c

last 5 error.log lines (debug-mode): [2014-01-14 08:28:25] DBUG stats/modify_node_event update "/m/channel2/mp3_128" total_mbytes_sent (100477) [2014-01-14 08:28:25] DBUG stats/modify_node_event update "/m/channel2/mp3_128" queue_size (115356) [2014-01-14 08:28:25] DBUG stats/modify_node_event update "/m/channel2/mp3_128" connected (699408) [2014-01-14 08:28:25] DBUG stats/modify_node_event update "global" stream_kbytes_sent (11397801245) [2014-01-14 08:28:25] DBUG stats/modify_node_event update "global" stream_kbytes_read (677041527)

last access.log entry 193.218.102.59 - - [14/Jan/2014:08:28:24 +0100] "GET /status.xsl HTTP/1.0" 200 235992 "-" "-" 0

what could i do to debug this?

thanks Chris

[karlheyes]

as I'm trying to get a kh10 out, can you get the latest build to verify that please, either use git to clone a copy or download the latest extract and rebuild with

./configure make debug

[make install]
you can run the binary from the src directory if you want

catchsegv /path/to/icecast -c /path/to/icecast.xml

or

run it to generate a core file, which depends on the security aspects like changeowner and directory permissions.

karl.

[karlheyes]

kh10 has a few crash fixes since the last update on this and seeing that no further information is available then can you verify with the latest update.

karl.

[niko]

I'm seeing the same (or a similar) problem. We're running Icecast 2.3.3-kh11 19-g17d0eb2 as one master and three relays on Ubuntu 14.04, Kernel 3.13.0 x86_64 machines. The relays exit on a regular basis (about 3 to 5 times a week; sometimes 5 days without issues, then again aborts each day) with an exit status of 134. There's nothing in the logfile that looks suspicious. Is this related or should I open a new Issue? How can I provide more information?

Niko.