i haven't changed to CP pbi for months. This is caused by issues in CPs update mechanism. someone should share logs with the CP dev on github.Hi Joshua,
Did you change anything when it comes to autoupdating couchpotato then?
I've got the same issue as ratzofftoya and I have kind of a fresh CP plugin-jail install (a couple of months old).
Is there anything we could check?
service couchpotato onestop rm -r /usr/pbi/couchpotato-amd64/share/couchpotato/CouchPotatoServer/ fetch --no-verify-peer https://github.com/RuudBurger/CouchPotatoServer/archive/master.zip unzip master.zip mv CouchPotatoServer-master/ /usr/pbi/couchpotato-amd64/share/couchpotato/CouchPotatoServer chown -R media:media /usr/pbi/couchpotato-amd64/share/couchpotato/CouchPotatoServer rm -r master.zip service couchpotato start
If they are gamestopper bugs in mylar the dev really should push those to the 'master' branchI'm a semi-noob when it comes to freenas jail command lines, and I have a question about the mylar plugin.
I'm trying to get over to the development branch after updating the freenas plugin to the most recent version. I have noticed a lack of updates on the mylar master branch, and I've run into a hiccup where the post processing script ends up getting stuck. The recommendation from the mylar dev was to use a couple of git commands to switch over to the dev version. I have no idea where to find git within the freenas jail though, and I'm wondering if anyone here knows what to do to make that happen. I imagine there's some sort of caveat since it's within freenas though.
I would appreciate any help on the issue.
Thanks
service mylar onestop pkg install git rm -r /usr/pbi/mylar-amd64/share/mylar/mylar git clone git://github.com/evilhero/mylar.git /usr/pbi/mylar-amd64/share/mylar/mylar git --git-dir=/usr/pbi/mylar-amd64/share/mylar/mylar/.git --work-tree=/usr/pbi/mylar-amd64/share/mylar/mylar checkout development chown -R media:media /usr/pbi/mylar-amd64/share/mylar/mylar service mylar start
If they are gamestopper bugs in mylar the dev really should push those to the 'master' branch
The freenas plugin doesn't use run mylar using git, but instead uses the source method.
Follow these steps to convert an existing mylar plugin install to use git and checkout the 'development' branch
Code:service mylar onestop pkg install git rm -r /usr/pbi/mylar-amd64/share/mylar/mylar git clone git://github.com/evilhero/mylar.git /usr/pbi/mylar-amd64/share/mylar/mylar git --git-dir=/usr/pbi/mylar-amd64/share/mylar/mylar/.git --work-tree=/usr/pbi/mylar-amd64/share/mylar/mylar checkout development chown -R media:media /usr/pbi/mylar-amd64/share/mylar/mylar service mylar start
awesome!Thanks a bunch for the help. Worked like a charm and it seems to be a bit snappier now.
rm -r /usr/pbi/couchpotato-amd64/share/couchpotato/CouchPotatoServer/ fetch --no-verify-peer https://github.com/RuudBurger/CouchPotatoServer/archive/master.zip unzip master.zip mv CouchPotatoServer-master/ /usr/pbi/couchpotato-amd64/share/couchpotato/CouchPotatoServer chown -R media:media /usr/pbi/couchpotato-amd64/share/couchpotato/CouchPotatoServer rm -r master.zip
# Cleanup leftover from last time if os.path.isdir(extracted_path): self.removeDir(extracted_path) os.umask(0002) self.makeDir(extracted_path) os.chmod(extracted_path,0o777)
As for CP needing an update after the manual source refrshing steps. That's because it doesn't know what version it's on anymore. It will do an 'update' which mean it will grab the latest version of CP from the repo, and write the version to a text file.What's really funny is that I ran the following (I did the stop and the start of the plugin via the FreeNas gui)
Code:rm -r /usr/pbi/couchpotato-amd64/share/couchpotato/CouchPotatoServer/ fetch --no-verify-peer https://github.com/RuudBurger/CouchPotatoServer/archive/master.zip unzip master.zip mv CouchPotatoServer-master/ /usr/pbi/couchpotato-amd64/share/couchpotato/CouchPotatoServer chown -R media:media /usr/pbi/couchpotato-amd64/share/couchpotato/CouchPotatoServer rm -r master.zip
... And CP is still telling me that I need to update.
It's a umask issue within the jail
I've changed a few lines in the main.py code of CP to get this straightened out
Look for the cleanup section. I've added the umask and the chmod line (overkill, I know).
Code:# Cleanup leftover from last time if os.path.isdir(extracted_path): self.removeDir(extracted_path) os.umask(0002) self.makeDir(extracted_path) os.chmod(extracted_path,0o777)
So root cause: python's mkDir results in folder creation with weird permissions.
How do I change the default umask setting for a jail?
Howcome this seems to be a problem for me/us and not for the majority of people?
you don't need to update, the update just fixed some issues with HTTPS that not everyone would experience.I've got a bunch of 9.3 / 9.3.1 plugins installed and I see there are updates for them
two questions
1) do I need to update at all
2) can I safely update without losing my settings for everything?
Thanks!
this plugin uses its own isolated version of python. May try this as the first command..Hey Josh,
There seem to be some issues going on with Mylar at the moment.
The dev is trying to work it out, but he has asked me to find out what version of OpenSSL I am running. He's given me this code, but it I guess it is Linux rather than FreeBSD. Any idea how I can find out?
python -c 'import ssl; print(ssl.OPENSSL_VERSION)'
/usr/pbi/mylar-amd64/bin/python2.7
this plugin uses its own isolated version of python. May try this as the first command..
Code:/usr/pbi/mylar-amd64/bin/python2.7
Yup, I'll need to recompile the plugin with the newer version of openssl and upload it to the repo. Then tomorrow you can try upgrading mylar in the Plugins > Installed tabOkay, so the Python package with Mylar uses OpenSSL 0.9.8za-freebsd 5 Jun 2014
The Dev has told me it will need an update to 1.0.1 to get it working again
Is that something that can be done?
Lol, hopefully we can get this fixed up.Thanks Josh.
For the first time I believe this may be an issue I've had with Mylar that wasn't completely down to my stupidity :D