Project

General

Profile

Bug #222

Sabnzbd 503 Error

Added by Anonymous about 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/28/2009
Due date:
% Done:

0%


Description

When install Sabnzbd it gives off a 503 Error, even on a fresh install of f9 and hda

sabnzbd.png View (105 KB) Anonymous, 05/28/2009 11:48 AM

History

#1 Updated by bsk about 12 years ago

Also get the same thing on a fresh install.

Fedora 10 on i686.

#2 Updated by shu almost 12 years ago

From f9 to f10 getting the same error

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.2.11 (Fedora) Server at sabnzbd.home.com Port 80

This is what my sabnzbd error logs say

[Thu Aug 27 13:05:22 2009] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 192.168.1.10:8080 (hda) failed
[Thu Aug 27 13:05:22 2009] [error] ap_proxy_connect_backend disabling worker for (hda)
[Thu Aug 27 13:05:22 2009] [error] proxy: HTTP: disabled connection for (hda)
[Thu Aug 27 13:05:25 2009] [error] proxy: HTTP: disabled connection for (hda)

#3 Updated by shu almost 12 years ago

access logs giving me

10.8.0.6 - - [27/Aug/2009:13:17:26 -0500] "GET / HTTP/1.1" 503 405 "http://hda/setup?tab=apps" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.13) Gecko/2009073022 Firef$

#4 Updated by shu almost 12 years ago

It think this issues is not related to the app itself but amahi I am getting the same error on subsonic now but with a little change

[Fri Aug 28 10:00:48 2009] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:8085 (localhost) failed
[Fri Aug 28 10:00:48 2009] [error] ap_proxy_connect_backend disabling worker for (localhost)
[Fri Aug 28 10:00:48 2009] [error] proxy: HTTP: disabled connection for (localhost)
[Fri Aug 28 10:00:51 2009] [error] proxy: HTTP: disabled connection for (localhost)

#5 Updated by cpg almost 12 years ago

this means the the server is not running.

the httpd is trying to forward thigns appropriately, but the server is not running.

what happens if you start the server by hand? i.e. as root, type this:

service sabnzbd start

#6 Updated by shu almost 12 years ago

Starting sabnzbd: Error:
Can't write to logfile
[FAILED]
is what i am getting

If I do a chkconfig I see the service running

I try to stop it but it fails

#7 Updated by cpg almost 12 years ago

Can't write to logfile

there you have your big clue.

chkconfig does not check status. it just configures the service to be on or off at startup time.

so, find the log file and that will lead you the salvation.

#8 Updated by cpg almost 12 years ago

look in

/var/spool/sabnzbd/logs/

#9 Updated by shu almost 12 years ago

rw-r--r- 1 apache apache 0 2009-02-24 16:01 sabnzbd.error.log
rw------ 1 root root 4489096 2009-08-28 14:34 sabnzbd.log
rw------ 1 root root 5242808 2009-03-26 12:17 sabnzbd.log.1
rw------ 1 root root 5242670 2009-03-22 15:02 sabnzbd.log.2
rw------ 1 root root 5242776 2009-03-18 22:05 sabnzbd.log.3
rw------ 1 root root 5242798 2009-03-18 17:26 sabnzbd.log.4
rw------ 1 root root 5242845 2009-03-18 17:06 sabnzbd.log.5
rw------ 1 apache apache 69804 2009-08-28 14:34 cherrypy.log

#10 Updated by shu almost 12 years ago

doing a recursive chmod on on the log folder in that dir fixed the issue. sabmzbd loads now

#11 Updated by bigfoot65 over 11 years ago

When updating to version 0.4.12, there is an error upon installing the rpm.

Warning: %post(amahi-sabnzbd-0.4.12-1.noarch) scriptlet failed, exit status 1

If installed with the --noscripts option, it works but displays this error when running from the CLI.

/usr/share/sabnzbd/cherrypy/lib/cptools.py:3: DeprecationWarning: the md5 module is deprecated; use hashlib instead
import md5
/usr/share/sabnzbd/cherrypy/filters/sessionfilter.py:33: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
import sha

There is a test app called sabnzbd 2. If the manual install of the rpm is accomplished as noted in special instructions, it appears to work. However the app must be started manual. Need to resolve the server feature as in version 0.4.6 for F10.

#12 Updated by bigfoot65 over 11 years ago

A new version has been released. This issue has been resolved and this ticket should be closed.

#13 Updated by bigfoot65 over 11 years ago

  • Status changed from New to Closed

Also available in: Atom