ni::dsc::osdep::PosixError on Linux with DAQmx 19.1

[yunsw]

Hello,

We installed the NI DAQmx 19.1 on 4 hosts running the Scientific Linux (SL) 7.5 which is a rebuild of RHEL.

After installation the all hosts were working well but an error was occurred on the all hosts after some time since running the hosts.

At the time the nilsdev tool displayed the following error message without a list of devices (PXIe or PCIe) installed:

 # nilsdev    (as a root)

 terminate called after throwing an instance of 'ni::dsc::osdep::PosixError'

   what():  No locks available

 Aborted (core dumped)

After reboot of the hosts, the issue was resolved and the all hosts were working again.

Now we are monitoring 3 hosts by executing the nilsdev tool periodically to know when the error is occuring.

For the information, they are working without the issue for 50 days as of now.

Could anyone please guide or share information on this issue?

Thanks in advance.

Sangwon

[Mark_SAI]

I have seen this issue on 2 different PCs, and a reboot solved it. I am posting this in the hope that it will get some exposure at NI.

On both PCs:

OS: CentOS-8
Driver:  DAQmx 19.5

I don't yet have clear steps to reproduce - it seems in my case, it was to leave the PCs idle for greater than a week (both of them showed the same error) then try running a DAQ application. There is a small possibility that I didn't call DAQmx.Clear() on the last execution of the process, so maybe the "No locks available" refers to a locked-up DAQmx Task that has been idle for too long from the previous execution of the application. (Just a thought, don't have any evidence to support that)

[yunsw]

For the information, recently I updated the DAQmx from 19.1 to 19.5 on 3 PCs with SL 7.5.

In my case,

• I call DAQmxClearTask()
• DAQ application works again after 9 days in idle state

Thanks.