Measurement Studio for VC++

cancel
Showing results for 
Search instead for 
Did you mean: 

NIDAQmx No locks available on Linux

Hi,

 

I am using a Linux server controlling a PXIe chassis. It basically works fine but sometimes (perhaps after operation of 2 months) the system enters a strange state and `nilsdev` results in a coredump.

 

Reboot solves this issue, but I want to know if there are any method to recover nidaqmx without restarting and how, i.e., restart some systemd services?

$ nilsdev

terminate called after throwing an instance of 'ni::dsc::osdep::PosixError'
what(): No locks available
Aborted (core dumped)

 

This is the trace log

           PID: 89581 (nilsdev)
           UID: 1000 (acc)
           GID: 1000 (acc)
        Signal: 6 (ABRT)
     Timestamp: Thu 2025-03-27 13:04:39 JST (3h 21min ago)
  Command Line: nilsdev
    Executable: /usr/bin/nilsdev
 Control Group: /user.slice/user-1000.slice/session-626306.scope
          Unit: session-626306.scope
         Slice: user-1000.slice
       Session: 626306
     Owner UID: 1000 (acc)
       Boot ID: aa718baffbcf4b97a24b037857c5ef67
    Machine ID: 4e70b8de4d764a2e8dafd08561566359
      Hostname: ACC-PM-PC-1
       Storage: /var/lib/systemd/coredump/core.nilsdev.1000.aa718baffbcf4b97a24b037857c5ef67.89581.1743048279000000.zst (present)
  Size on Disk: 483.6K
       Message: Process 89581 (nilsdev) of user 1000 dumped core.

                Stack trace of thread 89581:
                #0  0x00007f54c942b54c __pthread_kill_implementation (libc.so.6 + 0xa154c)
                #1  0x00007f54c93ded46 raise (libc.so.6 + 0x54d46)
                #2  0x00007f54c93b27f3 abort (libc.so.6 + 0x287f3)
                #3  0x00007f54c9654a01 _ZN9__gnu_cxx27__verbose_terminate_handlerEv.cold (libstdc++.so.6 + 0xa1a01)
                #4  0x00007f54c966037c _ZN10__cxxabiv111__terminateEPFvvE (libstdc++.so.6 + 0xad37c)
                #5  0x00007f54c96603e7 _ZSt9terminatev (libstdc++.so.6 + 0xad3e7)
                #6  0x00007f54c966069d __cxa_rethrow (libstdc++.so.6 + 0xad69d)
                #7  0x00007f54c6e988fe n/a (libmxsout.so + 0x9b8fe)
                #8  0x00007f54c6e98a1c n/a (libmxsout.so + 0x9ba1c)
                #9  0x00007f54c6e56b08 n/a (libmxsout.so + 0x59b08)
                #10 0x00007f54c6e5706e n/a (libmxsout.so + 0x5a06e)
                #11 0x00007f54c6e57741 n/a (libmxsout.so + 0x5a741)
                #12 0x00007f54c6e63195 n/a (libmxsout.so + 0x66195)
                #13 0x00007f54c6e63428 n/a (libmxsout.so + 0x66428)
                #14 0x00007f54c6e5fa9e n/a (libmxsout.so + 0x62a9e)
                #15 0x00007f54c6e612b6 n/a (libmxsout.so + 0x642b6)
                #16 0x00007f54c6e4808f n/a (libmxsout.so + 0x4b08f)
                #17 0x00007f54c6e1d23a mxsGetConfiguration2 (libmxsout.so + 0x2023a)
                #18 0x00007f54c70e8c02 n/a (libmxs.so + 0xcc02)
                #19 0x00007f54c70e8092 mxsGetConfiguration2 (libmxs.so + 0xc092)
                #20 0x00007f54ca849665 n/a (libnidmxfu.so.1 + 0x5b7665)
                #21 0x00007f54ca5b20dc n/a (libnidmxfu.so.1 + 0x3200dc)
                #22 0x00007f54ca5fb061 n/a (libnidmxfu.so.1 + 0x369061)
                #23 0x00007f54ca68ea41 n/a (libnidmxfu.so.1 + 0x3fca41)
                #24 0x00007f54ca68f583 n/a (libnidmxfu.so.1 + 0x3fd583)
                #25 0x0000000000408f6b n/a (nilsdev + 0x8f6b)
                #26 0x00000000004091ef n/a (nilsdev + 0x91ef)
                #27 0x00007f54c93c9eb0 __libc_start_call_main (libc.so.6 + 0x3feb0)
                #28 0x00007f54c93c9f60 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x3ff60)
                #29 0x0000000000404e99 n/a (nilsdev + 0x4e99)
                ELF object binary architecture: AMD x86-64

 

I have such services

$ systemctl status ni
ni-pxipf-nipxirm-bind.service  nidrum.service                 nipal.service                  niroco.service                 nisds.service                  nisvcloc.service
nidevldu.service               nimxssvr.service               nipxicmsd.service              nis-domainname.service         nismbioscached.service

 

0 Kudos
Message 1 of 2
(61 Views)

Hi Stopper3046,

 

appearantly you are not the first one who experiences this issue:

ni::dsc::osdep::PosixError on Linux with DAQmx 19.1 - NI Community

 

Here are some general steps that you can take to make sure you have the latest driver correctly installed:

1. Ensure the customer followed the steps in the link given: https://www.ni.com/en-my/support/documentation/supplemental/18/downloading-and-installing-ni-driver-...

2. Reinstalled the DAQmx driver

3. Upgrade the DAQmx driver

 

You can also try to regularly restart your services, as long as it does not affect your measurements.

Let me know if you have questions, or if you would to discuss this further.

 

Best regards

Leonard

Graduate Sales Engineer @ NI

0 Kudos
Message 2 of 2
(11 Views)