similar to: solution for YP problem

On Mon, 2005-07-25 at 23:55, mark burdett wrote: > For 100% reliability I ended up removing dir.xiph.org from my > list of YP directories. My guess is it was taking too long to > respond to requests, which could be a problem if an icecast > server has a large number of mounts. But it could be a > problem unique to me (I'd be curious to know if anyone else > has had

For 100% reliability I ended up removing dir.xiph.org from my list of YP directories. My guess is it was taking too long to respond to requests, which could be a problem if an icecast server has a large number of mounts. But it could be a problem unique to me (I'd be curious to know if anyone else has had trouble). the dir.xiph.org admins might want to make sure the db is well tuned (e.g.

At 04:30 PM 7/8/2003 -0400, you wrote: >On Tue, Jul 08, 2003 at 03:10:25PM -0500, oddsock wrote: > >Already checked that. this is the HTTP header for the stream: > >Content-Type: audio/mpeg >icy-bitrate:16 >icy-description:SF Indymedia >icy-genre:Talk >icy-name:Enemy Combatant Radio >icy-public:1 >icy-url:http://sf.indymedia.org/ >Server: Icecast 2.0-alpha2/cvs

Ok I've been discovering many bugs in Icecast's YP implementation.. The most serious of which is, if a YP server is rejecting a stream the server has a memory leak which, as it continues to re-try to publish it's rejected streams, grows until the server segfaults. On our server, for instance, we're relaying shoutcast streams (which does not relay the stream name and other

On Mon, Aug 04, 2003 at 02:09:58AM +0100, Karl Heyes wrote: > > Who said that the protocol had changed, libshout still sent what it had > before and I don't in fact know when the protocol was last changed. So > saying it keeps changing is completely wrong. Also the YP servers don't > see this part anyway. I thought that you had said that they source-server protocol had

yes this is darkice. perhaps we could work in 'icy-public' support...? --mark On Tuesday, Jul 8, 2003, at 19:58 US/Pacific, Arc wrote: > On Tue, Jul 08, 2003 at 03:40:42PM -0500, oddsock wrote: >> what source client is generating that ? > > I believe they run darkice, Mark Burdett would have to supply more > specific details as this is a relay of their lofi-mp3

At 03:58 PM 7/8/2003 -0400, you wrote: >That isnt the only bug. One one of our icecast servers the third >stream, sf-lofi.mp3, is not being announced to YP servers at all. On my >local diagnostics (logs all connections to the liveradio.indymedia.org >YP server) I see that icecast isnt even trying to add it. The other YP >servers are not showing this stream either. It doesnt

On Sun, Aug 03, 2003 at 06:50:56PM +0100, Karl Heyes wrote: > > > We've been having a major problem with our icecast servers, some streams > > are being sent to the YP servers and others are not, and yes the public > > bit is set as confirmed by connecting to the streams directly and > > looking at the headers they send. > > There was a header mismatch, make

On Wed, Jun 25, 2003 at 11:34:07AM +1000, Michael Smith wrote: > > > 2) Should relay icy/x-audiocast stream metadata when connecting to > > icecast1/shoutcast/etc so that this information is available to YP > > Eh? It does. I even tested that with someone's shoutcast stream. It works. > Just add >

On Wed, Jun 25, 2003 at 03:33:25PM +1000, Michael Smith wrote: > > Is the metadata relayed to connecting clients. i.e. take a client that > supports shoutcast-style metadata, like winamp (and probably most others). > Connect as a listener to the relay. Do you get metadata? You should. If you > don't, the metadata relaying could have been broken (I think this is >

i have two icecast servers on the same host (logging to the same file) one is a public server that people connect to one is a backend switcher to switch what they listen to and handle fallbacks. when a source or relay times out, the public server disconnects at the same time that the backend server switches to the fallback. what is the best way to deal w/ this? increase the source timeout on the

At 10:08 AM 7/8/2003 -0400, you wrote: >On Tue, Jul 08, 2003 at 11:36:10AM +0100, David Jones wrote: > > and Ross Levis wrote: > > > Sometimes when I restart my stream it appears for a while without > > > updating the title etc and then disappears a few minutes later. I'm > > > sure Dave will fix it eventually but he is away for the week. > > >

I am sorry, I don't understand. Karl Heyes napsal(a): > On Sun, 2005-06-05 at 14:18, Karel Du?ek wrote: > >>Is possible YP listing in >>http://dir.xiph.org/cgi-bin/yp-cgi >>and >>http://www.oddsock.org/cgi-bin/yp-cgi >> >>from Icecast2.2 with source Ices2? > > Im error.log of icecast2 I have [2005-06-05 15:33:20] DBUG yp/yp_recheck_config

ices.conf: <Public>1</Public> <!-- The name of you stream, not the name of the song! --> <Name>Poohba's Urban Sounds</Name> <!-- Genre of your stream, be it rock or pop or whatever --> <Genre>RnB</Genre> icecast.xml <directory> <yp-url-timeout>15</yp-url-timeout>

On 02 Jan 2005 18:16:01 +0000, Karl Heyes <karl@xiph.org> wrote: > On Sun, 2005-01-02 at 18:01, Dan Stowell wrote: > > Hi, > > > > My icecast2 config file includes > > > > <directory> > > <yp-url>http://www.oddsock.org/cgi-bin/yp-cgi</yp-url> > > </directory> > > > but when I go to the oddsock YP, I can't

Hi everyone: Thanks to me not setting a max log size in our icecast install, a problem with YP stuff caused the log to grow to almost 2 gig and fill the partition. Probably just as well it did, or we might not have noticed. The sysadmin had to trim the log to get space back, so the bit where it all started no longer appears. But in the 4 hours of log I still have, the following line appears

I have a problem with adding my icecast-stream till the YP-directory. I don't get any error messages regarding WHY my station isn't added to the YP either. Stream URL: bananradion.bananklubben.se:8086 Hostname: bananradion.bananklubben.se <listen-socket> <port>8086</port> <!-- <bind-address>127.0.0.1</bind-address> -->

On Tue, Jul 08, 2003 at 03:10:25PM -0500, oddsock wrote: > At 03:58 PM 7/8/2003 -0400, you wrote: > >That isnt the only bug. One one of our icecast servers the third > >stream, sf-lofi.mp3, is not being announced to YP servers at all. On my > >local diagnostics (logs all connections to the liveradio.indymedia.org > >YP server) I see that icecast isnt even trying to add

I am having problem with icecast2/winamp oddcast dsp/darkice being listed on dir.xiph.org and dir.oddsock.org. Now I've scanned the mailing list and found that there was a previous issue, however if I use icecast on Windows XP it works fine, but not from Fedora Core 1. I've made sure to check my config files multiple times and looked at the error logs but I still can't figure

Hi, My icecast2 config file includes <directory> <yp-url>http://www.oddsock.org/cgi-bin/yp-cgi</yp-url> </directory> but when I go to the oddsock YP, I can't find our stream anywhere. Am I doing something wrong, or is something more needed in the config? Thanks in advance. I'd also be grateful if you'd clarify which YP I *should* be using! Does it make any