Page 1 of 1

Domoticz stopped and does not start anymore

Posted: Sunday 31 January 2021 1:23
by Ptje
Hello,

My Domoticz installation has stopped and does not start anymore. I can't find what the problem is. I attached my Domoticz crashlog. Does someone can help my to see what the problem could by ? I hope I don't have to do a full new installation and configuration.......

Greetings,
Peter

Re: Domoticz stopped and does not start anymore

Posted: Sunday 31 January 2021 9:33
by Ptje
Hello,

When I start Domoticz I see the following,

Code: Select all

2021-01-31 09:30:48.122  Status: Domoticz V2020.2 (build 12896) (c)2012-2021 GizMoCuz
2021-01-31 09:30:48.122  Status: Build Hash: d5c2e6a46-modified, Date: 2021-01-30 10:52:18
2021-01-31 09:30:48.122  Status: Startup Path: /home/pi/domoticz/
2021-01-31 09:30:48.169  Sunrise: 08:17:00 SunSet: 17:25:00
2021-01-31 09:30:48.169  Day length: 09:07:00 Sun at south: 12:51:00
2021-01-31 09:30:48.169  Civil twilight start: 07:41:00 Civil twilight end: 18:01:00
2021-01-31 09:30:48.169  Nautical twilight start: 07:01:00 Nautical twilight end: 18:41:00
2021-01-31 09:30:48.170  Astronomical twilight start: 06:21:00 Astronomical twilight end: 19:21:00
2021-01-31 09:30:48.242  Status: PluginSystem: Started, Python version '3.7.3'.
2021-01-31 09:30:48.247  Active notification Subsystems: email, fcm (2/13)
2021-01-31 09:30:48.251  Error: WebServer(HTTP) startup failed on address 0.0.0.0 with port: 8080: bind: Address already in use
2021-01-31 09:30:48.251  Error: WebServer(HTTP) check if no other application is using port: 8080
2021-01-31 09:30:48.263  Error: WebServer(SSL) startup failed on address 0.0.0.0 with port: 443: bind: Permission denied
2021-01-31 09:30:48.263  Error: WebServer(SSL) check privileges for opening ports below 1024
2021-01-31 09:30:48.264  Error: No servers are configured. Hence mydomoticz will not be started either (if configured)
terminate called without an active exception
2021-01-31 09:30:48.264  Error: Domoticz(pid:2461, tid:2461('domoticz')) received fatal signal 6 (Aborted)
2021-01-31 09:30:48.264  Error: siginfo address=0x99d, address=0xffffffff
2021-01-31 09:30:52.027  Error: Thread 1 (Thread 0x76018010 (LWP 2461)):
2021-01-31 09:30:52.027  Error: #0  __waitpid (options=0, stat_loc=0x7edef920, pid=2466) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2021-01-31 09:30:52.027  Error: #1  __waitpid (pid=2466, stat_loc=0x7edef920, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
2021-01-31 09:30:52.027  Error: #2  0x002cd4cc in dumpstack_gdb(bool) ()
2021-01-31 09:30:52.027  Error: #3  0x002cda98 in signal_handler(int, siginfo_t*, void*) ()
2021-01-31 09:30:52.027  Error: #4  <signal handler called>
2021-01-31 09:30:52.027  Error: #5  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
2021-01-31 09:30:52.027  Error: #6  0x769b8230 in __GI_abort () at abort.c:79
2021-01-31 09:30:52.027  Error: #7  0x009cc084 in __gnu_cxx::__verbose_terminate_handler() ()
2021-01-31 09:30:52.028  Error: #8  0x0092f43c in __cxxabiv1::__terminate(void (*)()) ()
2021-01-31 09:30:52.028  Error: #9  0x0092f4b0 in std::terminate() ()
2021-01-31 09:30:52.028  Error: #10 0x001f17e4 in main ()
Aborted
 
But I don't see what is running on port 8080 or 443

Greetings,
Peter

Re: Domoticz stopped and does not start anymore

Posted: Sunday 31 January 2021 11:26
by waaren
Ptje wrote: Sunday 31 January 2021 9:33 ...but I don't see what is running on port 8080 or 443

Code: Select all

sudo netstat -tulpn | grep '8080\|433'
Will show you what is on these ports.

Most of the time a

Code: Select all

service domoticz stop 
before a

Code: Select all

service domoticz start
does work

Re: Domoticz stopped and does not start anymore

Posted: Sunday 31 January 2021 13:52
by erem
sometimes rasbian gets confused.
i believe a reboot of your pi will clear up the process that occupies port 8080

Re: Domoticz stopped and does not start anymore

Posted: Sunday 31 January 2021 14:50
by Ptje
waaren wrote: Sunday 31 January 2021 11:26
Ptje wrote: Sunday 31 January 2021 9:33 ...but I don't see what is running on port 8080 or 443

Code: Select all

sudo netstat -tulpn | grep '8080\|433'
Will show you what is on these ports.

pi@raspberrypi:~ $ sudo netstat -tulpn | grep '8080\|433'
tcp6 0 0 :::8080 :::* LISTEN 551/domoticz
I see this at my fathers Domoticz.

pi@raspberrypi:~ $ sudo netstat -tulpn | grep '8080\|433'
tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 430/motion
I see this at my Domoticz.

I don`t know of this is normal.

Greetings,
Peter

Re: Domoticz stopped and does not start anymore

Posted: Sunday 31 January 2021 16:17
by AllesVanZelf
Well, it looks like you have motion running on 8080.
Motion is surveillance software. Motion detection.
You could change the port Domoticz is using in /etc/init.d/domoticz.sh
fir example:

Code: Select all

DAEMON_ARGS="$DAEMON_ARGS -www 8090"

Re: Domoticz stopped and does not start anymore

Posted: Sunday 31 January 2021 16:33
by Ptje
Hello,

Maybe I see ghosts, but I did watch yesterday a not official stream of Rico Verhoeven. During the match, I received a message from Monit, that Domoticz was stopped. It is not possible that something is installed with a script on my raspberry ?

I don't use motion software. And I did not change anything on my Raspberry myself..........

Greetings.

Re: Domoticz stopped and does not start anymore

Posted: Sunday 31 January 2021 17:21
by AllesVanZelf
In that case: check if motion is installed indead:

Code: Select all

sudo apt list --installed |grep motion
Do you have a camera attached to your raspberry?

Re: Domoticz stopped and does not start anymore

Posted: Sunday 31 January 2021 17:49
by Ptje
Hello,

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

motion/stable,now 4.1.1-1.1+b2 armhf [installed]

So it is installed. I have no camera attached to the raspberry Pi

Greetings,
Peter

Re: Domoticz stopped and does not start anymore

Posted: Sunday 31 January 2021 18:00
by AllesVanZelf
Then I would have removed motion. But have a close look on dependencies before saying yes to removal.

Code: Select all

 sudo apt remove motion
If you can remove motion without dependency problems, you should find out why motion is installed in the first place.
But without motion, Domoticz should be able to start.

Code: Select all

sudo systemctl start domoticz

Re: Domoticz stopped and does not start anymore

Posted: Thursday 04 February 2021 21:31
by Ptje
Hello,

After the removal from "Motion" The port 8080 error was gone. I even had to place a old database back to get it running. I think that I killed soms stuff while trying to make Domoticz work. Thanks for the help !!

Greetings,
Peter

Re: Domoticz stopped and does not start anymore

Posted: Monday 10 April 2023 13:10
by monette999
Hi I have a similar issue.see attachment.
Are you still online and can help?Image

Gesendet von meinem CPH2343 mit Tapatalk