Coredump - docker - 0.7.48-3324

English Forums Bugs
#1

Hello Homegear Team/Developers,

I have got a spontaneous coredump received today morning.
I do not have anything special what could be the reason since I am using it since long time and no any previous dump is observed earlier.

This the last few messages prior to the coredump event is observed:

10/20/21 06:36:09.639 MAX packet received (nanoCUL, RSSI: 0x4C): 0E960202140EF5FD294200011B002A
10/20/21 06:36:09.646 Module MAX: Info: LOCKED on channel 1 of peer 8 with serial number MEQ1459638 was set to 0x00.
10/20/21 06:36:09.646 Module MAX: Info: SET_TEMPERATURE on channel 1 of peer 8 with serial number MEQ1459638 was set to 0x2A.
10/20/21 06:36:09.646 Module MAX: Info: VALVE_STATE on channel 1 of peer 8 with serial number MEQ1459638 was set to 0x00.
10/20/21 06:36:09.646 MQTT Client: MQTT Client Info: Publishing topic: hg/5756nc/plain/7/1/SET_TEMPERATURE
10/20/21 06:36:09.647 MQTT Client: MQTT Client Info: Publishing topic: hg/5756nc/plain/7/1/VALVE_STATE
10/20/21 06:36:09.647 MQTT Client: MQTT Client Info: Publishing topic: hg/5756nc/plain/8/0/RSSI_DEVICE
10/20/21 06:36:09.648 MQTT Client: MQTT Client Info: Publishing topic: hg/5756nc/plain/8/0/LOWBAT
10/20/21 06:36:09.678 Module MAX: CUL "nanoCUL": Info: Sending (nanoCUL, WOR: no): 0B960002FD2942140EF50000
10/20/21 06:36:09.679 MQTT Client: MQTT Client Info: Publishing topic: hg/5756nc/plain/8/1/LOCKED
10/20/21 06:36:09.680 MQTT Client: MQTT Client Info: Publishing topic: hg/5756nc/plain/8/1/SET_TEMPERATURE
10/20/21 06:36:09.680 MQTT Client: MQTT Client Info: Publishing topic: hg/5756nc/plain/8/1/VALVE_STATE
10/20/21 06:36:09.744 Module MAX: CUL "nanoCUL": Info: Sending (nanoCUL, WOR: yes): 0B960540FD2942140EF501EA
10/20/21 06:36:10.839 MAX packet received (nanoCUL, RSSI: 0x4B): 0E960202140EF5FD294200011B002A
10/20/21 06:36:10.839 Module MAX: Info: Queue 4547 is empty and there are no pending queues.
10/20/21 06:36:10.848 MQTT Client: MQTT Client Info: Publishing topic: hg/5756nc/plain/8/1/CONTROL_MODE
10/20/21 06:36:10.848 MQTT Client: Info: MQTT RPC call received. Method: setValue
10/20/21 06:36:10.848 RPC Server (Port 2001): Info: RPC Method called: setValue Parameters:
(Integer) 5
(Integer) 1
(String) CONTROL_MODE
(Integer) 3
10/20/21 06:36:10.878 Module MAX: CUL "nanoCUL": Info: Sending (nanoCUL, WOR: no): 0B970540FD2942140EF5016A
10/20/21 06:36:10.889 MQTT Client: MQTT Client Info: Publishing topic: hg/5756nc/plain/8/1/CONTROL_MODE
10/20/21 06:36:10.949 Module MAX: CUL "nanoCUL": Info: Sending (nanoCUL, WOR: yes): 0BAA0540FD29421AC12E01EA
10/20/21 06:36:10.967 MAX packet received (nanoCUL, RSSI: 0x4A): 0E970202140EF5FD2942000119172A
10/20/21 08:54:06.477 Starting Homegear...
10/20/21 08:54:06.477 Homegear version: 0.7.48-3324

Here are the logs and the core file:

Logs and core file

  • Could you kindly have a look into the details what could be the reason for that?

Anything else you might need for further checking kindly let me know and I will provide it for you.

Thanks a lot in advance
&
Regards
Tamás

#2

I am sorry, originally forgot to add the config files, now attached:
config.targz (8.0 KB)

#3

I have observed two more coredump recently. @sathya May I ask you to help me to figure out what could be wrong here?

Although this is not very critical since I can detect the crash and restart the docker container, it just would be good to know how to avoid this issue. :wink:

twomorecore.targz

Thanks a lot in advance
&
Kind Regards
Tmás

1 Like
#4

Hi @tamas2001,

thanks! The bug is fixed in the next nightly thanks to your Coredumps (the error is the same in all Dumps).

Cheers,

Sathya

1 Like
#5

Hi Sathya,

Thanks a lot for your effort on this.
I really appreciate it.

Best Regards
TAmás

#6

Hi @sathya ,

I wanted to apply your fix by using the nightly docker image.
It seems like Homegear could not start. I am getting the following error:

homegear: error while loading shared libraries: libexslt.so.0: cannot open shared object file: No such file or directory

Could you help how would be possible to fix that issue?

Thanks
&
Regards
TAmás

I just found this might be an already known issue according to my limited German knowledge:

I am sorry for noise here…
Best Regards

Tamás

#7

Hi @tamas2001,

yes, it’s a known issue. The webserver broke and we are using this “opportunity” to move our APT servers to a dedicated system right now. So it will take a few days until the nightly Docker images work again correctly. We are on it ;-).

Cheers,

Sathya

1 Like