[Icecast-dev] Icecast relay crash.

Sourav Saha sourav.saha048 at gmail.com
Mon Nov 7 13:42:41 UTC 2016


Thanks Philipp.

I agree with you, this looks like some buffer overrun issue. I know I'm
using a very old version of icecast software but still I am asking is there
any kind of workaround to this problem apart from upgrading the icecast
version (which is the last option).
Running Valgrind may help to capture the root cause, any thoughts?

BTW what's the latest stable version of icecast?


-- Sourav

On Sat, Nov 5, 2016 at 11:05 PM, Philipp Schafft <
phschafft at de.loewenfelsen.net> wrote:

> Good evening,
>
>
> On Sat, 2016-11-05 at 19:33 +0530, Sourav Saha wrote:
> > Hi,
> >
> >
> > I am using icecast 2.3.2 and I'm not in position to upgrade the
> > version right away since this version is already in use. Please let me
> > know if you need any additional details for this issue. Nevertheless
> > if there is any potential fix has gone towards this part of code in
> > later versions, I can just use that patch in my current code base.
>
> Version 2.3.2 is not just old but stone age. It has a range of known
> bugs, security vulnerabilities both local and remote.
>
> The problem you see is very likely because of some random buffer overrun
> bug. Maybe one of those vulnerabilities.
>
>
> > Also I'll try to catch up on Freenode but can't be very sure due to
> > time difference, so I'm betting on the replies on this thread.
> >
> with best regards,
>
>
> > Thanks/
> >
> > On Sat, Nov 5, 2016 at 7:08 PM, Philipp Schafft
> > <phschafft at de.loewenfelsen.net> wrote:
> > [...]
> >         On Sat, 2016-11-05 at 16:38 +0530, Sourav Saha wrote:
> >         > I'm facing a problem in icecast relay machines. I'm seeing
> >         frequently
> >         > that some of the relay machines are crashing and generates
> >         core dump
> >         > but the reason for the crash is not clear from the trace of
> >         the core.
> >         > Here is how the gdb trace looks like:
> >         >
> >         >
> >         > (gdb) bt
> >         > [...]
> >         > #6  0xf7474708 in malloc ()
> >         from /lib/i386-linux-gnu/libc.so.6
> >         > #7  0x080b66b7 in _accept_connection () at connection.c:598
> >         > #8  connection_accept_loop () at connection.c:826
> >         > #9  0x080a9c05 in _server_proc () at main.c:384
> >         > #10 main (argc=3, argv=0xffbbc554) at main.c:633
> >         >
> >         >
> >         > As you can see at frame #6 malloc() is failing but I don't
> >         know the
> >         > reason behind this. Does anybody has any idea how to fix
> >         this issue?
> >         > Note: this is happening only in the relay machines but not
> >         in edges.
> >
> >         Thank you for your report.
> >         What is the _exact_ version you run?
> >
> >
> >         You can also reach us on IRC (on Freenode, #icecast) for some
> >         live
> >         debugging (when the sun is over central Europe).
>
>
> --
> Philipp Schafft (CEO/Geschäftsführer)
> Telephon: +49.3535 490 17 92
>
> Löwenfelsen UG (haftungsbeschränkt)     Registration number:
> Bickinger Straße 21                     HRB 12308 CB
> 04916 Herzberg (Elster)                 VATIN/USt-ID:
> Germany                                 DE305133015
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20161107/61f0646f/attachment.html>


More information about the Icecast-dev mailing list