Walter vl: /* Check the Domoticz log files */

2026-03-26T23:12:54Z

Check the Domoticz log files

← Older revision		Revision as of 23:12, 26 March 2026
Line 38:		Line 38:
	For more info on command line parameters see wiki page [[Command line parameters]]		For more info on command line parameters see wiki page [[Command line parameters]]

	~~For~~ extra debug logging start domoticz manually with debug flags eg:		=== Enable extra debugging options ===
			Since version 2026.1 you can set easily extra debugging options in menu ''[[Setup Settings\|Setup - Settings, Tab Log]]''. When the issue is identified you can switch off the extra debug logging again.

			For older versions start domoticz manually with debug flags eg:

	<code>./domoticz -www 8080 -sslwww 443 -log "/var/log/domoticz.log" -loglevel all -debuglevel normal,auth,hardware,received,webserver,eventsystem,python,thread_id</code>		<code>./domoticz -www 8080 -sslwww 443 -log "/var/log/domoticz.log" -loglevel all -debuglevel normal,auth,hardware,received,webserver,eventsystem,python,thread_id</code>

Walter vl: /* Activate logging to OS-file (with or without debugging) */

2026-02-26T15:29:44Z

Activate logging to OS-file (with or without debugging)

← Older revision		Revision as of 15:29, 26 February 2026
Line 60:		Line 60:
	DAEMON_ARGS="$DAEMON_ARGS -loglevel normal,status,error" # these loglevels will make it to the logfile		DAEMON_ARGS="$DAEMON_ARGS -loglevel normal,status,error" # these loglevels will make it to the logfile
	#DAEMON_ARGS="$DAEMON_ARGS -debuglevel normal,hardware,received,webserver,eventsystem,python,thread_id"		#DAEMON_ARGS="$DAEMON_ARGS -debuglevel normal,hardware,received,webserver,eventsystem,python,thread_id"
			For servers configured with systemd services use the settings in file <code>/etc/systemd/system/domoticz.service</code>

			Find the ExecStart line and append the -log and -loglevel parameters. For example:
			<code>[Service]
			ExecStart=/home/pi/domoticz/domoticz -www 8080 -log /var/log/domoticz.log -loglevel normal,status,error</code>
			The in both cases reload and restart the Domoticz service:
	sudo systemctl daemon-reload		sudo systemctl daemon-reload
	sudo service domoticz stop		sudo service domoticz stop

Walter vl: /* Check the Domoticz log files */

2025-03-31T12:21:37Z

Check the Domoticz log files

← Older revision		Revision as of 12:21, 31 March 2025
Line 74:		Line 74:

	To open the crash log you normally need root (also called administrator) rights. Use for example <code>sudo cat domoticz_crash.log</code>		To open the crash log you normally need root (also called administrator) rights. Use for example <code>sudo cat domoticz_crash.log</code>

			=== Check log in Docker container ===
			To enable file logging in a Docker Domoticz container and to check those logs see wiki [[Docker#Debugging]]

	==Scripts==		==Scripts==

Walter vl: /* Windows */

2024-04-03T07:15:43Z

Windows

New page

After installing new hardware or a new update domoticz sometime seems to fail. 
Now this could happen if you are running a beta version, but 99,9% of the time this has no relationship with the beta version at all, 
and even more so, nothing changed on the part where they have problems with. '''So what could be wrong ?'''

 

==User account==
By default Domoticz is protected by a username (''admin'') and password (''domoticz'').

Please either change the password as soon as possible (trough menu [[MyProfile|Setup - My Profile]]) or create a different admin user and remove the default (admin) user.

Forgotten password: see the [[Lost Username Password|Lost Username Password page]] 

==Browser Cache==

The web frontend uses javascripts to connect with the server.

If for some reason, the page does not load correctly in Firefox / Chrome / Edge, refresh these scripts. Mostly this can be done with CTRL-F5 to refresh all Domoticz javascripts.

Also trying to start Domoticz in a incognito/private browser session can indicate javascript issues if it runs there.

==Check the Domoticz log files==
Check the Domoticz Log file for hints. Go to menu <code>Setup - Log</code> to see the Domoticz log. In the web this is a limited log file of only the last 300 lines.

So try to check this log file when the issue starts. If the issue cannot be found in the log or when the web UI is not working you can activate logging to OS-file.

Alternative you can stop the Domoticz Service and start Domoticz manually. Possible issue will appear in the terminal screen logging.
 
cd domoticz
sudo service domoticz stop

Test if domoticz can be started by hand:

./domoticz

Additional you can start domoticz with extra parameters eg <code>./domoticz -www 8080 -sslwww 443 -log "/var/log/domoticz.log"</code>

For more info on command line parameters see wiki page [[Command line parameters]]

For extra debug logging start domoticz manually with debug flags eg:

<code>./domoticz -www 8080 -sslwww 443 -log "/var/log/domoticz.log" -loglevel all -debuglevel normal,auth,hardware,received,webserver,eventsystem,python,thread_id</code>

If issue is solved you can start domoticz service again

sudo service domoticz start

===Activate logging to OS-file (with or without debugging)===

The log section in the Domoticz browser shows a max of 300 most recent log lines. This could be to small to check older issues so you can direct the logging to a log file.

Be aware, this can become a large file!

The domoticz logfile location and other settings are defined in <code>/etc/init.d/domoticz.sh</code>
the relevant settings are in set to the <code>DAEMON_ARGS</code> with a text editor of choice:
DAEMON_ARGS="$DAEMON_ARGS -log /var/log/domoticz.log" # or any other OS file
#DAEMON_ARGS="$DAEMON_ARGS -loglevel normal,status,error, debug" # debug disabled for now
DAEMON_ARGS="$DAEMON_ARGS -loglevel normal,status,error" # these loglevels will make it to the logfile
#DAEMON_ARGS="$DAEMON_ARGS -debuglevel normal,hardware,received,webserver,eventsystem,python,thread_id"

sudo systemctl daemon-reload
sudo service domoticz stop
sudo service domoticz start
sudo tail -f /var/log/domoticz.log

The system and other logfiles can be found with sudo ls -lrt /var/log/*log

===Crash log===
When Domoticz really crashes a domoticz_crash.log file is created in the domoticz install folder eg /home/<user>/domoticz.

In this crash log you can search for the phrase <code>signal_handler</code> that will show which thread caused the crash of Domoticz. The thread name (plugin/hardware/module) is is listed in the beginning of the crash log.

To open the crash log you normally need root (also called administrator) rights. Use for example <code>sudo cat domoticz_crash.log</code>

==Scripts==
Domoticz can make use of scripts (Lua, Python, Blockly, dzVents etc). It could be there is a problem with one of the scripts.

*Maybe updating a virtual sensor via JSON with invalid parameters.
*Try disabling the eventsystem in Domoticz (from the [[Application Settings#EventSystem .28Lua.2FBlockly.2FScripts.29|Setup - Settings]])
*Rename the 'scripts' and 'plugin' folder in <code>/home/<user>/domoticz/</code> to prevent the scripts and plugins from running loading and running. Enable them one by one to debug.

==Hardware==
There could be a problem with one of the added hardware in Domoticz.

*Disable all [[Hardware Setup|hardware]] in Domoticz (Not 'delete', just 'disable') If you are unable to do this because Domoticz does not start, download a SQLite editor (for example SQLite Expert Personal Edition), open the database, go to the 'hardware' table and disable all hardware here (put a 0 (zero) under the enabled column)
**Alternative to disable hardware or plugin from commandline

<blockquote><code>cd <domoticz dir></code>

<code>sudo service domoticz stop</code>

<code>sudo sqlite3 -header -list domoticz.db "SELECT Name, ID, Enabled FROM Hardware" -- get ID of misbehaving plugin</code>

<code>sudo sqlite3 -header -list domoticz.db "UPDATE Hardware set Enabled = 0 where ID = <ID of misbehaving plugin>" -- disable</code>

<code>sudo service domoticz start</code></blockquote>

*Now Domoticz should start, if that is the case:
**Enable ONLY 1 hardware ... test with this for at least a few hours (maybe a day!) until you are 100% sure this hardware is functioning properly, and only then, enable another hardware, and perform the same test, and when this is functioning, enable another -
**If during the test period Domoticz will crash, you know what hardware is causing the issue

==Database==

Sometimes an sqlite database database becomes corrupted. There can be many reasons but luckily it does not happen very frequent.
More details can be found at [https://www.sqlite.org/howtocorrupt.html How to corrupt a sqlite database] Typically you see something like <code>"database disk image is malformed"</code> or something similar. Worst case domoticz crashes or does not start.

Alternatively to browse through the SQLITE database install "DB Browser for SQLite": https://sqlitebrowser.org

Possible solutions for Linux and Windows based systems below.

===Linux===

Below check and repair actions for Linux based systems are written with the assumption that the sqlite3 program is installed. If that is not the case, it can be installed with
<source lang="bash">
sudo apt install sqlite3
</source>

====Check database====
<source lang="bash">
sudo service domoticz stop
cd <your domoticz directory>
sudo cp domoticz.db domoticz.keep # just to be sure

sudo sqlite3 domoticz.db 'SELECT name as Tablename ,SUM("pgsize")/4096 Size FROM "dbstat" WHERE name IN (SELECT name FROM "sqlite_master" WHERE type == "table" ) GROUP BY name HAVING Size > 10 ORDER BY size DESC;' # show size of tables. If preferences is in the list your problem is there
sudo sqlite3 domoticz.db "SELECT Key, LENGTH(SValue) size FROM Preferences WHERE LENGTH(sValue) > 1000;" # To identify the row
sudo sqlite3 domoticz.db "UPDATE Preferences SET sValue ='' WHERE LENGTH(sValue) > 1000"
sudo sqlite3 domoticz.db "vacuum"
sudo sqlite3 domoticz.db "PRAGMA integrity_check(10000)"
sudo sqlite3 domoticz.db "PRAGMA foreign_key_check"
sudo service domoticz start # When no other errors found
</source>

====Repair database====
This instruction requires sqlite3 v 3.29 or newer.<source lang="bash">
sudo service domoticz stop
cd /home/pi/domoticz # or other directory if domoticz is in another place
sudo cp domoticz.db domoticz.2repair
sudo service domoticz start

sudo sqlite3 domoticz.2repair
sqlite>.out dump.sql
sqlite>.recover
sqlite>.dump
sqlite>.quit
sudo sed -i '$ s/ROLLBACK;/COMMIT;/g' dump.sql # change last line in dump to prevent rollback and recover as much as possible
sudo sqlite3 domoticz.repaired < dump.sql
sudo sqlite3 domoticz.repaired
sqlite> pragma integrity_check;
sqlite> # other checks you want to do
sqlite> .quit
sudo service domoticz stop
sudo cp domoticz.repaired domoticz.db
sudo service domoticz start
</source>

===Windows (or Linux with Desktop GUI)===

Below check and repair actions for Windows based systems (or Linux systems with a Desktop GUI) are written based on the assumption that the "DB Browser for SQLite" (verzion >= 3.12.1 is installed. If that is not the case, it can be downloaded from [https://sqlitebrowser.org/ sqlitebrowser.org]

When opening the domoticz database with DB Browser for SQLite you will see something like

[[File:Db_browser_start_small.png]]

====Check database====

Tools => Integrity Check

Problems will be reported in a separate window segment.

When errors are encountered proceed with repair actions (see next alinea)

[[File:Db_browser_integrity_check.png]]

====Repair database====

File => Export => Database to SQL file

Save using a describing name (e.g. malformed) type SQL with options "Export everything" and "Keep old schema"

[[File:export.png]]

Close database

Check the last line of the created text file and if the line is ROLLBACK; change this into COMMIT;

File => Import => Database from SQL file => (e.g. malformed)

database name using a describing name (e.g. repaired)

[[File:import1.png]]

save the changes and copy the repaired database to replace your malformed database.

==Other problems==
If Domoticz does not start working with the above steps, try the below options

===Domoticz stops randomly===
When Domoticz stops randomly without proper indication check:

*Power supply. Some powersupplies are failing after a while. Also adding an USB stck (Zigbee, Zwave etc) could increase power usage that your power supply cannot handle.
*SD card is starting to fail. Be sure you have a backup ready. Even better to invest in an SSD solution.

===Domoticz stops or installation fails after an OS update===
On some RPi OS'es there are some issues after an OS update causing installation of Domoticz to fail:

1. /dev/serial/by-id is gone resulting in problamatic USB drive assignments

2. Domoticz is seen as a 64 bit application on a 32 bit machine

For a solution go to forum topic https://www.domoticz.com/forum/viewtopic.php?t=40536

===Domoticz stops after a new Beta update===
Sometimes the changes in a Beta release will cause issues. The Beta update script automatically creates a backup of your complete environment for easy restore.

See the following page for instructions: [[Raspberry Pi#Revert to backup after incorrect beta update.]]

===Linux filesystem rights (Raspberry)===
login with the user that you used to install Domoticz (on a raspberry pi this is the 'pi' user)
then issue:

cd domoticz
sudo service domoticz stop
sudo chown -R pi.pi *

Test if domoticz can be start by hand:

./domoticz

Now Domoticz should run, or tell you what the problem is, if it runs correctly press 'control-C' to stop it, and start the service

sudo service domoticz start

===Domoticz stops after cold boot===
When booting after a cold boot (no power attached or power failure) some users on Raspberry Pi report that Domoticz will run shortly and then stop.

This could be related with time settings that only can be restored after internet connection. Domoticz standard waits 30 seconds until time sync has occured.

Possible solutions for older versions or when your internet connection takes longer then 30 seconds to startup are:

*Add a battery powered Real Time Clock (RTC) so your systems knows the time directly after booting.
*Put a x seconds delay in the startup of Domoticz to give the system time to update time settings using [[Command line parameters|Command line parameter -startupdelay]]
*use crontab and add <code>@reboot sleep 180 && /etc/init.d/domoticz.sh restart</code> This will restart Domoticz after 180 seconds.
*force 'wait for network' to boot your RPi: <code>sudo raspi-config nonint do_boot_wait 0</code>
*Start Domoticz manually after a cold boot: <code>sudo service domoticz restart</code>

*update <code>/etc/init.d/domoticz.sh</code> to current version from <code>domoticz/domoticz.sh</code> and change line 70 <code>count=30</code> to <code>count=nnn</code> seconds to change the standard 30 seconds wait for internet connection is enabled.
*install ntpdate.

<code>sudo apt-get install ntpdate</code>
and put this as the first line in the do_start section in the file /etc/init.d/domoticz.sh
<code>ntpdate nl.pool.ntp.org</code>
This code will wait until time is set and then continue to start Domoticz

 
===Revert to backup after incorrect beta update===
For Beta updates an automatic backup of the complete domoticz environment including scripts and plugins is created in <code>domoticz/backups/domoticz_backup_yyyymmdd_hhmmss.tar.gz</code> by the update script.

To extract that backup:

*enter domoticz backup directory (where domoticz store a backup before upgrading)

<code>cd ~pi/domoticz/backups</code>

*run tar command to extract the backup (specify the right filename and correct domoticz folder)

<code>tar xvzf domoticz_backup_yyyymmdd_hhmms.tar.gz -C /home/pi/domoticz</code>

*restart domoticz

<code>service domoticz restart</code>

Always refresh the [[Browser Cache|browser cache]] after an update!

==Monitoring Domoticz==
Software crashes, it's a fact of life. Luckily there are a number of ways to keep an eye on Domoticz, and automaticallty restart it if it crashes.

See the wiki page [[Monitoring domoticz|Monitoring Domoticz]] for more information.
 
''Please feel free to make changes to this page if needed''

Troubleshooting - Revision history

Walter vl: /* Check the Domoticz log files */

Walter vl: /* Activate logging to OS-file (with or without debugging) */

Walter vl: /* Check the Domoticz log files */

Walter vl: /* Windows */