similar to: Icecast - Buffer/Disconnect help

Hi all, I'm experiencing a systematic crash with icecast2 when I goes in this case (tested with debian 2.3.1-5 2.3.1-6 and latest trunk) When there is more than ~1400 clients connected and a mountpoint that was not relaying goes online it crash. Without this I can go up to 5000 clients without problems. Changing the number of threadpool does'nt change anything. here is the term log:

Hi Mark, Add extensions to all of your mountpoints for the appropriate audio codec/format you're using. For example, <mount-name>/test.opus</mount-name> for an Ogg/Opus stream. Don't forget to add extensions in the <fallback-mount> sections, too. I didn't look too closely at your config otherwise, that error was standing out. Cheers, Jordan P.S. Please

Hi, could you please help me with this situation, the operating system in my computer is Windows 10, and icecast cannot start properly here is my configuration: <icecast> <!-- location and admin are two arbitrary strings that are e.g. visible on the server info page of the icecast web interface (server_version.xsl). --> <location>Earth</location>

Marc, Lines with a <!-- and --> are commented and not used. You need to remove these around the mount items. The <<!-- looks like it needs fixing. Ross. -----Original Message----- From: Mark [mailto:mark at tafn.org.uk] Sent: Monday, 17 October 2016 9:35 p.m. To: Ross Levis Subject: Re: [Icecast] Icecast help Hi Ross, First many thanks for your help I have done what you

My listeners connect to a publicly accessible Icecast server with the config below. Between broadcasts it uses a fallback mp3, which loops. During broadcasts it relays from a local Icecast server that I broadcast to (config also below). I am aiming for approx 30-45 seconds buffering, as the connection from public to local icecast server is 'less than ideal'. The set up is working fine

Hi, We have some time-outs when there connecting more thane 1400 listeners to Icecast. We use CentOS Linux release 7.6.1810 on port 80 and 443 for SSL on IPv4 and IPv6. The stream have many mountpoint 16 active (8 main en 8 fallback and 8 file when faillback is down) The server have 2 CPU's on 3Ghz and 6000mb memory. And we 1 GB uplink (we use 130mbit on peak). We use a hardware firewall

-----Originalmeddelande----- Fr?n: "Per Gunnarsson" <per at 80-244-81-186.customer.t3.se> Till: per.gunnarsson at lappstockholm.se Datum: 2012-02-19 17:45 ?mne: Icecast doesn't bind to my external network interface? I can listen to my stream with mplayer -cache 1024 http://localhost:8000/ices.mp3 but not mplayer -cache 1024 http://80.244.81.186:8000/ices.mp3 This

hi all how do i editing line that has to be uncommented so that the server starts?? <icecast> <!-- location and admin are two arbitrary strings that are e.g. visible on the server info page of the icecast web interface (server_version.xsl). --> <location>Earth</location> <admin>icemaster at localhost</admin> <limits>

Hello List Having great trouble relaying an icecast2 mp3 stream to a shoutcast server. My client program successfully streams to icecast which is listening on port 7000. I can listen to this stream with mozilla and xmms with no problems. I can also stream my client directly to the shoutcast server but it makes the client unstable (which is why i'm attempting a relay). The shoutcast server is

Hi, Many thanks for the build, I gave up trying to compile using vs.net! ;-) However, When trying to access the admin page it the server will crash... Ive tried this on 2 machines and both crash when trying to access /admin/ Is anyone else getting this? Thanks, This is the error log: [2005-07-13 23:49:34] INFO main/main.c Icecast icecast_kh_trunk server started [2005-07-13 23:49:34] DBUG

does anyone know how i can setup my own icecast server? On Sun, Feb 16, 2020 at 9:57 AM James Turner <james at switchbladeuk.com> wrote: > Hi team, > > Please accent my apologies if this is NOT the place/distro list to be > raising this. I had major dramas with the standard forum - registration and > decided this may be a better route. > > My current instance icecast

Hi, I am running Icecast 2.1.0 on a Debian Sarge with a 2.6.8 Kernel. After upgrading to the new version i have the problem that the icecast2 process. It is regularly dying after running 20-26 hours. There are no messages in the icecast logfile nor in any other logfile. The only message, which is written to the shell which started the process, is xsltApplyOneTemplate: template was not compiled

Folks: I'm trying to set up a streaming server under Fedora Core 2 using Icecast 2.2.0. Everything compiles; everything runs. There are no indications of a problem in any of the log files. When I look at http://192.168.0.128:8000/status.xsl, everything looks ok. But when I click on "Click to listen", it brings up xmms, but there's no indication of audio, and xmms shows a bit

Zahar, how are you testing? with some CURL stress test? BTW, IPTABLES is enabled? I was running most time in VMWARE, but i run 10k users in medium size box in AWS, just move out for the high transfer cost. 2016-06-10 2:36 GMT-03:00 Zahar Popov <zahar.popov1978 at yandex.com>: > Hi Alejandro, > Here is mine: > > <limits> > <workers>4</workers> >

Hi there, I am trying to use python-shout 0.2.1 to broadcast to a icecast 2.4.0 server, which result in a segmentation fault and I can't understand why. Is anyone else experiencing this problem? Here is the config that I use with icecast 2.4.0. <icecast> <limits> <clients>100</clients> <sources>2</sources>

Hello I have a problem when I use the intro to send a pre-roll, the main stream generates a 20 second delay, when the main stream is played it has no delay. Is there any parameter I can use to eliminate the delay? with pre-rolli: https://radiomarca-rrcast.flumotion.com/radiomarca/live.mp3 without pre-rolli: https://radiomarca-rrcast.flumotion.com/radiomarca/live-np.mp3 my conf: icecast>

Hello everyone. Thanks a lot! I got it working. Frankly speaking I had already tested the setup proposed, but I made two mistakes, first i tried to setup the port 443 and it was stupid as this port is already used by web service https. Second mistake was the .pem file that probably was wrongly concatenated and was not recognized/loaded by icecast. However I confirm that in most places on

I'm trying to broadcast a radio from a linux server that is coming from a windows machine using m3w. it's working very well for Winamp and linux mplayer as client - but while using Windows Media Player it's buffering for about 8 minutes then it start to work well w/ a delay of 8 minutes !! I've this set up : <burst-on-connect>1</burst-on-connect> <!--

In the past, i had used this method: http://icecast.org/loadtest/1/ But to be honest, nothing be compared with real use case, we found many issues when the connections arrive from many differents IPs, the stress test open all from small set of IPs, but almost this test case is used for many others, and present good results. 2016-06-10 2:40 GMT-03:00 Popov, Zahar <zahar.popov1978 at

We are pleased to announce that the long awaited 2.1 version of icecast is nearing release. Since there has been quite a bit of changes since 2.0, we thought it best to release a "release candidate" version. We welcome any testing on this version, and highly encourage current users to send us feedback about the testing. For those wondering what happened to RC1, we did a small RC1