ctrlX CORE virtual stops working after some time

[Akseer]

Hi,

My ctrlX CORE virtual has stopped working three times during the evaluation of two days. When suddenly it stops working, it shows the device is online but prompts the error "The control is not responding". Once it stops responding, I can't shut down the controller by pressing the power OFF button as it continuously stucks at showing the state of "Shutting down".

The virtual instance remains in the state of not being able to turn ON/OFF even by restarting the ctrlX WORKS software. This issue is observed to be resolved either by eliminating the background process of QEMU software or by restarting the PC.

I would be pleased to know about the possible event that is triggering this error. Furthermore, I want to confirm if this issue is limited to the ctrlX CORE virtual only and can't happen with the actual ctrlX CORE.

ctrlX WORKS version: 1.12.9

[CodeShepherd]

Because of licensing reasons the ctrlX COREvirtual will only work for 4h and then automatically shuts itself down.

But of course it should not get stuck in this case. Can you please send me a system report of your control, so we can see what is installed and get some more information. And also in ctrlX WORKS a system report can be created also via "About".

ctrlX CORE web UI - generate system report 1.12

[Akseer]

Hi, please find attached the generated system report.

[CodeShepherd]

Could you please confirm if ctrlX COREvirtual is shutting down after the regular 4h or is it independent of this?

[Akseer]

This error is independent of the 4 hours session. So far, I have faced this error only three times, two times on one ctrlX virtual device and once on the newly created virtual device. I created the second device just to observe if there is anything unusual that is causing the error on the previous instance. For that purpose, I kept the running apps as same as those (Mosquitto, Node-RED, and VPN). It's been the last few days and I have not faced this issue again.

[Akseer]

Update:
I am sharing with you the generated "systemreport" from a different PC. This time the same error is observed on another PC I use and can be found from the ctrlx-works logs at "2022-08-19 13:19:30" time. On this ctrlX virtual, I have installed almost all the apps but before the appearance of this error, I was mainly working on Mosquitto and Node-RED apps.

The ctrlX virtual was not able to start even after closing the ctrlX WORKS and its some running background processes showing from the task manager. So, I had to restart the PC and then the ctrlX virtual started working normally.

[CodeShepherd · Accepted solution]

We could find the reason in the ctrlX WORKS logs you provided. Could you please switch the logbook in your ctrlX CORE to persistent and generate an system report of it after the crash (like you can see in my picture). Beware that system report in ctrlX WORKS is not the same then in the ctrlX CORE. It is collecting totally different data.

Could you explain what you are exactly doing with your ctrlX CORE? You could send us also a configuration (app data) of your control.

[Akseer · Accepted solution]

Hi @CodeShepherd,

Thanks for the response. It's been some time since this error was observed. I reinstalled complete packages to make sure all the apps are up-to-date by downloading from the collaboration room.

Since then, I have not seen this error. Due to the complete new installation, I don't have previous logs.

In my previous testing, I was using the Node-RED app to generate some random data and send this information to a broker. From the broker, I used some clients to understand the working of MQTT protocol-based communication.