Sabnzbd Quits upon Launch (OS X Yosemite 10.10)

[shypike]

That what it should look like.
Please install release 0.8.0Beta1.
See Announcements.

[archigeek]

That what it should look like.
Please install release 0.8.0Beta1.
See Announcements.

I've installed from SABnzbd-0.8.0Beta1-osx-EL_CAPITAN.dmg

Still cannot launch it. I see the menu bar icon (arrow) show up for half a second and it goes away with no error messages.

[shypike]

Still, the only solution is to start it from Terminal, like I showed before.

[archigeek]

Still, the only solution is to start it from Terminal, like I showed before.

I still get the same error message after I installed the beta1 for el cap:

-bash: /Applications/SABnzbd.app/Content/MacOS/SABnzbd: No such file or directory

[shypike]

Oh dear, so easy to read over this.
You must use:

Code: Select all

/Applications/SABnzbd.app/Contents/MacOS/SABnzbd --console --server 127.0.0.1:8080

Note the "s" at the end of "Contents"!

[archigeek]

Oh dear, so easy to read over this.
You must use:

Code: Select all

/Applications/SABnzbd.app/Contents/MacOS/SABnzbd --console --server 127.0.0.1:8080

Note the "s" at the end of "Contents"!

Ah! Yes, that launched finally.

Thanks.

However, now I can only get to it by 0.0.0.0:8080/sabnzbd/

I used to be able to also use my domain something.com:8080 but that no longer works. Why?

[shypike]

External (so via domain) only works if you told your router to do port-forwarding.
127.0.0.1 means only access within the computer.
0.0.0.0 tells SABnzbd to listen to "all available IP addresses".
SABnzbd will then listen to both 127.0.0.1 and the LAN network address (something like 192.168.1.4).
0.0.0.0 is not an actual IP address.
When you want to access through the domain name, your router should forward incoming calls to port 8080
to the LAN IP address of your computer.

[archigeek]

External (so via domain) only works if you told your router to do port-forwarding.
127.0.0.1 means only access within the computer.
0.0.0.0 tells SABnzbd to listen to "all available IP addresses".
SABnzbd will then listen to both 127.0.0.1 and the LAN network address (something like 192.168.1.4).
0.0.0.0 is not an actual IP address.
When you want to access through the domain name, your router should forward incoming calls to port 8080
to the LAN IP address of your computer.

I understand how that works. the domain name used to work prior to updating to El Capitan. This El Capitan upgrade has broken all sorts of things that I don't know how to fix.

My computer is on a DMZ zone, so all the ports are forwarded to it.

[shypike]

Try release 0.8.0Beta1, at least that got some testing on El Capitan.
Although, not tested for external accessibility.
(See Announcements).

[Lars1]

Try release 0.8.0Beta1, at least that got some testing on El Capitan.
Although, not tested for external accessibility.
(See Announcements).

Any news on this?
Neither 7.xxx nor 8.xxx seems to work properly in El Capitan - without only listening on 127.0.0.1. External reachability is kind of essential...

[shypike]

Find out the actual IP address of your system and use that instead of 127.0.0.1
Make sure the IP stays the same.
That's all I can say for now.
So far I haven't seen problems with El Capitan (except that Apple changed signing of apps again).
You already disabled IPv6 stuff?
Config->Special->no_ipv6 should be ON

[deifi]

HI at all,

just to add some more Key-Words to the search engine, here are my experiences:

SABnzb won't start after upgrading to 10.11.3 (El Capitan).
So I startet as sudo from Terminal

Code: Select all

sudo /Applications/SABnzbd.app/Contents/MacOS/SABnzbd start &

That worked, almost always...

So I startet with --console and see what I found:

Code: Select all

devils-mini:~ me$ /Applications/SABnzbd.app/Contents/MacOS/SABnzbd --console
Error:
Can't write to logfile
[22/Feb/2016:22:36:15] ENGINE Bus STOPPING
INFO:cherrypy.error:[22/Feb/2016:22:36:15] ENGINE Bus STOPPING
[22/Feb/2016:22:36:15] ENGINE HTTP Server None already shut down
INFO:cherrypy.error:[22/Feb/2016:22:36:15] ENGINE HTTP Server None already shut down
[22/Feb/2016:22:36:15] ENGINE No thread running for Autoreloader.
INFO:cherrypy.error:[22/Feb/2016:22:36:15] ENGINE No thread running for Autoreloader.
[22/Feb/2016:22:36:15] ENGINE No thread running for _TimeoutMonitor.
INFO:cherrypy.error:[22/Feb/2016:22:36:15] ENGINE No thread running for _TimeoutMonitor.
[22/Feb/2016:22:36:15] ENGINE Bus STOPPED
INFO:cherrypy.error:[22/Feb/2016:22:36:15] ENGINE Bus STOPPED
[22/Feb/2016:22:36:15] ENGINE Bus EXITING
INFO:cherrypy.error:[22/Feb/2016:22:36:15] ENGINE Bus EXITING
[22/Feb/2016:22:36:15] ENGINE Bus EXITED
INFO:cherrypy.error:[22/Feb/2016:22:36:15] ENGINE Bus EXITED

I fixed the Issue by editing the config file:

Code: Select all

devils-mini:~ me$ vim /Users/me/Library/Application\ Support/SABnzbd/sabnzbd.ini

And there I changed from:

Code: Select all

log_dir = logs

to

Code: Select all

log_dir = /Users/me/Documents/

After that SABnzb was even starting from Launchpad.

Greets.

deifi

[shypike]

So, the conclusion is that SABnzbd is not allowed to write to /Users/me/Library/Application\ Support/SABnzbd/logs ?
Can you have a look at that folder's permissions and its current content?

[CloudDweller]

I'm getting he exact same issue in that SAB shuts down almost immediately after it's started. I've tried changing the ports installing the latest 1.0 RC2, but neither have fixed the issue which started as soon as I upgraded my Mac to El Capitain. The only way I've been able to fix it (touch wood) is to set the IP address to 127.0.0.1. If I change it to 0.0.0.0 then the issue returns.

I can sometimes get SAB to run with 0.0.0.0 but more often than not, it shuts down. Using 127.0.0.1 is the only way so far to get SAB to run reliably. The problem is I'm now forced to access SAB from my Mac so I've lost the ability to access from a remote system which is a bug shame. Any help or suggestions are greatly appreciated

[shypike]

Try starting SABnzbd once from a Terminal, like this:
/Applications/SABnzbd.app/Contents/MacOS/SABnzbd --no_ipv6
Then stop SABnzbd using the top menu icon.
After that it will no longer try to bind to IPv6 addresses.
It may be that OSX's IPv6 support is making a nuisance of itself.