YP Directory broken or wrong?

[chophouse]

When tailing my logfile I am getting an error every 5 minutes, and nothing else.

Error is " <11/28/12@11:25:08> [yp_add] yp.shoutcast.com gave extended error (Cannot see your station/computer (URL: http://212.72.187.16:-32668) from the Internet.

My port is not 32668 and I'm wondering where this info comes from and how or who to ask to change it so the correct port is being looked for?

[chophouse]

I can listen fine (and URL shows correct port), so the stream is up, but for some reason its wrong in the directory.

How to fix?

[DrO]

it comes from the information provided by the DNAS during it's connection to the Directory. other than checking 'portbase'. though -32668 is an negative signed integer so something is messed up with the data the DNAS is providing (and as it seems to be a v1 DNAS, if it is a bug then i don't know what to suggest).

-daz

[chophouse]

Thanks DrO

You mention , "other than checking portbase". How do I check that? Where does DNAS get the information it provides to the directory?

Thanks,

[DrO]

it would be specified in the configuration file (usually sc_serv.conf or sc_serv.ini) used by the DNAS server (unless it's not and then it's meant to use 8000 as the default in the v1 and v2 DNAS). from how you've worded things, i'd have to assume you're using a hosting provider and if so then there's not much you can directly check and may have to get them involved.

-daz

[chophouse]

I guess I'm not understanding how the stream can be up and I can connect to it, Shoutcast Administrator says the stream is up, but then the sc_serv.conf is wrong?. How is "the information provided by the DNAS during it's connection to the Directory" supplied? What file is it and what should it day if I'm on server 123.45.67.89 on port 12345 ? What should the exact entry be and where should it be?

This all happened immediately after switching from 1 shoutcast server to another at my provider. My provider is saying "The config file son the server is correct. The yp.shoutcast.com directory is broken. If the config file were incorrect, the server wouldn't be online and working."

Would appreciate any help you can provide as I am now on day 4 of losing listeners and I suspect its because my station is not showing up in the directory.

Thanks.

[DrO]

Originally Posted by chophouse

I guess I'm not understanding how the stream can be up and I can connect to it

the DNAS can run without having to be listed in the Directory, so that aspect failing doesn't prevent people (you) still being able to connect to the DNAS and so listen to the stream.

Originally Posted by chophouse

Shoutcast Administrator says the stream is up, but then the sc_serv.conf is wrong?.

without a config file to verify, i don't know if it is wrong or not. as i don't know if your host has changed the file or are using the same one and it's something else which was done.

Originally Posted by chophouse

How is "the information provided by the DNAS during it's connection to the Directory" supplied? What file is it and what should it day if I'm on server 123.45.67.89 on port 12345 ? What should the exact entry be and where should it be?

as i've already said, it uses 'portbase' from the config file or 8000 if it is not present in the config file which is specified to be used. as i'm not 100% on what platform version of the DNAS is being used, it could be sc_serv.ini or sc_serv.conf or any custom name the host has decided upon to use.

Originally Posted by chophouse

This all happened immediately after switching from 1 shoutcast server to another at my provider. My provider is saying "The config file son the server is correct. The yp.shoutcast.com directory is broken. If the config file were incorrect, the server wouldn't be online and working."

i don't know why it's not working but having had something changed (whatever they did) would make me wonder what was done as it running fine until then doesn't match with _any_ changes having been also made to the YP in the timescale that you seem to have had issues.

maybe it is a YP issue or even a DNAS issue (anything is possible with a legacy v1 DNAS) but as you're host is using the legacy v1 DNAS, there's little i can get to be changed in the config to have it target a specific YP server so i can then try to determine the issue (not without them changing firewall rules). then again, doing that would cause you more potentially impact than you're already having.


so i don't know what to say / suggest as unless your host provider gets in contact with me (my email address is at the bottom of here) or someone can provide me with a copy of the config file being used so it can be verified / tested with, there's little i can do for the time being.

-daz