DjElementDC

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 19 total)
  • Author
    Posts
  • in reply to: [ solved ]info on Sickbeard in Geexbox needed #9981

    DjElementDC
    Participant

    Alright!!!. @rudi – you’re awesome. Thanks to you and @tomlohave for all the support.

    I added those two lines as follows – this is the full service file. It works now. Maybe its possible to fix the package so others won’t have to fix manually?

    [Unit]
    Description=NZBGet
    
    [Service]
    ExecStart=/usr/bin/nzbget -D
    ExecStop=/usr/bin/nzbget -Q
    ExecReload=/bin/kill -HUP $MAINPID
    KillMode=process
    Type=forking
    PIDFile= /root/nzbget/nzbget.lock
    
    [Install]
    WantedBy=default.target
    in reply to: [ solved ]info on Sickbeard in Geexbox needed #9980

    DjElementDC
    Participant

    Not sure I understand – sorry, too new at this :/

    Are you suggesting I add that to the service file?

    in reply to: [ solved ]info on Sickbeard in Geexbox needed #9977

    DjElementDC
    Participant

    I’m not sure if this helps any – but those warning messages went away after I loaded the webserver and hit save to the configuration file in the new version (probably overwrote all the instances of deprecated settings).

    No warning messages, but still same result – server doesn’t start with service.

    root@geexbox:/# systemctl enable nzbget
    ln -s '/usr/lib/systemd/system/nzbget.service' '/etc/systemd/system/default.target.wants/nzbget.service'
    root@geexbox:/# systemctl start nzbget
    root@geexbox:/# systemctl status nzbget
    nzbget.service - NZBGet
       Loaded: loaded (/usr/lib/systemd/system/nzbget.service; enabled)
       Active: inactive (dead) since Sun 2015-07-19 17:06:22 UTC; 6s ago
      Process: 16004 ExecStart=/usr/bin/nzbget -D (code=exited, status=0/SUCCESS)
     Main PID: 16004 (code=exited, status=0/SUCCESS)
    in reply to: [ solved ]info on Sickbeard in Geexbox needed #9976

    DjElementDC
    Participant

    Hi @tomlohave – unfortunately the new service doesn’t seem to work and I’m stuck without a server. I tried reverting to my backup version, now that doesn’t work either. The new version (15.0) works fine when I do a nzbget -D command line start but the minute I close that remote ssh session, the server shuts down (the need for the custom service in the first place).

    It seems the service you bundled with the package is this one, right? http://lostsalad.co.za/2012/12/13/raspberry-pi-usenet-downloads-with-nzbget.

    Either way, the bundled one didn’t work as expected – instead I changed it to the following using default.target instead – the way my original one that I backed up did – which now doesn’t work either. So now I’m stuck without an operating server unless I’m connected via ssh 🙁

    Did your service work?

    The only difference in my version that used to work is using default.target.

    Here is a log:

    root@geexbox:/# systemctl enable nzbget
    ln -s '/usr/lib/systemd/system/nzbget.service' '/etc/systemd/system/multi-user.target.wants/nzbget.service'
    root@geexbox:/# systemctl start nzbget
    root@geexbox:/# systemctl status nzbget
    nzbget.service
       Loaded: loaded (/usr/lib/systemd/system/nzbget.service; enabled)
       Active: inactive (dead) since Sun 2015-07-19 16:58:41 UTC; 4s ago
      Process: 15696 ExecStop=/usr/bin/nzbget -Q (code=exited, status=0/SUCCESS)
      Process: 15689 ExecStart=/usr/bin/nzbget -D (code=exited, status=0/SUCCESS)
     Main PID: 15689 (code=exited, status=0/SUCCESS)
    
    Jul 19 16:58:41 geexbox nzbget[15689]: nzbget.conf(1483): Option "ReloadUrlQueue" is obsolete, ignored
    Jul 19 16:58:41 geexbox nzbget[15689]: nzbget.conf(1484): Option "ReloadPostQueue" is obsolete, ignored
    Jul 19 16:58:41 geexbox nzbget[15689]: nzbget.conf(1487): Option "CreateLog" is obsolete, ignored, use "WriteLog" instead
    Jul 19 16:58:41 geexbox nzbget[15689]: nzbget.conf(1488): Option "ResetLog" is obsolete, ignored, use "WriteLog" instead
    Jul 19 16:58:41 geexbox nzbget[15696]: nzbget.conf(1483): Option "ReloadUrlQueue" is obsolete, ignored
    Jul 19 16:58:41 geexbox nzbget[15696]: nzbget.conf(1484): Option "ReloadPostQueue" is obsolete, ignored
    Jul 19 16:58:41 geexbox nzbget[15696]: nzbget.conf(1487): Option "CreateLog" is obsolete, ignored, use "WriteLog" instead
    Jul 19 16:58:41 geexbox nzbget[15696]: nzbget.conf(1488): Option "ResetLog" is obsolete, ignored, use "WriteLog" instead
    Jul 19 16:58:41 geexbox nzbget[15696]: Request sent
    Jul 19 16:58:41 geexbox nzbget[15696]: server returned: Stopping server

    Here are both services (i got same status as above with both multi.user and default.target):

    Installed with opkg (i assume the raspberry pi version you got from that link?)

    [Service]
    # Even if you set up the Daemon User in nzbget.conf, you will still
    # need to set that name here. Otherwise, nzbget will be run as root
    # User=nzbget
    ExecStart=/usr/bin/nzbget -D
    ExecStop=/usr/bin/nzbget -Q
    ExecReload=/bin/kill -HUP $MAINPID
    KillMode=process
    
    [Install]
    WantedBy=multi-user.target
    

    My version that used to work on v.12 (backed up)

    [Unit]
    Description=NZBGet
    
    [Service]
    ExecStart=/usr/bin/nzbget -D
    ExecStop=/usr/bin/nzbget -Q
    ExecReload=/bin/kill -HUP $MAINPID
    KillMode=process
    
    [Install]
    WantedBy=default.target
    in reply to: [ solved ]info on Sickbeard in Geexbox needed #9895

    DjElementDC
    Participant

    Hey @tomlohave

    I used opkg to install NZBGet 15.0 from the link you provided. It installed and loaded fine (some config file errors but after saving settings via web GUI, it loaded without fail).

    One problem – the custom nzbget.service (systemd) I had created no longer functioned properly. My gut is it has to do with the version change so I removed v15.0 and went back to the v12 from the default opkg list and the service is running again fine.

    (See here – this was my solution that allowed the Daemon server to run without having an active SSH terminal open
    http://forum.solid-run.com/viewtopic.php?f=7&t=1443#p18499 )

    Thoughts?

    in reply to: [ solved ]info on Sickbeard in Geexbox needed #9887

    DjElementDC
    Participant

    To be absolutely clear – yes those are the packages and most up to date versions many people want 🙂

    in reply to: [ solved ]info on Sickbeard in Geexbox needed #9886

    DjElementDC
    Participant

    @tomlohave – amazing!! It’s christmas 😉 Thanks so much for these much needed updates.

    Sorry for the basic question – but is this now part of the standard updating process? Is it just the following?

    opkg update
    opkg upgrade

    Is that it? Will I have issues if I’ve already manually over-written the files inside /srv/sickrage and /opt/couchpotato. I can always force reinstall or something.

    Thanks!

    in reply to: [ solved ]info on Sickbeard in Geexbox needed #9881

    DjElementDC
    Participant

    @Peter- I also had those issues. I literally manually downloaded the files from github and I renamed /srv/couchpotato to /srv/couchpotato-backup and then put the zip file in the /srv/ directory and unzipped from SSH and renamed the new folder /srv/couchpotato/

    That worked – it was updated and now auto-updated! I think the installation from opkg allowed it to be a service and get all nice and configured and then I manually updated the core of the program by extracting a fresh zip at /srv/couchpotato

    I thought I’d break my system but it worked!

    @tomlohave– Is there any chance you can update those packages? This would avoid the need to ‘hack’ the update of these packages. The ones I personally have found awesome but have had to hack the updates for are:
    1. NZBGET
    2. SickRage
    3. CouchPotato

    Have seen many threads on the Cubox forum about them – people switching to other distros due to lack of ability to update them.

    Thanks!

    in reply to: [ solved ]info on Sickbeard in Geexbox needed #9800

    DjElementDC
    Participant

    Please ignore. After flashing my SD card with a fresh new copy of geexbox, i’ve reinstalled everything and it miraculously worked. Not sure if it was due to an updated library or what.. Here’s log for any future issues people may have.

    root@geexbox:/opt# opkg install couchpotato
    Installing couchpotato (2.6.0-2) on root.
    Downloading http://download.geexbox.org/snapshots/geexbox-xbmc-imx6-cuboxi/latest/binaries.cuboxi/packages//couchpotato_2.6.0-2_armv7.opk.
    Configuring couchpotato.
    Post install:
      Installing new config for Web server ...
    Done.
    root@geexbox:/opt# systemctl status couchpotato
    couchpotato.service - CouchPotato application instance
       Loaded: loaded (/usr/lib/systemd/system/couchpotato.service; disabled)
       Active: inactive (dead)
    
    root@geexbox:/opt# systemctl enable couchpotato
    ln -s '/usr/lib/systemd/system/couchpotato.service' '/etc/systemd/system/multi-user.target.wants/couchpotato.service'
    root@geexbox:/opt# systemctl status couchpotato
    couchpotato.service - CouchPotato application instance
       Loaded: loaded (/usr/lib/systemd/system/couchpotato.service; enabled)
       Active: inactive (dead)
    
    root@geexbox:/opt# systemctl start couchpotato

    I then loaded up http://my-geexbox-ip:5050/ and it worked!! 🙂

    in reply to: [ solved ]XBMC broken after update #9799

    DjElementDC
    Participant

    Hey everyone

    Please ignore…I got too impatient and just flashed my SD card with a fresh install of geexbox.

    in reply to: [ solved ]XBMC broken after update #9798

    DjElementDC
    Participant

    Sorry for so many messages – just want to give as much info as possible. This is the log of the opkg upgrade I did last night: http://pastebin.com/nfJzmk2L

    in reply to: [ solved ]XBMC broken after update #9797

    DjElementDC
    Participant

    If I simply try to type xbmc at command prompt, I get this:
    root@geexbox:~# xbmc

    sh: glxinfo: not found
    XBMC needs hardware accelerated OpenGL rendering.
    Install an appropriate graphics driver.
    
    Please consult XBMC Wiki for supported hardware
    http://wiki.xbmc.org/?title=Supported_hardware
    
    in reply to: [ solved ]XBMC broken after update #9796

    DjElementDC
    Participant

    Hi all,

    So it seems I”m stuck here – excuse the linux arch noob questions. Please help – the wife isn’t so happy without all her shows 🙂

    A couple days ago I thought it was a good idea to do a opkg upgrade command (… why can’t I remember if it aint broke, don’t fix it!).

    XBMC doesn’t seem to want to start at boot now. Not sure if this was connected cause I honestly can’t recall if I had it loaded after the upgrade.

    I tried doing a opkg –force-reinstall install xbmc and then hard-restarted my cubox but still nothing. Also tried to force downgrade libgcrypt, but not sure i’m doing it right. Here’s a log:

    
    root@geexbox:/etc# opkg --force-reinstall install xbmc
    Downloading http://download.geexbox.org/snapshots/geexbox-xbmc-imx6-cuboxi/latest/binaries.cuboxi/packages//xbmc_gotham-13.2-imx-rbf4eb6de87-1_armv7.opk.
    Reinstalling xbmc (gotham-13.2-imx-rbf4eb6de87-1) on root.
    Configuring xbmc.
    
    [RESTART]
    
    root@geexbox:~# systemctl status xbmc
    xbmc.service - XBMC Media Center
       Loaded: loaded (/usr/lib/systemd/system/xbmc.service; enabled)
       Active: failed (Result: start-limit) since Sun 2015-05-03 19:32:21 BST; 5s ago
      Process: 625 ExecStart=/usr/bin/runxbmc --standalone -fs -l /var/run/lirc/lircd (code=exited, status=1/FAILURE)
     Main PID: 625 (code=exited, status=1/FAILURE)
    
    May 03 19:32:21 geexbox systemd[1]: xbmc.service start request repeated too quickly, refusing to start.
    May 03 19:32:21 geexbox systemd[1]: Failed to start XBMC Media Center.
    May 03 19:32:21 geexbox systemd[1]: Unit xbmc.service entered failed state.
    
    root@geexbox:~# opkg --force-downgrade install libgcrypt
    Package libgcrypt (1.6.2-1) installed in root is up to date.
    
    [RESTART]
    
    
    in reply to: [Cubox-i] Problem with smbd after update #9791

    DjElementDC
    Participant

    I also had a problem with this – took my *ages* to figure out. The /etc/network file is a hidden gem that fixed a lot of services (FTP, telnet, samba, etc..) from starting up after a reinstall or update.

    in reply to: [ solved ]info on Sickbeard in Geexbox needed #9790

    DjElementDC
    Participant

    Hi all –

    Bumping up this old thread. I’ve been able to install nzbget & sickrage (sickbeard) properly and can access them on their respective ports on my cubox via web interface – they’re awesome.

    The Problem: I’ve installed couchpotato (referenced earlier in this thread) successfully. However, it seems that the service is not initializing or loading properly as the web interface does not work.

    I’ve installed it, forced reinstalled it, restarted, etc. Seems like it exits right after it loads. I can see the option when going to http://[my-server-ip]/ – clicking on it gives me http://[my-server-ip]:5050 which I assume is default port for couchpotato install.

    I’m not sure what the command level commands are for couchpotato… its a python script, right? Is there a config file somewhere? Help 🙂 This is the last step to completely automating our cubox.

    See my log below (and be easy on me.. i’m a linux / arch noob):

    root@geexbox:~# systemctl status couchpotato
    couchpotato.service - CouchPotato application instance
       Loaded: loaded (/usr/lib/systemd/system/couchpotato.service; enabled)
       Active: inactive (dead) since Sat 2015-05-02 12:10:24 BST; 1 day 4h ago
      Process: 28950 ExecStart=/bin/python /srv/couchpotato/CouchPotato.py --daemon (code=exited, status=0/SUCCESS)
    
    root@geexbox:~# systemctl restart couchpotato
    root@geexbox:~# systemctl status couchpotato
    couchpotato.service - CouchPotato application instance
       Loaded: loaded (/usr/lib/systemd/system/couchpotato.service; enabled)
       Active: inactive (dead) since Sun 2015-05-03 17:09:06 BST; 2s ago
      Process: 21103 ExecStart=/bin/python /srv/couchpotato/CouchPotato.py --daemon (code=exited, status=0/SUCCESS)
    
    oot@geexbox:~# opkg --force-reinstall install couchpotato
    Downloading http://download.geexbox.org/snapshots/geexbox-xbmc-imx6-cuboxi/latest/binaries.cuboxi/packages//couchpotato_2.6.0-2_armv7.opk.
    Reinstalling couchpotato (2.6.0-2) on root.
    Configuring couchpotato.
    Post install:
      Installing new config for Web server ...
    Done.
    root@geexbox:~# systemctl status couchpotato
    couchpotato.service - CouchPotato application instance
       Loaded: loaded (/usr/lib/systemd/system/couchpotato.service; enabled)
       Active: inactive (dead) since Sun 2015-05-03 17:09:06 BST; 3min 34s ago
      Process: 21103 ExecStart=/bin/python /srv/couchpotato/CouchPotato.py --daemon (code=exited, status=0/SUCCESS)
    
    Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended.
    root@geexbox:~# systemctl daemon-reload
    root@geexbox:~# systemctl status couchpotato
    couchpotato.service - CouchPotato application instance
       Loaded: loaded (/usr/lib/systemd/system/couchpotato.service; enabled)
       Active: inactive (dead) since Sun 2015-05-03 17:09:06 BST; 3min 45s ago
    
Viewing 15 posts - 1 through 15 (of 19 total)