search

jens-maus / RaspberryMatic

:house: A feature-rich but lightweight, buildroot-based Linux operating system alternative for your CloudFree CCU3/ELV-Charly 'homematicIP CCU' IoT smarthome central. Running as a pure virtual appliance (ProxmoxVE, Home Assistant, LXC, Docker/OCI, Kubernetes/K8s, etc.) on a dedicated embedded device (RaspberryPi, etc.) or generic x86/ARM hardware.
https://raspberrymatic.de
Apache License 2.0
1.54k stars 188 forks source link

v3.45.7.20190511 - hsd485d constantly restarts #627

Closed r4m3u5 closed 5 years ago

r4m3u5 commented 5 years ago

Describe the bug hsd485d constantly restarts

To Reproduce Steps to reproduce the behavior:

  1. install v3.45.7.20190511
  2. watch hs485d crashing

Expected behavior stable hs485d

Screenshots

image

System information (please complete the following information):

Additional context Downgrade to an earlier version doesn't seem to be possible in that state.

BOFH90 commented 5 years ago

Same here. My wired-gateway is not connected after the upgrade.

jens-maus commented 5 years ago

Then please check the content of /var/log/messages and see which reason it outputs for restarting hs485d.

r4m3u5 commented 5 years ago

A bit more detail from /var/log/messages:

# cat /var/log/messages | grep hs485
May 11 18:19:24 homematic-ccu2-2 user.err monit[911]: 'hs485d' failed protocol test [DEFAULT] at [localhost]:32000 [TCP/IP] -- Connection refused
May 11 18:19:24 homematic-ccu2-2 user.info monit[911]: 'hs485d' trying to restart
May 11 18:19:24 homematic-ccu2-2 user.info monit[911]: 'hs485d' restart: '/etc/init.d/S60hs485d restart'
May 11 18:19:24 homematic-ccu2-2 user.info hs485d: Using configuration file: /var/etc/hs485d.conf
May 11 18:19:26 homematic-ccu2-2 user.err hs485d: UnifiedLanCommController::connect(): Could not connect.
May 11 18:19:27 homematic-ccu2-2 user.crit hs485d: Could not connect to HomeMatic Lan Gateway with IP Address 192.168.222.171
May 11 18:19:42 homematic-ccu2-2 user.err monit[911]: 'hs485d' service restarted 1 times within 1 cycles(s) - exec
May 11 18:19:42 homematic-ccu2-2 user.info monit[911]: 'hs485d' exec: '/bin/triggerAlarm.tcl hs485d restarted WatchDog-Alarm'
May 11 18:19:42 homematic-ccu2-2 user.info monit[911]: 'hs485d' process is running after previous restart timeout (manually recovered?)
May 11 18:20:00 homematic-ccu2-2 user.err monit[911]: 'hs485d' failed protocol test [DEFAULT] at [localhost]:32000 [TCP/IP] -- Connection refused
May 11 18:20:00 homematic-ccu2-2 user.info monit[911]: 'hs485d' trying to restart
May 11 18:20:00 homematic-ccu2-2 user.info monit[911]: 'hs485d' restart: '/etc/init.d/S60hs485d restart'
May 11 18:20:00 homematic-ccu2-2 user.info hs485d: Using configuration file: /var/etc/hs485d.conf
May 11 18:20:02 homematic-ccu2-2 user.err hs485d: UnifiedLanCommController::connect(): Could not connect.
May 11 18:20:03 homematic-ccu2-2 user.crit hs485d: Could not connect to HomeMatic Lan Gateway with IP Address 192.168.222.171
May 11 18:20:18 homematic-ccu2-2 user.err monit[911]: 'hs485d' service restarted 1 times within 1 cycles(s) - exec
May 11 18:20:18 homematic-ccu2-2 user.info monit[911]: 'hs485d' exec: '/bin/triggerAlarm.tcl hs485d restarted WatchDog-Alarm'
May 11 18:20:18 homematic-ccu2-2 user.info monit[911]: 'hs485d' process is running after previous restart timeout (manually recovered?)
jens-maus commented 5 years ago

Well, obviously hs485d cannot connect to your LAN gateway with the IP 192.168.222.171

r4m3u5 commented 5 years ago

@jens-maus

Pretty sure I'm having a Déjà-vu here ...didn't we have the same problem a few versions in the past as well? I can't remember what the fix was though ... darn ...

r4m3u5 commented 5 years ago

Yeah well, no issue with v3.45.7.20190504 and I've got it on 2 different RPIs with different gateways.

BOFH90 commented 5 years ago

same here, works after a downgrade. tested on 2 different systems

# cat /var/log/messages | grep hs485
May 11 19:07:50 RPI3-CCU-2 user.info monit[911]: 'hs485d' process is running after previous restart timeout (manually recovered?)
May 11 19:08:08 RPI3-CCU-2 user.err monit[911]: 'hs485d' failed protocol test [DEFAULT] at [localhost]:32000 [TCP/IP] -- Connection refused
May 11 19:08:08 RPI3-CCU-2 user.info monit[911]: 'hs485d' trying to restart
May 11 19:08:08 RPI3-CCU-2 user.info monit[911]: 'hs485d' restart: '/etc/init.d/S60hs485d restart'
May 11 19:08:12 RPI3-CCU-2 user.err hs485d: UnifiedLanCommController::connect(): Could not connect.
May 11 19:08:13 RPI3-CCU-2 user.crit hs485d: Could not connect to HomeMatic Lan Gateway with IP Address 10.0.6.21
May 11 19:08:26 RPI3-CCU-2 user.err monit[911]: 'hs485d' service restarted 1 times within 1 cycles(s) - exec
May 11 19:08:26 RPI3-CCU-2 user.info monit[911]: 'hs485d' exec: '/bin/triggerAlarm.tcl hs485d restarted WatchDog-Alarm'
May 11 19:08:26 RPI3-CCU-2 user.info monit[911]: 'hs485d' process is running after previous restart timeout (manually recovered?)
May 11 19:08:44 RPI3-CCU-2 user.err monit[911]: 'hs485d' failed protocol test [DEFAULT] at [localhost]:32000 [TCP/IP] -- Connection refused
May 11 19:08:44 RPI3-CCU-2 user.info monit[911]: 'hs485d' trying to restart
May 11 19:08:44 RPI3-CCU-2 user.info monit[911]: 'hs485d' restart: '/etc/init.d/S60hs485d restart'
May 11 19:08:48 RPI3-CCU-2 user.err hs485d: UnifiedLanCommController::connect(): Could not connect.
May 11 19:08:49 RPI3-CCU-2 user.crit hs485d: Could not connect to HomeMatic Lan Gateway with IP Address 10.0.6.21
May 11 19:09:02 RPI3-CCU-2 user.err monit[911]: 'hs485d' service restarted 1 times within 1 cycles(s) - exec
May 11 19:09:02 RPI3-CCU-2 user.info monit[911]: 'hs485d' exec: '/bin/triggerAlarm.tcl hs485d restarted WatchDog-Alarm'
May 11 19:09:02 RPI3-CCU-2 user.info monit[911]: 'hs485d' process is running after previous restart timeout (manually recovered?)
May 11 19:09:20 RPI3-CCU-2 user.err monit[911]: 'hs485d' failed protocol test [DEFAULT] at [localhost]:32000 [TCP/IP] -- Connection refused
May 11 19:09:20 RPI3-CCU-2 user.info monit[911]: 'hs485d' trying to restart
May 11 19:09:20 RPI3-CCU-2 user.info monit[911]: 'hs485d' restart: '/etc/init.d/S60hs485d restart'
May 11 19:09:24 RPI3-CCU-2 user.err hs485d: UnifiedLanCommController::connect(): Could not connect.
May 11 19:09:25 RPI3-CCU-2 user.crit hs485d: Could not connect to HomeMatic Lan Gateway with IP Address 10.0.6.21
jens-maus commented 5 years ago

Please state which Pi Models you use for your tests.

BOFH90 commented 5 years ago

I tested with an Raspberry Pi 3B (non plus)

mifricke commented 5 years ago

In my case it is a rpi3B ( non +).

jens-maus commented 5 years ago

Ok, then this could be the issue. Already building a version with a downgraded kernel for you guys to test. I will send you the link for the test, so please keep tuned so that you can test it quickly and give feedback accordingly so that I can replace the current rpi3 image.

r4m3u5 commented 5 years ago

Both of them RPi2ModB

jens-maus commented 5 years ago

Ok, so please try the following alternative *-rpi3.zip archive potentially fixing the issue:

https://cloud.light-speed.de/s/goMg97A3sKkcmJk/download

mifricke commented 5 years ago

This version is working! Thank you very much for this testing release!

jens-maus commented 5 years ago

Ok, thanks for the tests. I just replaced the official -rpi3.zip file so that this version should work again:

https://github.com/jens-maus/RaspberryMatic/releases/download/3.45.7.20190511/RaspberryMatic-3.45.7.20190511-rpi3.zip

Just make sure that the file has the following sha256 checksum: 8a03c490b39f6ade0d04d706b14083b2975ede1320f8ea21bdf35e20ed08f29a

r4m3u5 commented 5 years ago

Can confirm that it works well with the fix version.

Thanks Jens! Have a good one.

jens-maus commented 5 years ago

9321d5b9bd0d45091468a3b4c5170cac8bb0cc8e fixes the issue.