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.11.1 available

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

problem service starting

I have just installed an ocs 2.8 server under ubuntu (I have already installed some without problem).
On all client computers, after restarting after installing ocs, the ocs service cannot start, it always remains in "starting".
Thank you in advance for your help !

in OCS Inventory NG agent for Windows by (1.3k points)

8 Answers

0 votes

Something in the event manager related to ocs inventory service ?

by (88.5k points)
0 votes
here are the logs on a client computer :

Starting OCS Inventory Agent on Wednesday, August 25, 2021 08:53:04.
AGENT => Running OCS Inventory Agent Version
AGENT => Using OCS Inventory FrameWork Version
AGENT => Loading plug-in(s)
AGENT => Using network connection with Communication Server
AGENT => Using Communication Provider <OCS Inventory cURL Communication Provider> Version <>
AGENT => Sending Prolog
AGENT => Prolog successfully sent
AGENT => Inventory required
AGENT => Launching hardware and software checks
AGENT => Communication Server asks for IpDiscover

I do not see any error?

In fact, the service can start but after a few hours ... Why?

The "last come" date is still updated every time the computers are restarted even 
if the service does not start (and "last inventory" is only updated when the 
service starts when it wants).

Thanks for help !
by (1.3k points)
edited by
0 votes
we had the same probleme on some computer the service start about 2 hours after....

and uninstall reinstall agent with no effect

you can try to upgrade agent to may be....
by (660 points)
0 votes

try to change the service to "delayed start". Also can try to configure agent to not do a inventory at startup but with delayed time

by (5.7k points)
0 votes
in fact, i realized that the problem is present only on hyper-v virtual machines.
On the other hand, no problem on Virtualbox virtual machines.
Why this problem on Hyper-v? 
An idea ?
by (1.3k points)
0 votes

it seems that the service start is finalized after each plugin is executed

> This may explain why this is taking a long time - especially if one of the plugins crashes

Grettings, Mat
by (1.2k points)
0 votes
no that's not it. I tried with or without plugins. 
And to test, on the same virtualized server, it works very well with virtualbox, but not with hyper-v...
by (1.3k points)
0 votes
disable the ip discover

go to computer,configuration on the left


networks scans

set ip discover to never assign again

snmp switch to off

the service start !
by (660 points)
Powered by Question2Answer