FusionInventory for GLPI

You mean when run 2 agents inventory in same time and send to server in the same time, it duplicates informations?

The agent duplicate information but I explain it more later because the environment is not exactly that I have said to you.

I have test this some minutes ago:

1. fusioninventory-agent --force &
2. fusioninventory-agent --force &

and

• when the client was inventoried previously, all is Ok
• when the client wasn't inventoried previously (is a new client) then
  the server creates two different computer's registries with the same information.

I think the parallel execution of the agent should not be allowed.

The problem related with bug #1130 happen when I do the agent installation. I explain it more later.

I managed to reproduce the error. All my Windows and Unix installations of the agents end up as follows:

NOTE: The computer isn't inventoried previously.

service fusioninventory-agent start
sleep 5
fusioninventory-agent --force

Sometimes, due to problems with proxy settings, the agent can not connect to the server.

[Wed Aug 31 10:42:12 2011][info] PROLOG_FREQ has been set: 1
[Wed Aug 31 10:42:12 2011][info] PROLOG_FREQ has been set: 1
[Wed Aug 31 10:42:12 2011][info] RPC service started at: http://127.0.0.1:62354
[Wed Aug 31 10:42:17 2011][error] Cannot establish communication with `https://ecumene.sociedad.imaginaria.es/ocsinventory: 500 Can't connect to ecumene.sociedad.imaginaria.es:443 (Bad service '8080/')`
[Wed Aug 31 10:42:17 2011][error] No anwser from the server
[Wed Aug 31 10:42:17 2011][error] Cannot establish communication with `https://ecumene.sociedad.imaginaria.es/glpi/plugins/fusioninventory: 500 Can't connect to ecumene.sociedad.imaginaria.es:443 (Bad service '8080/')`
[Wed Aug 31 10:42:17 2011][error] No anwser from the server

When this occurs, seconds after, I launch back the agent as follows

fusioninventory-agent --force

and then is when the information is duplicated in the server.

I think notes 2 and 3 are related with allow the parallel execution of the agent.

Even with a lock mechanism it will still be possible to push simultaneously two time the same inventory.
- users can push inventory with fusioninventory-injector
- the agent can be used by a normal user and so, it won't be possible to create a lock file

What about a lock table on the server side with the HARDWARE/DEVICEID of the machine being processed?

I don't know anything about the structure, schemes and design of FusionInventory project. Perhaps I should have written this 'bug' into the forum, like I have done with others before. I hope you excuse me.

But once I have made the mistake, I prefer continue here; if there is no problems.

I have some questions about this 'bug'.

a) In your opinion, there is actually a bug?.

I think it exist; it's no critical but there is.

b) Does this error is caused by the agent or the server?

I think that is due to both.

The agent must not allow parallel execution with the same parameters. It should allow it on the other hand if, for example, the destination of the inventories are different servers.

The server should serialize the input. Thus no difference between using fusioninventory-injector or receive data from the agents. All inputs are processed in the order received.

For my particular problem there is a simple solution, I think so. Instead of end up the agents installation like this

service fusioninventory-agent start
sleep 5
fusioninventory-agent --force

end up like this

service fusioninventory-agent stop
sleep 5
fusioninventory-agent --force
sleep 5
service fusioninventory-agent start

I think this has its importance. What if while doing the inventory agent on a computer, you force a new inventory remotely from the server?

Hi Tomás. This should won't append anymore with in incoming FusionInventory for GLPI.

Thanks Gonéri.