Hello,
I have had an issue in december on a full upgrade (new SD built on Debian 13 & reinstalled all Domoticz from scratch with Z4D plugin going to python venv etc ; everything else remained as-is, for instance zwave legacy inegration and any other domoticz core integrations). At the moment, no time to ding into this, unfortunately + system is headless & this looks to be a brutal kernel hang.
Today, after disabling services & restored a DB with Z4D plugin disabled (as this was the biggest integration change, with venv, on top of raspbian 11 -> 13 move due to openssl3, this was IMO most likely an issue there but looks I was wrong) & somoticz service start disabled as well to be able to start is manually & see some logs directly on console (crash is so sudden that no system/domoticz logs are on a SD after restart).
Maybe a good catch: Last log is about "Motherboard sensors" integration I had for ages... So the question is: Is there known issue there (maybe specific to PI3B) that rings a bell to someone??? If this is known to cause issue, maybe on last raspbian, IMO starting this may be disabled with a deprecation warning in the log as that's not easy to figure-out what's wrong due to the brutal hang that does not even allow logs to be written on storage for post-mortem check.
Stable upgrade 2025.1->2025.2 issue...
Moderators: leecollings, remb0
Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.
Use the following template when posting here:
Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....
If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly
If you are replying, please do not quote images/code from the first post
Please mark your topic as Solved when the problem is solved.
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.
Use the following template when posting here:
Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....
If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly
If you are replying, please do not quote images/code from the first post
Please mark your topic as Solved when the problem is solved.
-
gizmocuz
- Posts: 3026
- Joined: Thursday 11 July 2013 18:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Top of the world
- Contact:
Re: Stable upgrade 2025.1->2025.2 issue...
Might be good to mention which domoticz version you are running?
Quality outlives Quantity!
-
lost
- Posts: 716
- Joined: Thursday 10 November 2016 9:30
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Stable upgrade 2025.1->2025.2 issue...
Hello, sorry, this was only in the title not in the message: I'm currently running 2025.1 stable that was still Debian 11 based.
So, to make it clear, the attempt was a full reinstall (as I skipped raspbian 12, no direct upgrade path) to allow installing 2025.2 (with openssl3 needed): On this side all looked OK, a test start showed a default/empty webUI... so DB/scripts restore, Z4D plugin reinstalled (now using python venv as Debian13 now prohibits mixing OS python dependencies with requirements that may need specific/different versions), but the system then hang at Domoticz startup with no post-mortem logs/clues at restart, unfortunately.
So, to make it clear, the attempt was a full reinstall (as I skipped raspbian 12, no direct upgrade path) to allow installing 2025.2 (with openssl3 needed): On this side all looked OK, a test start showed a default/empty webUI... so DB/scripts restore, Z4D plugin reinstalled (now using python venv as Debian13 now prohibits mixing OS python dependencies with requirements that may need specific/different versions), but the system then hang at Domoticz startup with no post-mortem logs/clues at restart, unfortunately.