22nd June 2010, 04:28
|
#1 |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
YP NAK "Inconsistent Stream Behavior"
Has anyone seen this yp nak message before? This one starting popping up in our logs for no apparent reason:
<06/21/10@08:40:01> [yp_add] yp.shoutcast.com gave error (nak) <06/21/10@08:40:01> [yp_add] yp.shoutcast.com gave extended error (Inconsistent stream behaviour) Station does not show in the listings. Any ideas? |
|
|
|
22nd June 2010, 07:19
|
#2 | |
|
Moderator
Join Date: Nov 2004
Location: Streamsolutions Headquarters
Posts: 11,953
|
Its not a normal nak error tho.....
 Quote:
|
|
|
|
|
|
22nd June 2010, 10:58
|
#3 | |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
Quote:
|
|
|
|
|
|
22nd June 2010, 11:02
|
#4 | |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
Quote:
 and hoping someone can tell us what the problem is.
|
|
|
|
|
|
22nd June 2010, 16:40
|
#5 |
|
Moderator
Join Date: Nov 2004
Location: Streamsolutions Headquarters
Posts: 11,953
|
Sorry that was aimed @ Aquarius.
Looking at this error (Inconsistent stream behaviour) it would suggest connectivity issues however it looks like one of the new yp errors, Does this error keep appearing or is it randomly showing? |
|
|
|
|
22nd June 2010, 17:23
|
#6 |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
I don't have complete log files for the server, the provider pipes them to /dev/null except for if you're using the "tail logfile"... so I can't say exactly when it started or if it does this all the time. I can post more logs, but they only show this error and client "starting stream" and "connection closed" messages as listeners tune in or stop listening. I was alerted to the problem by a listener who complained that they couldn't find the station on shoutcast.com, so we went looking for the problem. Every time I look, it's getting this error message, so it's a least pretty consistent.
People can tune in via links on the station web site though, so it seems to be just a YP problem. What does this "Inconsistent stream behaviour" message usually indicate? I was not able to find any information on that error. |
|
|
|
|
22nd June 2010, 17:44
|
#7 |
|
Moderator
Join Date: Feb 2005
Location: USA
Posts: 4,024
|
Ya we're all guessing on this one. There are a bunch of new YP NAK error messages and some are pretty unhelpful when it comes to troublehooting.
Inconsistent Stream behaviour? What, it doesn't like the burst-on-connect? Too many source drops? YP doesn't agree with your taste in music? Genre settings outside of the allowable genres? Bitrate doesn't match? Cluster mismatch? We might get lucky and have one of the dev team look at this thread, but the more info you can post in advance, the better the chances of getting a helpful answer. Do you cluster? Are there relays? If yes, do the status pages all show the same genre, bitrate and stream name info? Have you had frequent source drops lately? |
|
|
|
|
22nd June 2010, 18:16
|
#8 |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
YP doesn't agree with your taste in music? Maybe
.. but there are other stations within the same genre.Genre settings outside of the allowable genres? No. Contains one of the key genre words ("blues"). Bitrate doesn't match? Always 128k everywhere. Do you cluster? No Are there relays? No If yes, do the status pages all show the same genre, bitrate and stream name info? N/A Have you had frequent source drops lately? No. We do have two sources though...one sends the stream 24/7 and one that is initiated by the DJ when they are "on the air". The 24/7 stream is a random playlist, the DJ kicks the source for that when he wants to go on the air. |
|
|
|
|
23rd June 2010, 07:24
|
#9 |
|
Moderator
Join Date: Nov 2004
Location: Streamsolutions Headquarters
Posts: 11,953
|
If you goto the logs and open the page on your machine and leave them running you should be able to copy and paste the logs out as they have been produced after leaving it running for a day or so.
or ask the host for the full logs, Untill we know if this has come from the server or the Dj stream or if its constant or random then we are not going to know for sure. it may not be visual issues and may Just be packet loss etc. |
|
|
|
|
23rd June 2010, 11:17
|
#10 |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
Thanks very much for your help. I've had the log streaming since earlier this morning and will capture a days worth anyway. We get 500,000+ tune-ins a month, so a days worth would be about 30,000 log lines - probably more than I can post here. I will grep out lines that do not match "starting stream" or "connection closed".
It seems though, that no matter what we're all just guessing at what the problem is. There must be someone, somewhere that knows what this error is (since they coded it). Is there no way to get in touch with them? |
|
|
|
|
23rd June 2010, 14:32
|
#11 | |
|
Moderator
Join Date: Feb 2005
Location: USA
Posts: 4,024
|
Quote:
|
|
|
|
|
|
23rd June 2010, 15:36
|
#12 |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
Aquarius Antares: Thanks for the info, I don't think it's packet loss either. Any time there's ever been packet loss, the stream will skip and listeners complain in emails or the site's shoutbox. Haven't had any of that in at least a year.
dotme: Thanks for checking on this with the devs! |
|
|
|
|
24th June 2010, 11:03
|
#13 |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
Collected log file for 24 hours and discounting the "starting stream" and "connection closed" messages from the clients, there are just the:
<06/23/10@23:53:52> [yp_add] yp.shoutcast.com gave error (nak) <06/23/10@23:53:52> [yp_add] yp.shoutcast.com gave extended error (Inconsistent stream behaviour) messages every 5 minutes. There are a handful of messages from crawlers: <06/23/10@23:50:04> [dest: 66.219.58.43] Invalid resource request(/robots.txt) if anyone wants to see the complete log, PM me and I can make it available. I'm not sure where to go from here. |
|
|
|
|
24th June 2010, 18:31
|
#14 |
|
SHOUTcast (Alumni)
Join Date: Sep 2008
Posts: 162
|
Attention everyone who's stations have mysteriously disappeared from the SHOUTcast directory:
Due to some recent upgrades to the platform our Ops team has had to re-provision some servers on the YP infrastructure. As a result the IPs of some of the servers behind the yp.shoutcast.com domain have changed. It is possible that broadcasters that are seeing their stations not listed on the directory are pinging older servers that were still pointing to old/defunt SC DB due to DNS caching. We recommend that you flush / purge your DNS cache and restart your SHOUTcast servers to see if this problem goes away. Additionally, we have permanently shut down the "old" IP servers, so you should start seeing errors now if your servers are still hitting the "old" IPs. It usually takes a few days for DNS to fully get purged so we will monitor this to see if this is addressed... Thanks for your patience and for helping us debug this issue...! Cheers f. |
|
|
|
|
24th June 2010, 19:24
|
#15 |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
Thanks very much for your response! I've email the stream provider to have them try this. In the meantime, I wonder about 2 things:
1) The DNS TTL for yp.shoutcast.com (aliases to ypdp.gypdp.shoutcast.com) is 30 seconds. If it's supposed to refresh the address every 30 seconds, how could we be stuck on an old address? 2) Is the error message: <06/23/10@23:53:52> [yp_add] yp.shoutcast.com gave error (nak) <06/23/10@23:53:52> [yp_add] yp.shoutcast.com gave extended error (Inconsistent stream behaviour) from the old YP or the new YP? If only on the new YP, then we must be using the new address and not the old one..no? I will post again noting the results of the DNS flush and restart. |
|
|
|
|
24th June 2010, 19:31
|
#16 | |
|
SHOUTcast (Alumni)
Join Date: Sep 2008
Posts: 162
|
Quote:
2. We will post all the YP errors and what they mean shortly... Not sure what "Inconsistent stream behaviour" even means! Ive asked our dev team to provide all error messages so I can review / edit to make them more descriptive if applicable. f. |
|
|
|
|
|
24th June 2010, 20:32
|
#17 | |
|
Junior Member
Join Date: Feb 2005
Posts: 43
|
No add neither YP listing for weeks now
Quote:
«Event log: <06/24/10@18:05:04> [SHOUTcast] DNAS/win32 v1.9.8 (Feb 28 2007) starting up... <06/24/10@18:05:04> [main] loaded config from C:\Program Files\SHOUTcast\sc_serv.ini <06/24/10@18:05:04> [main] initializing (usermax:10 portbase:8000)... <06/24/10@18:05:04> [main] No ban file found (sc_serv.ban) <06/24/10@18:05:04> [main] No rip file found (sc_serv.rip) <06/24/10@18:05:04> [main] opening source socket <06/24/10@18:05:04> [main] source thread starting <06/24/10@18:05:04> [main] opening client socket <06/24/10@18:05:04> [source] listening for connection on port 8001 <06/24/10@18:05:04> [main] Client Stream thread [0] starting <06/24/10@18:05:04> [main] client main thread starting <06/24/10@18:05:07> [source] connected from 127.0.0.1 <06/24/10@18:05:07> [source] icy-name:JAdSC\Portugal cefeidas@sapo.pt stereo Brasil\internationalCelticFolkBluesSoulPopRock ; icy-genre  ecades eclectic misc<06/24/10@18:05:07> [source] icy-pub:0 ; icy-br:96 ; icy-url:http://www.shoutcast.com <06/24/10@18:05:07> [source] icy-irc:#shoutcast ; icy-icq:0 ; icy-aim:N/A» or sometimes reply that [yp_add] error connecting to yp_shoutcast . It seems to have happened at the same time that the old listing - that I believe noone as I can access anymore - in http://classic.shoutcast.com has gone from Internet - funny the linking for it is still in the http://classic.shoutcast.com page, but nonoperational... You're really undergoing quite a change. Will it be accepted any new MP3 or AAC streaming again or not? Will there be new audio formats available, e.g. why not the open-source OGG? |
|
|
|
|
|
24th June 2010, 21:21
|
#18 |
|
Member
Join Date: Nov 2008
Posts: 55
 |
hey guys.. im getting the same errors.. I've been getting it for a full month. I run a dedicated server hosted out of DC so I'm not behind any fire wall.
I know I've restarted this server recently. code: Any help would be awesome guys. |
|
|
|
|
24th June 2010, 22:32
|
#19 | |
|
Junior Member
Join Date: Feb 2005
Posts: 43
|
Quote:
«; DestIP, IP to listen for clients on (and to contact yp.shoutcast.com) ; can and usually will be be ANY. If your machine has multiple IP addresses, ; set this to the one you want it to be accessed by. DestIP=ANY» which means ANY of your servers should listen to my stream, ain't it? |
|
|
|
|
|
28th June 2010, 17:53
|
#20 |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
Flushing DNS and restarting the server did not help. Still receiving error:
<06/28/10@09:29:42> [yp_add] yp.shoutcast.com gave error (nak) <06/28/10@09:29:42> [yp_add] yp.shoutcast.com gave extended error (Inconsistent stream behaviour) I did some additional research and set up another shoutcast server and set all the parameters of the server to be exactly the same as the server I'm having trouble with. The stream title, genre and url set to the exact settings that the troublesome server is having. This server also received the exact same error as above. I tried altering each parameter of the config and stopping/restarting the server and observe that if I change only the url of the station, the error goes away. Any hostname in the URL that resolves to the same IP address as the station site causes the error. For example, on this web server there are several web sites sharing the same IP with the station web site. If I put one of the web addresses for these other (unaffiliated) sites in the URL for the station in the server config, I still get the NAK error. If I put another web site, from a different IP address instead, no NAK error. It would appear that this is some kind of intentional block on the station by the YP (based on the IP address of the station web site). The reason for this block is still a mystery. |
|
|
|
|
28th June 2010, 18:21
|
#21 |
|
Moderator
Join Date: Feb 2005
Location: USA
Posts: 4,024
|
Ah... well done. I think you're onto something. Maybe if another YP-listed station has a website that resolves to the same IP address as yours does, the YP says "no" because it already has a station/stream with a website linked to that IP.
If this is true, it has to be a bug. I mean, IPv4 addresses are hard to come by and many web hosts will run hundreds of sites on one IP. I'll bring this thread to the attention of the devs - hopefully they'll respond. |
|
|
|
|
28th June 2010, 18:25
|
#22 |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
dotme, thanks for the quick response! There is only one shoutcast station web site on that IP address though. It's my own server, there are maybe 20 web sites on that IP, but only one shoutcast station, the rest are random businesses and personal web sites.
|
|
|
|
|
1st July 2010, 08:47
|
#23 |
|
Junior Member
Join Date: Jul 2010
Posts: 1
|
It seems though, that no matter what we're all just guessing at what the problem is. There must be someone, somewhere that knows what this error is (since they coded it). Is there no way to get in touch with them?
|
|
|
|
|
1st July 2010, 14:43
|
#24 | |
|
Forum King
Join Date: Jul 2004
Location: E*arth
Posts: 3,031
|
Quote:
Pray real hard. The yp is screwed right now because of new sc2 framework,this maybe the cause. So Long, and Thanks for All the Fish.  
|
|
|
|
|
|
1st July 2010, 15:31
|
#25 |
|
Moderator
Join Date: Feb 2005
Location: USA
Posts: 4,024
|
I did hear back, but no definitive answer on the "inconsistent stream behavior" error. That one's a real puzzler.
If you're getting that specific error, post as much info as possible about your setup. For example, how many Shoutcast servers are running for the station? Are they independently sourced (each has its own encoder connected), or chained together (relaying)? If relaying, do ALL status pages across all servers display identical station name, genre, URL information? If we get more data, we might collectively figure out how to resolve this. NOTE: Thread title updated to reflect the specific error. Do NOT post here unless you are receiving the "Inconsistent Stream Behavior" error. |
|
|
|
|
1st July 2010, 15:46
|
#26 |
|
Major Dude
Join Date: Jan 2009
Location: San Diego CA
Posts: 998
|
Just for a clearer understanding of this problem.
1) How are you trying to connect? Are you trying to use a DSP to your server, SC_trans, or using some Hosting server manager licensed program like WHMSonic/Centova. 2) What is the file type your trying to stream? Can I get: a) File format (MP3, AACP, OGG Vorbis, FLAC Vorbis, CELP, SPEEX, MP3LEGACY, LAME ?) b) File bitrate (128kbps, 64kbps, Quality 8 Vorbis?) c) File type is VBR or CBR? (when you listen to them in winamp, does the khz/kbps bounce around?) d) Channel (shouldnt matter, but why not ask?) This information might shed some light on the issue. KNSJ.org 89.1 FM San Diego |
|
|
|
|
1st July 2010, 16:35
|
#27 |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
There is just one server, no relays. Connection is either through Winamp plug-in directly to sc_serv running on a windows host in a data center - or - when the DJ is off the air, sc_trans connecting to the same sc_serv. File format is mp3, 128kbps, CBR. Channel?
Key fact I mentioned earlier (#25 above) regarding the resolved IP address of the station web site specified in the StreamURL parameter leads me to think this is a targeted action by the yp for this particular station, but the reason is a mystery. |
|
|
|
|
1st July 2010, 16:48
|
#28 |
|
Moderator
Join Date: Feb 2005
Location: USA
Posts: 4,024
|
Well crap. Can you bind a second IP to the box and move the website(s) to it? Just for giggles...
|
|
|
|
|
2nd July 2010, 03:35
|
#29 | |
|
Junior Member
Join Date: Mar 2003
Posts: 13
|
Quote:
So to be clear - to get re-listed, I had to change the IP address of the web site referenced in the StreamURL. I changed nothing on the shoutcast source or server. That's just weird. |
|
|
|
|
|
8th July 2010, 21:50
|
#30 |
|
SHOUTcast (Alumni)
Join Date: Sep 2008
Posts: 162
|
I think this has to do with the "bug" currently wherein YP will try to authenticate an addtch call by pinging it back, and if the IP is shared it will likely fail. Dev team is looking into this weird beahviour and we should have a fix soon...
f. |
|
|
|
|
8th July 2010, 22:10
|
#31 | |
|
Moderator
Join Date: Feb 2005
Location: USA
Posts: 4,024
|
Quote:
The Website URL IP address was the issue. If he changed the website URL to some other site on the same webserver, the error would continue. If the URL was changed to a different IP (www.google.com for example) the NAK error went away. Hope this helps! |
|
|
|
|
|
9th July 2010, 19:31
|
#32 |
|
Member
Join Date: Nov 2008
Posts: 55
|
I noticed a lot of my YP issues went away when the YP servers went down on July 4th and came back online.. However my relay servers still do not display in the listing.
I can post logs if you guys need them? |
|
|
|
 |
|
|||||||
«
Previous Thread
|
Next Thread
»
| Thread Tools | Search this Thread |
| Display Modes | |
Linear Mode
|
|
Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2023, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2023, Jelsoft Enterprises Ltd.