Unsolved
This post is more than 5 years old
1 Rookie
•
25 Posts
0
134675
October 1st, 2013 16:00
Inventory Collector Issues
I've implemented OpenManage Essentials 1.2 in our environment a couple of months ago, and it is currently monitoring 90+ servers. Along with the cutover from ITA to OME, I manually upgraded the OMSA agents on each of the servers to versions 7.2 or 7.3, depending on the OS.
Recently, I discovered that several of the servers I've upgraded to OMSA 7.3 (of of them SLES 10 SP4 or SLES 11 SP1) did not install the Inventory Collector. I first noticed it in the OME web interface in the System Update --> Issues and Resolutions For Updates section. After doing some searching, I discovered that on a 64-bit OS, the srvadmin-install.sh scripts do not install or update the Inventory Collector - that must be done manually.
So, taking the resolution provided by OME, I went back to a couple of those servers, installed the srvadmin-cm RPM from the install package, and restarted the OMSA services. After a few minutes, after using the SNMP test on the built-in Troubleshooting Tool, I can see that the Inventory Collector is now installed. However, after performing an Inventory scan from OME on those servers, they are still showing up as not having the Inventory Collector installed.
After some other searches, I came across the following command to test out the Inventory Collector:
./invcol -outc=/home/inv.xml
After a couple of minutes, I see this as output:
Update Failure: Error Messages File not found Invalid inventory results. Empty inventory results. Empty inventory results.
Any suggestions as to how to fix this? I've attempted an uninstall and re-install of OMSA, and I believe the dependencies for the srvadmin-cm RPM are installed.
Thanks,
Chadd
0 events found


TopHatSGI
1 Rookie
•
25 Posts
0
October 2nd, 2013 16:00
A bit of an update - after about 24 hours, I checked back on my Dell OpenManage Essentials server, it appears that the 2 servers I installed the srvadmin-cm RPM on are no longer being reported as not having an Inventory Collector installed. It would appear that I needed to be more patient (although I assumed the status would update shortly after performing an Inventory Scan from OME).
I still get the error I mentioned above when I attempt running that command to test the Inventory Collector. Perhaps that command is no longer supported in versions 7.2/7.3?
My other servers still have older versions of the Inventory Collector installed, and don't have the invcol tool in the /opt/dell/srvadmin/sbin/ folder, so I'm unable to see if I get the same error output or not.
DELL-Pupul M
2 Intern
•
1K Posts
0
October 3rd, 2013 00:00
Hi,
Thanks for the post.
Couple of things to check.
* To Install OMSA on 64 bit Linux System, please install below mentioned 32 bit rpms and their dependent packages before running OMSA Deploy task from OME.
compat-libstdc++-33.i686
libxml2.i686
pam.i686
glibc.i686
zlib.i686
libgcc.i686
What i can think as of now is that the invcol service did not start properly on some of the servers because of which OME was not able to fetch data for you instantly. Once, the invcol is up and running, OME should be able to give you all the details. I hope this helps.
TopHatSGI
1 Rookie
•
25 Posts
0
October 3rd, 2013 07:00
Thanks for the reply Pupul,
The servers that are reported as not having the Inventory Collector installed are all running 64 bit Suse Linux. I checked, and all of the packages you listed are installed. Something to note, I was manually installing/upgrading OMSA on these servers, and not running a deployment task from OME.
Also, when I was restarting the OMSA services, I was using the srvadmin-services.sh script with the restart option. That script includes all of the OMSA services, including the Inventory Collector, correct?
I haven't tried using the deployment features with OME as of yet. I should be able to push out the srvadmin-cm RPM to the problematic servers and create a task to install the RPM, correct?
TopHatSGI
1 Rookie
•
25 Posts
0
October 4th, 2013 08:00
After copying the RPM to the remaining problematic servers, installing it, cycling OMSA services, and Refreshing Inventory for those servers from OME, OME seems to no longer be complaining about missing Inventory Collectors.
That seems to have done the trick. I guess the invcol test I came across is no longer something that can be used with this version of OMSA.
Chadd
DELL-Pupul M
2 Intern
•
1K Posts
0
October 6th, 2013 04:00
Hi,
Thanks for taking time and letting us know the final result. It really helps :)