Hello,
I am running sabnzbd+ 0.4.11 under OSX Leopard with the smpl skin (but the default skin shows the same issues). A few days ago my Mac showed me, that there is an update to safari 4.0 possible. So I did it. I don't know exactly if my problems started exactly with this safari update, but it feels like it.
The problem is this: I don't get significant downloadspeed since the update. Often there is only a third of the speed availible, but the most time there is no connection to my usenetserver at all. Before it worked great so I am a little worried what to do.
My usenetserver should be ok. Because I tryed to conect and download from it with an windows PC and altbinz and it worked great.
Does anyonoe have an Idea, what this is and what I could do?
Here are the warnings sab shows me:
"2009-06-17 12:53:30,063 WARNING [downloader] Thread [email protected]:563: timed out
2009-06-17 12:53:30,064 WARNING [downloader] Thread [email protected]:563: timed out
2009-06-17 12:53:30,096 ERROR [downloader] Exception?
2009-06-17 12:53:30,105 WARNING [downloader] Thread [email protected]:563: server broke off connection
2009-06-17 12:54:50,072 ERROR [newswrapper] Failed to connect: (60, 'Operation timed out') [email protected]:563
2009-06-17 12:56:44,587 ERROR [newswrapper] Failed to connect: (60, 'Operation timed out') [email protected]:563"
But I can't read anything from it (yes, I'm a noob - sorry!!!). So please, any help?
Can it be that the update to Safari 4.0 crashed sabnzbd+ ?
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Can it be that the update to Safari 4.0 crashed sabnzbd+ ?
Safari itself will not be the cause. The only result could be that the Web-ui doesn't work properly anymore.
In that case installing FireFox would solve the problem.
Maybe more patches were installed along with Safari?
"ERROR [downloader] Exception?" means that internally something went wrong.
Unfortunately our OSX expert is not availble now.
Es an experiment: try using port 119 and no SSL.
In that case installing FireFox would solve the problem.
Maybe more patches were installed along with Safari?
"ERROR [downloader] Exception?" means that internally something went wrong.
Unfortunately our OSX expert is not availble now.
Es an experiment: try using port 119 and no SSL.
- interfacelift
- Jr. Member
- Posts: 75
- Joined: June 19th, 2008, 12:58 am
- Location: Coruscant
Re: Can it be that the update to Safari 4.0 crashed sabnzbd+ ?
I've been running 10.5.7 and Safari 4 (first the beta, now the final) and have had zero issues with SAB.
I think it's something else causing the problem.
I think it's something else causing the problem.
Re: Can it be that the update to Safari 4.0 crashed sabnzbd+ ?
Thanx for the answer. Tryed the firefox and the no SSL Angel. Nothing changed.shypike wrote: Safari itself will not be the cause. The only result could be that the Web-ui doesn't work properly anymore.
In that case installing FireFox would solve the problem.
Maybe more patches were installed along with Safari?
"ERROR [downloader] Exception?" means that internally something went wrong.
Unfortunately our OSX expert is not availble now.
Es an experiment: try using port 119 and no SSL.
I don't know, if other patches where installed, with the safari update...
Hum, any other Idea, what I could possibly try?
I also tryed to reinstall sabnzbd+ - it also changed nothing.
Re: Can it be that the update to Safari 4.0 crashed sabnzbd+ ?
I have no idea.
Unfortunately our OSX porter is not available for some weeks.
If it's a general OSX issue, I'm sure he will fix it. But not right now
Unfortunately our OSX porter is not available for some weeks.
If it's a general OSX issue, I'm sure he will fix it. But not right now
- interfacelift
- Jr. Member
- Posts: 75
- Joined: June 19th, 2008, 12:58 am
- Location: Coruscant
Re: Can it be that the update to Safari 4.0 crashed sabnzbd+ ?
You said you reinstalled SABnzbd. Have you tried removing the invisible folder ~/.sabnzbd where your settings reside?
You can remove it by using the terminal or by using the finder "Go" command to go to "~/.sabnzbd" and removing the sabnzbd.ini, cache and logs folders.
Then launch sabnzbd again, and have it rebuild them. You'll have to set sabnzbd up again from scratch, but that might help.
You can remove it by using the terminal or by using the finder "Go" command to go to "~/.sabnzbd" and removing the sabnzbd.ini, cache and logs folders.
Then launch sabnzbd again, and have it rebuild them. You'll have to set sabnzbd up again from scratch, but that might help.
Re: Can it be that the update to Safari 4.0 crashed sabnzbd+ ?
Thanks for the Idea - it did not workinterfacelift wrote: You said you reinstalled SABnzbd. Have you tried removing the invisible folder ~/.sabnzbd where your settings reside?
You can remove it by using the terminal or by using the finder "Go" command to go to "~/.sabnzbd" and removing the sabnzbd.ini, cache and logs folders.
Then launch sabnzbd again, and have it rebuild them. You'll have to set sabnzbd up again from scratch, but that might help.
I even tryed to switch to an older Version. I removed ~/.sabnzbd again, put the sabnzbd.app (0.4.11) in the trash and installed 0.4.8 which worked before with me pretty good. Again, same result. No change.
The Downloadspeed - if I get a conection - is still pretty low. But most of the time I get no conection to the newsserver, while Internet runs. And If I try to connect via altbinz on my Windowsstation it connects instantly to the newsserver (like sabnzbd before did too).
Any other Idea, what I could change or get a look at?
And is there any other nzb downloader for the mac? I would hate to leave SAB behind, but if does not work proper - what should I do else?
So pleaaaaase HELP!
- interfacelift
- Jr. Member
- Posts: 75
- Joined: June 19th, 2008, 12:58 am
- Location: Coruscant
Re: Can it be that the update to Safari 4.0 crashed sabnzbd+ ?
Is your Leopard firewall on? (Security system preference).
Unison is another Mac usenet reader/downloader. See if you get the same results, which might indicate an issue with the entire machine, not just SABnzbd.
Unison is another Mac usenet reader/downloader. See if you get the same results, which might indicate an issue with the entire machine, not just SABnzbd.
Re: Can it be that the update to Safari 4.0 crashed sabnzbd+ ?
Thanks for the Help!interfacelift wrote: Is your Leopard firewall on? (Security system preference).
Unison is another Mac usenet reader/downloader. See if you get the same results, which might indicate an issue with the entire machine, not just SABnzbd.
No, firewall isn't on.
Tryed Unison and NZB Drop. With the same result as SAB. So, I think it's save to say, it is not SAB which is causing the Problem, but I have to look somewhere in Macworld... Problem is, I'm an absolut newby at OSX. Just bought the Minni Mac as entertainment Center to watch my HD Files... which I get via SAB... (see where the problem lies... ;-) ).
Does someone has an Idea, where I can look in OSX to get SAB work flawless again?
If nobody, maybee I have to install OSX completely new, to get a clean start... Won't love to do so, but what the heck.
- interfacelift
- Jr. Member
- Posts: 75
- Joined: June 19th, 2008, 12:58 am
- Location: Coruscant
Re: Can it be that the update to Safari 4.0 crashed sabnzbd+ ?
If you can, you may want to try another connection type. If you're using wifi, switch to ethernet temporarily. If you're using ethernet, switch to wifi. See if you get any different results.
Re: Can it be that the update to Safari 4.0 crashed sabnzbd+ ?
Hi,
If other softwares give the same result, maybe it's a your ports are filtered by you internet provider.
Try to change your port to 443...
If other softwares give the same result, maybe it's a your ports are filtered by you internet provider.
Try to change your port to 443...