Domotz How-to: Obtaining the Domotz Collector logs

Many times, when the Collector does not behave as expected and issues occur, the Collector logs are what helps the Domotz team to pinpoint the exact root cause of the problem. You will find how to extract and provide us with these logs in this article.

On Windows

You can find the complete set of logs in these folders:

– C:\ProgramData\domotz\log

– C:\Program Files (x86)\domotz\bin\daemon

Also, from the agent host, you need to access the following address to collect the latest logs (these are still in the memory, they were not saved into the files above).

http://127.0.0.1:3000/api/v1/log/flush

Best way to proceed is to save the output in a .txt file. Compress all the logs in a .zip file and send it to us. Such logs are instrumental in discovering the root causes of different issues and why is happening. 

On Domotz Pro Collector installed using the .deb package (Same for Synology and QNAP)

tar -zcvf /tmp/domotz_logs_$agent_name.tar.gz /var/log/domotz/*

Logs will reside in the zipped file named: /tmp/domotz_logs_$agent_name.tar.gz

Please note that $agent_name has to be replaced with your agent name without any spaces (put dashes or underscores).

Domotz Pro Collector installed using the Snap package

tar -zcvf /tmp/domotz_logs_$agent_name.tar.gz /var/snap/domotzpro-agent/common/log/*

Logs will reside in the zipped file named: /tmp/domotz_logs_$agent_name.tar.gz

Please note that $agent_name has to be replaced with your agent name without any spaces (put dashes or underscores).

On Linux/Debian
Ubuntu/Linux Container:

1. Connect to the Container host.
2. Get the Container ID: sudo docker ps
3. Connect to the Container bash shell: sudo docker exec -it CONTAINER_ID /bin/bash
4. save logs to a file: tar -zcvf /var/log/domotz_logs_$agent_name.tar.gz /var/log/domotz/*
5. Exit from the container: exit
6. Copy logs to the host: sudo docker cp CONTAINER_ID:/var/log/domotz_logs_$agent_name.tar.gz /tmp/
7. Send us the file: /tmp/domotz_logs_$agent_name.tar.gz