how to get nvmlInit or remove video card probe?

Question

Hello,

I have a system with Scientific Linux 7.7 (very similar to RHEL 7.7).  The ocs-inventory agent is failing as follows:

[root@myserver ~]# /usr/local/bin/ocsinventory-agent
/usr/bin/perl: symbol lookup error: /root/perl5/lib/perl5/x86_64-linux-thread-multi/auto/nvidia/ml/bindings/bindings.so: undefined symbol: nvmlInit

The machine has a somewhat old NVidia graphics card:

[root@myserver ~]# lspci |grep -i nvidia
03:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] (rev a1)

I suspect it is relevant that I am not using the nouveau driver, but rather the driver available in the elrepo:

[root@myserver ~]# rpm -qa |grep -i nvidia
kmod-nvidia-340xx-340.107-3.el7_7.elrepo.x86_64
nvidia-x11-drv-340xx-340.107-3.el7_6.elrepo.x86_64

For what it's worth, the perl installation on the system is "stock" perl rpms (a lengthy list of perl-*.rpm, which I'll omit here for brevity, but can post if it might help).  I have the following cpan modules installed:

Installed modules are:
   Exporter
   ExtUtils::MakeMaker
   Ocsinventory::Unix::Agent
   Perl
   local::lib
   nvidia::ml::bindings

Any advice how to get past the seemingly missing nvmlInit?  Some rpm package or cpan package I need to install?  An environment alteration (ld_library_path or some such)?

Some way to bypass the graphics adapter inventorying process?  (I don't particularly care if the video adapter information is lost or incorrect in the system inventory.)

Thanks for you time and consideration,

-Wayne

Answer 1

Hi,

Agent has been updated and now it does not use any more nividia perl module. Inventory is maded by nvidia-smi and nvidia-settings commands. If you can update to the latest version of the unified agent. This version needs OCS Server 2.6.

Best regards

Frank

Answer 2

Hello Frank.  Thank you for your answer.  It was silly of me not include the versions of the OCSInventory agent (v.2.3) and server/reports (UNIX v2.4) in my original post.  We'll be upgrading when the opportunity arises and likely this will be resolved.  I've put it on todo list to update this post when we get to that point.