Problem with directory

[noxerpus]

Hi,

Is this a problem again?

http://forums.winamp.com/showthread.php?t=333706

I am having the exact problem as i did when this error was occuring.

[SnowHow]

Originally Posted by noxerpus

Hi,

Is this a problem again?

http://forums.winamp.com/showthread.php?t=333706

I am having the exact problem as i did when this error was occuring.

They had pushed an update a few days ago that was intended to fix different stations from being clustered together and it broke more than it fixed....

I checked my servers this morning and it seems to have been cleared up. See this thread:

http://forums.winamp.com/showthread.php?t=336669



SH

[noxerpus]

ah okey, as per 31.10.11 09:25 GMT im still having problems with directory, only a few channels showing etc. and problem is identical to the link that i postet earlier..

[DrO]

see http://forums.winamp.com/showpost.ph...1&postcount=15 and the note about not being able to actually find out wtf happened until another few hours from the time of this reply.

SnowHow: i don't think it was directly related to that and the other changes in the new push since it was otherwise running ok for 3 days (ignoring the clustering issue), though from what i've been able to find out so far (which is not much), something else failed which may have caused the YP to then not respond even if it was still running ok.

-daz

[noxerpus]

thank you daz for the update

ill wait and see when you have resolved the issue if my problem goes away

and no, you dont need to get another job, i think your doing just wonderful:P

[DrO]

further update is that not all 'api' based actions are working correctly - that's being resolved by someone else (though the yp going down the way it did appears to have thrown some parts of the system into an invalid state).

should improve over the next few hours though a better fix is likely to be deployed (not yp related) which will resolve that in the future.

-daz

[SnowHow]

Originally Posted by DrO

SnowHow: i don't think it was directly related to that and the other changes in the new push since it was otherwise running ok for 3 days (ignoring the clustering issue), though from what i've been able to find out so far (which is not much), something else failed which may have caused the YP to then not respond even if it was still running ok.

-daz

Thanks for the clarification!

SH

[noxerpus]

FYI, my problem has been resolved, thanks.

[DrO]

thanks for the confirmation. we've found a few things which is likely to have caused the api failure so hopefully should be resolved over the next few days.

-daz