• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Issue with Automatic Import to GLPI Inventory
#1
I'm using the FusionInventory Agent with GLPI, and I'm having an issue with the automatic addition of the computers to GLPI inventory. I have, for example, a range of hosts rnode00 through rnode04. These are RHEL4-based Linux systems. If I run the agent on the first one, it works fine, and the system shows up both in the GLPI -> Plugins -> FusionInventory -> Agent Management section, as well as the GLPI -> Inventory -> Computers section. This works as expected for the first three (rnode00, rnode01, rnode02); however, when I run the agent on the fourth system (rnode03), the GLPI Inventory entry for the first system (rnode00) disappears. The system still shows up in the Plugins -> FusionInventory -> Agent Management section, but the Computer Link field shows up blank, and the system is missing from the Inventory -> Computers section.

I don't have the agent installed on enough Windows machines to see if I get a similar behavior there. I'm also fairly new to both GLPI and FusionInventory that I don't really know where to look for debug information or what sorts of rules would cause this behavior? Any help would be appreciated.

Also, should mention that GLPI is version 0.78.4, FusionInventory plugins are 2.3.1.

-Nick
  Reply
#2
I think some fields in inventory to identify and link inventory with computer in GLPI is bad. So you must check "import equipment link rules". Perhaps 2 computers have same UUID (I have seen this some times) so you must disable this rule.

Tu check fields (UUID, computer name, serial number), you can see in each computer tab "fusinv xml"
Co-leader, official developper
DCS official PARTNER: dcs.glpi@dcsit-group.com
  Reply
#3
Same problem here, my 'uuid' and 'computer name' fields are different, I don't find the 'serial number' field.

<UUID>11246C05-08C5-11D7-0498-000423BCB73A</UUID>
<NAME>snserv001</NAME>

<UUID>226D7885-08C5-11D7-3A8B-000423C164C4</UUID>
<NAME>snserv004</NAME>

Any idea ?
  Reply
#4
try to test rules with these values and see what rule match
Co-leader, official developper
DCS official PARTNER: dcs.glpi@dcsit-group.com
  Reply
#5
When I only enable UUID and MAC I still have the problem, but when I disable every rules everything work fine.

I'll try to figure out what's going on later,

Anyway, thanks for you help.
  Reply
#6
How can I do the inventory for the computer using this rules about UUID etc ?

I can grab only name and ip number and other else for other computers different from the computer link for the FI agent?

How can activate this massive import for all the computers (including, for example, data about antivirus ) ?
  Reply
#7
Hi,

I'm having exactly the same problem like the OP, except my agents are all running on Windows hosts.
glpi-0.78.5
fusion-inventory-2.3.6

I've checked UUIDs, serial numbers, tokens of the agent's - they are all different.
Now when the agents report back to the server uploading inventory data, the last one "wins" e.g this will be the one appearing in the computers list.

When looking at the device history it seems that the gathered data for those 3 computers/agents is written to the same computer record in GLPI.
There are lots of "software removed", "software added" records and the hardware info like serial numbers always get changed.

By looking at the rules for device import and running data through the rule checker I have not been able to isolate the problem.

Does someone have an advice where to look next?

Peter
  Reply
#8
You have the default rules for import devices?
Co-leader, official developper
DCS official PARTNER: dcs.glpi@dcsit-group.com
  Reply
#9
Yes, the rules for import of computers are the default ones (I had to change the rules for printers to get them to correctly import).

I tried playing around with actions of the rules "FusionInventory link->Assign->Link if possible" / "FusionInventory link->Assign Link->if possible, else import denied" which looked like it solved the problem, but led to strange behaviour with other agents.

I'm currently trying to figure out where exactly things go wrong - is there a debug log for the imports?
  Reply
#10
There is bugs in rules, i'm working now to fix that, so wait for tomorrow
Co-leader, official developper
DCS official PARTNER: dcs.glpi@dcsit-group.com
  Reply
#11
Hello to all,

First of all I show to you information about my test environment:

.- The server
.- Ubuntu 10.04.3 LTS (Lucid Lynx) - Architecture AMD64
.- OCS Inventory NG Management Server v2.0
.- GLPI v0.78.5
.- GLPI v0.78.5 Agents
.- FusionInventory for GLPI v2.3.6 (MetaPackage)
.- FusionInventory v2.3.6
.- FusionInventory INVENTORY v2.3.6-1
.- FusionInventory SNMP v2.3.6-1
.- Shell Commands v1.3.0
.- Bays Management v1.1.0

.- The agents
.- FusionInventory-Agent v2.1.9-3 (for Windows)
.- FusionInventory-Agent v2.1.9-3 (for GNU/Linux)

I had set this import rules. With about 1000 desktop clients, they seem to work properly.

Quote:Equipment import and link rules (ordered from highest to lowest priority)
Computer serial + uuid
Logical operator:
and
Criteria:
Assert to import: Item type is Computer
Assert to import: Serial Number is present in GLPI Yes
Assert to import: Serial Number exist Yes
Assert to import: UUID is present in GLPI Yes
Assert to import: UUID exist Yes
Actions:
FusionInventory link Assign Link if possible


Computer serial
Logical operator:
and
Criteria:
Assert to import: Item type is Computer
Assert to import: Serial Number is present in GLPI Yes
Assert to import: Serial Number exist Yes
Actions:
FusionInventory link Assign Link if possible


Computer uuid
Logical operator:
and
Criteria:
Assert to import: Item type is Computer
Assert to import: UUID is present in GLPI Yes
Assert to import: UUID exist Yes
Actions:
FusionInventory link Assign Link if possible

Computer mac
Logical operator:
and
Criteria:
Assert to import: Item type is Computer
Assert to import: MAC is present in GLPI Yes
Assert to import: MAC exist Yes
Actions:
FusionInventory link Assign Link if possible


Computer import (by serial)
Logical operator:
and
Criteria:
Assert to import: Item type is Computer
Assert to import: Serial Number exist Yes
Actions:
FusionInventory link Assign Link if possible


Computer import (by uuid)
Logical operator:
and
Criteria:
Assert to import: Item type is Computer
Assert to import: UUID exist Yes
Actions:
FusionInventory link Assign Link if possible


Computer import (by mac)
Logical operator:
and
Criteria:
Assert to import: Item type is Computer
Assert to import: MAC exist Yes
Actions:
FusionInventory link Assign Link if possible


Computer import denied
Logical operator:
and
Criteria:
Assert to import: Item type is Computer
Actions:
To be unaware of import Assign Yes


Printer serial
Logical operator:
and
Criteria:
Assert to import: Item type is Printer
Assert to import: Serial Number is present in GLPI Yes
Assert to import: Serial Number exist Yes
Actions:
FusionInventory link Assign Link if possible


Printer mac
Logical operator:
and
Criteria:
Assert to import: Item type is Printer
Assert to import: MAC is present in GLPI Yes
Assert to import: MAC exist Yes
Actions:
FusionInventory link Assign Link if possible


Printer import (by serial)
Logical operator:
and
Criteria:
Assert to import: Item type is Printer
Assert to import: Serial Number exist Yes
Actions:
FusionInventory link Assign Link if possible


Printer import (by mac)
Logical operator:
and
Criteria:
Assert to import: Item type is Printer
Assert to import: MAC exist Yes
Actions:
FusionInventory link Assign Link if possible


Printer import denied
Logical operator:
and
Criteria:
Assert to import: Item type is Printer
Actions:
To be unaware of import Assign Yes


NetworkEquipment serial
Logical operator:
and
Criteria:
Assert to import: Item type is NetworkEquipment
Assert to import: Serial Number is present in GLPI Yes
Assert to import: Serial Number exist Yes
Actions:
FusionInventory link Assign Link if possible


NetworkEquipment mac
Logical operator:
and
Criteria:
Assert to import: Item type is NetworkEquipment
Assert to import: MAC exist Yes
Actions:
FusionInventory link Assign Link if possible


NetworkEquipment import (by serial)
Logical operator:
and
Criteria:
Assert to import: Item type is NetworkEquipment
Assert to import: Serial Number exist Yes
Actions:
FusionInventory link Assign Link if possible


NetworkEquipment import (by mac)
Logical operator:
and
Criteria:
Assert to import: Item type is NetworkEquipment
Assert to import: MAC exist Yes
Actions:
FusionInventory link Assign Link if possible


NetworkEquipment import denied
Logical operator:
and
Criteria:
Assert to import: Item type is NetworkEquipment
Actions:
To be unaware of import Assign Yes


Find serial in all GLPI
Logical operator:
and
Criteria:
Assert to import: Serial Number is present in GLPI Yes
Assert to import: Serial Number exist Yes
Actions:
FusionInventory link Assign Link if possible



Find mac in all GLPI
Logical operator:
and
Criteria:
Assert to import: MAC is present in GLPI Yes
Assert to import: MAC exist Yes
Actions:
FusionInventory link Assign Link if possible

I hope it will usefull for you.
Tomás Abad
  Reply
#12
The issue seems to have disappeared magically.
I can't tell exactly what fixed the problem for me.

My guess is that the magic happened when I checked all the import rules, deactivated them, reactivated them and clicked the "Update" button on every rule.

Thanks for your efforts

Peter
  Reply
#13
I have made many fixes about 2 hours ago on rules on dev version.
Co-leader, official developper
DCS official PARTNER: dcs.glpi@dcsit-group.com
  Reply
#14
Hi,

Is there a way to reactivate the default rules for import of computers ?
I flushed all of them to test something, but now nothing import in GLPI and no computer appear in "Unknwn device"

Best regards
Diedeer
  Reply
#15
You have disabled or deleted the rules ?
Co-leader, official developper
DCS official PARTNER: dcs.glpi@dcsit-group.com
  Reply
#16
I have deleted them...
  Reply
#17
No real issue, create them by hand or reinstall plugins (may not better solution) ....
Co-leader, official developper
DCS official PARTNER: dcs.glpi@dcsit-group.com
  Reply
#18
Hi

Just to let you know I've experienced this same issue with GLPI 0.80.4 + FusionInventory 2.4.0

The last computer added to the inventory has updated an existing entry instead of adding a new one. There were a lot of updates to that record and I lost details from the other computer...
  Reply
#19
I started from scratch, deleted the glpi database, reinstalled the server, the FI plugin, etc.

I repeated the same test and I was able to reproduce the symptom.
One first computer was added, everything OK.
Then the second computer installs the agent (with option to report immediately after installation) and it links to the previous computer instead of creating a new one.

UUID is different; serial is different; everything is different...
The only thing similar is the name (CRIINF03 vs CRIINF05), but even this is not exactly the same...if I test the rules engine before, it validates OK (create device).

If I delete both computers and force the agent to run a second time (--force) they are created correctly! It seems like the problem only happens once.

Somehow the import rules are failing on specific scenarios...I just can't understand which...
  Reply
#20
Finally I found the root cause!

The problem lies on the "Computer mac" rule.

The 2 computers I was testing have a virtual "RAS Async Adapter" network adapter for which the assigned MAC address is exactly the same: 20:41:53:59:4E:FF

The rule parses EVERY existing network adapters and consequently it maps this virtual MAC address to an existing device.

Disabling the rule was enough to solve the issue.

This should be reviewed on next versions as it will likely cause a bunch of issues for those using this tool on a Windows network.
  Reply
#21
But you don't have serial + UUID in first rule ? Or it's you MAC address the first rule?
Co-leader, official developper
DCS official PARTNER: dcs.glpi@dcsit-group.com
  Reply
#22
Sure I do.

The first rules are supposed to link agents to existing computers only (hence the reason they have the condition "exists in GLPi").

The problem here is that the second computer (a new computer) was getting linked to the first one, meaning that one of the rules was making the association to the existing computer, and this should never happen! This second computer should never match any of the first rules, it should only match the "computer import" rule. But it was matching the "Computer mac" rule instead due to the virtual network card that I mentioned before.

I'm not sure I made myself clear.
  Reply
#23
Can you send me the XML files of these 2 agents/computers by mail (d.durieux@siprossii.com), you can find it in tab "fusinv - XML" of each computer form
Co-leader, official developper
DCS official PARTNER: dcs.glpi@dcsit-group.com
  Reply
#24
Sure. They are on their way to your mailbox!
  Reply
#25
I have the same issue. I had installed 4 laptops that started with the same name "MININT-xxxxxxx". Suddenly only the last of the 4 had a link to a computer in the inventory. I tried removing them & installing fusioninventory agent after I renamed the agent. But still it doesn't work.

So what is the solution?
  Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)