Station ID wrong on one server...why?

[MegaRock]

Been trying to figure this one out for awhile but something is amiss between the YP and one single stream server.



For some reason this one single server refuses to show the same station ID as all the other relay servers. Have tried making it a main server and having others relay from it. Nope. So I thought..well it should pull that from the main server so I feed to another and have this server relay from it. Nope. 13 servers and this one single one refuses to show the right station ID. Below is correct.



Every other server shows the right info. And the only major problem is if anyone hits the listen link on the incorrect server the playlist file only loads that stream. Any of the other servers spit out all the relays in the same file. The authhash and pretty much every configuration file used is a copy of the previous to keep things consistent.

The YP hates me.

[djSpinnerCee]

if i had to guess, it's the authhash that must be different.

that said, i'm sure you carefully checked the authhash, so how about the config file itself? maybe win (cr/lf) encoded on a unix box? that would make the authhash look the same to the eye in an editor, but not to the dnas parser. ie: i get unprintable chars in my posts that don't show up until i submit.

another question - do you see the orphan dnas in the shoutcast directory? it should have its own entry since it has a unique id. then on the other side, do the relays that are correctly grouped report the orphan in their pls file (that would be unlikely)?.

the last thing could be that you have an authhash that was created before rmo registration was required -- that would link to a grandfathered directory id that is found once by the orphan (remember, the old yp was host/port based), then the rest of your stations find the new rmo style directory entry. a longshot, i know, but its really the only way the same single dnas would exhibit the behavior you describe. you can outrule it by changing the portbase if you can.

[MegaRock]

Well these are all recent installs because until a few months ago I stuck with the old 1.9 line. The orphan one does show in the directory and same as on the server it only loads playlist from the one server. I have even gone as far as to completely delete the server and all the files, download a fresh install and turn it back on and it returns to this station ID. I do believe I have multiple IP's I can use on that box maybe I need to try a different IP or port because it's the only thing I haven't tried but in the end I have to keep that port because there are tons of links going to it. If things are what they are it is almost as if it's stuck in the YP on just that IP and isn't letting it join the others even with it relaying off a server showing correct info.

And no the orphan does not show up in the other playlists..again very weird what with it relaying from a correct server.