similar to: Icecast source number problem, ices frozen after reconnect attemps failure (icecastkh13 iceskh48)

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

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%

Hello, I have a problem with icecast icecast-2.0-kh8: - the source disconnect - icecast didn't notice it - the source cannot reconnect until - the source cannot reconnect (it tries every 8 seconds) - after two hours, the source is able to reconnect Here is the interesting parts of the log files: Thanks for your advices and help. Chris (icecast machine has +3sec in its time, that's

Hello, ogg123 | ices2 are doing transcoding but ogg123 is staying frozen under certain circumstances here is the stack #0 0x401f25d4 in __pthread_sigsuspend () from /lib/libpthread.so.0 #1 0xbffff94c in ?? () #2 0x401f2398 in __pthread_wait_for_restart_signal () from /lib/libpthread.so.0 #3 0x401eef0b in pthread_cond_wait@GLIBC_2.0 () from /lib/libpthread.so.0 #4 0x0804b0d3 in

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

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

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 have some troubles with the latest icecast kh. I'm not sure it an icecast problem, but I have no idea... Does someone have an idea about that problem? The thing is that icecast is running on a uml linux. But this worked some weeks ago, then I come back to it, and I can't get it work again... Thanks, Chris <p>stalwook:~$ wget -Sd http://rbg.XXXXnet/radio-bro-gwened.ogg

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

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

Hi everybody, I'm in charge of an ices2 setup that's broadcasting a local radio station on the Net, and I'm currently under fire because one of our streams has been down twice in two days, forcing me to restart ices2 on each occasion. Our client is understandably unhappy about this. OUR SETUP: I've got ices2 installed on a local machine, broadcasting to an icecast server across

Hello I found that in this version, in the access log, the source log lines are wrong. The number of bytes transfered for the source is always 19 bytes... bla.bla.bla.bla - - [17/Nov/2003:23:25:22 +0100] "SOURCE /radio-bro-gwened.ogg HTTP/1.0" 200 19 "-" "IceS 2.0-Beta2" 13325 bla.bla.bla.bla - - [17/Nov/2003:23:25:52 +0100] "SOURCE /radio-bro-gwened.ogg

Main source: http://radio.stalig.com:443/radio-bro-gwened-ori.ogg reencoded OGG: http://radio.stalig.com:443/radio-bro-gwened-16.ogg http://radio.stalig.com:443/radio-bro-gwened.ogg http://radio.stalig.com:443/radio-bro-gwened-64.ogg reencoded to mp3: http://radio.stalig.com:443/radio-bro-gwened.mp3 (very bad, but mp3 is here just to have some mp3 in case of the listener is under Mac OS9 or

Hello, Karl, you added a compile-time flag to enable IP logging in icecast. But, this changed a lot the log procuded: 81.53.41.160 - - [30/Nov/2003:10:09:11 +0100] "GET /admin/metadata HTTP/1.0" 200 155 "-" "ices/0.3 libshout/2.0-kh22" 0 81.53.41.160 - - [30/Nov/2003:11:20:14 +0100] "SOURCE /radio-bro-gwened.mp3 HTTP/1.0" 200 19 "-" "ices/0.3

On Wed, 2003-11-19 at 11:49, iceuse@kezako.net wrote: > Hello > I found that in this version, in the access log, the source log lines are wrong. > The number of bytes transfered for the source is always 19 bytes... > bla.bla.bla.bla - - [17/Nov/2003:23:25:22 +0100] "SOURCE /radio-bro-gwened.ogg HTTP/1.0" 200 19 "-" "IceS 2.0-Beta2" 13325 >

On Wed, 2003-12-03 at 12:31, iceuse@kezako.net wrote: > Hello, > Karl, you added a compile-time flag to enable IP logging in icecast. > But, this changed a lot the log procuded: > 81.53.41.160 - - [30/Nov/2003:10:09:11 +0100] "GET /admin/metadata HTTP/1.0" 200 155 "-" "ices/0.3 libshout/2.0-kh22" 0 > 81.53.41.160 - - [30/Nov/2003:11:20:14 +0100]

On Wed, 2003-11-26 at 10:17, iceuse@kezako.net wrote: > 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): >

Hello, I have some trouble in the access log regarding to the source lines: 127.0.0.1 - - [13/Jan/2004:16:13:22 +0100] "SOURCE /radio-bro-gwened.ogg HTTP/1.0" 200 19 "-" "IceS 2.0-kh48" 30410 127.0.0.1 - - [13/Jan/2004:16:13:22 +0100] "SOURCE /radio-bro-gwened.ogg HTTP/1.0" 200 19 "-" "IceS 2.0-kh48" 30410 amount of data transfered for

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

Hello, I had a big trouble with ices (ices-2kh60). It is reading a playlist file containing "-" to tell "read stdin". But I think that when stdin is having problem, then ices become mad. It tries hundreds of time per second to play the playlist file content, generating huge amount of traces, which are rotated, but causing a denial of service on the server which become