update failed from 0.27.2 to 0.28.2 about motioneye HOT 25 CLOSED

pip install --upgrade motioneye==0.27.2.post2

-> works again but pip install --upgrade motioneye failed again to work
same problem if i try 0.28.1 version or 0.28

thanks

from motioneye.

What is the output of the command pip install --upgrade motioneye?

from motioneye.

Collecting motioneye
Requirement already up-to-date: pycurl in /usr/local/lib/python2.7/dist-packages (from motioneye)
Requirement already up-to-date: tornado>=3.1 in /usr/local/lib/python2.7/dist-packages (from motioneye)
Requirement already up-to-date: pillow in /usr/local/lib/python2.7/dist-packages (from motioneye)
Requirement already up-to-date: jinja2 in /usr/local/lib/python2.7/dist-packages (from motioneye)
Requirement already up-to-date: certifi in /usr/local/lib/python2.7/dist-packages (from tornado>=3.1->motioneye)
Requirement already up-to-date: backports.ssl-match-hostname in /usr/local/lib/python2.7/dist-packages (from tornado>=3.1->motioneye)
Requirement already up-to-date: MarkupSafe in /usr/local/lib/python2.7/dist-packages (from jinja2->motioneye)
Installing collected packages: motioneye
Found existing installation: motioneye 0.27.2
Uninstalling motioneye-0.27.2:
Successfully uninstalled motioneye-0.27.2
Successfully installed motioneye-0.28.2

from motioneye.

Upgrading looks alright. And after upgrading, can you please send me the motioneye.log file? (usually found at /var/log/motioneye.log)?

from motioneye.

here it is : https://dl.dropboxusercontent.com/u/18722948/motioneye2.log

from motioneye.

Wait what? Do you use motionEyeOS? If you do, you must not upgrade your motionEye manually. Instead wait for the next release of motionEyeOS.

from motioneye.

Now you changed the URL of the log file and it appears to be a totally different log file. I'm confused. What computer and what OS are you using? How did you install motionEye?

from motioneye.

sorry, i uploaded first a wrong log (from motioneyeos, i have 2 rpis). I installed motioneye on raspbian using your guide. thanks

from motioneye.

What does cat /usr/lib/python2.7/site-packages/motioneye/__init__.py say? If the file does not exist, what does cat /usr/local/lib/python2.7/site-packages/motioneye/__init__.py say?

from motioneye.

cat /usr/lib/python2.7/site-packages/motioneye/init.py -> file does not exist
cat /usr/local/lib/python2.7/site-packages/motioneye/init.py -> file does not exist

from motioneye.

It's __init__.py, not init.py.

from motioneye.

yes,
/usr/lib/python2.7/site-package does not exist
/usr/local/lib/python2.7/site-packages is empty

from motioneye.

Alright, then you must have /usr/lib/python2.7/dist-packages/motioneye/__init__.py.

from motioneye.

i don't have any motioneye folder on /usr/lib/python2.7/dist-packages
but i have init.py in usr/local/lib/python2.7/dist-packages/motioneye/

cat /usr/local/lib/python2.7/dist-packages/motioneye/init.py :

VERSION = "0.28.2"

i noticed i also have motioneye-0.28.2.dist-info folder in /usr/local/lib/python2.7/dist-packages

from motioneye.

Then everything seems to be fine. By the way have you restarted motionEye after upgrade (/etc/init.d/motioneye restart)?

from motioneye.

No. but here is the result :
sudo /etc/init.d/motioneye restart
[....] Restarting motioneye (via systemctl): motioneye.serviceJob for motioneye.service failed. See 'systemctl status motioneye.service' and 'journalctl -xn' for details.

And : sudo systemctl status motioneye.service
● motioneye.service - LSB: Start the motionEye server
Loaded: loaded (/etc/init.d/motioneye)
Active: failed (Result: exit-code) since mer. 2015-10-21 15:38:42 CEST; 1min 38s ago
Process: 21240 ExecStop=/etc/init.d/motioneye stop (code=exited, status=0/SUCCESS)
Process: 21578 ExecStart=/etc/init.d/motioneye start (code=exited, status=1/FAILURE)

oct. 21 15:38:42 karmapi motioneye[21578]: Starting motionEye server:CRITICAL:root:failed to read settings from "/etc/motioneye/motioneye.con...atic_url
oct. 21 15:38:42 karmapi motioneye[21578]: failed!
oct. 21 15:38:42 karmapi systemd[1]: motioneye.service: control process exited, code=exited status=1
oct. 21 15:38:42 karmapi systemd[1]: Failed to start LSB: Start the motionEye server.
oct. 21 15:38:42 karmapi systemd[1]: Unit motioneye.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

from motioneye.

Well not restarting it was the cause of your issue. Now the problem is that between 0.27 and 0.28 the settings have changed a bit. If you haven't touched your motioneye.conf, please remove it and copy the sample file over (see the install instructions for that).

from motioneye.

And : journalctl -xn
-- Logs begin at lun. 2015-10-19 12:27:01 CEST, end at mer. 2015-10-21 15:42:04 CEST. --
oct. 21 15:42:04 karmapi motioneye[22530]: Starting motionEye server:CRITICAL:root:failed to read settings from "/etc/motioneye/motioneye.conf": unknown
oct. 21 15:42:04 karmapi sudo[22539]: pi : TTY=unknown ; PWD=/media/Data/Sauvegarde/XBMC/kankupicam ; USER=root ; COMMAND=/bin/rm -r /media/Data/Sauvega
oct. 21 15:42:04 karmapi motioneye[22530]: failed!
oct. 21 15:42:04 karmapi systemd[1]: motioneye.service: control process exited, code=exited status=1
oct. 21 15:42:04 karmapi systemd[1]: Failed to start LSB: Start the motionEye server.
-- Subject: L'unité (unit) motioneye.service a échoué
-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- L'unité (unit) motioneye.service a échoué, avec le résultat failed.
oct. 21 15:42:04 karmapi systemd[1]: Unit motioneye.service entered failed state.
oct. 21 15:42:04 karmapi sudo[22521]: pam_unix(sudo:session): session closed for user root
oct. 21 15:42:04 karmapi sudo[22539]: pam_unix(sudo:session): session opened for user root by (uid=0)
oct. 21 15:42:04 karmapi sudo[22539]: pam_unix(sudo:session): session closed for user root
oct. 21 15:42:04 karmapi CRON[22458]: pam_unix(cron:session): session closed for user pi

from motioneye.

failed to read settings from "/etc/motioneye/motioneye.conf": unknown
this file is rw-r--r--

from motioneye.

As I said, use the new sample file that comes with 0.28.2.

from motioneye.

with this command line ?
sudo cp /usr/local/share/motioneye/extra/motioneye.conf.sample /etc/motioneye/motioneye.conf
is that file the 0.28.2 sample ?
thanks

from motioneye.

Yeap :)

from motioneye.

And don't forget to restart it afterwards.

from motioneye.

thanks, it works.
Should i copy this file again for next releases/updates ?

from motioneye.

Normally not, unless you get errors related to the settings after upgrading.

from motioneye.