Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched. Close

Codesys PFC200 Runtime, no log after reboot, can I get a Post-Mortem log?

  • MadsKaizer

    MadsKaizer - 2022-01-03

    I have a Wago PFC200 SL Runtime, that freezes up on me every 2-3 weeks. All it needs is a reboot and it runs again. But after the reboot, the log is "empty", I can only see the boot messages, not any messages from what made it halt.

    Is there a way to get a post-mortem log on freezing PLC?

    It looses network connection, so there is no OPC-UA connection, no webinterface, no shell access and cant even ping it.

    • damian177

      damian177 - 2022-07-28

      Hi, I have the same situation since 2 years. I do not how solve this problem. Do you have any soultions ?

  • nothinrandom

    nothinrandom - 2022-01-03


    The PFC200 is nothing more than a device that's running on Linux operating system (OS). This sounds like a kernel panic that's stopping everything. I would recommend you check, if exists, the kern.log file or other files that's OS related. Try to SSH in and look under the /var/log/ path.

  • MadsKaizer

    MadsKaizer - 2022-01-04

    All the log files there are only with data from after the latest reboot.

    There is a logrotate.status file that contains this:
    logrotate state -- version 2
    "/var/log/sudo.log" 2021-12-21-14:0:0
    "/var/log/runtime.log" 2021-12-21-14:0:0
    "/home/log/wagolog.log" 2021-12-21-14:0:0
    "/var/log/openvpn.log" 2021-12-21-14:0:0
    "/var/log/syslog.log" 2022-1-2-18:1:0
    "/var/log/lighttpd/error.log" 2021-12-21-14:0:0
    "/var/log/kernel.log" 2021-12-21-14:19:0
    "/var/log/lighttpd/access.log" 2021-12-21-14:0:0
    "/var/log/earlymsg" 2021-12-21-14:19:0
    "/var/log/cron.log" 2022-1-4-7:35:0
    "/log/fwupdate.log" 2021-12-21-14:0:0
    "/var/wagoearlylog.log" 2021-12-21-14:0:0
    "/var/log/messages" 2021-12-21-14:0:0
    "/var/log/wago/wagolog.log" 2021-12-21-14:0:0

    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.

    This does not seem to be the right place for a continues log, that would have information about a crash :(

  • eschwellinger

    eschwellinger - 2022-01-04

    the plclogger is saved on /tmp/codesyscontrol.log
    so in case of any runtime crash you should see this in this log.
    (attention this is temp file after reboot gone)

    In case you have reproducible errors I would recommend to start the PFC manually (via ssh connection) by:
    1. login by ssh
    2. stop the pfc:
    /etc/init.d/codesyscontrol stop
    3. start it manually:
    LD_LIBRARY_PATH=/opt/codesys/lib/compat LD_PRELOAD=/lib/libwretain.so
    /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg

    open a second ssh client and
    tail -f /tmp/codesyscontrol.log

    or change:
    nano /etc/default/codesyscontrol

    (remove '#'DEBUGOUTPUT=1
    and '#'DEBUGLOGFILE=/tmp/codesyscontrol_debug.log


    Last edit: eschwellinger 2022-01-04
  • nothinrandom

    nothinrandom - 2022-01-04


    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.


    If you SSH in and run this command ls -la /var/log/, do you see log files that have been gzipped? If yes, then try zcat the files (e.g. zcat /var/log/kernel.*)... 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.

  • eschwellinger

    eschwellinger - 2022-01-05

    maybe, but never seen so far, which Wago firmware version is it? Which CODESYS runtime version?

  • somlioy

    somlioy - 2022-01-09

    What environment is the PLC mounted in? Do you use Wagos power filter card? 750-624 og 750-626 for instance.


Log in to post a comment.