similar to: ices2 routinely abandons one of its streams

Hiya Karl (and everybody else), I noticed today that ices 2.0-kh60a came out last January, and opted to give it a try. Unfortunately, it just wouldn't work at all, so I had to back down to 2.0-kh60. What I get in my log is this: [2006-04-21 21:16:18] DBUG om_shout/check_shout_connected Time we started stream on ice.imars.net:8000/cigr.ogg [2006-04-21 21:16:19] EROR

Hello, I will take your last version, but I have fresher news about the bug that occurs every mornings in fact... I think this is ntpdate which is causing the problem, as the time of the machine change for more than one second. Here is all the info: 09:46:17 up 1 day, 1:22, 2 users, load average: 0.60, 0.71, 0.68 86 processes: 84 sleeping, 2 running, 0 zombie, 0 stopped CPU states: 10.4%

Hi Karl, I just tried the latest - same problem :( One of the lines in the log file seems interesting - see the (Out of memory) error.. After that appears it seems to never want to connect after that. My box has plenty of memory - ices seems to only use 30 megs of memory and around 29% cpu. Memory leak maybe? [2003-10-12 17:29:40] EROR om_shout/output_ogg_shout Failed to write to

G'day Karl, I've been using your multiple instance version ices-2.0-kh43 for live streaming from my soundcard. After about 24 hours, connection to my icecast server is lost - checking my netstat I see that the connection is in "CLOSE_WAIT" status - this seems to stop it from being able to reconnect. Here is some sample ices.log output: [2003-10-09 06:57:17] DBUG

Got it all compiled nicely.. I called it ices2 so I can keep using my existing ices executable as well.. Tried getting it up and running but it seems to be having trouble connecting to my soundcard.. sample from ices.log [root@darkice root]# less ices.log [2003-08-06 01:11:09] INFO ices-core/main Streamer version IceS 2.0-kh35 [2003-08-06 01:11:09] INFO ices-core/main libshout version 2.0-kh19

Thanks Karl, I will give it a try. Do I have to install your modified libshout or isn't it required if I am live streaming? Cheers, Matt On 5 Aug 2003, Karl Heyes wrote: > not in CVS ices2, the problem is fairly involved to get into, not so > much for the initial filename but for things such as timing out or if > there's a problem with the link to icecast. > > If you

Fr?d?ric Bri?re wrote: > Hiya Karl (and everybody else), hi > I noticed today that ices 2.0-kh60a came out last January, and opted to > give it a try. Unfortunately, it just wouldn't work at all, so I had to > back down to 2.0-kh60. ok, send me your xml, so I know what parts are being used, I have to check the code for something else, but it does look to be the libshout part

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:

Hello, ices kh48 seems to have some trouble... See the stranges characters avec metadata update. (before, it was written bad address) and also, it is not connecting to icecast: socket error, ... I go back to kh47 for the moment. Chris [2003-11-25 10:45:50] INFO ices-core/main Streamer version IceS 2.0-kh-pre48 [2003-11-25 10:45:50] INFO ices-core/main libshout version 2.0-kh22 [2003-11-25

On Sun, 31 Oct 2004 22:32:17 +0000, andy wrote: > On Mon, 18 Oct 2004 16:06:00 +0100, Andy Baxter wrote: > >> I've been having a problem where ices-kh (the jack'ified version) >> disconnects from its jack input source unexpectedly. This happens mainly >> while other jack clients are being started/stopped, or >> connected/disconnected, but also at other times

I've been having a problem where ices-kh (the jack'ified version) disconnects from its jack input source unexpectedly. This happens mainly while other jack clients are being started/stopped, or connected/disconnected, but also at other times (e.g. switching between different X sessions). I'm planning to do a bit more work on tuning up the jack setup to see if I can get rid of the

Hello. I am running an up-to-date cvs snapshot (10 Aug 03) of ices2, and I cannot get the Metadata update from file to work (indeed this has always been true on all previous versions of ices2 that I have used). If I send the ices process a SIGUSR1, then the error log shows that the update is taking place, but immediately followed by a read error from the OSS input module, causing ices to die. I

Hello, I changed my config for ices and added passthru. I will see how it will run now. I have realtime I think: [2003-11-24 22:54:25] INFO ices-core/main Streamer version IceS 2.0-kh47 [2003-11-24 22:54:25] INFO ices-core/main libshout version 2.0-kh22 [2003-11-24 22:54:25] INFO ices-core/main realtime scheduling has been enabled

On Tue, 2003-08-05 at 16:00, Matt Trim wrote: > Got it all compiled nicely.. I called it ices2 so I can keep using my > existing ices executable as well.. > > Tried getting it up and running but it seems to be having trouble > connecting to my soundcard.. sample from ices.log > > [root@darkice root]# less ices.log .. > [2003-08-06 01:11:09] DBUG

Hello, I had a very strange behavior of ices: [2003-11-22 10:27:17] EROR playlist-builtin/write_ogg_data failed buffer allocation [2003-11-22 10:27:17] WARN input/input_sleep Sleeping for over 1 second (46364899), resetting timer [2003-11-22 10:27:17] WARN input/input_sleep Sleeping for over 1 second (46407041), resetting timer [2003-11-22 10:27:17] WARN input/input_sleep Sleeping for over 1

On Fri, 2003-10-10 at 04:51, Matt Trim wrote: > G'day Karl, > > I've been using your multiple instance version ices-2.0-kh43 for live > streaming from my soundcard. well it's multiple input really but... > After about 24 hours, connection to my icecast server is lost - checking > my netstat I see that the connection is in "CLOSE_WAIT" status - this seems

Package: logcheck Version: 1.2.39 Severity: normal Since I've upgraded my servers to sarge, I'm getting mail every hour for stuff that was duly included in /etc/logcheck/logcheck.ignore. Turns out that sarge's version no longer reads that file. If this was a conscious decision, then there should be some warning about this when upgrading (via debconf of NEWS.Debian). Also, the

When I try to make a call, I have this error: dial 06302@gatekeeper -- Executing Dial("OSS/dsp", "OH323/06302|20|tT") in new stack *CLI> WrapH323Connection::WrapH323Connection: WrapH323Connection created. -- Called 06302 WARNING[1272234688]: File chan_oss.c, Line 624 (oss_read): Error reading from sound device (If you're running 'artsd' then kill it):

Karl, > > [2003-08-10 10:41:32] DBUG encode/encode_clear Clearing encoder > > engine [2003-08-10 10:41:32] INFO encode/encode_initialise Encoder > > initialising in VBR mode: 2 channel(s), 44100 Hz, quality 5.000000 > > [2003-08-10 10:41:50] INFO signals/signal_usr1_handler Metadata > > update requested [2003-08-10 10:41:50] EROR > input-oss/oss_read

On Mon, 2004-11-01 at 03:23, andy wrote: > I just had a look at it and it's still dropping ports - I set a test > running which has ices-kh running from an ecasound process which is > connected to a new source every 10 minutes, and after about 3 hours it had > lost the jack port connection to ecasound. Can you send me the full log? > 2004-11-01 01:28:09] DBUG