Hello, so after 10 days my application didn't crashed, and the codesys runtime is still alive. So I confirm that the problem was really caused by the openned files limit, due to the missing close I had in my code. Problem solved ! 😄 Best regards.
Hi, I suppose I've found what's wrong, and it was in my codesys application... I really have a SysFileOpen with no SysFileClose that was called each minutes 😓... So it takes about 16 hours to reach the limit file count by process which is 1024 (command line ulimit -n to see the limit). I will run some tests, but I suppose it will be ok now... Best regards.
Dear Edwin, Thanks for your answer. I used Codesys for Raspberry SL. You're right, the runtime didn't stopped after 2 hours like I supposed and like indacated in the logs: Linux version 4.4.45-v7+ (root@bartosz-VirtualBox) (gcc version 4.8.3 20140106 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2014.01 - Linaro GCC 2013.11) ) #19 SMP Fri Feb 10 12:54:17 CET 2017 PlcStartSL[752]: fork child: ppid: 17444 7824 ********* CoDeSysControl DEMO VERSION - runs 2 hours********* PlcStart[205]: using /etc/CODESYSControl.cfg...
Hello, About after 16 hours of well execution, the runtime stops. In the codesyscontrol.log I can see the line: #### Exception: *EXCEPTION* in CommCycleHook <IP>0x76db7d6c</IP> <BP>0x1000</BP> <SP>0x73f63d38</SP> And just a few seconds later, the runtime stops. Like Edwin Schwellinger adviced in this topic (it seems to be a similar issue?) https://forge.codesys.com/forge/talk/Deutsch/thread/c8bb956c6b/?limit=25#3484 I tried to run Codesys manually via SSH. But the problem is that after 2hours it...