Homegear Crashing at night

#1

I don’t know if I should start a new topic (I’ve been the only one creating topics lately!) but now I have an issue of homegear crashing, usually during the night…
Here is the log from last night, where it crashed at 4:38, and I restarted it manually at 7:15…

05/07/19 04:35:33.426 IPC Server: Error: No or invalid response received to RPC request. Method: broadcastEvent
05/07/19 04:35:25.501 MAX packet received (max-cube, RSSI: 0x50): 0900060400000000000D
05/07/19 04:35:35.392 IPC Server: Info: Connection accepted. Client number: 148
05/07/19 04:35:37.618 IPC Server: Error: No or invalid response received to RPC request. Method: broadcastEvent
05/07/19 04:35:38.082 IPC Server: Error calling "broadcastEvent" on client 79: No response received.
05/07/19 04:35:38.083 IPC Server: Info: Client 81 successfully registered RPC method "managementGetCommandStatus" (this method is registered by 2 client(s)).
05/07/19 04:35:38.083 IPC Server: Error calling "broadcastEvent" on client 79: No response received.
05/07/19 04:35:48.079 IPC Server: Info: Connection accepted. Client number: 150
05/07/19 04:35:48.770 IPC Server: Info: Client 82 successfully registered RPC method "managementGetCommandStatus" (this method is registered by 3 client(s)).
05/07/19 04:35:58.963 IPC Server: Info: Connection accepted. Client number: 151
05/07/19 04:36:09.757 IPC Server: Info: Connection accepted. Client number: 152
05/07/19 04:35:55.757 MAX packet received (max-cube, RSSI: 0x50): 0900060400000000000D
05/07/19 04:36:09.804 MAX packet received (max-cube, RSSI: 0x39): 0CDC0442182F821B8F5C0022B9
05/07/19 04:36:18.711 IPC Server: Info: IPC client 79 removed.
05/07/19 04:36:20.574 IPC Server: Info: Connection accepted. Client number: 154
05/07/19 04:36:33.284 IPC Server: Info: Connection accepted. Client number: 155
05/07/19 04:36:33.383 MQTT Client: Error: No PINGRESP received.
05/07/19 04:36:43.385 IPC Server: Info: Client 83 successfully registered RPC method "managementGetCommandStatus" (this method is registered by 4 client(s)).
05/07/19 04:36:46.904 IPC Server: Info: Connection accepted. Client number: 157
05/07/19 04:36:48.748 IPC Server: Info: Client 84 successfully registered RPC method "managementGetCommandStatus" (this method is registered by 5 client(s)).
05/07/19 04:37:01.944 IPC Server: Info: Connection accepted. Client number: 159
05/07/19 04:37:04.239 IPC Server: Info: Client 86 successfully registered RPC method "managementGetCommandStatus" (this method is registered by 6 client(s)).
05/07/19 04:37:06.643 IPC Server: Error: IPC client with ID 80 is not responding... Closing connection.
05/07/19 04:37:09.157 IPC Server: Error: No or invalid response received to RPC request. Method: broadcastEvent
05/07/19 04:37:10.931 IPC Server: Info: Client 85 successfully registered RPC method "managementGetCommandStatus" (this method is registered by 6 client(s)).
05/07/19 04:37:13.631 IPC Server: Info: Connection accepted. Client number: 162
05/07/19 04:37:14.586 MQTT Client: Error: Connection to MQTT server with protocol version 3 failed.
05/07/19 04:37:16.682 Critical: Physical interface's (max-cube) lifetick was not updated for more than 60 seconds.
05/07/19 04:37:17.515 Critical: Killing child process.
05/07/19 04:37:18.214 Info: Process with id 2786 ended.
05/07/19 04:37:18.215 Homegear was terminated. Restarting (1)...
05/07/19 04:37:28.298 Homegear was terminated. Restarting (2)...
05/07/19 04:37:28.991 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
05/07/19 04:37:28.992 Info: Core file size now is "4294967295".
05/07/19 04:37:28.992 Info: Setting maximum thread priority to "0" for user with id 0 and group with id 0.
05/07/19 04:37:28.993 Info: Maximum thread priority now is "0".
05/07/19 04:37:29.697 Info: Backing up database...
05/07/19 04:37:30.112 Initializing database...
05/07/19 04:37:30.353 Info: Loading family module (type 1) mod_sonos.so
05/07/19 04:37:30.968 Info: Loading settings from /etc/homegear/families/sonos.conf
05/07/19 04:37:31.336 Info: Loading family module (type 1) mod_beckhoff.so
05/07/19 04:37:31.404 Info: Loading settings from /etc/homegear/families/beckhoff.conf
05/07/19 04:37:31.485 Module Beckhoff: Error in file Interfaces.cpp line 45 in function virtual void MyFamily::Interfaces::create(): The provided hostname is empty.
05/07/19 04:37:31.500 Info: Loading family module (type 1) mod_homematicwired.so
05/07/19 04:37:31.607 Info: Loading settings from /etc/homegear/families/homematicwired.conf
05/07/19 04:37:31.626 Info: Loading family module (type 1) mod_homematicbidcos.so
05/07/19 04:37:31.816 Info: Loading settings from /etc/homegear/families/homematicbidcos.conf
05/07/19 04:37:31.916 Info: Loading family module (type 1) mod_philipshue.so
05/07/19 04:37:32.019 Info: Loading settings from /etc/homegear/families/philipshue.conf
05/07/19 04:37:32.087 Info: Loading family module (type 1) mod_ipcam.so
05/07/19 04:37:32.233 Info: Loading settings from /etc/homegear/families/ipcam.conf
05/07/19 04:37:32.413 Info: Loading family module (type 1) mod_max.so
05/07/19 04:37:32.531 Info: Loading settings from /etc/homegear/families/max.conf
05/07/19 04:37:32.568 Info: Loading family module (type 1) mod_enocean.so
05/07/19 04:37:32.668 Info: Loading settings from /etc/homegear/families/enocean.conf
05/07/19 04:37:32.698 Info: Loading family module (type 1) mod_knx.so
05/07/19 04:37:32.865 Info: Loading settings from /etc/homegear/families/knx.conf
05/07/19 04:37:32.881 Info: Loading family module (type 1) mod_intertechno.so
05/07/19 04:37:32.932 Info: Loading settings from /etc/homegear/families/intertechno.conf
05/07/19 04:37:32.971 Info: Loading family module (type 1) mod_insteon.so
05/07/19 04:37:33.071 Info: Loading settings from /etc/homegear/families/insteon.conf
05/07/19 04:37:33.104 Info: Loading family module (type 1) mod_miscellaneous.so
05/07/19 04:37:33.273 Info: Loading settings from /etc/homegear/families/miscellaneous.conf
05/07/19 04:37:33.275 Info: Loading family module (type 1) mod_ccu.so
05/07/19 04:37:33.350 Info: Loading settings from /etc/homegear/families/ccu.conf
05/07/19 04:37:33.355 Info: Loading family module (type 1) mod_kodi.so
05/07/19 04:37:33.436 Info: Loading settings from /etc/homegear/families/kodi.conf
05/07/19 04:37:33.449 Info: Loading family module (type 1) mod_zwave.so
05/07/19 04:37:34.049 Info: Loading settings from /etc/homegear/families/z-wave.conf
05/07/19 04:37:34.445 Info: Loading family module (type 1) mod_mbus.so
05/07/19 04:37:34.493 Info: Loading settings from /etc/homegear/families/m-bus.conf
05/07/19 04:37:34.520 Info: Setting up physical interfaces and GPIOs...
05/07/19 04:37:34.619 Info: Dropping privileges to user homegear (1000) and group homegear (1000)
05/07/19 04:37:34.679 Info: Homegear is (now) running as user with id 1000 and group with id 1000.
05/07/19 04:37:35.424 Starting script engine server...
05/07/19 04:37:35.682 Initializing licensing controller...
05/07/19 04:37:35.683 Loading licensing controller data...
05/07/19 04:37:35.684 Loading devices...
05/07/19 04:37:35.686 Loading XML RPC devices...
05/07/19 04:37:39.723 Loading device 1
05/07/19 04:37:40.275 Module HomeMatic BidCoS: Info: Central address set to 0xFDD019.
05/07/19 04:37:40.452 Loading XML RPC devices...
05/07/19 04:37:40.955 Loading device 2
05/07/19 04:37:40.993 Loading XML RPC devices...
05/07/19 04:37:41.110 Loading device 3
05/07/19 04:37:41.185 Loading XML RPC devices...
05/07/19 04:37:41.701 Loading device 4
05/07/19 04:37:41.959 Module MAX: Info: Central address set to 0xFD1111.
05/07/19 04:37:42.045 Module MAX: Loading MAX! peer 1
05/07/19 04:37:46.730 Module MAX: Loading MAX! peer 2
05/07/19 04:37:48.113 Module MAX: Loading MAX! peer 3
05/07/19 04:37:48.568 Module MAX: Loading MAX! peer 4
05/07/19 04:37:48.635 Module MAX: Loading MAX! peer 5
05/07/19 04:37:48.794 Module MAX: Loading MAX! peer 6
05/07/19 04:37:48.851 Module MAX: Loading MAX! peer 7
05/07/19 04:37:48.914 Module MAX: Loading MAX! peer 8
05/07/19 04:37:48.958 Module MAX: Loading MAX! peer 9
05/07/19 04:37:49.021 Module MAX: Loading MAX! peer 10
05/07/19 04:37:49.358 Info: Not initializing device family Philips hue, because it is disabled in it's configuration file.
05/07/19 04:37:50.366 Info: Disposing family module mod_philipshue.so
05/07/19 04:37:51.644 Loading XML RPC devices...
05/07/19 04:37:57.162 Loading device 5
05/07/19 04:37:59.929 Loading XML RPC devices...
05/07/19 04:38:01.139 Warning: Unknown parameter property: label
05/07/19 04:38:01.831 Warning: Unknown parameter property: label
05/07/19 04:38:02.433 Loading device 6
05/07/19 04:38:02.692 Loading XML RPC devices...
05/07/19 04:38:03.608 Loading device 7
05/07/19 04:38:04.037 Loading XML RPC devices...
05/07/19 04:38:04.407 Warning: Unknown parameter property: label
05/07/19 04:38:04.505 Warning: Unknown parameter property: label
05/07/19 04:38:04.516 Warning: Unknown parameter property: label
05/07/19 04:38:04.517 Warning: Unknown parameter property: label
05/07/19 04:38:04.531 Warning: Unknown parameter property: label
05/07/19 04:38:04.532 Warning: Unknown parameter property: label
05/07/19 04:38:04.556 Warning: Unknown parameter property: label
05/07/19 04:38:04.557 Warning: Unknown parameter property: label
05/07/19 04:38:04.567 Warning: Unknown parameter property: label
05/07/19 04:38:04.567 Warning: Unknown parameter property: label
05/07/19 04:38:04.587 Warning: Unknown parameter property: label
05/07/19 04:38:04.588 Warning: Unknown parameter property: label
05/07/19 04:38:04.599 Warning: Unknown parameter property: label
05/07/19 04:38:04.600 Warning: Unknown parameter property: label
05/07/19 04:38:04.605 Warning: Unknown parameter property: label
05/07/19 04:38:04.606 Warning: Unknown parameter property: label
05/07/19 04:38:04.631 Warning: Unknown parameter property: label
05/07/19 04:38:04.632 Warning: Unknown parameter property: label
05/07/19 04:38:04.650 Warning: Unknown parameter property: label
05/07/19 04:38:04.650 Warning: Unknown parameter property: label
05/07/19 04:38:04.668 Loading device 8
05/07/19 04:38:04.743 Loading XML RPC devices...
05/07/19 04:38:04.745 Loading device 9
05/07/19 04:38:04.860 Loading XML RPC devices...
05/07/19 04:38:06.883 Loading device 10
05/07/19 04:38:07.732 Loading XML RPC devices...
05/07/19 04:38:09.408 Loading device 11
05/07/19 04:38:11.036 Loading XML RPC devices...
05/07/19 04:38:15.709 Loading device 12
05/07/19 04:38:18.154 Loading XML RPC devices...
05/07/19 04:38:19.333 Loading device 13
05/07/19 04:38:22.105 Info: Not initializing device family CCU, because it is disabled in it's configuration file.
05/07/19 04:38:22.526 Info: Disposing family module mod_ccu.so
05/07/19 04:38:23.029 Loading XML RPC devices...
05/07/19 04:38:29.615 Loading device 14
05/07/19 04:38:31.808 Initializing RPC client...
05/07/19 04:38:33.039 Starting MQTT client...
05/07/19 04:38:36.537 Starting XML RPC server FamilyRPCServer listening on :::2000...
05/07/19 04:38:43.413 MQTT Client: Info: Successfully connected to MQTT server using protocol version 4.
05/07/19 04:38:43.600 Info: Subscribing to topic homegear/climate/rpc/#
05/07/19 04:38:43.705 Signal 11 received.
05/07/19 04:38:57.587 Info: Process with id 3438 ended.
05/07/19 04:38:57.776 Warning: Pipe to child process closed.
05/07/19 04:38:57.791 Error: Core was dumped.
05/07/19 04:38:57.792 Homegear was terminated. Restarting (1)...
05/07/19 04:39:08.895 Homegear was terminated. Restarting (2)...
05/07/19 04:39:09.473 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
05/07/19 04:39:09.474 Info: Core file size now is "4294967295".
05/07/19 04:39:09.474 Info: Setting maximum thread priority to "0" for user with id 0 and group with id 0.
05/07/19 04:39:09.474 Info: Maximum thread priority now is "0".
05/07/19 04:39:09.873 Info: Backing up database...
05/07/19 04:39:10.153 Initializing database...
05/07/19 04:39:10.294 Info: Loading family module (type 1) mod_sonos.so
05/07/19 04:39:10.803 Info: Loading settings from /etc/homegear/families/sonos.conf
05/07/19 04:39:10.991 Info: Loading family module (type 1) mod_beckhoff.so
05/07/19 04:39:11.017 Info: Loading settings from /etc/homegear/families/beckhoff.conf
05/07/19 04:39:11.033 Module Beckhoff: Error in file Interfaces.cpp line 45 in function virtual void MyFamily::Interfaces::create(): The provided hostname is empty.
05/07/19 04:39:11.035 Info: Loading family module (type 1) mod_homematicwired.so
05/07/19 04:39:11.081 Info: Loading settings from /etc/homegear/families/homematicwired.conf
05/07/19 04:39:11.089 Info: Loading family module (type 1) mod_homematicbidcos.so
05/07/19 04:39:11.160 Info: Loading settings from /etc/homegear/families/homematicbidcos.conf
05/07/19 04:39:11.215 Info: Loading family module (type 1) mod_philipshue.so
05/07/19 04:39:11.281 Info: Loading settings from /etc/homegear/families/philipshue.conf
05/07/19 04:39:11.308 Info: Loading family module (type 1) mod_ipcam.so
05/07/19 04:39:11.378 Info: Loading settings from /etc/homegear/families/ipcam.conf
05/07/19 04:39:11.450 Info: Loading family module (type 1) mod_max.so
05/07/19 04:39:11.513 Info: Loading settings from /etc/homegear/families/max.conf
05/07/19 04:39:11.527 Info: Loading family module (type 1) mod_enocean.so
05/07/19 04:39:11.612 Info: Loading settings from /etc/homegear/families/enocean.conf
05/07/19 04:39:11.625 Info: Loading family module (type 1) mod_knx.so
05/07/19 04:39:11.734 Info: Loading settings from /etc/homegear/families/knx.conf
05/07/19 04:39:11.741 Info: Loading family module (type 1) mod_intertechno.so
05/07/19 04:39:11.787 Info: Loading settings from /etc/homegear/families/intertechno.conf
05/07/19 04:39:11.842 Info: Loading family module (type 1) mod_insteon.so
05/07/19 04:39:11.894 Info: Loading settings from /etc/homegear/families/insteon.conf
05/07/19 04:39:11.912 Info: Loading family module (type 1) mod_miscellaneous.so
05/07/19 04:39:12.044 Info: Loading settings from /etc/homegear/families/miscellaneous.conf
05/07/19 04:39:12.048 Info: Loading family module (type 1) mod_ccu.so
05/07/19 04:39:12.175 Info: Loading settings from /etc/homegear/families/ccu.conf
05/07/19 04:39:12.182 Info: Loading family module (type 1) mod_kodi.so
05/07/19 04:39:12.252 Info: Loading settings from /etc/homegear/families/kodi.conf
05/07/19 04:39:12.256 Info: Loading family module (type 1) mod_zwave.so
05/07/19 04:39:12.703 Info: Loading settings from /etc/homegear/families/z-wave.conf
05/07/19 04:39:13.247 Info: Loading family module (type 1) mod_mbus.so
05/07/19 04:39:13.302 Info: Loading settings from /etc/homegear/families/m-bus.conf
05/07/19 04:39:13.361 Info: Setting up physical interfaces and GPIOs...
05/07/19 04:39:13.503 Info: Dropping privileges to user homegear (1000) and group homegear (1000)
05/07/19 04:39:13.693 Info: Homegear is (now) running as user with id 1000 and group with id 1000.
05/07/19 04:39:14.017 Starting script engine server...
05/07/19 04:39:14.135 Initializing licensing controller...
05/07/19 04:39:14.135 Loading licensing controller data...
05/07/19 04:39:14.135 Loading devices...
05/07/19 04:39:14.136 Loading XML RPC devices...
05/07/19 04:39:22.541 Loading device 1
05/07/19 04:39:25.541 Module HomeMatic BidCoS: Info: Central address set to 0xFDD019.
05/07/19 04:39:29.624 Loading XML RPC devices...
05/07/19 05:08:59.490 Loading device 2
05/07/19 05:09:52.625 Loading XML RPC devices...
05/07/19 05:17:48.978 Loading device 3
05/07/19 05:18:27.667 Loading XML RPC devices...
05/07/19 07:14:40.368 Starting Homegear...
05/07/19 07:14:40.372 Homegear version 0.7.37-2722
05/07/19 07:14:40.372 Git commit SHA of libhomegear-base: -
05/07/19 07:14:40.372 Git branch of libhomegear-base:     -
05/07/19 07:14:40.373 Git commit SHA of Homegear:         -
05/07/19 07:14:40.373 Git branch of Homegear:             -
05/07/19 07:14:40.373 Starting Homegear...
05/07/19 07:14:40.374 Homegear version 0.7.37-2722
05/07/19 07:14:40.374 Git commit SHA of libhomegear-base: -
05/07/19 07:14:40.374 Git branch of libhomegear-base:     -
05/07/19 07:14:40.375 Git commit SHA of Homegear:         -
05/07/19 07:14:40.375 Git branch of Homegear:             -
05/07/19 07:14:40.377 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
05/07/19 07:14:40.377 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
05/07/19 07:14:40.378 Info: Core file size now is "4294967295".
05/07/19 07:14:40.378 Info: Core file size now is "4294967295".
05/07/19 07:14:40.378 Info: Setting maximum thread priority to "0" for user with id 0 and group with id 0.
05/07/19 07:14:40.378 Info: Setting maximum thread priority to "0" for user with id 0 and group with id 0.
05/07/19 07:14:40.378 Info: Maximum thread priority now is "0".
05/07/19 07:14:40.378 Info: Maximum thread priority now is "0".
05/07/19 07:14:40.495 Info: Backing up database...
05/07/19 07:14:40.892 Initializing database...

any idea? I’m using the 0.7.37-2722 version in docker on a RPi

MQTT commands not received
#2

Feel free to open new topics. I think it’s better this way do differenciate between the issues.

@sathya Could you help here as I don’t have any idea…

#3

just to let you know, for example it happened again this night with the same symptoms (same log messages)
in order to try to analyze the issue: if I set up a homegear on another Pi or computer, can I connect it directly with the same parameters to the Cube, or do I need to repair everything?

#4

ok, I tried something new: I schedule via cron a restart of the docker container at 1am every night.
I haven’t checked the nights before, but today I had a chance to look at the log: even with the restart, I had a homegear crash at around 2:25am…
same thing the night before at around 2:35am…
I have no clue on what is going on, as far as I know, no specific action/process/script starting at that time

I’d give a try on another RPI, but only if I don’t have to repair the cube and the devices…

1 Like
#5

Hi @Ganfoud,

it’s not an error, it’s a feature ;-).

05/07/19 04:37:16.682 Critical: Physical interface’s (max-cube) lifetick was not updated for more than 60 seconds.

Homegear monitors if something is happening on the physical interfaces. Actually this feature is only used with init (as in Docker), so from my perspective it’s a deprecated feature. 60 seconds was definitely too short and it was not configurable. In the next nightly the lifetick timeout is increased to 15 minutes, which should be enough.

Cheers,

Sathya

1 Like