Page 1 of 2

unable to start cp after db copy

PostPosted: Wed Feb 12, 2014 5:02 pm
by bostoneric
Not sure exactly how I screwed this one up. I copied the couchpotato.db file from an old Nas to new Asustor.
copied it to:
/volume1/.@plugins/AppCentral/couchpotato/config

after copy CP wont start. removed the CP APP, double checked there are no CP dir in APPCentral folder.

reinstalled CP. same problem, CP wont start.

Re: unable to start cp after db copy

PostPosted: Wed Feb 12, 2014 6:42 pm
by clinton.hall
via ssh
Code: Select all
/usr/local/AppCentral/couchpotato/CONTROL/start-stop.sh restart


post the output here.

Re: unable to start cp after db copy

PostPosted: Thu Feb 13, 2014 12:46 pm
by bostoneric
ok logged into my asustor tonight noticed the CP app wasnt installed. guess it just took time to delete.


Can i copy the "wanted" db from another computer to the CP install on my Asustor?

thanks for all the hard work!

Re: unable to start cp after db copy

PostPosted: Fri Feb 14, 2014 5:47 am
by clinton.hall
You can copy the CouchPotato.db, into the data_dir, but you will need to delete any manage movies first/afterwards since the paths won't be valid.

Re: unable to start cp after db copy

PostPosted: Fri Feb 14, 2014 11:41 am
by bostoneric
clinton.hall wrote:You can copy the CouchPotato.db, into the data_dir, but you will need to delete any manage movies first/afterwards since the paths won't be valid.


Can you direct me where the "data_dir" is? I dont see it with the CouchPotato dirs.

/volume1/.@plugins/AppCentral/couchpotato/CouchPotato
or
/usr/local/AppCentral/couchpotato/config

Re: unable to start cp after db copy

PostPosted: Sat Feb 15, 2014 4:35 am
by clinton.hall
/volume1/.@plugins/AppCentral/couchpotato/config
or
/usr/local/AppCentral/couchpotato/config

(These are both the same).

This location can be verified in CouchPotato, settings, about. This page lists the data_dir location.

Re: unable to start cp after db copy

PostPosted: Sat Feb 15, 2014 8:01 am
by bostoneric
data_dir='/usr/local/AppCentral/couchpotato/config

got it thanks. I'll ssh copy the .db file over tonight see what happens.

I'm guessing I should stop/retart cp after copy?

Re: unable to start cp after db copy

PostPosted: Sat Feb 15, 2014 4:02 pm
by bostoneric
ok copied the db file. restarted CP. checked the logs found this.

Code: Select all
02-14 23:57:05 WARNING [ couchpotato.runner] <type 'exceptions.DeprecationWarning'> the sha module is deprecated; use the hashlib module instead /volume1/.@plugins/AppCentral/couchpotato/CouchPotato/libs/xmpp/auth.py line:24
02-14 23:57:05 WARNING [ couchpotato.runner] <type 'exceptions.DeprecationWarning'> the md5 module is deprecated; use hashlib instead /volume1/.@plugins/AppCentral/couchpotato/CouchPotato/libs/xmpp/auth.py line:26

Re: unable to start cp after db copy

PostPosted: Sun Feb 16, 2014 3:04 pm
by bostoneric
also noticed a few of these...

Code: Select all
[otato.core.providers.base] Failed to parsing NzbIndex: Traceback (most recent call last):
  File "/volume1/.@plugins/AppCentral/couchpotato/CouchPotato/couchpotato/core/providers/base.py", line 89, in getRSSData
    data = XMLTree.fromstring(ss(data))
  File "/usr/local/AppCentral/python/lib/python2.7/xml/etree/ElementTree.py", line 1301, in XML
    parser.feed(text)
  File "/usr/local/AppCentral/python/lib/python2.7/xml/etree/ElementTree.py", line 1643, in feed
    self._raiseerror(v)
  File "/usr/local/AppCentral/python/lib/python2.7/xml/etree/ElementTree.py", line 1507, in _raiseerror
    raise err
ParseError: mismatched tag: line 6, column 2

Re: unable to start cp after db copy

PostPosted: Sun Feb 16, 2014 7:20 pm
by clinton.hall
yeah... those warnings are standard (annoying, but standard).

The issues with nzbIndex are related to that site... either unstable, or returning junk... try other providers...