Plugins are disabled?

[Quax1507]

I'm on Stretch. Just updated to 8809.
Python plugins crash immediately

[Quax1507]

Success!

Removed python3.5* and libpython3.5*

At least no immediate crash after startup!!!

Looks like that at the moment:

Code: Select all

libpython-dev/stable,now 2.7.13-2 armhf [installed,automatic]
libpython-stdlib/stable,now 2.7.13-2 armhf [installed,automatic]
libpython2.7/stable,now 2.7.13-2+deb9u2 armhf [installed,automatic]
libpython2.7-dev/stable,now 2.7.13-2+deb9u2 armhf [installed,automatic]
libpython2.7-minimal/stable,now 2.7.13-2+deb9u2 armhf [installed,automatic]
libpython2.7-stdlib/stable,now 2.7.13-2+deb9u2 armhf [installed,automatic]
libpython3.4/stable,now 3.4.4-3 armhf [installed,automatic]
libpython3.4-dbg/stable,now 3.4.4-3 armhf [installed]
libpython3.4-dev/stable,now 3.4.4-3 armhf [installed,automatic]
libpython3.4-minimal/stable,now 3.4.4-3 armhf [installed,automatic]
libpython3.4-stdlib/stable,now 3.4.4-3 armhf [installed]
python/stable,now 2.7.13-2 armhf [installed]
python-apt/stable,now 1.1.0~beta5 armhf [installed]
python-apt-common/stable,now 1.1.0~beta5 all [installed]
python-bluez/stable,now 0.22-1 armhf [installed]
python-cffi-backend/stable,now 1.9.1-2 armhf [installed,automatic]
python-chardet/stable,now 2.3.0-2 all [installed]
python-colorama/stable,now 0.3.7-1 all [installed]
python-cryptography/stable,now 1.7.1-3+b2 armhf [installed,automatic]
python-dev/stable,now 2.7.13-2 armhf [installed]
python-distlib/stable,now 0.2.4-1 all [installed]
python-enum34/stable,now 1.1.6-1 all [installed,automatic]
python-html5lib/stable,now 0.999999999-1 all [installed]
python-idna/stable,now 2.2-1 all [installed,automatic]
python-ipaddress/stable,now 1.0.17-1 all [installed,automatic]
python-minimal/stable,now 2.7.13-2 armhf [installed,automatic]
python-openssl/stable,now 16.2.0-1 all [installed,automatic]
python-pkg-resources/stable,now 33.1.1-1 all [installed,automatic]
python-pyasn1/stable,now 0.1.9-2 all [installed,automatic]
python-requests/stable,now 2.12.4-1 all [installed]
python-rpi.gpio/stable,now 0.6.3~stretch-1 armhf [installed]
python-setuptools/stable,now 33.1.1-1 all [installed,automatic]
python-six/stable,now 1.10.0-3 all [installed,automatic]
python-urllib3/stable,now 1.19.1-1 all [installed,automatic]
python-webencodings/stable,now 0.5-2 all [installed,automatic]
python2.7/stable,now 2.7.13-2+deb9u2 armhf [installed,automatic]
python2.7-dev/stable,now 2.7.13-2+deb9u2 armhf [installed]
python2.7-minimal/stable,now 2.7.13-2+deb9u2 armhf [installed,automatic]
python3.4/stable,now 3.4.4-3 armhf [installed]
python3.4-dev/stable,now 3.4.4-3 armhf [installed]
python3.4-minimal/stable,now 3.4.4-3 armhf [installed,automatic]

[Raspberry Piet]

Success!

Removed python3.5* and libpython3.5*

At least no immediate crash after startup!!!

Bingo!

Thank you very much. I had exactly the same trouble here.
I hope it will run stable from now on with python plugins.

edit:
.bash_history:

Code: Select all

sudo apt-get remove python3.5
sudo apt-get remove python3.5-minimal
sudo apt-get remove libpython3.5
sudo apt-get remove libpython3.5-minimal

[Siewert308SW]

Great...
As i mentioned earlier my suspicion is right.
Let's hope a dev read this and know how to get old and newer python version compatible.

Edit:
Opened a issue on Github: https://github.com/domoticz/domoticz/issues/2073

[Quax1507]

So happy it is working now. System runs stable for hours now with two Python plugins enabled

[domoticzag]

This unfortionatly did not work for my system, its also on stretch. Python plugins are installed correctly but not showing in Hardware.

Any other advice?

Else installing Jessie seems to be the solution?

[garethhowell]

My suspicion is that there is an incompatibility between versions of the python3 libraries. Whether you experience the crashing with the pre-built binaries depends on whether you have the same configuration of libraries as the machine on which the binaries are built.
The solution for me was to build from source. It’s not hard and there is a comprehensive how-to in the wiki (google “build domoticz from source”). It does take a long time, but your main domoticz install runs at the same time so why worry.
I use a headless Pi2 and only access using a console. I installed screen so I could disconnect and leave the build running. If you access using the desktop then you don’t need to do this.

On my Pi2 it took about 30 hours to build from scratch. After that I simply shutdown the running domoticz, copied the database to the dev-domoticz folder, modified domoticz.sh to start the version of domoticz in domoticz-dev rather than domoticz and restarted. All the plugins work now.

[Dnpwwo]

@domoticzag,

Switching to Jessie won't make a difference.

Can you post some of the Domoticz start up log?

@garethhowell ,

The plugin framework does seem way more stable on RPi for people who build from source but not for the reason you think. Domoticz does not link to Python during the build, it links to it at runtime to allow people without Python on their system to still run Domoticz.

[garethhowell]

The plugin framework does seem way more stable on RPi for people who build from source but not for the reason you think. Domoticz does not link to Python during the build, it links to it at runtime to allow people without Python on their system to still run Domoticz.

OK, thanks for the clarification. Too bad, it seemed like a credible hypothesis

[Quax1507]

Just cloned my live system to a second one for testing.

Here is my startup log:

Code: Select all

2018-01-18 14:28:41.975  RxQueue: queue worker started...
2018-01-18 14:28:43.976  Hardware Monitor: Started
2018-01-18 14:28:43.997  Wunderground: Worker started...
2018-01-18 14:28:43.998  Kodi: Started
2018-01-18 14:28:43.998  DarkSky: Started...
2018-01-18 14:28:43.998  (Sonos) Started.
2018-01-18 14:28:43.999  (Wintergarten) Started.
2018-01-18 14:28:44.000  EventSystem: reset all events...
2018-01-18 14:28:44.005  EventSystem: Write file: /home/pi/domoticz/scripts/dzVents/generated_scripts/Check_Battery_Levels.lua
2018-01-18 14:28:44.019  EventSystem: reset all device statuses...
2018-01-18 14:28:44.100  Kodi: (Wohnzimmer) Starting thread.
2018-01-18 14:28:44.168  PluginSystem: Entering work loop.
2018-01-18 14:28:44.201  Kodi: Starting I/O service thread.
2018-01-18 14:28:44.543  Error: Domoticz received fatal signal 11 !...
2018-01-18 14:28:44.546  Error:   /home/pi/domoticz/domoticz() [0x23753c]
2018-01-18 14:28:44.546  Error:   /home/pi/domoticz/domoticz(_Z14signal_handleri+0x4c) [0x2375f4]
2018-01-18 14:28:44.546  Error:   /lib/arm-linux-gnueabihf/libc.so.6(__default_sa_restorer+0) [0x76bef6b0]

[Quax1507]

I just did some more testing...

If "libpython3-5" is installed, system crashes immediately, if not it starts up without issues!

EDIT: not reproducable

[Dnpwwo]

@Quax1507,

Can you please try turning off the event system (Settings / Other tab) and restart?

[domoticzag]

What would be the solution to this problem now?

Rebuild from source? On Stretch or Jessie?

[Geitje]

For me also python scripts stopped working after an update.

I use Xiaomi Me Vacuum robot (Gen 1) plugin https://github.com/mrin/domoticz-mirobot-plugin, and I use a small python script to trun on and off my TP-link smart plugs. None of them work.

Today there was a new update of Domoticz beta, but it does not resolve the issue. Hope a solution is at hand.

[garethhowell]

It’s difficult to offer advice when the root of the problem is no known. All I can say is that building from source worked for me. It’s not difficult to do provided you are familiar with working with the command prompt.

[olicot]

Hello
Same issue avec some latest beta...

not only python plugins, but all EventSystem (Lua/Blockly/Scripts).

So to enable :
go to : settings/others and enable ! EventSystem (Lua/Blockly/Scripts):
Domoticz should be restarted
and python plugins are back

It works for me
Hope this help

[Siewert308SW]

@domoticzag,

Switching to Jessie won't make a difference.

I just wonder then why i still run Jessie and plugins enabled and running fine.
No matter what Domo build i use, Pre compiled binary or manually compiled on RPi3 with jessie and Python3.4 / libpython3.4 no issues.
If i upgrade to 3.5 or try the same on Stretch the entire system gets unstable and eventually ending in a Segmentation fault.
Something isn't right here.
Or you do or amend something so it runs where we have issues.
Or something is missing from our normal installation, my 2 cents

[domoticzag]

Hello
Same issue avec some latest beta...

not only python plugins, but all EventSystem (Lua/Blockly/Scripts).

So to enable :
go to : settings/others and enable ! EventSystem (Lua/Blockly/Scripts):
Domoticz should be restarted
and python plugins are back

It works for me
Hope this help

This also worked for me !

[Phantom]

@domoticzag,

Switching to Jessie won't make a difference.

I just wonder then why i still run Jessie and plugins enabled and running fine.
No matter what Domo build i use, Pre compiled binary or manually compiled on RPi3 with jessie and Python3.4 / libpython3.4 no issues.
If i upgrade to 3.5 or try the same on Stretch the entire system gets unstable and eventually ending in a Segmentation fault.
Something isn't right here.
Or you do or amend something so it runs where we have issues.
Or something is missing from our normal installation, my 2 cents

Same here for me, on Stretch it was impossible for me to run the beta with python plugins, i get segmentation fault direct when try to start domoticz or when i activate the plugin when domoticz is running.
Precompiled or from source makes no difference. Stable was running without any issue's.
Today went back to jessie installed everything and it works perfect, newest beta with all python plugins enabled.
Domoticz on RPi3 with Stretch is having an issue.

[Daoud]

Hello,
I have an issue with Python and Domoticz beta.
The system was fine since 2 months and since 1 weeks, plugins not work anymore and python 3.5 seems not be loaded at domoticz startup. No message in the log about plugins...
I'm disapointed