Shoutcast YP errors today

[digitboy]

I have been running a server for a few weeks without issue. I haven't changed any configuration parameters or programs. Today, my server log is showing "[YP] Stream #1 connection attempt failed. YP2 error code is 493 [Internal error - unable to acquire data source]" every 5 minutes.

Is this a server side issue? Is there any place I can query whether the YP is up and functioning correctly?

Thanks,
Dave

[digitboy]

I can listen to the stream, but it's not listed in the station search on www.shoutcast.com

See attached...

Any help, please?

[LouR]

yeah we're getting same thing since about mid-day today: yp_add] yp.shoutcast.com gave extended error (Internal error - unable to acquire data source). Last time this happened, DrO mentioned that it was on their end. Things just aren't relaying like they should be. Hoping they fix it soon.

[ram130]

Seeing similar issue. Mainly says waiting on directory response. I wouldn't worry.

[digitboy]

Thank you for the reassurance that it's not a problem on my end.

Best to all,
Dave

[ram130]

Yep...seems to be a issue on their end for V2 servers

Heres another server with the issue: http://69.64.33.220:8015

V1: http://s7.voscast.com:7000/

I wouldn't too much unless most of your listeners comes from the directory. People can still tune in regardless.

[djwhitelion]

yeah i just set up a server the other day everything was fine then i got this

200
2015-01-14 21:04:53 WARN [YP] Unable to automatically create an authhash for stream #1
2015-01-14 21:04:53 WARN [YP] Error code is 462 [Parameter error]
2015-01-14 21:04:53 WARN [YP] Detailed error message is: Invalid parameter k
2015-01-14 21:04:53 ERROR [YP] Manual authhash creation for stream #1 is required. Aborting registering the stream in the SHOUTcast

so can this be caused by their side cause im not getting my stream in shout cast list

[ram130]

I've seen this before. It's a directory registration issue. I've ping the dev team. It should be fixed soon. I think it's because they updated the servers to a new release.

[djwhitelion]

kool i hope so im set to launch this show tomorrrow and im not down testing

[ram130]

This issue is now fixed

[DrO]

the issue had nothing to do with the YP itself or the DNAS version and was an unexpected issue on the backend.

as such all DNAS versions (1.x and 2.x) were affected by the backend issue despite what the legacy 1.x DNAS indicates (as it only shows public or private and not anything that is helpful like the 2.x DNAS does to better show what is going on - you can see more information by logging into the DNAS if the public summary page indicates an issue).

http://yp.shoutcast.com now provides a more visible indication if there is an issue as well as the message which is provided back to the DNAS having been adjusted.

finally, if in doubt, there is the feedback / support links on shoutcast.com or you can email support@shoutcast.com directly.