similar to: no go, same ices/icecast errors

We just built a new server to run Icecast 1.3.11 and Ices 0.22. It's a Dual PIII running RH7.1. We put it online last night and Icecast ran fine for 20 hours. Then it started throwing some errors.. That's when Ices died. Ices reported a libshout error. Part of the Icecast log is included. What can I do about this? Hunter [26/Aug/2001:16:05:01] [32:Connection Handler] Accepted

Why does my stream not show up in the Icecast directory but it does show up in the Shoutcast directory? I have the following lines listed in my icecast.conf file. icydir yp.shoutcast.com directory yp.icecast.org If I check the icecast.log file I see the following is occurring every couple minutes. [28/Dec/2001:11:12:04] [1:Calendar Thread] directory_touch_xa([yp.icecast.org:80 ])

Icecast has been working flawlessly for months serving hundreds of users a day... But something strange is now going on... Do you know what it could be? I start the icecast as usual: /usr/sbin/icecast -c /etc/icecast/icecast.conf Then the ices "player" /usr/local/icecast/bin/ices -c /usr/local/icecast/conf/ices.conf But now, the player is now dying constantly with Invalid

Ahhhh, this is very strange! MY icecast server started doing the same exact thing today out of the blue! it looks as if hundreds of sources try to connect or something. but why would we both have the same problem at the same time after months of it working fine? paul On Thu, 3 Jan 2002, Roy Harvey wrote: > Icecast has been working flawlessly for months serving hundreds of users a >

Well, hi folks: I am still having this problem with ices crashing regularly. I have upgraded to todays cvs for ices and icecast hoping that would take care of it but no such luck. I am not sure just what is going on. It seems to happen fairly often which is not exactly making my listeners happy. I will include the relevant portion of the ices.log below. I would appreciate any suggestions

Hello! I've just started useing Icecast and Ices. Both has mainly the defaults in their conf files. fe.: Ices uses the default /ices mount point, end so on. After playing serveral hours, problems come up... Ices dies. In the ices.log these can be found: Error during send: Libshout reported send error, disconnecting: Libshout socket error. Error during send: Mount failed on

Hi ! I am new to the list. I have been using icecast togeahter with ices and live streamers for almost a year now. We have between 10 to 300 listeners, localsite and outside world. It has not been troublefree, icecast was stable util a week ago, just crashed and refused to work anymore. We upgraded in hope to get rid of problems. It worked for maby 24 hours and then it just stops by random after

Hey all, I've been having the same "Client not receiving data fast enough" errors. I've got icecast configured so as not to send info to ANY yp directories. Even on a quiet 100MB connection between client and server, I can stay connected for only about 5 minutes at a shot if I'm lucky. I'm using Icecast 1.3.11, and Shout 0.8.0. The files I'm streaming are all

> Um, why wouldn't you just use apache for this? Exactaly, I would recommend the mod_mp3 project for something like that. http://media.tangent.org/ They are doing almost exactaly what sound like you are looking for. There is also the project 'ampache' that takes this one step further and adds a MySQL database backend to a PHP front. JStanley --- >8 ---- List archives:

Hello, I'm struggling with getting my stream at the various directory services out there. Here are my experiences with icecast up to and including 1.3.9, which I installed today. I've had the same problems with previous versions, dating back to when I begain using icecast last July. My icecast.conf contains the following lines: icydir yp.shoutcast.com directory yp.icecast.org touch_freq

On Wed, 14 Mar 2001 lists@returntonature.com wrote: > I have the same problem below; does anyone know what the problem is with > that and how to fix it -- I haven't seen any response to the message below > .. > > Louis > > > > Hello, > > > > I'm struggling with getting my stream at the various directory services > > out there. Here are my

Hi Folks: I am either using the multiport of the -m or --match option of iptables in correctly or there is a bug with it. Is anyone else using it with no problem? This is the way I am trying to use it: my_ports=21,25,80 iptables -t nat -A PREROUTING -i $wan_addr -p tcp -m multiport --dports $my_ports -j DNAT --to $my_internal_address I have used this in the past successfully but that was a

I have the same problem below; does anyone know what the problem is with that and how to fix it -- I haven't seen any response to the message below .. Louis > Hello, > > I'm struggling with getting my stream at the various directory services > out there. Here are my experiences with icecast up to and including > 1.3.9, which I installed today. I've had the same

>However, we've disappeared from yp.icecast.org as far as I can tell. > >Looking in the logfile, I see the following:- > >[03/Apr/2001:15:30:49] >[1:Calendar Thread] directory_touch_xa([yp.icecast.org:80]) >completed...server id = 69 >Other info: I'm using streamcast I've been meaning to follow up to a similar post I made a few weeks back, so this seems like a

Folks, I've been running an icecast server for about a year, and never really had the chance to test it out on the other side of our Internet link. We've had a lot of people trying us out, but very short connect times in the whole. I finally got a cable modem at home, tried having a listen, and found the stream to be very stuttery. So, first things first, I went and grabbed the

Hmmm, I am using Winamp for my client, will upgrade it, but it works for other shoutcast/icecast streams. There has to be something buggered up in my config somewhere. It sounds as if Ices is sending data too quickly to icecast(?), will blow it away and re-complie it and see what happens. Thanks for the help so far. yeah, essentialmix.ca is directly related to the Essential mix broadcasts off

Brendan Cully <brendan@kublai.com> writes: > Well, it didn't work until yesterday, when I checked in a new > version. As a matter of fact it only works with extremely current lame > CVS, some things in lame were just fixed which would cause the current > code to crash in versions older than June 7. Talk about coincidences! I didn't have time until yesterday afternoon

Hi, I've been doing some work on ices, and I'd like to put out a release shortly so I can get to work on MultiStreaming (tm). Some bugs are fixed (eg now ices:BaseDirectory works (but note it is no longer called ices:Base_Directory - I figured since it was broken odds were good no one was using it), and song length is correct in the cue file), but mostly I've done a ton of work on the

Hi, I've been doing some work on ices, and I'd like to put out a release shortly so I can get to work on MultiStreaming (tm). Some bugs are fixed (eg now ices:BaseDirectory works (but note it is no longer called ices:Base_Directory - I figured since it was broken odds were good no one was using it), and song length is correct in the cue file), but mostly I've done a ton of work on the

I'm using icecast 1.3.10 and ices 0.1.0. I'm streaming through adsl which seems to do about 350Kb up. Everything is fine and stable for up to the 2 simultaneous subscribers I've tested so far. But... when I uncommented a directory server (yp.icecast.org) I see in the log: directory_touch_xa([yp.icecast.org:80]) completed...server id = 69 and about the same time the clients