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

Control Linux SL runtime - segmentaton fault on startup

Runtime 🇬🇧
krps
2022-05-23
2022-05-25

  • krps - 2022-05-23

    Hi,

    I freshly installed Control Linux SL to a AMD Ryzen machine with Ubuntu 20.04 via the Codesys Development environment with Tools -> Update Linux.

    When I click on the "Runtime - Start" button, I just receive the message "Failed to start codesyscontrol".
    When I run codesyscontrol directly from the linux command line, I just get a segmentation fault.

    ~# /opt/codesys/bin/codesyscontrol.bin /etc/CODESYSControl_User.cfg

********* CoDeSysControl DEMO VERSION - runs 2 hours*********

Segmentation fault (Code dumped)

    How can I debug this problem?

    BR KRPS

     
    Thumbnail
    codesys.png

  • eschwellinger

    eschwellinger - 2022-05-23

    Is your Ubuntu system a 64bit version? check by uname -a
    could you use 4.4.1.0 version for a test?

     

    Last edit: eschwellinger 2022-05-23

  • krps - 2022-05-23 
    ~$ uname -a
Linux xxxxxx-desktop 5.4.0-110-generic #124-Ubuntu SMP Thu Apr 14 19:46:19 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS"

    I will test 4.4.1.0 in the afternoon. Can I download it in the store?

     

    Last edit: krps 2022-05-23

  • krps - 2022-05-23

    I updated to 4.4.1.0. The error message on the command line changed a little bit, but the result is the same: segmentation fault.

    ~$ /opt/codesys/bin/codesyscontrol.bin
CODESYS Control V3.5.17.30 for x86-64Bit - build Mar 18 2022
Device type: 4102 id: 0x00000005
Device vendor: 3S - Smart Software Solutions GmbH
Device name:   CODESYS Control for Linux SL
INFO: no config file configured, using default
Segmentation fault (Core dumped)
     
    Thumbnail
    codesys2.png

  • krps - 2022-05-24

    Does anyone have a suggestion for me?

     

  • i-campbell

    i-campbell - 2022-05-24

    Try instead the command
    /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg

    because CODESYSControl.cfg references CODESYSControl_User.cfg, plus has some additional required settings.

    Also try to delete all applications form runtime deploy tool.

     

  • krps - 2022-05-25

    Unfortunaetly this also did not help.

    ~$ /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg
CODESYS Control V3.5.17.30 for x86-64Bit - build Mar 18 2022
Device type: 4102 id: 0x00000005
Device vendor: 3S - Smart Software Solutions GmbH
Device name:   CODESYS Control for Linux SL
INFO: using /etc/CODESYSControl.cfg as config file
Speicherzugriffsfehler (Speicherabzug geschrieben)
     

  • i-campbell

    i-campbell - 2022-05-25

    sudo? or su -

     

    • krps - 2022-05-25

      Also "sudo" does not help.

      The situation is extremely disappointing for me. That's why I invested the last hour trying to debug the problem and I found a workaround.
      Conclusion: I think it is a bug in codesyscontrol. When reading /proc/stat, a buffer overflow occurs because I am using a machine with 24 CPU cores and the developer of codesyscontrol apparently did not expect /proc/stat to be so large.

      Details:
      I tried to run condesyscontrol with gdb to find out why it is crashing:

      ~$ gdb /opt/codesys/bin/codesyscontrol.bin -d 
...
warning: /etc/CODESYSControl.cfg ist kein Verzeichnis.
Reading symbols from /opt/codesys/bin/codesyscontrol.bin...
(No debugging symbols found in /opt/codesys/bin/codesyscontrol.bin)
(gdb) run -d /etc/CODESYSControl.cfg´
Starting program: /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg´
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
CODESYS Control V3.5.17.30 for x86-64Bit - build Mar 18 2022
Device type: 4102 id: 0x00000005
Device vendor: 3S - Smart Software Solutions GmbH
Device name:   CODESYS Control for Linux SL
INFO: using /etc/CODESYSControl.cfg´ as config file

Program received signal SIGSEGV, Segmentation fault.
_IO_fgets (buf=0x7fffffffde3a "cpu22", n=6, fp=0x555500000016) at iofgets.c:47
47      iofgets.c: Datei oder Verzeichnis nicht gefunden.

      So it seams, the process crashes while reading something from a file into a buffer, which already contains "cpu22".
      Of course, codecontrolsys.bin is a stripped binary, so a stack trace didn't really help me.

      (gdb) bt
#0  _IO_fgets (buf=0x7fffffffde3a "cpu22", n=6, fp=0x555500000016) at iofgets.c:47
#1  0x000055555d7c339c in ?? ()
#2  0x000055555d7c1270 in ?? ()
#3  0x000055555d5a84da in ?? ()
#4  0x000055555d5ab629 in ?? ()
#5  0x000055555d5a42c1 in ?? ()
#6  0x000055555d6e7a38 in ?? ()
#7  0x000055555dad9a42 in ?? ()
#8  0x000055555d6e7d43 in ?? ()
#9  0x00007ffff7dd30b3 in __libc_start_main (main=0x55555d6e7d00, argc=3, argv=0x7fffffffe3e8, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffffffe3d8) at ../csu/libc-start.c:308
#10 0x000055555d5a402a in ?? ()

      So I tried strace to find out which file codesys reads from when it crashes.

      ~$ strace /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg

...

write(1, "INFO: using /etc/CODESYSControl."..., 51INFO: using /etc/CODESYSControl.cfg as config file
) = 51
futex(0x7ffd86ce8194, FUTEX_UNLOCK_PI_PRIVATE) = -1 EPERM (Vorgang nicht zulässig)
openat(AT_FDCWD, "/proc/stat", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(4, "cpu  3250587 3387 1678186 412361"..., 1024) = 1024
read(4, " 69856 1717541 39 0 251 0 0 0\ncp"..., 1024) = 1024
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x55c900000016} ---
+++ killed by SIGSEGV (core dumped) +++
Speicherzugriffsfehler (Speicherabzug geschrieben)

      So it looks like the programme is crashing while reading from /proc/stat. I checked that file and it also contains the "cpu22" string I have seen in gdb. I'm using a Ryzen 3900 CPU with many cpu cores.

      ~$ cat /proc/stat
cpu  3258529 3387 1682207 41332585 1685 0 28881 0 0 0
cpu0 137178 156 69312 1716518 40 0 14133 0 0 0
cpu1 136470 72 69556 1720665 16 0 5116 0 0 0
cpu2 135868 96 70020 1722103 29 0 2229 0 0 0
cpu3 136099 96 71471 1719204 93 0 1322 0 0 0
cpu4 134970 86 71446 1721324 53 0 668 0 0 0
cpu5 134810 92 70451 1723008 38 0 467 0 0 0
cpu6 136844 113 70557 1720923 35 0 367 0 0 0
cpu7 136211 252 70286 1722190 41 0 339 0 0 0
cpu8 136189 101 70143 1722254 41 0 289 0 0 0
cpu9 137788 517 69379 1720564 151 0 280 0 0 0
cpu10 137197 84 70172 1721311 45 0 271 0 0 0
cpu11 136312 377 69706 1722414 37 0 283 0 0 0
cpu12 135802 136 70005 1722904 41 0 257 0 0 0
cpu13 135026 77 68778 1724814 67 0 253 0 0 0
cpu14 134683 82 68949 1725315 52 0 275 0 0 0
cpu15 134579 98 70908 1723098 39 0 264 0 0 0
cpu16 134353 158 70072 1723985 103 0 265 0 0 0
cpu17 133893 170 70958 1723526 103 0 256 0 0 0
cpu18 134947 81 69812 1723616 95 0 240 0 0 0
cpu19 134890 173 71277 1721522 129 0 243 0 0 0
cpu20 134513 68 70147 1724198 95 0 255 0 0 0
cpu21 137221 117 70022 1721624 39 0 251 0 0 0
cpu22 136713 93 69936 1721657 127 0 272 0 0 0
cpu23 135964 80 68834 1723837 166 0 278 0 0 0
intr 423605973 35 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 55 0 0 0 0 0 0 0 0 0 1465032 0 0 0 0 0 0 0 0 0 24 1 55049 10898 69427 18238 27747 4736 11318 16477 11491 17411 29740 13819 27821 0 0 0 0 0 0 0 0 211 0 1167 0 137846 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ctxt 2104030974
btime 1653444332
processes 168088
procs_running 3
procs_blocked 0

      It looks to me like the buffer that "read" uses is not big enough. My first thought therefore: "How can I make /proc/stat smaller"? Of course: Disable CPU cores

      ~$ sudo su -
~# echo 0 > /sys/devices/system/cpu/cpu21/online
~# echo 0 > /sys/devices/system/cpu/cpu22/online
~# echo 0 > /sys/devices/system/cpu/cpu23/online


~$ cat /proc/stat
cpu  3319213 3387 1712791 42107430 1743 0 29423 0 0 0
cpu0 139988 156 70668 1747762 40 0 14417 0 0 0
cpu1 139204 72 70942 1751993 16 0 5202 0 0 0
cpu2 138626 96 71410 1753409 29 0 2271 0 0 0
cpu3 138791 96 72809 1750646 93 0 1344 0 0 0
cpu4 137756 86 72865 1752591 53 0 676 0 0 0
cpu5 137642 92 71849 1754309 38 0 477 0 0 0
cpu6 139111 113 71782 1752915 35 0 373 0 0 0
cpu7 138399 252 71441 1754317 41 0 343 0 0 0
cpu8 138490 101 71344 1754227 41 0 293 0 0 0
cpu9 140272 517 70568 1752371 151 0 283 0 0 0
cpu10 139697 84 71343 1753118 45 0 276 0 0 0
cpu11 138833 377 70924 1754180 37 0 288 0 0 0
cpu12 138487 136 71283 1754424 41 0 260 0 0 0
cpu13 137662 77 70136 1756299 67 0 259 0 0 0
cpu14 137429 82 70338 1756659 52 0 280 0 0 0
cpu15 137272 98 72302 1754502 39 0 274 0 0 0
cpu16 137035 158 71389 1755492 103 0 280 0 0 0
cpu17 136643 170 72271 1754941 103 0 264 0 0 0
cpu18 137264 81 71075 1755529 95 0 242 0 0 0
cpu19 137102 173 72509 1753492 130 0 246 0 0 0
cpu20 136737 68 71446 1756170 95 0 256 0 0 0
intr 431369094 35 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 55 0 0 0 0 0 0 0 0 0 1492374 0 0 0 0 0 0 0 0 0 24 1 55802 11095 70675 18576 28242 4741 11329 16504 11546 17500 29740 13889 27896 0 0 0 0 0 0 0 0 211 0 1167 0 140009 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ctxt 2147413002
btime 1653444332
processes 171015
procs_running 3
procs_blocked 0
softirq 158449602 10 57219845 7655 7981197 15947 3 1462 64929335 2798 28291350

      Now I tried to start codesys again:

      ~$ /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg
CODESYS Control V3.5.17.30 for x86-64Bit - build Mar 18 2022
Device type: 4102 id: 0x00000005
Device vendor: 3S - Smart Software Solutions GmbH
Device name:   CODESYS Control for Linux SL
INFO: using /etc/CODESYSControl.cfg as config file
machine: x86_64
timer resolution: 1nsec
Linux version 5.4.0-113-generic (buildd@lcy02-amd64-067) (gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)) #127-Ubuntu SMP Wed May 18 14:30:56 UTC 2022

SysTaskCreate[527]: create CMHooksTask(prio:128,interval:0us,stacksize:131072)
SysTaskFrame[448]:  CMHooksTask(tid:178986,OSprio:0) running
SysExceptOSHookFunction[455]: setting fpu-exceptions from 0x0 to 0x4
SysMemOSHookFunction[53]: mlockall: Cannot allocate memory
SysDirCreate_[258]: mkdir(.pki/own/cert/):File exists
SysDirCreate_[258]: mkdir(.pki/quarantine/):File exists
SysDirCreate_[258]: mkdir(.pki/trusted/cert/):File exists
SysDirCreate_[258]: mkdir(.pki/trusted/crl/):File exists
SysDirCreate_[258]: mkdir(.pki/untrusted/):File exists
SysDirCreate_[258]: mkdir(cert/import/):File exists
SysDirCreate_[258]: mkdir(cert/export/):File exists
SysDirCreate_[258]: mkdir(.pki/own/key/):File exists
SysDirCreate_[258]: mkdir(.pki/own/key_exportable/):File exists
SysFileGetSize_[394]: stat(.UserMgmtDB.csv):No such file or directory
SysFileGetSize_[394]: stat(UserMgmtDB.csv):No such file or directory
SysFileGetSize_[394]: stat(.UserMgmtDB.csv):No such file or directory
SysFileGetSize_[394]: stat(UserMgmtDB.csv):No such file or directory
SysFileGetSize_[394]: stat(.SoftContainer_CmRuntime.wbb):No such file or directory
SysFileGetSize_[394]: stat(Firmware/.SoftContainer_CmRuntime.wbb):No such file or directory
openRxSocket[595]: Opened socket for reading (can0)
openRxSocket[601]: ioctl(SIOCGIFINDEX): No such device
Socket_CanMiniDriver_Setup[1098]: interface can0 is not available
SysFileDelete_[304]: unlink(.UserMgmtDB.csv):No such file or directory
SysFileGetSize_[394]: stat(.UserMgmtRightsDB.csv):No such file or directory
SysFileGetSize_[394]: stat(UserMgmtRightsDB.csv):No such file or directory

 _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

        _/_/_/_/      _/_/_/_/    _/_/_/_/_/    _/_/_/_/_/_/    _/_/_/_/_/  _/_/    _/_/    _/_/_/_/_/          _/
     _/_/_/_/_/_/  _/_/_/_/_/_/  _/_/_/_/_/_/  _/_/_/_/_/_/  _/_/_/_/_/_/  _/_/    _/_/  _/_/_/_/_/_/        _/_/_/
    _/_/    _/_/  _/_/    _/_/  _/_/    _/_/  _/_/          _/_/          _/_/    _/_/  _/_/              _/_/_/_/_/
   _/_/          _/_/    _/_/  _/_/    _/_/  _/_/_/_/        _/_/_/_/      _/_/_/_/      _/_/_/_/      _/_/_/_/_/_/_/
  _/_/    _/_/  _/_/    _/_/  _/_/    _/_/  _/_/                  _/_/      _/_/              _/_/      _/_/_/_/_/
 _/_/_/_/_/_/  _/_/_/_/_/_/  _/_/_/_/_/_/  _/_/_/_/_/_/  _/_/_/_/_/_/      _/_/      _/_/_/_/_/_/        _/_/_/
  _/_/_/_/      _/_/_/_/    _/_/_/_/_/    _/_/_/_/_/_/  _/_/_/_/_/        _/_/      _/_/_/_/_/            _/

 _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

      Yep, it works.

      @Codesys team: Can you fix this bug? I bought a Control Linux SL licence because I wanted to implement automation with a machine vision task on a powerful CPU platform. I have to deliver this project to my customer in a few weeks. I look forward to a fix in a timely manner.

       
      👍
      1

  • eschwellinger

    eschwellinger - 2022-05-25

    you need to add a bug report- https://store.codesys.com/en/#
    my question -> bug report /8 add all information/details.
    This is the official way how it will work and come hopefully into the product.

     

    • krps - 2022-05-25

      Thanks for the link. I submitted a bug report.

       

Log in to post a comment.