nidevldu: [nidevldu] Fatal: Unexpected error in APAL device observer

[jefferyanderson]

All, my NI cDAQ 9134 NI RT Linux based system is now failing into Safe Mode.

The system boot log shows the following. Does anyone have any idea on what this is caused by? As the system is remote and MAX isn't an option, I'd like to know if I can correct this by copying files/directories from a good unit (the mate of this system) to correct the issue.

Thanks and Regards,
Jeff

Nov 23 17:53:38 NI-cDAQ-9134-019E3C0F ntpd[1417]: Listening on routing socket on fd #22 for interface updates
Nov 23 17:53:38 NI-cDAQ-9134-019E3C0F avahi-dnsconfd[1432]: Successfully connected to Avahi daemon.
Nov 23 17:53:38 NI-cDAQ-9134-019E3C0F NI WSD Watchdog[1442]: starting child server
Nov 23 17:53:38 NI-cDAQ-9134-019E3C0F NI WSD Watchdog[1442]: child indicated failure on start (status 1)
Nov 23 17:53:39 NI-cDAQ-9134-019E3C0F NI WSD Watchdog[1442]: child indicated failure on start (status 1)
Nov 23 17:53:39 NI-cDAQ-9134-019E3C0F NI WSD Watchdog[1442]: could not start child process
Nov 23 17:53:39 NI-cDAQ-9134-019E3C0F NI WSD Watchdog[1442]: stopping child server process
Nov 23 17:53:39 NI-cDAQ-9134-019E3C0F SystemWebServer: Failed to start Daemon
Nov 23 17:53:39 NI-cDAQ-9134-019E3C0F /usr/local/natinst/bin/nirtmdnsd[1490]: starting
Nov 23 17:53:40 NI-cDAQ-9134-019E3C0F shutdown[1676]: shutting down for system reboot
Nov 23 17:53:40 NI-cDAQ-9134-019E3C0F init: Switching to runlevel: 6
Nov 23 17:53:41 NI-cDAQ-9134-019E3C0F nidevldu: [nidevldu]  Fatal: Unexpected error in APAL device observer
Nov 23 17:53:41 NI-cDAQ-9134-019E3C0F -52006
Nov 23 17:53:41 NI-cDAQ-9134-019E3C0F Error code could not be found. Reinstalling the driver might fix the issue. Otherwise, contact National Instruments technical support.

[GeraldM]

Hey Jeff,

I know this was posted awhile ago but I recently had a customer with the same issue so I wanted to give a quick update for anyone who was/is currently seeing this. This is a documented bug (CAR 698530) known by NI R+D. This error shows up when nidevldu is stopped, typically around a target reboot. However, the error should have no functional harm. This bug has since been fixed in the 18.5 release of DAQmx.  

All the best,