similar to: Icecast relay crash.

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. Also I'll try to catch up on Freenode but

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?

Hi All, 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 #0 0xffffe435 in __kernel_vsyscall () #1 0xf742c607 in raise () from /lib/i386-linux-gnu/libc.so.6 #2 0xf742fa33 in

Good morning, On Sat, 2016-11-05 at 16:38 +0530, Sourav Saha wrote: > Hi All, > > > 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 >

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

Hello, I work at SmarctJog.com, we have here some patches on IceCast for performance and reliability, these are mostly client/connection/source cleanups (a slave merge is underway, and some more good stuff (c)), but we'd like this to be merged in before the list gets any longer. Please find attached a list of our patches with a short desc: This one is actually not from us/me, it was found

Hi All, I am interested in applying for the two projects listed in the Xapian Gsoc 2019 project idealist: "Learning to Rank Stabilisation" and "Weighting Schemes". I have downloaded the codebase and going through some of the commits related to Letor API, BM25, and DFR weighting schemes. Can anyone tell me how to write about the formal proposal for the above-mentioned projects?

Hi, I am new to Icecast open source project and I would like to contribute into this open source project. Looking for some kind of guidelines how to get started and where to browse for the open issues or features to look into. Any kind of help would be much appreciated. - Sourav Saha -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, icecast2 doesn't want to run stable on my Slackmachine: Linux tyson 2.4.18 #9 Fri Oct 4 17:13:35 CEST 2002 i586 unknown I followed the guidelines at http://melmoth.dyndns.org. I use Winamp v2.81 in combination with Oddcast DSP plugin. I can get the stream up and running. I also can connect to it and listen to it through another instance of Winamp. The seg fault is reproducable: 1. I

changes, there are lots of formatting changes, and things like additions of "XXX: ..." comments that don't say anything helpful - these will need removing before the patches are really reviewable. A higher-level description of what you're attempting to accomplish with these patchsets would also be very helpful - but much more detail than "performance and reliability".

My icecast server has been running happily for months now, but just yesterday it locked up, chewing up all the cpu time it could find, and not allowing connections. The last snippet of the error log shows this: [2005-06-01 09:36:13] WARN connection/_accept_connection accept() failed with error 24: Too many open files [2005-06-01 09:36:15] WARN connection/_accept_connection accept() failed

Hi all, I am trying to stream for over 1k users on Ubuntu 16.04. I notice that when stream connection is over 1024, it get warning like this: WARN connection/_accept_connection accept() failed with error 24: Too many open files Tried these configs and reboot, it won't work! /etc/pam.d/common-session session required pam_limits.so /etc/sysctl.conf fs.file-max = 100000

Does anyone have any ideas why my recently updated * 1.2.5 system should spawn multiple * process at seemingly random intervals? Regards L:ee ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/ -------------- next part -------------- An HTML attachment was scrubbed...

Hi, Our icecast server (version 2.2.0) locked up whilst I was out this evening. Looking at the error log, I find a lot of the following: [2005-04-28 08:21:16] WARN connection/_accept_connection accept() failed with error 24: Too many open files [2005-04-28 08:21:17] WARN connection/_accept_connection accept() failed with error 24: Too many open files [2005-04-28 08:21:17] WARN

Hi all, I was wondering why there is a timeout (100msec) in the _acception_connection function (icecast/src/connection.c) where it calls the util_timed_wait_for_fd. To me this seems to incur unecessary load on the machine on which the icecast server runs, since each time the timeout expires some more user time is used up by the process. In my particular setup I run an icecast server 24/7, but

Good evening, On Mon, 2016-05-02 at 17:19 +0530, Sourav Saha wrote: > Hi, > > > I am new to Icecast open source project and I would like to contribute > into this open source project. Looking for some kind of guidelines how > to get started and where to browse for the open issues or features to > look into. We're always happy to see when people are interested to help.

Hi all, 'm trying to setup an icecast server. It works, bu I want to test how many clients it can serve. Server: Icecast2 on PIII 933Mkz, 512Mo RAM Linux Debian 3.0 One source sent by darkice (can't make ices2 working) The problem is: "The server can't serve more than 1020 clients, because of a file limit" [2003-03-13 14:18:50] WARN connection/_accept_connection accept()

A non-text attachment was scrubbed... Name: smime.p7m Type: application/x-pkcs7-mime Size: 5151 bytes Desc: not available Url : http://lists.xiph.org/pipermail/icecast/attachments/20050407/26a2da7f/smime.bin

http://bugs.freedesktop.org/show_bug.cgi?id=10927 Summary: segmentation fault in NVUploadToScreen, called from exaPutImage Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Two VPSs. Identical setups with the exception of the extension. Same version of everything, Asterisk 14.1, Ubuntu 16.10, same firewall rules and so on - box 2 was cloned from box 1. Both VPSs run in the same datacentre. Suddenly, after weeks of OK, I'm getting lots of this on ONE box only: [Nov 4 21:23:04] NOTICE[1468]: res_hep.c:466 hep_queue_cb: Unable to send packet: Address Family