openhab 2.1.0 on raspbery pi 3
was working all good. played around with voice binding earlier in day.
decided to make upgrade; it failed with segmentation error; tried to use habpanel - can ZWave items are working, but not MQTT ones. Checked openhab.log file and it is full of errors.
Also following bundles in Resolve state, not starting: scheduler service; Xtext; Sound support; Basic UI Fragment; Paper UI Theme;
Tried remove /var/cache/apt/archives/python-samba_2%3a4.2.14+dfsg-0+deb8u9_armhf.deb
sudo dpkg -i --force-overwrite
and same result
The following packages will be upgraded:
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
49 not fully installed or removed.
Need to get 0 B/851 kB of archives.
After this operation, 73.7 kB disk space will be freed.
(Reading database ... 45607 files and directories currently installed.)
Preparing to unpack .../python-samba_2%3a4.2.14+dfsg-0+deb8u9_armhf.deb ...
dpkg: warning: subprocess old pre-removal script returned error exit status 139
dpkg: trying script from the new package instead ...
dpkg: error processing archive /var/cache/apt/archives/python-samba_2%3a4.2.14+dfsg-0+deb8u9_armhf.deb (--unpack):
subprocess new pre-removal script returned error exit status 139
dpkg: error while cleaning up:
subprocess installed post-installation script returned error exit status 139
Errors were encountered while processing:
Updating FireMotD available updates count ...
Crashing my head - is the root cause python-samba related? how to get over or workaround it (I’m not using samba shares anyways)? or how to better debug? Thank You!
I had a image burned earlier in day (probably from the original sd beeing corrupt already - if that’s the case). So, wrote that image on a new SD card, put in raspbery, loaded - trying to upgrade and getting same segmentation fault error for python-samba. don’t have proper backup/restore strategy yet, but have some results from few backup scripts. will probably give up with this “segmentation fault” and try restoring on a fresh install.