[YP] [XML] mismatched tag at line 1

[keijo]

I've been redistributing conf files to separate general admin setup from streams. It all worked fine for about 24 hours until today early when my source decided tho give up in the middle of the night (died in her sleep).

Now the new source broadcasts fine but I've been getting this log entry on every title update:

2017-07-17 14:16:02 INFO [SRC xxx.xxx.xxx.xxx:xxxxx sid=1] Title update [Orange Blue - She's Got That Light]
2017-07-17 14:16:21 ERROR [YP] [XML] mismatched tag at line 1
2017-07-17 14:16:21 ERROR [YP] Stream #1 connection attempt failed. YP2 error code is 400 [Generic Error]

All previous posts/threads look marked as resolved by staff intervention, probably something to do within the Shoutcast directory servers, and not my local setup.

I've seen that before, like a month or so ago, and it magically went away.
What can be causing this?

Best regards,
keijo.-

[djSpinnerCee]

several yp servers are acting up.

ypaddr=tomcat1.winamp.com

i added the above to sc_serv.conf and reloaded config to force one that seems to be ok.

tomcat2, tomcat3, and tomcat4 were no good. they could be replicating bad code, so this may only be a temp fix.

[keijo]

2017-07-17 16:07:23 INFO [YP] Stream #1 has been added to the SHOUTcast Directory.

GO tomcat1

Thank you @djSpinnerCee

[djSpinnerCee]

you can add the following to your sc_serv.conf

;
; yp settings...
;
; use these to see which yp you're connected to in netstat, etc...
; 37.59.25.124 -- tomcat1.winamp.com
; 37.59.25.125 -- tomcat2.winamp.com
; 37.59.27.98 -- tomcat3.winamp.com
; 37.59.27.86 -- tomcat4.winamp.com
; 46.105.114.166 -- tomcat5.winamp.com
;
; uncomment the one you want to use...
;
;ypaddr=tomcat5.winamp.com
;ypaddr=tomcat4.winamp.com
;ypaddr=tomcat3.winamp.com
;ypaddr=tomcat2.winamp.com
ypaddr=tomcat1.winamp.com

;the default... will re-resolve to one of the above when your dns cache entry expires
;ypaddr=yp.shoutcast.com

[DJ Egg]

FYI, This issue is now fixed.

Note that only 1,3+5 can be used for YP, not 2+4

However, we do NOT recommend that you specify a particular server in the config
and you should remove/comment out all those lines now that the issue is fixed.

Sure, this doesn't mean that the issue won't ever come back... servers will be servers,
but it's something which will always be fixed as soon as someone who can fix it arrives at the office :-)


EDIT

We're still investigating some reports of "waiting on a directory response" errors.... watch this space.....

EDIT 2

All fixed :-)

[keijo]

Thank you all for your insights.

[YP] Updating listing details for stream #1 succeeded.

Back to normal...

[Geeque112]

All my streams are also getting "Waiting on a Directory response" error and all of my listeners cannot connect.

[neralex]

Originally Posted by Geeque112

All my streams are also getting "Waiting on a Directory response" error and all of my listeners cannot connect.

That's not true, streams are working also without YP connection.

[Geeque112]

Originally Posted by neralex

That's not true, streams are working also without YP connection.

Mine are not, I've never had this issue before, no one is able to connect to any of the streams.