PLCnext Stopped because fatal error

Hello, I was making some test withe the PLC AXC F 2152. The PLC has installed in it the following apps: PLCnextbot, BalenaEngine-Docker IOT-ARM, PLCnext Patch PndOff, IXON Cloud Connector. The PLC was working correctly after I installed the last App, which is Balena, after a reset the PLC its with the Orange LED inidcador in D. I can´t acces through the web server or the PLCnext Store so i can uninstall it. I tried to acces through PLCnext Engineer but I can’t access. Also I acces to then ftp server of PLCnext with the following log: 20.03.21 08:06:17.607 Arp.System.Acf.Internal.ApplicationBase FATAL - Fatal error occurs in application ‘MainProcess’: 20.03.21 08:06:17.608 Arp.System.Acf.Internal.ApplicationBase FATAL - Exception occurs: Exception of type ‘Arp::System::Commons::InvalidOperationException’ was thrown Could not start all processes at Arp::System::Acf::Internal::Sm::ProcessesController::StartProcesses() at Arp::System::Acf::Internal::Sm::SystemManager::SetupSystemSettings() at Arp::System::Acf::Internal::Sm::SystemManager::SetupSystem() at Arp::System::Acf::Internal::ApplicationBase::SetupBasicComponents(Arp::System::Acf::Internal::ApplicationSetupKind, Arp::System::Acf::Internal::ProcessKind) at Arp::System::Acf::Internal::ApplicationBase::Setup(Arp::System::Commons::Diagnostics::Logging::LogLevel, char const*) at Arp::System::Acf::Internal::ApplicationBase::Main(int, char**, Arp::System::Commons::Diagnostics::Logging::LogLevel) at Arp.System.Application(+0x2000c) [0x4c500c] at /lib/libc.so.6(__libc_start_main+0x97) [0xb66159a4] What can I do to solve this problem? I will appreciate your help.

Hello juanmejia, mostlikely this is caused by the apps that are setup to start via a demon synchronously to the PLCnext runtime. Usually these apps should only start after the PLCnext runtime. These tasks might block the PLCnext runtime for a long time and stop its correct execution. If you want to fix this you will have to take a look into the script files starting your apps. (mostlikely ixon and balena.) Adding a sleep 10 in the start commands before the actual binary or deamon call should give the FW enough time to boot without interruption. You can find the scripts at /etc/init.d In FW 2021.3 this timeoutbehavior of the plcnext FW will be adaptable. We try to improve our tests for app providers to check for errors due to sideffects of multiple apps working together. Also the app integration guide will take close attention to the start up sheduling and permissions of apps in the future. Related issue: Sampleruntime might crash at boot when an additional App is installed · Issue #13 · PLCnext/SampleRuntime · GitHub