Not all relays showing up in Directory

[DJ Overload]

Right then, basically what I have is a main server with 2 relays, like this:

SERVER 1 (20 listeners max)
- SERVER 2 (120 listeners max)
- SERVER 3 (200 listeners max)

Servers 2 and 3 both relay the first one, but sometimes only 1 or 2 of the servers actually show up in the directory, which means that it shows less listeners than are actualy on and therefore the stations is lower on the page than it should be

Does anyone have an idea of why this is happening and how I can solve the problem?

Thanks

[dotme]

Check logfiles for YP errors... post them.

[DJ Overload]

Ahh log files - good idea - I had a look and it said this:

<08/05/06@17:00:46> [yp_tch] yp.shoutcast.com gave error (nak)
<08/05/06@17:00:46> [yp_tch] yp.shoutcast.com gave extended error (100)
<08/05/06@17:02:06> [dest: 72.192.2.78] service full, disconnecting
<08/05/06@17:02:46> [dest: 84.179.198.212] connection closed (8927 seconds) (UID: 3483)[L: 19]{Bytes: 141036243}(P: 0)
<08/05/06@17:04:08> [dest: 84.9.114.13] starting stream (UID: 3634)[L: 20]{A: WinampMPEG/5.21}(P: 0)
<08/05/06@17:05:47> [dest: 207.200.98.4] service full, disconnecting
<08/05/06@17:05:47> [yp_add] yp.shoutcast.com gave error (nak)
<08/05/06@17:05:47> [yp_add] yp.shoutcast.com gave extended error (Cannot verify server since all listener slots are full. Please wait or reserve IPs: 205.188.234.[97-100] and 207.200.98.[1-4].)


I have put these ips in the reserve list:

207.200.98.1 and 205.188.234.97

but will I need to also add 205.188.234.98, 205.188.234.99, 205.188.234.100 etc?

Thanks

[DJ Overload]

I've tried putting all of the ips in that it said but I dont think that thats the problem, becaus the 1st server is never listed on there.

I have PublicServer set to always but still no luck. According to the log file it is being added, but still only the 2 relays are actually showing up :/ here is the log file from after the server is restarted:

<08/08/06@01:21:03> [SHOUTcast] DNAS/Linux v1.9.7 (Jun 23 2006) starting up...
<08/08/06@01:21:03> [main] pid: 30461
<08/08/06@01:21:03> [main] loaded config from temp/8026_1154996463.conf
<08/08/06@01:21:03> [main] initializing (usermax:20 portbase:8026)...
<08/08/06@01:21:03> [main] No ban file found (sc_serv.ban)
<08/08/06@01:21:03> [main] No rip file found (sc_serv.rip)
<08/08/06@01:21:03> [main] opening source socket
<08/08/06@01:21:03> [main] source thread starting
<08/08/06@01:21:03> [main] opening client socket
<08/08/06@01:21:03> [main] Client Stream thread [0] starting
<08/08/06@01:21:03> [source] listening for connection on port 8027
<08/08/06@01:21:03> [main] client main thread starting
<08/08/06@01:21:05> [source] connected from xx.xx.xx.xx
<08/08/06@01:21:05> [source] icy-name:xxxxxxxxxxxxx ; icy-genre:drum and bass
<08/08/06@01:21:05> [source] icy-pub:1 ; icy-br:128 ; icy-url:http://www.xxxxxxxxxxxxxx
<08/08/06@01:21:05> [source] icy-irc:N/A ; icy-icq: ; icy-aim:N/A
<08/08/06@01:21:07> [yp_add] yp.shoutcast.com added me successfully
<08/08/06@01:21:17> [dest: xx.xx.xx.xx] starting stream (UID: 0)[L: 1]{A: WinampMPEG/5.0}(P: 0)........ etc

Any ideas? The host that I am using (mouse-mouse) uses Cast-Control by the looks of it (might be an issue?) or maybe a problem with the directory?

Thanks

[fc*uk]

well, the original error that you were getting (nak 100) is a known error and I believe that the folks at SHOUTcast have mainly resolved the issue.

The other error appears to be due to the fast that all your server slots are full. Cant cram 51 people on a 50 slot stream...

I know there have been clustering issues along with the nak100 that people are getting. Maybe if you post 100% of your dnas output one of the admins around here would take a look at it for you and shed some light on the issue.

[dotme]

nak 100 is back... no timeframe on a resolution that I am aware of. And yes, add ALL the IPs to the reserve list. That will fix the "Cannot verify server" issue.

[deppy]

can you provide me with your iport of all 3 servers?

Thanks!

[DJ Overload]

Hi,

Thanks for your help, it seems to have sorted itself out now, all servers are listed.

I contected my hosting provider and they said that it is probably something to do with the yp directory acting up recently.

Thanks for your time,

Gav

[dotme]

I have one that may be an issue. 208.53.131.66 port 2000

It developed the "No Tester" issue Saturday afternoon. For me, it was a critical server so I hard-coded a working YP IP into the Hosts file and moved on... it's been fine ever since... but it's possible that this IP/Port combo may still not work with all YP servers on startup. Hope the info helps.

[deppy]

that does help....i'll take another look at this, it might be a little different this time cause the things i was seeing last time aren't happening anymore.

i should have more info later this evening.

[DJ Overload]

It looks like the directory is just showing each server as and when it wants, sometimes it only displays one, other times it displays 2 or 3 etc.

@deppy, here are my ip/ports if it helps:

212.227.65.62:8026
66.79.164.213:8000
74.52.25.89:8014

[deppy]

The new NAK 100's should be going away (I have some stuff running to clean them up right now). I'll keep a closer eye on things to make sure they don't come back. I've put another fix into place that I'm hoping will keep this from coming back.

[Zoab]

I have also a NAK 100 problem and I don't see any touch by YP.
But I have had a lot of disconnects before I was getting the NAK 100 error again, maybe that is the reason that the dir tester won't come by again...
This is the IP and port : 208.53.170.120:20042
The server is a stand-alone, my other servers are working properly!
I hope that the problem can be solved.

[Zoab]

Strange......I got touches again and I am listed....
Maybe there is a sort of timer @ YP to prevent the servers against connecting overload or something?

[GhettoRadio]

Originally posted by deppy
The new NAK 100's should be going away (I have some stuff running to clean them up right now). I'll keep a closer eye on things to make sure they don't come back. I've put another fix into place that I'm hoping will keep this from coming back.

our relays stop being listed again, nak errors. only the main relay is listed now.. here's the ips:

207.210.90.107:8090 <-- main, seems to stay listed
67.159.5.160:8005 <-- nak error
208.101.33.203:9710 <-- nak error

[Gorbymedia]

Aha, same thing here, seems these have the NAK100 error.

66.90.101.184 ports 7050, 7055, 7065 and 7069

My relays are fine, and I think this server was previously banned when someone else on the subnet misbehaved.

Hope this helps, Richard

[urbansoulnation]

Earlier today all my three servers were listed. Then, sometime this afternoon, this particular server 66.111.216.148:6256 dissappeared from the listings. I checked the logs and saw this error:

yp.shoutcast.com gave extended error (100)

How long should I expect this to occour?

[urbansoulnation]

Ok nevermind. Looks like it was just a temporary glitch.

[BELLonline]

Yeah only one of my relays is currently listed, suppose we're just going to have to wait for it to be fixed.

[Goodtimez]

I've had similar problems, but the shoutcast directory is borderline flakey all day long. *shrug* I'm just happy my stream shows up period on there.