Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.12.3 available

The official documentation can be found on https://wiki.ocsinventory-ng.org. Read it before asking your question.

ocsinventory-agent command reboot the server. [closed]

Dear OCS Team!

I have a Red Hat Enterprise Linux Server release 6.8 (Santiago) Virtual machine. On this an OCS Inventory Server and a Unix agent. The server is working fine but when I start to run the agent with the ocsinventory-agent command the whole server reboot itself.
Agent version: Ocsinventory unified agent for UNIX, Linux and MacOSX (2.3)
Server version: OCSNG_UNIX_SERVER-2.3

Do you know what can cause this? An OCS server and agent are allowed on the same server?

Thanks for your help!
closed with the note: Problem solved by user
in OCS Inventory NG agent for Unix by (280 points)
closed by

8 Answers

0 votes

So agent restarts the server even if you try run for example just:

ocsinventory-agent --help

command?

by (1.5k points)
0 votes

No, that part is working.

As I experienced when the agent try to connect to the server E.g.:
ocsinventory-agent --ssl=0 --server=https://server_name/ocsinventory

by (280 points)
0 votes

Did you try an older version of agent e.g. 2.1.1?
Personally I use this version against server 2.3 with perl version 5.18.1

This is still downoadable grom github 

Try it.

by (1.5k points)
0 votes
During the agent (Ocsinventory-Unix-Agent-2.1.1.tar.gz) installation:
Copying SNMP MIBs XML files...
Activating modules if needed...
Launching OCS Inventory NG Unix Unified agent...

Killed the server again.
by (280 points)
0 votes

And what about locally:

./ocsinventory-agent -l /tmp --debug --logfile=log.log

Check log.log file for errors and try import *.ocs file (XML fomatted) from /tmp folder manually to OCS Server via "Manage -> Local import".

And what about other machines? They kill a server during connection too?

by (1.5k points)
0 votes
Sorry, I can't test it on other server, because I don't want to be in the same situation.
And with a test system I can't create the same situation.

The locally command kill the server as well. No entries in the /var/log/messages just the booting method after the reboot.
The last message block in the ocsinventory-agent.log:
[Fri Mar  3 08:28:45 2017][debug]  - Sys::Hostname loaded
[Fri Mar  3 08:28:45 2017][debug] Running Ocsinventory::Agent::Backend::OS::Generic::Lspci
[Fri Mar  3 08:28:45 2017][debug] Running Ocsinventory::Agent::Backend::OS::Generic::Lspci::Controllers
[Fri Mar  3 08:28:46 2017][debug] Running Ocsinventory::Agent::Backend::OS::Generic::Lspci::Modems
[Fri Mar  3 08:28:46 2017][debug] Running Ocsinventory::Agent::Backend::OS::Generic::Lspci::Sounds
[Fri Mar  3 08:28:46 2017][debug] Running Ocsinventory::Agent::Backend::OS::Generic::Lsusb
[Fri Mar  3 08:28:46 2017][debug] Running Ocsinventory::Agent::Backend::OS::Generic::Lsusb::Usb
[Fri Mar  3 08:28:46 2017][debug] Running Ocsinventory::Agent::Backend::OS::Generic::Screen
by (280 points)
0 votes
Which hardware do you use? We have seen this (reboot or crash) on HP DL360 G9 systems, but only on a very small fraction.
by (620 points)
0 votes
Sorry, I don't know exactly the hardware parameters because it is a virtual machine.

I have renamed the following file what checking the screen:
/usr/share/perl5/vendor_perl/Ocsinventory/Agent/Backend/OS/Generic
mv Screen.pm Disabled_Screen.pm

Now the ocs agent is working fine.
Our ESX team recommend a VMware tools and hardware tools update.
by (280 points)
edited by
 
Powered by Question2Answer
...