SABnzbd Forums

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.

I now put sab34 back because i dont know how to get it to work.

I only have small problem now, my sab 34 doesnt show a queue aND HISTORY ANYMORE after putting it back. Will try a reboot later. Hopefully that helps, does sab40 write to the registry?


    *  2008-04-08 22:07:39,953 ERROR [downloader] Connecting 1@news.xxx.xx: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 - info@xxx.xx
    * 2008-04-08 22:07:39,953 WARNING [downloader] Thread 1@news.xxx.xx:119: connecting failed
    * 2008-04-08 22:07:39,953 ERROR [downloader] Connecting 2@news.xxx.xx: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 - info@xxx.xx
    * 2008-04-08 22:07:39,953 WARNING [downloader] Thread 2@news.xxx.xx:119: connecting failed
    * 2008-04-08 22:07:39,953 ERROR [downloader] Connecting 3@news.xxx.xx: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 - info@xxx.xx
    * 2008-04-08 22:07:39,953 WARNING [downloader] Thread 3@news.xxx.xx:119: connecting failed

reboot didnt work, i use nzbstatus now too see if i dload. I lost my windows queue/hist.

I see only sabnzbplush     +NZB   Options   Config  Help.

Only config seems to work. Teh only thing i remember i did was copying my old SAB34 to a other map
Install SAb40 and put old ini in it.
after problems stopped sa40, renamed sab dir
copy old sab34 dir back 

No clue what happened here, should be possible in theorie at least.

This solution didnt work either.
------------For most cases it is perfectly safe to move back versions, there are just three things to keep in mind:

    * Clear out your queue
    * If you use user-scripts: Clear out your history
    * If you set up a scheduling for bandwidth limiting: remove that schedule

That's it!

Q. But I have already moved back and now I can't see my history:
A. Navigate to: http://localhost:8080/sabnzbd/history/purge (change localhost:8080 to the ip and port if you have changed them)

check out this thread for downgrade advice: http://forums.sabnzbd.org/index.php?topic=475.0

It wasn't stickied before, but now is.

The error mentioned is nothing to do with any changes to sabnzbd as far as I am aware.
You mention using the same ini so a user/password problem is unlikely, but enter them in again to double check.

Entered the logon/password again, didnt make difference.


Did everything in the sticky didnt work either 
Now i have 2 not working versions. 

For most cases it is perfectly safe to move back versions, there are just three things to keep in mind:

    * Clear out your queue
    * If you use user-scripts: Clear out your history
    * If you set up a scheduling for bandwidth limiting: remove that schedule

That's it!

Q. But I have already moved back and now I can't see my history:
A. Navigate to: http://localhost:8080/sabnzbd/history/purge (change localhost:8080 to the ip and port if you have changed them)

Q. But I have already moved back and now I can't see my queue:
A. Navigate to: http://localhost:8080/sabnzbd/queue/purge (change localhost:8080 to the ip and port if you have changed them)

Q. But I can't do either! Help!:
A. Launch sabnzbd with the command line -c this will clear the cache folder.

Tried something else, extracted the original sab34 and put all the files in my sab dir.
Had a copy of the old ini file copied that too.
Started sab34 again, still no luck

I am beginning to think that the only thing that maybe "could" work is do a rollback. I havent got a clue what to do else.

You may send the INI files to bugs@sabnzbd.org please.
Remember to remove confidential info!

I use the same INI for 0.3.x and 0.4.x. Only the history is incompatible.

shypike wrote: You may send the INI files to bugs@sabnzbd.org please.
Remember to remove confidential info!

I use the same INI for 0.3.x and 0.4.x. Only the history is incompatible.

Thanks but that would be a waste of your time.
The Ini file is ok, did some more testing, all the interfaces work except in the plush interface. Also i tested with a 100% working before backup INI file.

When i open it in internet explorer also the same problem.

Could it be that the ajax part of plush messed some thing up? Or that the other modules saved something to windows itself instead of to their own directories?

Have you tried the "Default" interface or "Smpl" ?
Try clearing the browser cache when switching skin's.
Also don't keep an old Plush tab open while starting SABnzbd with another skin.

shypike wrote: Have you tried the "Default" interface or "Smpl" ?

Like i said, i tried the other interfaces and they worked
If it was a cache problem, then i may not had the same problem when i tried IE, which i normally never use. 

shypike wrote: Also don't keep an old Plush tab open while starting SABnzbd with another skin.

Oh please give me some credit 
I am not beginner entering the computerworld 

nzb_leecher wrote: I am not beginner entering the computerworld 

It would not be the first time that I forgot to close the Plush or Smpl tab, when restarting with Default.
The problem is that Plush and Smpl are active templates that keep querying SABnzbd.

I would say, forget about Plush for now. pairofdimes is busy working on improvements.

shypike wrote:

nzb_leecher wrote: I am not beginner entering the computerworld 

It would not be the first time that I forgot to close the Plush or Smpl tab, when restarting with Default.
The problem is that Plush and Smpl are active templates that keep querying SABnzbd.

I would say, forget about Plush for now. pairofdimes is busy working on improvements.

With this sort of testing i always shutdowns sab and firefox.

I finally got it to work. First i rolled back to 2 days ago. However after logging in to sab, i got a 404 could not connect to server error.  Then i unpacked sab34 for the second time in that dir and then 34 worked again