failed Traceback: File "sabnzbd\downloader.pyo", line 356

[nzb_leecher]

Becuase my other topic is going about getting 34 to work again, i made a new topic for my sab40 problem.

    *  2008-04-08 22:07:39,953 ERROR [downloader] Connecting [email protected]:119 failed Traceback (most recent call last): File "sabnzbd\downloader.pyo", line 356, in run File "sabnzbd\newswrapper.pyo", line 173, in finish_connect NNTPPermanentError: 502 news.xxx.xx: Access denied to your node - [email protected]
    * 2008-04-08 22:07:39,953 WARNING [downloader] Thread [email protected]:119: connecting failed
    * 2008-04-08 22:07:39,953 ERROR [downloader] Connecting [email protected]:119 failed Traceback (most recent call last): File "sabnzbd\downloader.pyo", line 356, in run File "sabnzbd\newswrapper.pyo", line 173, in finish_connect NNTPPermanentError: 502 news.xxx.xx: Access denied to your node - [email protected]
    * 2008-04-08 22:07:39,953 WARNING [downloader] Thread [email protected]:119: connecting failed
    * 2008-04-08 22:07:39,953 ERROR [downloader] Connecting [email protected]:119 failed Traceback (most recent call last): File "sabnzbd\downloader.pyo", line 356, in run File "sabnzbd\newswrapper.pyo", line 173, in finish_connect NNTPPermanentError: 502 news.xxx.xx: Access denied to your node - [email protected]
    * 2008-04-08 22:07:39,953 WARNING [downloader] Thread [email protected]:119: connecting failed

In the beginning it dloaded normally, the first 5 minutes. I looked at the settings change a few while dloading (clean install to XP dir and plced my old ini file in it)
Then i noticed, it had stopped dloading. I stopped and started sab a few times, but no luck. Some refuse to dload error.
Newsleecher and sab34 dload without problems.

[shypike]

Which news provider?
You set  SSL off (port 119 usually does not support SSL) ?

There's not a second instance of SABnzbd running (on this or another system) and connecting to the server?

[nzb_leecher]

1. There was no other instance running.

2. tweakdsl.nl

3. i never set ssl on, but what i did change was in the settings menu, looking at my server page. Saw the options for ssl on-of. it was off and i let it off. But saved that page too see, what it would enter in the ini file.
I wonder or that was the cause of this problem.


ps i use __version__ = 016 ini file

[shypike]

So it works now correctly?

I'll check what the behavior is when no SSL field is defined in the INI file.
Maybe we default to on (that would be a really silly mistake).

[nzb_leecher]

So it works now correctly?

I'll check what the behavior is when no SSL field is defined in the INI file.
Maybe we default to on (that would be a really silly mistake).

Unfortanaly no, had to go back to 34. There was no way to get it dloading again. I tried to look up the ini file, but it seemed i deleted the whole 40 dir to try to get  34 running again.

[DeXeS]

what if you install sab 0.4 without any user settings and set it up with your usenet provider. Does that work?

[shypike]

I'll check what the behavior is when no SSL field is defined in the INI file.
Maybe we default to on (that would be a really silly mistake).

Checked, a missing SSL statement in the INI file is handled properly.

[nzb_leecher]

what if you install sab 0.4 without any user settings and set it up with your usenet provider. Does that work?

Man i just spend 2 days to get sab34 to work again and you ask me to try again, do i look like a masogist 

Maybe i try again with the next beta 

[shypike]

Just make sure that you do not mix the 0.3.4 and 0.4.x setup.

It does say this in the README.txt:

===>> THIS IS Beta SOFTWARE, DO NOT OVERWRITE OLDER RELEASES  <<===

OK, maybe we should have told you not to use the admin data either.

[nzb_leecher]

Dont worry i dont mind, if i was afraid i didnt try it. But i could not resist :-)

The funny thing however that i am 99% sure that i didnt mix things, i only took the ini file from sab34, and did the old dir rename trick. cant explain why it happened.
Maybe i try again depends on how soon a new beta is expected? if its out in 2 days ill wait, if in 2 weeks i willtry the "old" beta2

[shypike]

Definitely not in 2 days.

[nzb_leecher]

Ok i tried everything again and within 5 minutes i killed sab40 beyond repair  , its not only dead in the water.  There is also no way to get it starting again, no restart will help. Like it remember it was damaged and after a restart it went directly i fault mode

Nzb_leecher strikes again 

What i did was exactly the same as before, checked ini file, it looked good. Made a backup of sab34.
Closed sab34 and firefox
Then copied sab40 to my sab34 dir overwriting everything.
Started sab40, added some nzb's, looked at the ini again, still looked ok, ssl was 0
Then changes some parameters in the config menu, seemed to work dloading went ok.

Then i looked at the server page, changed nothing but clicked on save server 1 and save server2 (backup server)
It took 10 secs to compete
After that dload speed went quickly to 0 kps.
And from then its completly dead, there is no way to get it to work again.

This seems not like an incident, but a structural problem within sab and imho a showstopper. 

I shall add some errors in the next reply to keep it readable.

[nzb_leecher]

Mostly this kind of stuff

2008-04-10 20:57:49,265::INFO::[downloader] [email protected]:119: Initiating connection
2008-04-10 20:57:49,265::INFO::[downloader] [email protected]:119: Initiating connection
2008-04-10 20:57:49,265::INFO::[downloader] [email protected]:119: Initiating connection
2008-04-10 20:57:51,233::INFO::SABnzbd shutting down...
2008-04-10 20:57:51,233::INFO::[sabnzbd.misc] URLGrabber shutting down
2008-04-10 20:57:51,233::INFO::[sabnzbd.misc] Dirscanner shutting down
2008-04-10 20:58:09,078::ERROR::[downloader] Connecting [email protected]:119 failed
Traceback (most recent call last):
  File "sabnzbd\downloader.pyo", line 356, in run
  File "sabnzbd\newswrapper.pyo", line 173, in finish_connect
NNTPPermanentError: 502 news.xxx.nl: Access denied to your node - [email protected]
2008-04-10 20:58:09,078::WARNING::[downloader] Thread [email protected]:119: connecting failed
2008-04-10 20:58:09,078::ERROR::[downloader] Connecting [email protected]:119 failed

[nzb_leecher]

And like expected sab34 doesnt work 100% anymore too(see my other topic).

I copied the old sab dir back but this time in an other directory sabnzbd34 instead of sabnzbd. Because all the dirs are ./backup, ./nzb, etc it would not be a problem.

But it start, i dont see an interface only the above border withs plush name. But no queue and no history anymore.
But nzbstatus says it is dloading, so it works but somehow the interface is now broken. Not a big issue however.

[shypike]

Cleaning the browser cache might be the solution.