Addon enters boot loop due to "bad marshal data" of precomplied python package
joernnilsson opened this issue · comments
Problem/Motivation
0.18.0 fails to start
Expected behavior
A normal boot, bringing up motioneye and cameras
Actual behavior
Addon enters a boot loop due to a (seemingly) corrupt complied version of the pkg_resources package:
[09:17:49] INFO: Starting motionEye...
Traceback (most recent call last):
File "/usr/bin/meyectl", line 6, in <module>
from pkg_resources import load_entry_point
ValueError: bad marshal data (unknown type code)
[09:17:50] INFO: Starting motionEye...
Traceback (most recent call last):
File "/usr/bin/meyectl", line 6, in <module>
from pkg_resources import load_entry_point
ValueError: bad marshal data (unknown type code)
[09:17:51] INFO: Starting motionEye...
Traceback (most recent call last):
File "/usr/bin/meyectl", line 6, in <module>
from pkg_resources import load_entry_point
ValueError: bad marshal data (unknown type code)
[09:17:52] INFO: Starting motionEye...
Traceback (most recent call last):
File "/usr/bin/meyectl", line 6, in <module>
from pkg_resources import load_entry_point
ValueError: bad marshal data (unknown type code)
This can be correct on the fly by entering the container and running
find /usr/lib | grep pkg | grep pyc$ | xargs rm
Which deletes these files:
/usr/lib/python2.7/site-packages/pip/_vendor/pkg_resources/py31compat.pyc
/usr/lib/python2.7/site-packages/pip/_vendor/pkg_resources/__init__.pyc
/usr/lib/python2.7/site-packages/pkg_resources/extern/__init__.pyc
/usr/lib/python2.7/site-packages/pkg_resources/py31compat.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/six.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/pyparsing.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/appdirs.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/_compat.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/utils.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/specifiers.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/version.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/markers.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/_structures.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/requirements.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/__about__.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/__init__.pyc
/usr/lib/python2.7/site-packages/pkg_resources/_vendor/__init__.pyc
/usr/lib/python2.7/site-packages/pkg_resources/__init__.pyc
/usr/lib/python2.7/pkgutil.pyc
After deletion of the pyc files, the addon starts as expected. This is of course only temporary, as the issue returns when the addon is restarted.
Steps to reproduce
This happened when I upgraded to v0.18.0. There must be something from my environment affecting this, as I cannot believe this applies to all users. The system is a fully patched Home Assistant OS, running on NUC (Generic x86-64).
I have not yet tried a full removal of the addon, as I'm not certain if I'll loose my configuration. Keeping the issue reproducible would probably also help while this issue id being processed. Please advice what to do next 👍
Proposed changes
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
bump to keep from auto closing
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
bump to keep active