more 404s

[BIGDADDY]

the 404 errors are flying now.. and it was fine all day.. so i dun think its on the user end..

[BIGDADDY]

i dunno, if you let the servers slice n dice for a bit it seems to straighten out .. but i'm sure thats annoying the heck outta the machine doing the checking on these additions.

[Highway 420]

Aye, this has to do with their new security protocols, i think...that and their servers are probably overloading as well, that's been a problem for some time.

[peppert]

This problem will increase for servers when your pipes are overstuffed. Again, 404 means no audio data was received in 10 seconds, while connection refused means it couldn't get a connection to your server at all. If this is happening at peak times, I'd suggest reducing your max listeners.

[Highway 420]

So, why has the problem only been happening for the last few weeks? I haven't changed anything on my end, it *doesn't* only happen at peak times, and trust me, my connection speed is just fine. Once I get in to yp.shoutcast.com, all's good. It just takes forever to get listed there if I shut down my broadcast for any reason whatsoever.

[radstream]

I have never seen this error before today. I shut down my server, after running fine for 5 or 6 days straight, changed from a 24k to 32k stream and now I get nothing but:

<06/01/00@21:07:35> [yp_add] yp.shoutcast.com gave error (nak)
<06/01/00@21:07:35> [yp_add] yp.shoutcast.com gave extended error (404)
<06/01/00@21:07:35> [dest: scastweb2-qfe0.winamp.com] connection closed (sent 81
92 bytes total) (0/20)

This is rather irritating. I have been waiting for 30 minutes for it to connect. Any more ideas from anyone else???

Ken

[radstream]

Whew... Ok... A little research... Above, peppert (Tom???) indicated that a 404 is caused when no data is received within 10 seconds. Do you mean my server received no audio from the ShoutcastDSP plugin, or do you mean something else? While my server was receiving this error, I went to a second PC, dialed up to MSN with a Flex56 modem, connected to my Shoutcast server (running on a 500/250k cable modem) and was able to recieve the 32k stereo stream into WinAmp from the server, through MSN, with no problem. As a matter of fact, about 10 minutes after I started playing the audio on my secondary PC, the errors went away. Could there be a link?

I don't mean to be picky, I am just trying to fish for answers. I am the computer geek type that likes specific info. http://forums.winamp.com/ubb/wink.gif

TNX
Ken

[peppert]

The reason 404s have started in the past few weeks is that we just implemented checking. Before, anyone could get in the directory without verification of whether or not a stream was running.

Latency is the problem. If we don't see mpeg data at the shoutcast directory within 10 seconds (which seems pretty reasonable to me), you get a 404. try doing a traceroute to yp.shoutcast.com (you won't make it all the way, but mail me with the latency of the last hop in your route) -- i want to see you guys in the directory.

[Highway 420]

Hey, Tom

Last night I had a power failure, and had to reset everything when the power came back on. There were no problems listing on yp.shoutcast.com at all when I logged back on...so I'm thinking the few times I've had that problem revolved around latency issues, as you say. Doesn't bother me that much anyway...just did a traceroute and right now the ping is running 95-125 milliseconds as far as it will go.

Thanks for all your hard work, by the way. I've been streaming since September, and have had *very* few problems with Shoutcast. Thanks for a great service!

Cheers,

H420

[radstream]

AHHH, PEPPERT! Thanks for the info. The 404s have completely stopped now. Maybe a problem between my ISP & AOL.

Great work & TNX!
Ken

[Radio National]

Hu Peppert!

I mean it´s kinda strange! I was today 3.8.2000 5 times logged on and broadcasting succesful. But now I get error 404. First I start the Server. Then I start Winamp and connect! But then I get this error!!! Can you help me??

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by peppert:
The reason 404s have started in the past few weeks is that we just implemented checking. Before, anyone could get in the directory without verification of whether or not a stream was running.

Latency is the problem. If we don't see mpeg data at the shoutcast directory within 10 seconds (which seems pretty reasonable to me), you get a 404. try doing a traceroute to yp.shoutcast.com (you won't make it all the way, but mail me with the latency of the last hop in your route) -- i want to see you guys in the directory.<HR></BLOCKQUOTE>