[Icecast-dev] Icecast relay crash.
phschafft at de.loewenfelsen.net
Wed Nov 9 08:44:30 UTC 2016
On Mon, 2016-11-07 at 19:12 +0530, Sourav Saha wrote:
> 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?
I just feel like that even if we would find that with a big amount of
work to dig into it you will likely just end up with the next problem.
And the next one may be something even more hidden.
There are about 41k lines of changes since 2.3.2. A version which were
released at a time with a team which has no overlapping with the current
Unless you really want to get into the next problem that will be ahead
and putting some budget into it I can just strongly recommend you to
> BTW what's the latest stable version of icecast?
Current stable version is Icecast2 2.4.3. We're working on a 2.4.4 at
with best regards,
> -- 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
> > version right away since this version is already in use.
> Please let me
> > know if you need any additional details for this issue.
> > 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
> Version 2.3.2 is not just old but stone age. It has a range of
> 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
> 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
> > > I'm facing a problem in icecast relay machines.
> I'm seeing
> > frequently
> > > that some of the relay machines are crashing and
> > 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
> > > #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:
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 490 bytes
Desc: This is a digitally signed message part
More information about the Icecast-dev