nak error 100 is back

[abc666]

it looks like the nak error is back... after going several months without the nak error it appears to be back. i'm sure they'll fix it soon though.

<08/29/06@04:23:58> [yp_tch] yp.shoutcast.com gave error (nak)
<08/29/06@04:23:58> [yp_tch] yp.shoutcast.com gave extended error (100)
<08/29/06@04:29:00> [yp_add] yp.shoutcast.com added me successfully

[dotme]

Yep - It's been back for a little while. My understanding is that the goal hasn't been to make it "go away" but to make it temporary. It can happen when the server sends too many add/remove requests in rapid succession. I *think* it's supposed to clear by itself after a few hours, but maybe somebody from AOL/Nullsoft can confirm?

[MegaRock]

Cough.

(bump)

[abc666]

thanks

[FS-Randy]

I have noticed it pop up every now and then, but it is not nearly as bad as it was, where we would recieve several tickets per day. So far we have recieved none since the fix.

[Gorbymedia]

I'm seeing it periodically along with being "permenantlt banned for violating TOS" and "banned for falsifying info", yet after a while, I'll be added, then banned, then added.

This is only on one of my servers. I keep meaning to get a new IP for it from the ISP.

It gave me kittens early on as my listed cluster maxed out but then the banned ones rejoined the cluster and took the overspill.

[forumtalk]

Same thing If I change stream title , after change port it will fix

[drlovejones]

can not see station because of extended error 404

[drlovejones]

how to put my web site up and to fix a link for the station

[dotme]

Originally posted by drlovejones
how to put my web site up and to fix a link for the station

What??? Please don't hijack threads to post unrelated questions.

[tuckerm]

maybe we should bump the orignal thread...deppy seemed to keep close tabs on that one..?

[CraigF]

ive seen this thread, but as yet not had time to raise the issue

[Gorbymedia]

Originally posted by CraigF
ive seen this thread, but as yet not had time to raise the issue

Thanks. I can send portions of logs as needed. I can see all the errors in an hour... Just let me know and I'll help as I can.

Here's an edited sample of the nak's relating bans and then working fine etc.

code:
<08/28/06@08:58:32> [yp_tch] yp.shoutcast.com gave error (nak)

<08/28/06@08:58:32> [yp_tch] yp.shoutcast.com gave extended error (Your server has been permanently banned for providing falsified information.)

<08/28/06@09:03:32> [yp_add] yp.shoutcast.com gave error (nak)

<08/28/06@09:03:32> [yp_add] yp.shoutcast.com gave extended error (This network has been permanently banned due to a previous violation of the SHOUTcast directory terms of service.)

<08/28/06@09:08:33> [dest: 207.200.98.2] starting stream (UID: 30)[L: 5]{A: SHOUTcast Directory Tester}(P: 4)

<08/28/06@09:08:46> [yp_add] yp.shoutcast.com added me successfully

<08/28/06@09:08:48> [dest: 207.200.98.2] connection closed (16 seconds) (UID: 30)[L: 4]{Bytes: 311296}(P: 4)

<08/28/06@09:15:46> [yp_tch] new backup server 66.90.101.184:7075

<08/28/06@09:15:46> [yp_tch] yp.shoutcast.com touched!



<08/31/06@10:32:46> [yp_tch] new backup server 66.90.101.184:7075

<08/31/06@10:32:46> [yp_tch] yp.shoutcast.com touched!

<08/31/06@10:39:48> [yp_tch] new backup server 208.53.131.66:7200

<08/31/06@10:39:48> [yp_tch] yp.shoutcast.com touched!

<08/31/06@10:46:49> [yp_tch] new backup server 66.90.101.184:7075

<08/31/06@10:46:49> [yp_tch] yp.shoutcast.com touched!

<08/31/06@10:53:50> [yp_tch] yp.shoutcast.com gave error (nak)

<08/31/06@10:53:50> [yp_tch] yp.shoutcast.com gave extended error (Your server has been permanently banned for providing falsified information.)

<08/31/06@10:59:06> [yp_add] yp.shoutcast.com added me successfully

<08/31/06@11:06:07> [yp_tch] new backup server 208.53.131.66:7200

<08/31/06@11:06:07> [yp_tch] yp.shoutcast.com touched!

<08/31/06@11:13:08> [yp_tch] yp.shoutcast.com touched!

The server in question is 66.90.101.184:7200, although I get the issues on port 7065 and 7069 as well.

[drlovejones]

very sorry please help get the station up in the directory and to get my web site attached to and to get a link for shoutcast, again i am very sorry , i did not mean to make a problem, ok thank you very much

[destroyerdotnet]

hmm yeah definitely an intermittent sort of thing, last night 2 servers were acting this way, today theyre acting normal. noticed that the yp appears stuck now as well. id post logs but theyre nearly identical to the one above.

*and sorry craigF at posting a new thread, when i searched last night my keywords didnt get this thread.

[CraigF]

no need to apologise, we're here to keep things in order

[dotme]

bump

[jant77]

When I open http://yp.shoutcast.com/addsrv in browser, which is the actual "touch URL", sometimes I see this error:

Unable to connect to Shoutcast DB server
MySQL Error: 1129 Host 'scweb-ntc0s-2.shoutcast.com' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'
Session halted.

:-)

[Gorbymedia]

I'm getting Invalid ID errors from the 98.2 yp server.

Hey ho

[DDock3287]

Well the odd thing for me is that I am getting the errors like everyone else, but I am not getting banned... Today, I have not seen it stop doing it for me. My server is 74.132.207.254:8275. Im guessing this is normal (well not really) but just want to make sure. Here is a bit of the log:

<09/03/06@15:39:10> [yp_tch] yp.shoutcast.com gave error (nak)
<09/03/06@15:39:10> [yp_tch] yp.shoutcast.com gave extended error (100)
<09/03/06@15:44:11> [yp_add] yp.shoutcast.com added me successfully
<09/03/06@16:44:10> [yp_tch] yp.shoutcast.com gave error (nak)
<09/03/06@16:44:10> [yp_tch] yp.shoutcast.com gave extended error (100)
<09/03/06@16:49:11> [yp_add] yp.shoutcast.com added me successfully
<09/03/06@17:49:10> [yp_tch] yp.shoutcast.com gave error (nak)
<09/03/06@17:49:10> [yp_tch] yp.shoutcast.com gave extended error (100)
<09/03/06@17:54:11> [yp_add] yp.shoutcast.com added me successfully
<09/03/06@18:14:12> [dest: 192.168.1.1] starting stream (UID: 265)[L: 1]{A: WinampMPEG/5.24}(P: 0)
<09/03/06@18:54:13> [yp_tch] yp.shoutcast.com gave error (nak)
<09/03/06@18:54:13> [yp_tch] yp.shoutcast.com gave extended error (100)
<09/03/06@18:59:14> [yp_add] yp.shoutcast.com added me successfully
<09/03/06@19:59:13> [yp_tch] yp.shoutcast.com gave error (nak)
<09/03/06@19:59:13> [yp_tch] yp.shoutcast.com gave extended error (100)
<09/03/06@20:04:14> [yp_add] yp.shoutcast.com added me successfully

[dotme]

Yep - classic symptom. 60 minute touches. With the long weekend, I wouldn't expect this to get addressed soon - unless there are automated cleanup routines that run every now and then.

[CraigF]

dotme, there are. but they arent (or werent?) running often enough. streamops are aware of the issue, but as you've said, its a long weekend.

[dotme]

Thanks Craig. Let's hope today's the day... Things look really screwed up this morning, in part due to MySQL "Too many connection" errors from the YP.

[CraigF]

aye, ill chase it when i get home from work.

[dotme]

Originally posted by MegaRock
Cough.

(bump)

Given how many stations are completely missing, or showing with broken clusters on the YP this morning, I'm giving this another bump to hopefully reduce the number of new threads on this topic today.

[serenidad]

Gee, lets hope things get back to normal, this really affects the stability and interest of the audience with so many cuts.

[CraigF]

The fault has been raised, but it would appear its not the same issue as before and seems to be a general mysql issue.

I'm sure it will be dealt with as fast as it can be.

[dotme]

Thanks for the update Craig

I also filed a report yesterday of servers that actually dump current listeners (closing about 20% of active connections from players) on a failed YP touch. I've had this behavior confirmed by some stream hosts who are seeing the same thing on their servers. I hope that report also arrived safely. I'm guessing it's a DNAS bug, exposed by the recent YP errors.

/Edit - and the YP is looking better right now! Clusters are reappearing! Yes!!

[dotme]

Just when I was starting to see listener counts climb...

<09/06/06@10:12:36> [yp_tch] yp.shoutcast.com gave error (nak)
<09/06/06@10:12:36> [yp_tch] yp.shoutcast.com gave extended error (Your server has been permanently banned for providing falsified information.)
<09/06/06@10:17:38> [yp_add] yp.shoutcast.com gave error (nak)
<09/06/06@10:17:38> [yp_add] yp.shoutcast.com gave extended error (This network has been permanently banned due to a previous violation of the SHOUTcast directory terms of service.)

lmao. That's just friggin' great. The cherry on the cake of my day.

Only one server in the whole cluster is doing this, but it happens to be the one I sent listeners to when launching. If it's not one thing, it's another.

[CraigF]

Yes, I saw your email, along with a few other peoples. Just to confirm that the issue has been sent to those who can check and identify the dnas fault (I assume this is tag). Hopefully it'll be fixed promptly.

The yp issues are assumed to be fixed at the moment. If you are continuing to get errors, please dont hesitate to punch off another email.

[ramblreb]

Still not as stable as it was, I am still getting errors:

<09/06/06@17:44:03> [yp_tch] yp.shoutcast.com gave error (nak)
<09/06/06@17:44:03> [yp_tch] yp.shoutcast.com gave extended error (100)
<09/06/06@17:49:05> [dest: 207.200.98.2] starting stream (UID: 2)[L: 2]{A: SHOUTcast Directory Tester}(P: 1)
<09/06/06@17:49:17> [dest: 207.200.98.2] connection closed (0 seconds) (UID: 2)[L: 1]{Bytes: 180224}(P: 1)
<09/06/06@17:49:18> [yp_add] yp.shoutcast.com added me successfully
<09/06/06@17:56:18> [yp_tch] yp.shoutcast.com touched!
<09/06/06@18:03:40> [yp_tch] error connecting to yp.shoutcast.com
<09/06/06@18:10:41> [yp_tch] yp.shoutcast.com touched!
<09/06/06@18:18:03> [yp_tch] yp.shoutcast.com gave error ()
<09/06/06@18:25:24> [yp_tch] error connecting to yp.shoutcast.com
<09/06/06@18:32:26> [yp_tch] yp.shoutcast.com touched!
<09/06/06@18:39:28> [yp_tch] yp.shoutcast.com touched!
<09/06/06@18:46:29> [yp_tch] yp.shoutcast.com touched!
<09/06/06@18:53:51> [yp_tch] error connecting to yp.shoutcast.com
<09/06/06@19:00:53> [yp_tch] yp.shoutcast.com touched!
<09/06/06@19:08:17> [yp_tch] error connecting to yp.shoutcast.com

[dotme]

Yes. It's still not right. I've switched a couple of streams to Private to avoid dropping listeners again tomorrow. I sent a report in. All we can do is wait and hope somebody can find the silver bullet tomorrow.

[struckpx]

Hi Craig, you said to "punch off another e-mail." Who do we send the e-mail too? I am still getting the nak error tonight. Not as often, though.

[dotme]

I think it's safe to assume that the powers at Nullsoft know there are still some issues to deal with in the morning. It's so widespread that when it's fixed, it should be fixed for everyone. So I'd just sit tight for now.

[CraigF]

struckpx, I didnt specify the actual address because it wouldnt be productive for people to mass message the address.

As dotme says, the powers that be are aware of the issue and have multiple reports and contacts to chase up in an effort to fix, and hopefully, given a little bit of time, things will be back in order soon.

I'll obviously keep you guys up to date as and when i learn more.

[dotme]

Originally posted by CraigF
...hopefully, given a little bit of time, things will be back in order soon.

Within the past hour, I've seen things returning to normal for the YP touches on all servers. If this latest change holds, then I'm giving a huge thumbs up to Craig and the Dev team. Any station operator who has server clusters is gonna be smiling this morning.

[FS-Randy]

I would like to add that it appears the touch errors also cause corrupted (unparsable) XML stats on a couple of our Linux servers.

[dotme]

The fix lasted 3 hours. Everything is all F-ed up again. And I'm watching helplessly as my 1000-slot servers dump hundreds of listeners in a single second after a YP touch error. Ouch.

[CraigF]

I guess its going to be an ongoing issue until a new DNAS is released to fix it.

[vboogieman]

sorry about my getting two threads invloved CraigF thx for directing to which I should post...

I saw the issue all night last night and I'm trying to arrange my servers so the bulk of my listeners goes to a private server. Although this will considerably lower me in the genre specific listings that I usually rank high in.

I'm gonna cross my fingers and hope we get a fix soon.

Thx for all teh great respononses to my posts an emails. I've gotten someone from aol/nullsoft answering my emails now and they are reproducing and working on this.