https://forge.codesys.com/forge/talk/Runtime/thread/92be148c24/2025-03-31T08:13:32.487000ZRecent posts to Codesys PFC200 Runtime, no log after reboot, can I get a Post-Mortem log?2025-03-31T08:13:32.487000Z2025-03-31T08:13:32.487000ZMadsKaizerhttps://forge.codesys.com/u/madskaizer/https://forge.codesys.com0814640a6130a3118b487e77cf8c0de5966d23ac

<div class="markdown_content"><p>Thank you, this came in handy a few years later :)</p></div>

2023-01-27T19:33:50.202000Z2023-01-27T19:33:50.202000Zdore2138https://forge.codesys.com/u/dore2138/https://forge.codesys.com4142c5f019416a0319a90d9250082c55b0f16280

<div class="markdown_content"><p>Hello eschwellinger,</p> <p>Thank you for the advice!</p> <p>The firmware was indeed 4.6.0.0 . I ran updates. I will check logs on regular basis for similar entries after the update. </p></div>

2023-01-27T14:02:17.508000Z2023-01-27T14:02:17.508000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comd2a979470c58efdcb384733a491ea98af24a207c

<div class="markdown_content"><p>on BeagleBone for sure solution is to update to 4.7.0.0 version, for this memory leak problem.</p></div>

2023-01-26T21:36:21.980000Z2023-01-26T21:36:21.980000Zdore2138https://forge.codesys.com/u/dore2138/https://forge.codesys.comd7028eb55e991243c69301d8c063a09321863ca4

<div class="markdown_content"><p>I experience the same phenomenon with the CODESYS Control for BeagleBone SL.<br/> After rebooting the controller, the softPLC works again.<br/> There is no fixed interval but it is definitely longer than hours, rather about 3 weeks.<br/> The runtime is version 3.5.18.20 but certainly I also had this problem with the two previous versions.</p> <p>Has any cause been found for this issue?</p></div>

2022-07-28T05:08:15.300000Z2022-07-28T05:08:15.300000Zdamian177https://forge.codesys.com/u/damian177/https://forge.codesys.com8206abe9cfe2a6c6336662a7449dc56b7a867943

<div class="markdown_content"><p>Hi, I have the same situation since 2 years. I do not how solve this problem. Do you have any soultions ?</p></div>

2022-01-09T21:11:23.022000Z2022-01-09T21:11:23.022000Zsomlioyhttps://forge.codesys.com/u/somlioy/https://forge.codesys.com430124b46112ed375bd6befacceaa1b5b6552c0c

<div class="markdown_content"><p>What environment is the PLC mounted in? Do you use Wagos power filter card? 750-624 og 750-626 for instance.</p></div>

2022-01-05T05:44:51.236000Z2022-01-05T05:44:51.236000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com56be9647ba213d1643f67dcb495c7a123b97052c

<div class="markdown_content"><p>maybe, but never seen so far, which Wago firmware version is it? Which CODESYS runtime version?</p></div>

2022-01-04T20:38:22.166000Z2022-01-04T20:38:22.166000Znothinrandomhttps://forge.codesys.com/u/nothinrandom/https://forge.codesys.com610fbb7b97c35d217a1d3238e90cbe11d5356de1

<div class="markdown_content"><p><a class="user-mention" href="/u/eschwellinger/">@eschwellinger</a>,</p> <p>Wouldn't this be more than a runtime crash because the device can't be pinged or accessed via SSH. This seems like an OS layer issue.</p> <p>@MadsKaizer,</p> <p>If you SSH in and run this command <strong>ls -la /var/log/</strong>, do you see log files that have been gzipped? If yes, then try <strong>zcat</strong> the files (e.g. <strong>zcat /var/log/kernel.</strong>*)... though I'm not sure if zcat is installed. If not, then move the file to your computer using WinSCP or something similar and try to read the file.</p></div>

2022-01-04T08:53:35.823000Z2022-01-04T08:53:35.823000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com26bb109c29a5c6eb014781d38d9879093aed4fe2

<div class="markdown_content"><p>Hi,<br/> the plclogger is saved on /tmp/codesyscontrol.log<br/> so in case of any runtime crash you should see this in this log.<br/> (attention this is temp file after reboot gone)</p> <p>In case you have reproducible errors I would recommend to start the PFC manually (via ssh connection) by:<br/> 1. login by ssh<br/> 2. stop the pfc:<br/> /etc/init.d/codesyscontrol stop<br/> 3. start it manually:<br/> LD_LIBRARY_PATH=/opt/codesys/lib/compat LD_PRELOAD=/lib/libwretain.so <br/> /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg</p> <p>open a second ssh client and<br/> tail -f /tmp/codesyscontrol.log</p></div>

2022-01-04T07:28:57.869000Z2022-01-04T07:28:57.869000ZMadsKaizerhttps://forge.codesys.com/u/madskaizer/https://forge.codesys.com0466e7b9718e99466678ad8c5008ea21af806521

<div class="markdown_content"><p>All the log files there are only with data from after the latest reboot.</p> <p>There is a logrotate.status file that contains this:<br/> logrotate state -- version 2<br/> "/var/log/sudo.log" 2021-12-21-14:0:0<br/> "/var/log/runtime.log" 2021-12-21-14:0:0<br/> "/home/log/wagolog.log" 2021-12-21-14:0:0<br/> "/var/log/openvpn.log" 2021-12-21-14:0:0<br/> "/var/log/syslog.log" 2022-1-2-18:1:0<br/> "/var/log/lighttpd/error.log" 2021-12-21-14:0:0<br/> "/var/log/kernel.log" 2021-12-21-14:19:0<br/> "/var/log/lighttpd/access.log" 2021-12-21-14:0:0<br/> "/var/log/earlymsg" 2021-12-21-14:19:0<br/> "/var/log/cron.log" 2022-1-4-7:35:0<br/> "/log/fwupdate.log" 2021-12-21-14:0:0<br/> "/var/wagoearlylog.log" 2021-12-21-14:0:0<br/> "/var/log/messages" 2021-12-21-14:0:0<br/> "/var/log/wago/wagolog.log" 2021-12-21-14:0:0</p> <p>which seems to suggest that all logs was rotated on the hour of reboot. There is a ".1" of the older logs, but that is just the reboot information. </p> <p>This does not seem to be the right place for a continues log, that would have information about a crash :(</p></div>