Not sending signal!!!
 

Hi guys and gals, i have previously made a radio station throught shoutcast followed all steps and made it work. But not to long ago i had to restore my XP system, now i started over and followed all steps, unblocked everything from XP firewall and everything. But it seem the server only gets as far as:
[yp_add] yp.shoutcast.com added me successfully
when shouldnt it go on to:
[yp_add] yp.shoutcast.com touched!
and on top of that shoutcast.com doesnt receive my radio station when i search it. So if anything can help i would appreciate it thanks:winamp:

It's fine. The YP has been laggy lately, wait it out.

Thanks, i was so worried, it good know:up:

Ah - wait up. Look closely at your logfile. When you start streaming, you get the

[yp_add] yp.shoutcast.com added me successfully

right?

Do you also get a visit from the directory tester?

Example:

<06/09/06@09:58:45> [source] creating relay socket
<06/09/06@09:58:46> [source] relay host gave success (ICY 200 OK)
<06/09/06@09:58:46> [source] relay from xx.xx.xx.xx established.
<06/09/06@09:58:46> [source] icy-name:Atlantic Sound Factory - ASF Radio ; icy-genre:70s 80s 90s Rock Pop Alternative
<06/09/06@09:58:46> [source] icy-pub:1 ; icy-br:64 ; icy-url:http://www.ASFRadio.com
<06/09/06@09:58:46> [source] icy-irc:N/A ; icy-icq:N/A ; icy-aim:N/A
<06/09/06@09:58:47> [dest: 205.188.234.99] starting stream (UID: 8)[L: 8]{A: SHOUTcast Directory Tester}(P: 7)
<06/09/06@09:58:58> [dest: 205.188.234.99] connection closed (0 seconds) (UID: 8)[L: 7]{Bytes: 278528}(P: 7)
<06/09/06@09:58:58> [yp_add] yp.shoutcast.com added me successfully

If you didn't see the directory tester, you're probably a member of the nak(100) club. I run 11 servers. Five of them developed this problem last weekend. When I changed the PortBase on those servers, they were visited by the directory tester and were back on the YP within 15 minutes.

Sorry found nothing on a tester but just got this
<06/09/06@14:13:11> [yp_tch] yp.shoutcast.com gave error (nak)
<06/09/06@14:13:11> [yp_tch] yp.shoutcast.com gave extended error (100)

yp is broken, no you. nothing you can do it fix it. doesnt mean your stream isnt working, it means the server that lists your stream on shoutcast.com is fukd upd..

Alrite, but on the example shown above of the tester by dotme shows that it goes directly to the rock website. Could i do the same and just send it to my website.

Right. I don't know how many times to say this. It can be fixed. Edit your config file, change your PortBase= value to something different. Restart server after you have updated port forward settings on your router.

Note that I said you were a member of the nak(100) club. Look at the error you posted. See where it says "nak" and "100"???

Of course, don't worry about it if you don't care. I don't - all my streams are now listed and my clusters/relays are working.

thanks!!:)

if you move your stream to another port and still get NAK 100 errors, dont waste your time :)

I run my stream on port 8080, and por 80, never on port 8000 :) no nak errors when I run the stream either.

hate the YP, dont you dotme ?

lol - I wish I didn't depend on it. But I do. iTunes only works with the first server in the .pls file - So if that server is full, iTunes won't automatically go to the next server in the file. A good 65% of my audience are iTunes listeners.

When the YP works, the full server redirects the listener to a backup (relay) server. When the YP broke this weekend, the relays lost track of each other. The result was hundreds of connection attempts were refused while I had 500 open slots on the station. I coded around it, but it was good yesterday to finally figure out how to put everything back in working order.

The nak(100) isn't necessarily related to port 8000. For example, one of my servers was on port 4000 and started getting the nak(100) problem. I changed it to 4050 and the YP listing came back. Just for grins, I put it back to 4000 and the nak(100) reappeared. It's been 16 hours now, and if I fire up a DNAS on port 4000, it still won't get listed.

Whatever port you were running on at the time of this malfunction, that port's the one the tester won't hit. It's almost like it thinks you're already streaming.

This fix works for me - I hope it works for others too.

Thanks guys moved it to port 7100 and it works perfect. Hope i wont have to come bak. :)

dotme wrote:

Whatever port you were running on at the time of this malfunction, that port's the one the tester won't hit. It's almost like it thinks you're already streaming.

--------------------------------------------------------
hehe dotme i get it...its like..fx if ya wish to reboot
ya server you get screwed by da yp-tester if its in mailfunction and you have to do evrything all over again..
man man...da yp-tester..da bitch..love it.. :D