"Serious problem detected"

[SDeath 68]

We can only hope.

[SDeath 68]

I guess not.

But then again if there can be different reasons for the cause, then I'd confirm something fixed with the one who reported it first, before marking it as fixed.

[jprobbe 0]

The same,
I created a ticket, gave the logs, gave access with port redirections.

The response yesterday from the suport:

 

"Please try update to 5.092.19 and check if that would resolve your issue?"

 

I think there is an internal communication problem regarding this issue...
 

[SmartLifeSystems 20]

6 hours ago, jprobbe said:

The same,
I created a ticket, gave the logs, gave access with port redirections.

The response yesterday from the suport:

 

"Please try update to 5.092.19 and check if that would resolve your issue?"

 

I think there is an internal communication problem regarding this issue...
 

 

The update don't resolved the problem...

[jprobbe 0]

8 hours ago, SmartLifeSystems said:

The update don't resolved the problem..

 

I know it well !
That's why I'm saying there is a communication problem with them ...

 

 

[SDeath 68]

Let's see if this helps:

Quote

 

Other
Stability improvements related to "Serious problem detected" notification.
Changed translation for "Serious problem detected" notification.

 

 

Edited January 21, 2022 by SDeath

[SmartHomeEddy 1,005]

Sounds like you get the same error with a different text ?

[SDeath 68]

40 minutes ago, SmartHomeEddy said:

Sounds like you get the same error with a different text ?

You are right they are just talking about the notification.
Let's hope they also mean the problem itself.

Edited January 21, 2022 by SDeath

[m.roszak 763]

Notification itself is clarified.
As for the issue itself, we have 3 major changes which should at least reduce the problem if it won't eliminate it completely. 

[SDeath 68]

Installed this morning. 
Let’s see how this goes.

[SDeath 68]

FYI:

The Error now reads: The system recovered from an unexpected error
And the explanation: The system was automatically rebooted due to the detection of an unexpected problem. Please contact support if the problem persists

[m.roszak 763]

Guys, is there any indications about the outcome?
We are hoping that this does not occur now. 


EDIT:
I mean on 5.093 beta  

[SDeath 68]

Not seen it yet, but only 4 days into the new version, so way too short to tell for sure if it doesn't happen anymore.
I need at least a month without the crash to maybe confirm and at least several months to be sure.
The crash happened with me between 2-14 days.

[petergebruers 1,268]

2 hours ago, m.roszak said:

Guys, is there any indications about the outcome?

Too soon to tell - with confidence. System up time: 5 days - that is since last boot, no crash, running 5.093. As Sdeath mentioned... Crash could happen after 14 days or even later in my case.

[m.roszak 763]

I will wait patiently then

[SDeath 68]

@m.roszak @A.Socha I think I had a reset on 5.100.22, but no message. But I can see the uptime is 3 hours now.
Installed 5.100.22 yesterday afternoon, about 22 hours ago.

Edited February 3, 2022 by SDeath

[m.roszak 763]

Have you got a notification about system error?

Something like:
Title: The system recovered from an unexpected error
Description: The system was automatically rebooted due to the detection of an unexpected problem. Please contact support if the problem persists.

Is it possible that it was restarted due power drop? 
We did not do anything to just remove this log, I assure you
 

[SDeath 68]

1 minute ago, m.roszak said:

Have you got a notification about system error?

Something like:
Title: The system recovered from an unexpected error
Description: The system was automatically rebooted due to the detection of an unexpected problem. Please contact support if the problem persists.

Is it possible that it was restarted due power drop? 
We did not do anything to just remove this log, I assure you
 

No message at all.
And no power outage either.
It's inside a rack and all network equipment is running fine and hasn't been rebooted.

Please login or register to see this attachment.

[SDeath 68]

Part of the log file, the red lines are the time it reset and the only things I can see out of the ordinary.
I have a full logDump available if you'd like.
 

Feb  3 11:54:53 HC3-00000000 HCServer[4598]: 10:54:53:344475#033[1;32m [Error] #011LOADER: [setProperty @Device.cpp:1575] [Device::setProperty] deviceId=<293> propertyName=<unit> device property doesn't exist, update ignored #033[0m
Feb  3 11:54:55 HC3-00000000 HCServer[4598]: 10:54:55:343154#033[1;32m [Error] #011LOADER: [setProperty @Device.cpp:1575] [Device::setProperty] deviceId=<293> propertyName=<unit> device property doesn't exist, update ignored #033[0m
Feb  3 11:54:57 HC3-00000000 HCServer[4598]: 10:54:57:342112#033[1;32m [Error] #011LOADER: [setProperty @Device.cpp:1575] [Device::setProperty] deviceId=<293> propertyName=<unit> device property doesn't exist, update ignored #033[0m
Feb  3 11:55:00 HC3-00000000 HCServer[4598]: *** Error in `/opt/fibaro/HCServer': corrupted double-linked list: 0x0000ffff340dda30 ***
Feb  3 11:55:15 HC3-00000000 HCServer[3659]: 10:55:15:780251#033[1;32m [Error] #011LOADER: [operator() @Home.cpp:210] Invalid main energy meter value:  #033[0m
Feb  3 11:55:16 HC3-00000000 HCServer[3659]: 10:55:16:100006#033[1;32m [Error] #011LOADER: [getInterfaces @DeviceService.cpp:536] XML: reading interface error:No such node (device.interfaces) #033[0m
Feb  3 11:55:16 HC3-00000000 HCServer[3659]: 10:55:16:114691#033[1;32m [Error] #011LOADER: [parseUI @DeviceService.cpp:183] Cannot find config xml file for device type: com.fibaro.denonHeosGroup #033[0m
Feb  3 11:55:16 HC3-00000000 HCServer[3659]: 10:55:16:145697#033[1;32m [Error] #011LOADER: [parseUI @DeviceService.cpp:183] Cannot find config xml file for device type: com.fibaro.logitechHarmonyActivity #033[0m
Feb  3 11:55:16 HC3-00000000 HCServer[3659]: 10:55:16:146512#033[1;32m [Error] #011LOADER: [parseUI @DeviceService.cpp:183] Cannot find config xml file for device type: com.fibaro.logitechHarmonyHub #033[0m
Feb  3 11:55:16 HC3-00000000 HCServer[3659]: 10:55:16:153757#033[1;32m [Error] #011LOADER: [parseUI @DeviceService.cpp:183] Cannot find config xml file for device type: com.fibaro.nuvoZone #033[0m
Feb  3 11:55:16 HC3-00000000 HCServer[3659]: 10:55:16:157263#033[1;32m [Error] #011LOADER: [parseUI @DeviceService.cpp:183] Cannot find config xml file for device type: com.fibaro.philipsHueLight #033[0m
Feb  3 11:55:16 HC3-00000000 HCServer[3659]: 10:55:16:159321#033[1;32m [Error] #011LOADER: [parseUI @DeviceService.cpp:183] Cannot find config xml file for device type: com.fibaro.pko #033[0m

Edited February 3, 2022 by SDeath

[m.roszak 763]

Please MP full logs dump, I will forward this to the developers.

Looks like system actually crashed but not on low level (which triggers notification mentioned before).
This is not related with "serious problem detected" issue, so that is good.
Bad thing - it happened (crash).