Hi, y all.
After suffering from a malfunctioning SD card ( and not beeing able to get an USB sctick working) i started buiding a new domoticz instance om my Pi. Because I was suffering from some ghost devices which kept popping op in my devices list I decided to start from scratch
I downloaded the latest Pi build, updated it and installed a clean version of Domoticz.
After installing for a while i noticed that it wasn't possilbe to save my stettings from a chrome session on mij laptop, but it worked just fine on the browser on my Pi. thinking that I would sole this later i proceed
After a day if installing end configuring my Zwave devices Domoticz just stoped working, WTF, tryd repairing teh database, no errors.
I Idiot used the malfunctioning SD card instead of the new one i had. > No worries, moved the instance from the bad to the good card and proceed.
You Guess, this didn't work. Domoticz keeps crashing, althoug the serice seems to run I don't get access to the website..
Please help... ( iI will post the loggings as soon as i'm able to get them)
Recovering database
Moderator: leecollings
-
- Posts: 9
- Joined: Wednesday 13 June 2018 10:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Last Sta
- Location: Netherlands
- Contact:
Re: Recovering database
sudo service domoticz.sh status results in:
i@raspberrypi:~ $ sudo service domoticz.sh status
● domoticz.service - LSB: Home Automation System
Loaded: loaded (/etc/init.d/domoticz.sh; generated)
Active: active (exited) since Sun 2020-03-08 13:28:47 CET; 10min ago
Docs: man:systemd-sysv-generator(8)
Process: 394 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/SU
mrt 08 13:28:45 raspberrypi systemd[1]: Starting LSB: Home Automation System...
mrt 08 13:28:47 raspberrypi domoticz.sh[394]: 2020-03-08 13:28:47.357 Status: D
mrt 08 13:28:47 raspberrypi domoticz.sh[394]: 2020-03-08 13:28:47.368 Status: B
mrt 08 13:28:47 raspberrypi domoticz.sh[394]: 2020-03-08 13:28:47.369 Status: S
mrt 08 13:28:47 raspberrypi domoticz.sh[394]: domoticz: Domoticz is starting up.
mrt 08 13:28:47 raspberrypi domoticz[414]: Domoticz is starting up....
mrt 08 13:28:47 raspberrypi domoticz[460]: Domoticz running...
mrt 08 13:28:47 raspberrypi systemd[1]: Started LSB: Home Automation System.
lines 1-14/14 (END)
i@raspberrypi:~ $ sudo service domoticz.sh status
● domoticz.service - LSB: Home Automation System
Loaded: loaded (/etc/init.d/domoticz.sh; generated)
Active: active (exited) since Sun 2020-03-08 13:28:47 CET; 10min ago
Docs: man:systemd-sysv-generator(8)
Process: 394 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/SU
mrt 08 13:28:45 raspberrypi systemd[1]: Starting LSB: Home Automation System...
mrt 08 13:28:47 raspberrypi domoticz.sh[394]: 2020-03-08 13:28:47.357 Status: D
mrt 08 13:28:47 raspberrypi domoticz.sh[394]: 2020-03-08 13:28:47.368 Status: B
mrt 08 13:28:47 raspberrypi domoticz.sh[394]: 2020-03-08 13:28:47.369 Status: S
mrt 08 13:28:47 raspberrypi domoticz.sh[394]: domoticz: Domoticz is starting up.
mrt 08 13:28:47 raspberrypi domoticz[414]: Domoticz is starting up....
mrt 08 13:28:47 raspberrypi domoticz[460]: Domoticz running...
mrt 08 13:28:47 raspberrypi systemd[1]: Started LSB: Home Automation System.
lines 1-14/14 (END)
-
- Posts: 9
- Joined: Wednesday 13 June 2018 10:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Last Sta
- Location: Netherlands
- Contact:
Re: Recovering database
content of my crash.log
[New LWP 0]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
__waitpid (options=0, stat_loc=0x7ed39040, pid=465) at ../sysdeps/unix/sysv/linux/waitpid.c:30
30 ../sysdeps/unix/sysv/linux/waitpid.c: Bestand of map bestaat niet.
Id Target Id Frame
* 1 Thread 0x76ff1fb0 (LWP 460) "domoticz" __waitpid (options=0, stat_loc=0x7ed39040, pid=465) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2 Thread 0x75e0a220 (LWP 461) "Watchdog" __GI___nanosleep (remaining=0x75e09bc8, requested_time=0x75e09bc8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
Thread 2 (Thread 0x75e0a220 (LWP 461)):
#0 __GI___nanosleep (remaining=0x75e09bc8, requested_time=0x75e09bc8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
#1 __GI___nanosleep (requested_time=0x75e09bc8, remaining=0x75e09bc8) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2 0x002785cc in sleep_milliseconds(long) ()
#3 0x002d8f7c in Do_Watchdog_Work() ()
#4 0x009f18fc in execute_native_thread_routine ()
#5 0x76efa494 in start_thread (arg=0x75e0a220) at pthread_create.c:486
#6 0x76d3b578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 1 (Thread 0x76ff1fb0 (LWP 460)):
#0 __waitpid (options=0, stat_loc=0x7ed39040, pid=465) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1 __waitpid (pid=465, stat_loc=0x7ed39040, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
#2 0x002d8840 in dumpstack_gdb(bool) ()
#3 0x002d8e2c in signal_handler(int, siginfo_t*, void*) ()
#4 <signal handler called>
#5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#6 0x76c7b230 in __GI_abort () at abort.c:79
#7 0x00a1ad7c in __gnu_cxx::__verbose_terminate_handler() ()
#8 0x0097b45c in __cxxabiv1::__terminate(void (*)()) ()
#9 0x0097b4d0 in std::terminate() ()
#10 0x001f5fbc in main ()
Main thread:
#0 __waitpid (options=0, stat_loc=0x7ed39040, pid=465) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1 __waitpid (pid=465, stat_loc=0x7ed39040, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
#2 0x002d8840 in dumpstack_gdb(bool) ()
#3 0x002d8e2c in signal_handler(int, siginfo_t*, void*) ()
#4 <signal handler called>
#5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#6 0x76c7b230 in __GI_abort () at abort.c:79
#7 0x00a1ad7c in __gnu_cxx::__verbose_terminate_handler() ()
#8 0x0097b45c in __cxxabiv1::__terminate(void (*)()) ()
#9 0x0097b4d0 in std::terminate() ()
#10 0x001f5fbc in main ()
[Inferior 1 (process 460) detached]
[New LWP 0]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
__waitpid (options=0, stat_loc=0x7ed39040, pid=465) at ../sysdeps/unix/sysv/linux/waitpid.c:30
30 ../sysdeps/unix/sysv/linux/waitpid.c: Bestand of map bestaat niet.
Id Target Id Frame
* 1 Thread 0x76ff1fb0 (LWP 460) "domoticz" __waitpid (options=0, stat_loc=0x7ed39040, pid=465) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2 Thread 0x75e0a220 (LWP 461) "Watchdog" __GI___nanosleep (remaining=0x75e09bc8, requested_time=0x75e09bc8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
Thread 2 (Thread 0x75e0a220 (LWP 461)):
#0 __GI___nanosleep (remaining=0x75e09bc8, requested_time=0x75e09bc8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
#1 __GI___nanosleep (requested_time=0x75e09bc8, remaining=0x75e09bc8) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2 0x002785cc in sleep_milliseconds(long) ()
#3 0x002d8f7c in Do_Watchdog_Work() ()
#4 0x009f18fc in execute_native_thread_routine ()
#5 0x76efa494 in start_thread (arg=0x75e0a220) at pthread_create.c:486
#6 0x76d3b578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 1 (Thread 0x76ff1fb0 (LWP 460)):
#0 __waitpid (options=0, stat_loc=0x7ed39040, pid=465) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1 __waitpid (pid=465, stat_loc=0x7ed39040, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
#2 0x002d8840 in dumpstack_gdb(bool) ()
#3 0x002d8e2c in signal_handler(int, siginfo_t*, void*) ()
#4 <signal handler called>
#5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#6 0x76c7b230 in __GI_abort () at abort.c:79
#7 0x00a1ad7c in __gnu_cxx::__verbose_terminate_handler() ()
#8 0x0097b45c in __cxxabiv1::__terminate(void (*)()) ()
#9 0x0097b4d0 in std::terminate() ()
#10 0x001f5fbc in main ()
Main thread:
#0 __waitpid (options=0, stat_loc=0x7ed39040, pid=465) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1 __waitpid (pid=465, stat_loc=0x7ed39040, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
#2 0x002d8840 in dumpstack_gdb(bool) ()
#3 0x002d8e2c in signal_handler(int, siginfo_t*, void*) ()
#4 <signal handler called>
#5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#6 0x76c7b230 in __GI_abort () at abort.c:79
#7 0x00a1ad7c in __gnu_cxx::__verbose_terminate_handler() ()
#8 0x0097b45c in __cxxabiv1::__terminate(void (*)()) ()
#9 0x0097b4d0 in std::terminate() ()
#10 0x001f5fbc in main ()
[Inferior 1 (process 460) detached]
Re: Recovering database
Hi swilting.
Do I understand you correctly if I state that you stil have a good backup of the database? In that case you could reinstall Domoticz on a (different) as card and try to restore the database.
Do I understand you correctly if I state that you stil have a good backup of the database? In that case you could reinstall Domoticz on a (different) as card and try to restore the database.
Check these howto's: https://sancla.com
Re: Recovering database
The crashes could be related to plugins, first try it without of with minimal plugins and see how that works out for you. Just to be sure...
Check these howto's: https://sancla.com
Who is online
Users browsing this forum: No registered users and 0 guests