Open philipa opened 2 years ago
Can you mention which devices are attached, or enable VRM + Remote Support + internet access and which site this is about. Without more details / a reproducer, it is not possible to fix this.
Thanka for picking up on this. The site id is 113424
I've enabled remote access. Do I need to set up an account for you?
Hi, this is a modified gui, you need to ask that here, https://community.victronenergy.com/spaces/31/index.html.
Sorry, I should have mentioned that. I have previously reproduced the problem without the gui modifications.
I'll uninstall the modifications and report back when the problem happens again.
If you know how to reproduce that with a standard install, please let us know and we will look into that.
The problem has repeated a few times a day without the gui modifications.
I've left the modifications uninstalled and the site remains available for remote support over VRM.
@jhofstee I can't re-open this ticket, should I open a new one?
Opened #955.
@mpvader @jhofstee, I'd be grateful if someone could grab whatever diagnostics are useful so I can disable remote support. Also, the system is on a travelling yacht, so connectivity can be patchy.
Hi @philipa , yes we have the diagnostics; thanks! You're welcome to close the Remote Support if you want to.
Its not an easy thing to solve by the way, hard to reproduce, and seems rather deep down in a third party library we use.
Thanks @mpvader.
I'll reconfigure the system, but let me know if you need access again. Happy to help if I can.
Hi @philipa : is this still happening to your system? We havent, at least not as far as I know, explicitly fixed it. But then again we also never explicitly broke something: the current theory is that this is some bug that already resided deep down in the Qt library. And now triggered due to some unrelated change we made somewhere.
Yes, still occurring regularly with v2.89.
It seems strange that no one else is reporting it.
Probably goes mostly unnoticed. Though I did get other reports as well. And thanks for reminding me that its on versions prior to v2.90 as well! So at least its not a blocker for releasing v2.90
Any progress on this? It's still happening with 2.92. I'm reminded every evening when I see the display restart in the corner of the cabin.
I'd be happy to deploy debug builds to track this down, or help how
Hello,
i've detected the same issue on my Cerbo GX. I've updated to the latest version 2.94 but the issue is still there.
Do you have any updates on this?
Here some entries from the last four days:
messages.5:Jun 9 04:56:26 einstein user.info kernel: [1555307.044409] potentially unexpected fatal signal 11.
messages.5:Jun 9 14:34:40 einstein user.info kernel: [1590000.341490] potentially unexpected fatal signal 11.
messages.5:Jun 9 16:20:52 einstein user.info kernel: [1596372.692552] potentially unexpected fatal signal 11.
messages.4:Jun 9 18:31:23 einstein user.info kernel: [1604203.111487] potentially unexpected fatal signal 11.
messages.4:Jun 9 21:13:55 einstein user.info kernel: [1613955.359497] potentially unexpected fatal signal 11.
messages.4:Jun 9 23:44:30 einstein user.info kernel: [1622989.914503] potentially unexpected fatal signal 11.
messages.3:Jun 10 02:59:29 einstein user.info kernel: [1634688.625935] potentially unexpected fatal signal 11.
messages.3:Jun 10 05:40:53 einstein user.info kernel: [1644372.465185] potentially unexpected fatal signal 11.
messages.3:Jun 10 08:23:06 einstein user.info kernel: [1654104.946154] potentially unexpected fatal signal 11.
messages.3:Jun 10 10:38:38 einstein user.info kernel: [1662237.154165] potentially unexpected fatal signal 11.
messages.2:Jun 10 14:55:31 einstein user.info kernel: [1677649.698713] potentially unexpected fatal signal 11.
messages.2:Jun 10 17:14:50 einstein user.info kernel: [1686009.050445] potentially unexpected fatal signal 11.
messages.2:Jun 10 20:13:38 einstein user.info kernel: [1696736.288597] potentially unexpected fatal signal 11.
messages.2:Jun 10 22:31:28 einstein user.info kernel: [1705006.080807] potentially unexpected fatal signal 11.
messages.2:Jun 11 01:02:12 einstein user.info kernel: [1714050.748313] potentially unexpected fatal signal 11.
messages.1:Jun 11 04:41:40 einstein user.info kernel: [1727217.987286] potentially unexpected fatal signal 11.
messages.1:Jun 11 07:34:08 einstein user.info kernel: [1737565.532092] potentially unexpected fatal signal 11.
messages.1:Jun 11 09:37:26 einstein user.info kernel: [1744961.160222] potentially unexpected fatal signal 11.
messages.0:Jun 11 12:25:37 einstein user.info kernel: [1755054.223897] potentially unexpected fatal signal 11.
messages.0:Jun 11 15:53:56 einstein user.info kernel: [1767553.286626] potentially unexpected fatal signal 11.
messages.0:Jun 11 18:54:23 einstein user.info kernel: [1778380.780260] potentially unexpected fatal signal 11.
messages.0:Jun 11 22:14:12 einstein user.info kernel: [1790369.113086] potentially unexpected fatal signal 11.
messages.0:Jun 12 01:29:51 einstein user.info kernel: [1802107.840382] potentially unexpected fatal signal 11.
messages.0:Jun 12 04:49:54 einstein user.info kernel: [1814110.486705] potentially unexpected fatal signal 11.
messages.0:Jun 12 07:35:27 einstein user.info kernel: [1824043.470034] potentially unexpected fatal signal 11.
messages:Jun 12 10:20:54 einstein user.info kernel: [1833970.232015] potentially unexpected fatal signal 11.
messages:Jun 12 12:57:41 einstein user.info kernel: [1843377.525065] potentially unexpected fatal signal 11.
Perhaps it's related to this: https://community.victronenergy.com/questions/131941/touch-gx-and-i-assume-cerbo-rebooting.html
Because I'm also using the Ruuvi tags with an additional bluetooth dongle.
Cerbo GX, running Venus 2.84.
The GUI restarts a few times a day. The following is logged:
Looks similar to #143.
It happens when the system is quiet (no heavy loads etc.) and no one is touching the screen.
I don't recall this happening before 2.84.