[A1xx/200/300/400*] CouchPotato/SickBeard

[astronyu]

(02-26-2012 10:49 PM)Cherek Wrote:  How did you install CP and Sickbeard? By using the packages in the first post, or by installing through CSI?
I'm starting to think you used the latter, and maybe that causes issues (wrong daemon.sh)?

I installed both sickbeard and couchpotato using NMT Community Installer and they both worked without any hiccups except for couchpotato, not UNTIL I update Couchpotato the the latest build.

[jhmiller]

There is something quite not right here, either as Cherek has said or something else.

what are you running it on A1xx,C200 ect.

your not still starting it via putty?

[astronyu]

I'm running it on A210.
Weird enough, I restart my nmt again, and now couchpotato works. Although it takes quite a while to load the whole page this time but now search works!

[jhmiller]

ok, glad you got it working in the end.

[tenshu]

Hi jhmiller,

Can you package CouchPotatoServer?
It is a complete rewrite of CouchPotato which won't be updated anymore.

I'm about to help with it developement, that would be really nice

Big thanks

[jhmiller]

I'm working on it m8, look back a couple of pages.

Its not as simple as CPv1 so its takinga bit of time as i dont want to put something out there that does not work. Until i release somthing here or i say its safe to update to CPv2 DONT

I had problems with updates as git does not want to play ball, i think i may have found a solution for it but needs more testing.

Sorry A1xx owners its not looking to good for you, as far as im aware it will run but will have some issues, but i will try my best to find work arounds for them.

When you say "I'm about to help with it developement" do you mean help with the developement of CPv2? as if you are im sure other here may have some suggestions for you

[Cherek]

I'm not using CP, but it might be interesting to know (especially for A1xx users):
Are there still bugs in CP v1? Or other problems? Since it won't be updated, people might want to know.

[jhmiller]

As far as i know it should be working ok. My main progs run on my C200 and I only tested the install and updating on the A1xx as these are the only things that may cause errors. This is something an A1xx user here could answer better then my self.

I am trying to find work arounds for the A1xx issues, but as my main unit is a C200 I am working on getting a stable release for that first, and on that score I can say I am almost done, this will give me more time to work on the A1xx series.

[Cherek]

Naturally. Your work is very much appreciated, so getting a stable version on the A/C2xx needs to be a priority. As long as CP works, people won't mind to use the older version. Maybe tenshu could address some problems your running into, or get them addressed by Ruud Burger faster.

[jhmiller]

I was thinking the same thing but not sure what he ment in his last line, either going to help with coding CP or would help me with CP, not sure.

The main issue with the A1xx's is the updating, it should run and function as normal but the updates wont work as they have changed the way CPv2 updates If he is a CP coder then maybe he can ask if they can go back to the way CPv1 updates

There was an update for CPv2 and now i'm not getting the wizard page no more, i'll stop testing for the moment as i hope this is a coding issue but if not i have a workaround that skips the wizard part, shame as i liked the big green button

[PrOeSt]

This morning I checked my sickbeard web interface because I was missing some episodes of my favorite serie.

I saw that it reported 95 Errors.. This is what it stated in my log :

Quote:2012-02-27 02:47:52.101731 SEARCHQUEUE-RSS-SEARCH :: DB error: attempt to write a readonly database

after hitting the update button I get the following error message :

Quote:Traceback (most recent call last):
File "/opt/sybhttpd/localhost.drives/SATA_DISK/Apps/sickbeard/cherrypy/_cprequest.py", line 660, in respond
response.body = self.handler()
File "/opt/sybhttpd/localhost.drives/SATA_DISK/Apps/sickbeard/cherrypy/lib/encoding.py", line 193, in __call__
self.body = self.oldhandler(*args, **kwargs)
File "/opt/sybhttpd/localhost.drives/SATA_DISK/Apps/sickbeard/cherrypy/_cpdispatch.py", line 25, in __call__
return self.callable(*self.args, **self.kwargs)
File "/opt/sybhttpd/localhost.drives/SATA_DISK/Apps/sickbeard/sickbeard/webserve.py", line 2131, in update
updated = sickbeard.versionCheckScheduler.action.update() #@UndefinedVariable
File "/opt/sybhttpd/localhost.drives/SATA_DISK/Apps/sickbeard/sickbeard/versionChecker.py", line 101, in update
return self.updater.update()
File "/opt/sybhttpd/localhost.drives/SATA_DISK/Apps/sickbeard/sickbeard/versionChecker.py", line 451, in update
f = open(tar_download_path, 'wb')
IOError: [Errno 30] Read-only file system: '/share/Apps/sickbeard/master'

Can anyone tell me what happend? I understand its trying to write to a readonly database but I didnt change anything on the C-200

[jhmiller]

New one on me. does this happen every time you run sickbeard?

I dont know where '/share/Apps/sickbeard/master' has come from as there should be no file or folder in that position.

You could try deleting everything inside your sickbeard folder except the following

cache (folder)
appinfo.json
cache.db
config.ini
daemon.sh
sickbeard.db
sickbeard.db.v0

and sickbeard will redownload required files.

If that dont help then maybe your database is fooked, if that is the case you can try a firefox addon called sqlite manager to edit your database to try and find what maybe wrong with it.

[Cherek]

Miller, I asked Senaxx on the Dutch forum if it was correct that AutoSub scan the whole drive. But according to him it should be limited to the rootpath directory. It works right (that way) for him.
(http://gathering.tweakers.net/forum/list...7#37763987

[jhmiller]

Like i said, it scanned the path i set and then went on to scan my HD and my network share. If you want i could get a scan log and pm to you to forward on to see if its anything he can resolve?

[Cherek]

Well Senaxx is only doing the GUI as far as I know.
But I could always report it in the Issues page on google-code and the developer also is said to be on another forum.
Looking by the date you tried it, it does seem to be the last version so that can't be it