similar to: Icecast locks with WARN connection/_accept_connection accept() failed with error 24: Too many open files

On 6/1/05, Joel Ebel <jbebel@ncsu.edu> wrote: > 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: snip... > The error had repeated itself for almost 24 hours before I noticed it. > Obviously it had too many files

On Thu, 13 Jan 2005 13:19:08 -0500, Joel Ebel <jbebel@ncsu.edu> wrote: > I asked this questions before, but I think it got lost/ignored in all > the traffic. So I'm asking it again. > > Why would my clients number always be 113 larger than my number of > listeners? It was right earlier today, but when I restarted the sources > it increased by 113, and it has stayed

Hello, I had a problem with ices kh48 and icecastkh13. I usually restart them by cron at 00:00. ----------1---------- This night, icecast told ices "Too many sources" for radio-bro-gwened.ogg... All right, I've just seen that my config file is wrong for icecast (I have 3 sources): <sources>2</sources> But, with this configuration, I can have 3 sources:

I discovered an interesting problem with ezstream. I'm using version 1.2. I see 2 is listed on the website but appears to be a broken link. Otherwise I'd try it to see if it exhibits the same problem. I'm using ezstream as a fallback mount for a radio station. It plays a 30 second ogg file over and over. The ogg file is just a 5 second message with 25 seconds of silence

On Thu, 13 Jan 2005 19:11:08 -0500, Joel Ebel <jbebel@ncsu.edu> wrote: > > - icecast version (and what platform you're running it on) > Icecast 2.2.0 running on Slackware Linux 10.0 > > > - icecast config file (with passwords blanked out, of course) > Config file is attached > > > - description of _precisely_ what figure you're looking at

I have an experimental installation of ices 0.4 streaming to icecast 2.2.0 on the same server (libshout 2.1). Ices had been very stable until this weekend, when it began dying after playing only a few MP3s (same files as before). Nothing in the ices.log to indicate a problem. The icecast error log shows this when ices dies: [2005-07-25 13:24:21] INFO source/source_main listener count on

Two quick questions: 1. Is it ok to use the same password file for multiple mountpoints, or will that cause problems? 2. Why would my clients number 113 larger than my number of listeners? It was right earlier today, but when I restarted the sources it increased by 113, and it has stayed that high since then. I find it especially odd since I have clients set to 100 in icecast.xml, and

Michael Smith wrote: > On Thu, 3 Feb 2005 14:10:50 +1000, Geoff Shang <geoff@hitsandpieces.net> wrote: > >>Ron Blok wrote: >> >> >>>Could it be a file/directory permission issue ? >> >>I have a vague recollection that the file needs to be able to be opened for >>writing as well as reading, if that helps. > > > Your recollection

I am very new on this list, so that I will first say hello to everybody. I been this morning on the IRC and some guy there explained me that if I want real help I must pay him 60 euros pe hour. I hope you dont charge me 60 euros for readiung this email and giving a hint. I have tryed to install icecast2 and ices2 on my dedicated server and followed allthe steps described on your site. in the end

Hello, I have trouble with icecast 2kh30. Sources connects, clients connects but : root@Yglar:/tmp# wget http://uml31:444/uml30.ogg --12:38:53-- http://uml31:444/uml30.ogg => `uml30.ogg' Resolving uml31... 192.168.0.31 Connecting to uml31[192.168.0.31]:444... connected. HTTP request sent, awaiting response... <p>client is blocked... on icecast side, I have

Linux blort.psg.com 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:02:19 UTC 2014 i686 i686 i686 GNU/Linux # icecast2 --version Icecast 2.3.3 <listen-socket> <port>43000</port> </listen-socket> <listen-socket> <port>43001</port> <shoutcast-compat>1</shoutcast-compat> </listen-socket> source is

Hello. A couple questions. When I execute curl http://myserver.xxx.xxx:8000/test.mp3 , I get "<b>The source you requested could not be found.</b>" I've placed my error.log and icecast.xml files below. Could someone help me understand my error.log a little better - to maybe see why I'm not getting a stream when I make the above curl call. Also, you'll see in

Karl Heyes wrote: > Seann Clark wrote: > >> The biggest being is that the server binds to whatever port it feels >> like instead of the bind port specified. The rest of the issues I have > > a random port bind is a new issue. Can you show us the > netstat -tnlp | grep icecast > for the xml provided? Thu Jul 03-13:54:17-root at haruhi-new:~> netstat -tnlp | grep

Hello, I’m new to icecast and I’m trying to setup icecast on Debian 8, with the 2.4.3 version, compiled manually. The thing is I can’t make the ssl part work. I have a listen directive like this : <listen-socket> <port>8483</port> <ssl>1</ssl> </listen-socket> and ssl-certificate :

Hello all; I have Icecast2 and Liquidsoap installed on an Ubuntu Server. This is the error log from the server [2018-08-08 02:22:18] INFO sighandler/_sig_die Caught signal 15, shutting down... [2018-08-08 02:22:18] INFO main/main Shutting down [2018-08-08 02:22:18] INFO fserve/fserve_shutdown file serving stopped [2018-08-08 02:22:18] INFO slave/_slave_thread shutting down current relays

Out of necessity, a friend of mine and I have created a patch for syslinux to allow it to modify the mbr and partition table in windows. It adds a -m option to syslinux. If given, it will overwrite the MBR of the drive specified with the mbr.bin provided in syslinux, and if the bootable flag is not set on the partition being syslinuxed, it will set it. This was done to distribute with my USB

This is what I get in the icecast logfile. [2005-03-27 15:35:13] INFO main/main Icecast 2.2.0 server started [2005-03-27 15:35:13] WARN main/main YP server handling has been disabled [2005-03-27 15:35:13] INFO stats/_stats_thread stats thread started [2005-03-27 15:35:13] INFO fserve/fserv_thread_function file serving thread started [2005-03-27 15:36:38] INFO admin/admin_handle_request Bad

On 02/24/2015 11:40 AM, Dean Sauer wrote: > On Mon, 23 Feb 2015 06:26:16 +0000, Thomas B. R?cker wrote: > >> We'd need error logs from such an incident, perferably at log level 4. > The error log from Icecast is as follows when this happened last: > [2015-02-15 16:24:08] DBUG source/get_next_buffer last 1424035387, > timeout 60, now 1424035448 > [2015-02-15

Hello everyone, I am searching and searching and can't find an answer. I try to register a sighandler in my extension's C code. But my sighandler is never called. Is there anything preventing extensions to receive signals? I register like this: [.. some code that works ..] // register the sigint listeners. if (signal(SIGTERM, killReceiver) == SIG_ERR) {

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