[not] listing debugging tool? (I'm not listed... why?)

[geniegate]

About a year ago, I had a stream, using the 1.n version of shoutcast. Everything worked great, took about 15 minutes and got listed.

Fast-forward a year, DNAS 2.0.0.29/posix(linux 64):

I've created the key, it says it's public, the error log gives me this:

msg:[YP2] Connected to yp.shoutcast.com. The station should now be listed in the SHOUTcast Radio Directory (YP).

I waited ~24 hours, no listing. The logs say it's connecting to the directory.

One thing that is different this time around is that I'm relaying a private "master" server, (for technical reasons I hope aren't relevant) does that make a difference?

Any way for us mortals to investigate why it's not showing up?

If you search for "triviacompanion" it should be there.

I've just rebooted sc_serv, (was that even helpful?)

Is there a tool of some kind I can use to find out whats happening, why it's not showing up?

Thanks!



Secondary:

I'm puzzled about the genre string, I used have this:
"Cool Jazz,Orchestral Pop,Retro"

After generating the key, it gave me "Cool Jazz" and that was it. Can I go back some way and put those secondary genres in there? (for now, I've pretty much just left it as the key generator wanted)

[DrO]

i've just searched for 'triviacompanion' and it's showing up via a direct backend check i.e. using the Winamp SHOUTcast Radio view but not on the main site.

as for why it's not showing no the site, i'm really not sure and it's something i've still to properly look into though as it shows up in the backend, it's probably something on the site handling that just isn't liking relays (and ironically is on my todo list for next week to figure out what is going on).

I'm puzzled about the genre string, I used have this:
"Cool Jazz,Orchestral Pop,Retro"

After generating the key, it gave me "Cool Jazz" and that was it. Can I go back some way and put those secondary genres in there? (for now, I've pretty much just left it as the key generator wanted)

only one genre is associated against a listing be it v1 where you could specify a number of them or v2 where it only allows one. to add the other ones, you'd need to enter them into the 'keywords' section of the authhash details - which is what the YP does automatically for a v1 based listing when multiple genres are provided.

-daz

[geniegate]

Originally Posted by DrO

as for why it's not showing no the site, i'm really not sure and it's something i've still to properly look into though as it shows up in the backend, it's probably something on the site handling that just isn't liking relays (and ironically is on my todo list for next week to figure out what is going on).

Hmm.. interesting! is there a clean way to hide the fact that it's a relay? I wonder if it's seeing the relay and then following the path of "Oh, it's a relay, we should lump this in with the other streams relaying the same master" (which of course, there aren't any.)

I could see where this would be useful for multiple PUBLIC relays, but not in this case.

The master server is private, firewalled from public use. I'd prefer no one knew what it was or that it existed, if I can hide this, all the better.

Is there much harm in me restarting the stream... a lot? I'm thinking I might launch 2 sc_serves (I can't do this as a permanent solution...) and/or dabble around a bit just to confirm it's a relay issue... but I don't want to get myself black listed.

Originally Posted by DrO

only one genre is associated against a listing be it v1 where you could specify a number of them or v2 where it only allows one. to add the other ones, you'd need to enter them into the 'keywords' section of the authhash details - which is what the YP does automatically for a v1 based listing when multiple genres are provided.

As a listener, I really liked your old directory, where the other genres (keywords) were next to the stations. When I found a station I liked, I'd look at the genres it filed itself under and click them, other stations using the same tags. It was a neat way to explore the directory.

Anyway, if someone connects, I wish they could see the full genre list. As it is, when I launch it in mplayer, the ICY data only provides "Cool Jazz" as the genre. (no big deal, really)

Thanks for your time!

[DrO]

Originally Posted by geniegate

Hmm.. interesting! is there a clean way to hide the fact that it's a relay? I wonder if it's seeing the relay and then following the path of "Oh, it's a relay, we should lump this in with the other streams relaying the same master" (which of course, there aren't any.)

most likely something with how the site cache is built up is incorrectly taking the relay flag from the backend data, but there's no way to not have that sent through as the public build of v2 DNAS will always send through if it's running in a relay setup (never was too sure why that was done but that's how it goes currently).

Originally Posted by geniegate

I could see where this would be useful for multiple PUBLIC relays, but not in this case.

i really don't think it should be working like that at all. if a stream either for a direct source connection or for a relayed instance is set to be listed, just because it's a relay doesn't mean it shouldn't be listed if it's set to be public. and as the v2 clusters listings based on the authhash set for the stream, it should be treating the stream just like any non-relayed stream.

all i know is that listing relays doesn't work in the desired manner compared to a v1 based stream and it comes down to an issue either in the YP or in the site's handling of the information it pulls from the YP databases.

Originally Posted by geniegate

Is there much harm in me restarting the stream... a lot? I'm thinking I might launch 2 sc_serves (I can't do this as a permanent solution...) and/or dabble around a bit just to confirm it's a relay issue... but I don't want to get myself black listed.

it depends if you've got streamid values in your config file or not to ensure the authhash isn't lost (see http://forums.winamp.com/showthread....79532#remember). though restarting it isn't going to make any change to how the listing is dealt with if it's still being done as a relay as mentioned in my earlier part of this reply.

Originally Posted by geniegate

As a listener, I really liked your old directory, where the other genres (keywords) were next to the stations. When I found a station I liked, I'd look at the genres it filed itself under and click them, other stations using the same tags. It was a neat way to explore the directory.

that still can be done if you hover over the listing so the information tip appears and then you can click on the keywords to get that as the new search. though i really cannot remember how the old site used to work so i'm not sure how clunky that approach is compared to old (though i thought it's been like the current way for ~3years now).

-daz

[geniegate]

Originally Posted by DrO

all i know is that listing relays doesn't work in the desired manner compared to a v1 based stream and it comes down to an issue either in the YP or in the site's handling of the information it pulls from the YP databases.

Originally Posted by DrO

restarting it isn't going to make any change to how the listing is dealt with if it's still being done as a relay as mentioned in my earlier part of this reply.

Well, I've gotten rid of the relaying element completely, did this approx. an hour ago, still hasn't shown up in the listing. (probably takes awhile?)

Any chance my change will some how set a flag some place that renders the key invalid or something?

If this doesn't work.. is there any way I can use some kind of legacy approach? I'm starting to like the old way.

[DrO]

i cannot check the backend system directly (i shouldn't even be online at the moment) but it is showing via the base api as was the case before. so something is most likely being kept incorrectly set from what went before (as the hired help from before never considered such things happening or weren't kept on to actually finish the job properly *grumble*) but i cannot check what is actually causing that any time today.

there are a few things i could try but i need to be around to be able to deal with any failures that come from it and as that isn't something i can do, is down to you what you now do. the fact is shows via backend api queries i.e. in Winamp or other services using it means it is available and working, just not via the site search itself.

-daz

[geniegate]

Originally Posted by DrO

i cannot check the backend system directly (i shouldn't even be online at the moment) but it is showing via the base api as was the case before. so something is most likely being kept incorrectly set from what went before (as the hired help from before never considered such things happening or weren't kept on to actually finish the job properly *grumble*) but i cannot check what is actually causing that any time today.

there are a few things i could try but i need to be around to be able to deal with any failures that come from it and as that isn't something i can do, is down to you what you now do. the fact is shows via backend api queries i.e. in Winamp or other services using it means it is available and working, just not via the site search itself.

I certainly don't expect anything to be done about it on a sunday! It's good to know part of it works at least, so it's likely a website malfunction.

When someone gets back, during the normal, human working hours, I hope they check into it... if there's anything I should try, let me know. (and you're right, doing the cat utility thing is an ugly kludge.. that didn't even work... there must be better ways..)

Thanks for trying! (No one should have to sacrifice their weekend!) looking forward to this week... but I hope they'll give you monday off. :-)

[DrO]

Originally Posted by geniegate

When someone gets back, during the normal, human working hours, I hope they check into it...

that would still be me.

from the quick look against a non-relay setup, there's nothing clearly different between your listing and the other ones i've checked. when i've got a better idea or something to try out then i'll send you a pm with any test builds / specific setting changes to do, etc.

Originally Posted by geniegate

(and you're right, doing the cat utility thing is an ugly kludge.. that didn't even work... there must be better ways..)

with the relay failure, it's fixed in the internal builds as confirmed in the other thread so that is known to be ok now. and additionally since that test build i've been adding in a 'backupurl' support which will be used (if specified) if the original direct source or relay source fails and then hands things back if the actual source comes back (usually without dropping the YP connection).

-daz

[DrO]

pm sent...

-daz