xsusenet flood delay problem

[ZayDar]

Anyone else getting into a flood delay loop with xsusenet?

I'm getting it even with 1 connection.

[Quade]

Flood Delay just means the connection is dropping out quickly. It's a symptom of a connection problem. Besides flood delay messages, what other messages do you see in the logging tab?

[DThor]

Keep in mind if you previously had, say, 20 connections or something huge, the problem could have been number of connections exceeded, and it can take a while for that connection state to clear, so if you quickly slammed the connections down to 1 and restarted Newsbin, that could still be the problem. Might take a few minutes to reset.

DT

[ZayDar]

ERROR NNTPSocket - NNTP Perform Auth - free.xsusenet.com-Password: Username was rejected by Server:281
ERROR NNTPSocket - Socket HandleError - Server: free.xsusenet.com SendCommand - Server Disabled Service on connection:
DEBUG Download Engine xsusenet - NNTP_CloseChunk - closing a dirty connection
HIGH - DG - Connect Flood Delay Active: xsusenet 22 secs Remaining before Reconnect


I've only ever used it as a fill server with 2 connections and after some testing i just noticed it only starts if parts are not available.

[Quade]

NNTP Perform Auth - free.xsusenet.com-Password: Username was rejected by Server:281

Seems pretty clear. XS has a 25 gig a month limit. Wonder if you hit it?

[ZayDar]

Nope, 781mb last month and it's just turned over to 0mb as it's a new month.

It only starts spitting out that error at red chunks requests as unlike other servers like atsraweb that sends a message that it's not available on the server, xsusenet keeps hard rejecting your logins until you request something that is available for download.If you signup to the free xsusenet to try it yourself it's very fast and simple as all they ask for is a username and email address to send the password.

[Plankton]

xsusenet does seem to have some odd ideas on how to run a server as sabnzb have started to add fixes to their software so people can use it as for a free server it has nearly 900 days of retention.

amusingly in their own words.

Problems solved in Beta3:
Add support for the peculiar Usenet provider "free.xsusenet.com".

[nikkil]

Great! I'll try Beta3 in a few days.

[Hoola]

Great! I'll try Beta3 in a few days.

hopefully when Quade notices this thread and updates the situation he will add a fix for newsbin instead as i must say i'm really impressed with xsusenet for it's retention for free but the way it treats your connection if parts are missing is very odd.

[Quade]

Newsbin should just work with XSusenet. That error is coming right from them. For some reason they've decided to invalidate your free password. The question is why. I don't see software changes fixing that. I imagine if the server gets busy, the free users are put on the back burner.

Free limit is 2 connections right? I'd probably run ,1 if you want it to be reliable. It's also possible that sab put a really long connection delay when the connection dies because servers are slow to release connections. The nice thing about having a bunch of connections available, is that the long delay between disconnect and the server freeing up the connection slot is handled through your spare connections.

[Hoola]

Unless you are tired or very busy you seem to be doing selective reading. [ insert smiley ]

As pointed out by zaydar and as i have just found out the server only gives the error for trying to download parts that are not available so it makes absolutely no difference if you run 1 or 2 connections but they don't invalidate your free password permanently only why requesting those parts.When the flood delay loop stops or if you restart newsbin and you get to a part of the download that is available then it carrys on as normal.

[Quade]

As pointed out by zaydar and as i have just found out the server only gives the error for trying to download parts that are not available so it makes absolutely no difference if you run 1 or 2 connections but they don't invalidate your free password permanently only why requesting those parts.When the flood delay loop stops or if you restart newsbin and you get to a part of the download that is available then it carrys on as normal.

Yeah, I wait for someone to explain it to me in small words...

Makes no sense though. Newsbin doesn't disconnect if there's a missing part. Do you know what error they return when there's a missing part? Should be a 430 or 423. It they're returning a 500+ error that tells Newsbin to disconnect. That would probably drive you over the 2 connection limit. Because usenet is old, servers return a bad password error when there are too many connections.

[Hoola]

Exactly as zaydar posted when you get to red parts in the download this turns up in the logs over and over again until you get back to requesting green parts then it works as normal.

ERROR NNTPSocket - NNTP Perform Auth - free.xsusenet.com-Password: Username was rejected by Server:281
ERROR NNTPSocket - Socket HandleError - Server: free.xsusenet.com SendCommand - Server Disabled Service on connection:
DEBUG Download Engine xsusenet - NNTP_CloseChunk - closing a dirty connection
HIGH - DG - Connect Flood Delay Active: xsusenet 22 secs Remaining before Reconnect
21 sec , 20 secs and so on and on

I don't know how anybody can explain it in smaller words unless you try it yourself and see and as zaydar says it does not give the usual error for missing parts as it just chucks you off.

[Quade]

Naw, you're just showing the auth error. If your theory is correct the auth error is just a symptom and not the actual problem.

How it normally works:

1 - You're connected to XS downloading on 2 connections

2 - One of the chunks you're looking for isn't there.

3 - You get a 423 or 430 error.

4 - Newsbin uses the connection for the next block of data

5 - Repeats forever.

What you're describing seems to be:

1 - You're connected to XS downloading on 2 connections

2 - One of the chunks you're looking for isn't there. Something happens here and there's a disconnect.

3 - Newsbin re-connects for the next chunk.

4 - At this point XS still thinks you have 2 connections because that's just how news servers are. They're slow to detect disconnects and give you your connection back.

5 - XS then sends back an auth failure because it thinks you're trying to have more than 2 connections.

6 - Eventually XS notices the disconnect, free's up the connection and you're back to 2 connections again.

Every news server is slow to notice disconnects but, most news server aren't capped at 2 connections so, the unused connections act as a buffer and you don't see any auth errors. So, I'm wondering what's happening at step 2. Why there's a disconnect.

[ZayDar]

Quade if you can't test xsusenet yourself is there anyway i can just log xsusenet seperate from my other servers and is there any extra verbose debug settings for newsbin logging?

[Quade]

You can disable the other servers and just download from XS till this fails. If it's too much hassle don't bother.

Eventually, I'll get an account and try it. I was just hoping for a shortcut. If you tell me it's returning a 500 error for instance instead of 430, that would be a real clue.

I'll see if Dex has an account. I'll make an NZB file, then tweak the message-id's to force a chunk failure.

[ZayDar]

Thankyou

I need to test with more modern files as most of downloads in the queue are dated over 400 days so i'm unsure how xsusenet handles {out of retention} over {missing parts} to see if it gives different logging messages.just a thought unless they should be treated the same by the server?

[Quade]

in the queue are dated over 400 days so i'm unsure how xsusenet handles {out of retention} over {missing parts} to see if it gives different logging messages.just a thought unless they should be treated the same by the server?

Yeah, it's all the same and the server should be returning the same results whether it's missing or out of retention. 430 and 423 errors are the catch all for both states.

[Hoola]

my apologies if i came across with a bad attitude before as it's been a rough day.

[Quade]

Sometimes I need a kick too. I missed the "bad chunk = disconnect". Still skeptical but, willing to test it.

[dexter]

I just recreated it. I think it has something to do with xfeatures failing intermittently. Turn off XFeatures in Server Options for XSUsenet and see if you still have the issue.

[dexter]

Hmm, no, failed again with xfeatures turned off. We have a message in to the xsusenet guys to see if they can help figure it out.

[Quade]

Looks to me like XS returns a 480 error instead of a 430.

[Quade]

Dex talked to them and they might have fixed it. I'm still looking into it.

[ZayDar]

Thankyou Dexter and Quade for verifying the problem and working with them for a fix.

[Hoola]

Thanks from me to. Image link not allowed for unregistered users

It is now working and sending out the correct error 430 with the message that the post isn't on the server.

though a new error has turned up in the logs, LOL

ERROR NNTPSocket - Socket HandleError - Server: free.xsusenet.com SendCommand - Server returned an unexpected response: 403 Remote Server Unavailable
HIGH NNTPSocket - 403 Remote Server Unavailable

Though luckly so far it hasn't caused any flood protection.

[ZayDar]

I can confirm that it is working aswell , thanks guys

though a new error has turned up in the logs, LOL

ERROR NNTPSocket - Socket HandleError - Server: free.xsusenet.com SendCommand - Server returned an unexpected response: 403 Remote Server Unavailable
HIGH NNTPSocket - 403 Remote Server Unavailable

Though luckly so far it hasn't caused any flood protection.

How long ago did you do your testing as i've been downloading the last few hours at 100mb and the log only gives a single 403 remote error way back at the start of the log so it may have been a server glitch that has now cleared unless it happens under certain events but it doesn't seem like it will be a problem even if it does happen from time to time.

[Quade]

I don't know that particular error but, it suggests that a a front end to the actual server can't contact the actual server.

[Hoola]

I've not had anymore 403 remote errors so it must have been a glitch.