similar to: Curious ices2 log entries

I just built icecast and ices from CVS source. The compile went fine. But I'm having trouble connecting to the server and hearing anything. In one shell, I start icecast with: src/icecast -c conf/icecast.xml That appears to start things off fine. Then in another shell, I start ices: src/ices conf/ices-playlist.xml At this point, icecast prints some text: connection added.... DEBUG: source

Dear All: I have Icecast2 and IceS2 successfully built and installed on a Debian 3.0 system. After tinkering with the config files, both applications are running and seem to be talking to each other without problem. However, when I try to connect with a client, I run into problems: with Winamp 2.8, I get an [HTTP/1.0 200 OK] message, but then the stream is apparently dropped before buffering.

[In case anyone is wondering, the missing message is because I emailed Mike directly, not realising I wasn't sending to the list.] On Tue, Aug 16, 2005 at 12:56:57PM +0200, Michael Smith wrote: > On 8/16/05, Paul Martin <pm@nowster.zetnet.co.uk> wrote: > > On Tue, Aug 16, 2005 at 10:31:09AM +0200, Michael Smith wrote: > > > > > This shouldn't cause any

I'm using ices2's metadata facility to update the name of a track in a vorbis stream: <input> <module>alsa</module> <param name="rate">44100</param> <param name="channels">2</param> <param name="device">hw:1,0</param> <param name="metadata">1</param>

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

hi everyone, congratulations on the release of icecast 2.1.0 I presume this is the right place to post about iceS. please correct if wrong. I have a two instance setup, and have been finding that after a network error occurs, the instance does not reconnect. The source server is behind a linux NAT box. I have simulated the problem by using iptables REJECT with tcp-reset and here is the

Hi all! I just finished an install of icecast/iceS but I'm having problems. I followed the documentation provided here: http://melmoth.dyndns.org/stream/doc/ to the letter and this is the problem I'm having: Everything seems to function (icecast runs, iceS runs) and it generates messages such as: [root@icecast stream]# bin/ices conf/ices-playlist.xml [2003-06-04 06:43:17] INFO

Hi, I'm currently migrating from Shoutcast/MP3 to Icecast/OGG/Vorbis using ices. Unfortunately, when initialising the encoder, ices crashes with a bus error. Is there anything I can look into? Details as follows: icecast2-2.1.0,1 ices-2.0.0,1 libshout2-2.0_5,1 libogg-1.1.2_1,3 libvorbis-1.1.0_1,3 (All were installed from the ports tree) On FreeBSD ares.radiozilvervos.com 5.3-RELEASE-p4

On Sun, 2003-08-10 at 10:56, Ben Middleton wrote: > 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,

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 Folks: Every now and then my ogg123 quits while loistening to > the stream. It isn't a bandwidth problem because my ogg123 is on a > machine which is just a few feet from the server and is in fact on the > same machine with ices2 doing the streaming. It happened this morning > and I decided to take a look at the log and found some curious > messages and thought

Hi: Well, up until about a week ago, we had our stream up and running on 3 seperate mountpoints and it was rock solid. then we started hitting problems with disconnects and the like. I recompiled everything this morning and set it running again. But one mount has died already. We have 3 streams running. the first is the ogg files as they were encoded (egoplay.ogg). the second is a

Hello I've discovered, that sending a SIGUSR1 signal to ices causes it's shutdown when recording from an alsa dsnoopped device. > [2004-11-01 18:51:51] INFO signals/signal_usr1_handler Metadata update requested > [2004-11-01 18:51:51] DBUG metadata/metadata_thread_signal meta thread wakeup > [2004-11-01 18:51:51] DBUG stream-shared/stream_wait_for_data Shutdown signalled:

it is possible to play the same song after it finished in ices2? i'm geting this error, even if i rename the song: log: EROR playlist-builtin/playlist_read Cannot play same file twice in a row, skipping [2007-06-16 03:47:23] WARN playlist-builtin/playlist_read Skipping "/var/www/radio/playlist/espaco_vital_080607_conv2.ogg" as the serial number is the same as previous

Hello, I'm testing icecast2(apha2) and ices2(beta2). (sources 2003-08-12) ices2 with ices-playlist works fine! But I have troubles whith ices-live. When ices2 trays to read /dev/dsp a log message appears: INFO input-oss/oss_read Reached EOF, no more data available. and ices2 shutdown. the complete log file (debug=4): ******************* log *******************************************

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

On 8/16/05, Paul Martin <pm@nowster.zetnet.co.uk> wrote: > > Caught it yesterday, as I was already running level 4: This line: [2005-08-15 04:10:58] EROR stream/ices_instance_stream Send error: No error (Success) is the one that catches my attention. Unfortunately, ices's error logging is somewhat sub-standard. Can you cross reference this against your icecast error.log to see

Hi Pete, El jue, 28-11-2019 a las 09:51 -0500, Rondejavu escribió: > I am starting IceCast first. The log indicates that everything is > working. Maybe I need to change something in my HTML code? > > audio controls > Source src=“ipaddress:port/stream” > /audio > > -Pete > Not change your HTML code, in fact, it is already working ok. You must solve the problem on the

... [2009-02-14 20:54:27] INFO ices-core/main Shutdown complete [2009-02-14 21:01:02] INFO ices-core/main IceS 2.0.1 started... [2009-02-14 21:01:02] INFO signals/signal_usr1_handler Metadata update requested [2009-02-14 21:01:02] INFO playlist-basic/playlist_basic_get_next_filename Loading playlist from file "/etc/ices2/playlist.txt" [2009-02-14 21:01:02] WARN