Re: port issue I think [SuSE] - SOLVED

[JeepNut]

yes the word Start then nothing more until I hit ^C.

[sander]

yes the word Start then nothing more until I hit ^C.

So that does work.

Then I'm out of ideas.

[JeepNut]

I do very much appreciate the help.
So at this point I'll try an full reinstallation with the pkg parked on my /home/user path and will follow up with the results.
Where ever you are in this round world, have an excellent day!

[JeepNut]

I've still not been successful running SABnzbd so I wanted to document all steps of the installation process on an openSuSE 13.2 system.
My installation overview with comments with pkgs available on the 13.2 repositories:

• Python 2.7.8-1.1 believed to meet install requirement
  Python-Cheetah 2.4.4-9.1.4 believed to meet install requirement
  Python-CherryPy 3.3.0-2.1.4 MAY NOT meet install requirement for CherryPy

The SABnzbd Install txt says: Embedded modules (only use the included version) CherryPy-3.2 rev2138 with patches http://www.cherrypy.org
I've not found any such version available although there are several 3.2 releases. New version is 3.6 but not sure that will work...
So the question is do I need to install something different that what I have installed with Python-CherryPy from the openSuSE repos?

• par2 0.4-8.1 SuSE 13.2 repos contain no par2cmdline file but the par file installed from repos...

Concerned that the routine specifically requires the par2cmdline file I downloaded and extracted par2cmdline-0.4.tar.gz to the /home/user/par2cmdline-0.4 path.
Then navigated to that path and ran ./configure:

Code: Select all

user@MyPC:~/par2cmdline-0.4> ./configure
configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for g++... g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU                                                                                  
checking dependency style of g++... gcc3                                                                                           
checking for a BSD-compatible install... /usr/bin/install -c                                                                       
checking for gcc... gcc                                                                                                            
checking whether we are using the GNU C compiler... yes                                                                            
checking whether gcc accepts -g... yes                                                                                             
checking for gcc option to accept ANSI C... none needed                                                                            
checking dependency style of gcc... gcc3
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for ANSI C header files... (cached) yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking endian.h usability... yes
checking endian.h presence... yes
checking for endian.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking for size_t... yes
checking whether byte ordering is bigendian... no
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for _LARGE_FILES value needed for large files... no
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for fseeko... yes
checking for working memcmp... yes
checking for stricmp... no
checking for strcasecmp... yes
checking for strchr... yes
checking for memcpy... yes
checking for getopt... yes
checking for getopt_long... yes
configure: creating ./config.status
config.status: creating stamp-h
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
user@MyPC:~/par2cmdline-0.4> 

Looks like it came out pretty clean with a couple of exceptions. Not sure if those are show stoppers or not.
Will need advice whether there is an issue there.

• Optional Modules:
  UnRar 5.1.7-2.1.2 believed to meet install requirement.
  UnZip 6.00-26.1.2 believed to meet install requirement.
  Python-pyOpenSSL 0.13.1-9.1.4 believed to meet install requirement.
  openSSL 1.0.1j-2.10.1 believed to meet install requirement.
  Yenc 0.3 believed to meet install requirement. d/l from: http://sabnzbd.sourceforge.net/yenc-0.3.tar.gz

I noticed the line in the install.txt that says: “Make sure the OpenSSL libraries match with PyOpenSSL”
Match? Match in what way? Surely it doesn't mean the same version numbers on both of those pkgs. I suspect to get both pkgs with the same version # is near impossible.. so I'm confused there. My libraries show this:

• libopenssl1_0_0 1.0.1j-2.10.1
  libopenssl1_0_0-32bit 1.0.1j-2.10.1
  openssl 1.0.1j-2.10.1
  python-pyOpenSSL 0.13.1-9.1.4

Are those OK?
If I can confirm that the little hiccups in the install process are irrelvant to the issue of SABnzbd not being able to start up then I can begin to look elsewhere for those issues.
Thanks!

[JeepNut]

All the installation appears to be fine. I have now been succesful starting.
Someone on the openSuSE forum did finally reply. It seems it's just a matter of how you say it....
This works:

Code: Select all

user@MYPc:~/SABnzbd-0.7.20> python SABnzbd.py --server 127.0.0.1:8080

This doesn't:

Code: Select all

user@MyPc:~/SABnzbd-0.7.20> python SABnzbd.py --server localhost:8080

A quirk of openSuSE I suppose. But good to pass along...
Thanks again for the great support provided on this forum!