debmatic unreachable
Closed this issue · 2 comments
I have debmatic installed on a debian based system.
The last years over it run smooth. Thanks for the work you invested to make this possible.
Now I came up with the idea to do backups and store them directly on the same harddrive; just as a starting point. I lost my eye on it and harddrive went 100% fill state.
With this everything crashed.
All services are up and running (green), but neither web ui nor home assistant can access the interfaces.
I just re-installed debmatic (only this special package), but it didn't help...
root@surfer:/etc/debmatic# debmatic-info
debmatic version: 3.77.7-117 OS: Debian GNU/Linux 12 (bookworm) Kernel: 6.1.0-25-amd64 x86_64 Service Status: Running Kernel modules: Available Raw UART dev: Available HMRF Hardware: HMIP-RFUSB Connected via: eQ-3 HmIP-RFUSB@usb-0000:00:1d.0-1.1 (/dev/raw-uart) Board serial: 1D89B5541D Radio MAC: 0xFF66D9 HMIP Hardware: HMIP-RFUSB Connected via: eQ-3 HmIP-RFUSB@usb-0000:00:1d.0-1.1 (/dev/raw-uart) SGTIN: 3014F711A000041D89B5541D Radio MAC: 0xBEF489
root@surfer:/etc# systemctl status lighttpd
● lighttpd.service - Lighttpd Daemon Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; preset: enabled) Active: active (running) since Wed 2024-10-02 17:39:52 CEST; 2s ago Process: 40489 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=e> Main PID: 40494 (lighttpd) Tasks: 1 (limit: 19030) Memory: 1012.0K CPU: 269ms CGroup: /system.slice/lighttpd.service └─40494 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
Oct 02 17:39:52 surfer systemd[1]: Starting lighttpd.service - Lighttpd Daemon...
Oct 02 17:39:52 surfer systemd[1]: Started lighttpd.service - Lighttpd Daemon.
root@surfer:/etc# systemctl status debmatic
● debmatic.service - debmatic Loaded: loaded (/lib/systemd/system/debmatic.service; enabled; preset: enabled) Active: active (exited) since Wed 2024-10-02 17:29:37 CEST; 11min ago Process: 39873 ExecStart=/usr/share/debmatic/bin/initsystem.sh (code=exited, status=0/SUC> Main PID: 39873 (code=exited, status=0/SUCCESS) CPU: 436ms
Oct 02 17:29:34 surfer systemd[1]: Starting debmatic.service - debmatic...
Oct 02 17:29:37 surfer systemd[1]: Finished debmatic.service - debmatic.
root@surfer:/etc# systemctl status debmatic-rega.service
● debmatic-rega.service - debmatic rega Loaded: loaded (/lib/systemd/system/debmatic-rega.service; enabled; preset: enabled) Active: active (running) since Wed 2024-10-02 17:30:05 CEST; 12min ago Process: 40273 ExecStartPre=/usr/share/debmatic/bin/wait_network_up.sh (code=exited, stat> Process: 40279 ExecStartPre=/usr/share/debmatic/bin/add_fw_block.sh debmatic_rega 8183 31> Process: 40286 ExecStart=/usr/share/debmatic/bin/start_rega.sh (code=exited, status=0/SUC> Process: 40288 ExecStartPost=/usr/share/debmatic/bin/wait_sysvar_creation.tcl (code=exite> Main PID: 40287 (ReGaHss.normal) Tasks: 22 (limit: 19030) Memory: 4.7M CPU: 221ms CGroup: /system.slice/debmatic-rega.service └─40287 /bin/ReGaHss.normal -f /etc/rega.conf -l 2
Oct 02 17:29:55 surfer ReGaHss[40287]: ERROR: IseAddFavorite failed! ID=204 [IseAddFavorite()>
Oct 02 17:29:55 surfer start_rega.sh[40287]: HTTP server started successfully (6 workers)
Oct 02 17:29:55 surfer start_rega.sh[40287]: Waiting for child to finish
Oct 02 17:29:55 surfer start_rega.sh[40298]: Executing /bin/hm_startup in child 40298
Oct 02 17:30:01 surfer start_rega.sh[40298]: No functions defined, creating default functions
Oct 02 17:30:01 surfer start_rega.sh[40298]: No rooms defined, creating default rooms
Oct 02 17:30:01 surfer start_rega.sh[40298]: No system variables defined, creating default sy>
Oct 02 17:30:05 surfer wait_sysvar_creation.tcl[40288]: Waiting for ReGa startup .. Done
Oct 02 17:30:05 surfer systemd[1]: Started debmatic-rega.service - debmatic rega.
Oct 02 17:30:07 surfer start_rega.sh[40287]: ReGa entering normal operation
root@surfer:/etc# lsof | grep 8234
lighttpd 40494 www-data 4u IPv6 482337 0t0 TCP *:8234 (LISTEN) lighttpd 40494 www-data 5u IPv4 482338 0t0 TCP *:8234 (LISTEN)
root@surfer:/etc# sudo systemctl list-dependencies debmatic
debmatic.service ● ├─debmatic-eq3configd.service ● ├─debmatic-hmserver.service ○ ├─debmatic-hs485d.service ● ├─debmatic-hssled.service ○ ├─debmatic-lighttpd.service ○ ├─debmatic-monitor-hb-rf-eth.service ● ├─debmatic-multimacd.service ● ├─debmatic-prepareinterfaceslist.service ● ├─debmatic-rega.service ● ├─debmatic-rfd.service ● ├─debmatic-setinterfaceclock.timer ● ├─debmatic-ssdpd.service ● ├─debmatic-startupfinished.service ● ├─debmatic-updatelgwfirmware.service ● ├─debmatic-updatelgwkey.service ● ├─debmatic-updaterffirmware.service ○ ├─pivccu-dkms.service ● ├─system.slice ● └─sysinit.target ● ├─apparmor.service ● ├─dev-hugepages.mount ● ├─dev-mqueue.mount ● ├─keyboard-setup.service ● ├─kmod-static-nodes.service ● ├─proc-sys-fs-binfmt_misc.automount ● ├─sys-fs-fuse-connections.mount ● ├─sys-kernel-config.mount ● ├─sys-kernel-debug.mount ● ├─sys-kernel-tracing.mount ● ├─systemd-ask-password-console.path ● ├─systemd-binfmt.service ○ ├─systemd-firstboot.service ● ├─systemd-journal-flush.service ● ├─systemd-journald.service ○ ├─systemd-machine-id-commit.service ● ├─systemd-modules-load.service ● ├─systemd-network-generator.service ○ ├─systemd-pcrphase-sysinit.service ○ ├─systemd-pcrphase.service ○ ├─systemd-pstore.service ● ├─systemd-random-seed.service ○ ├─systemd-repart.service ● ├─systemd-sysctl.service ● ├─systemd-sysusers.service ● ├─systemd-timesyncd.service ● ├─systemd-tmpfiles-setup-dev.service ● ├─systemd-tmpfiles-setup.service ● ├─systemd-udev-trigger.service ● ├─systemd-udevd.service ● ├─systemd-update-utmp.service ● ├─cryptsetup.target ● ├─integritysetup.target ● ├─local-fs.target ● │ ├─-.mount ● │ ├─boot-efi.mount ● │ ├─media-backup.mount ● │ ├─media-nextcloud.mount ○ │ ├─systemd-fsck-root.service ● │ └─systemd-remount-fs.service ● ├─swap.target ● │ └─dev-disk-by\x2duuid-7b127ff9\x2d9a0f\x2d4375\x2db0ad\x2db775293acce1.swap ● └─veritysetup.target
it's strange that lighttpd is running as www-data. This user is for apache2.
all files within /www are assigned to root:root
reboot tut gut.
Now I need to reset all devices and establish the new connections (party)