Problems detecting memory type and number of threads on some PCs

glpiabuser · 2021-07-15 08:00:43

Hello all. I have GLPI 9.4.4 and FI 2.5.2. In some actives in "type of memory" section glpi cleans type of memory DDR3/DDR4 and write physical. In the same actives, glpi cant define number of threads. The most interesting thing is that there are similar actives in terms of characteristics and everything is fine in them.

gbougard · 2021-07-21 10:40:18

Hi glpiabuser,

this is probably an agent issue. Can you check the related parts in the XML inventory you can manually create with fusioninventory-inventory script ? Check it on each related active computers.

glpiabuser · 2021-07-22 13:13:38

I checked xml files, same result in local inventory, fusion Inventory cant define TYPE of Memory and NUMBER of threads, but, when i used FI on this PC's first time, FI defined the TYPE of memory, then GLPI overwrited them like "Physical memory" instead "DDR". IDK what to do. Normal and broken actives have the same characteristics, the same domain policies are applied to them.

Last edited by glpiabuser (2021-07-22 13:15:31)

glpiabuser · 2021-07-22 13:14:23

Also i tried use FI 2.6 - same result

Last edited by glpiabuser (2021-07-22 13:29:23)

gbougard · 2021-07-22 14:44:20

It seems to me you're talking about inventory on windows systems. On such systems, we try first to start "dmidecode" provided by the agent and then if not found we try WMI calls to get the infos. If I remember well, this does not provide identical results for few kind of components and I guess memories and cpus are concerned. Maybe a first inventory was possible usgin dmidecode. You should then check if the dmidecode program has not been removed or is blocked by an antivirus or so. You should find it under the perl\bin folder into the installation folder. Do you use standard installation ? I mean local agent install into the "C:\Program Files" folder.

glpiabuser · 2021-07-23 08:29:17

Hello.

>Do you use standard installation ? I mean local agent install into the "C:\Program Files" folder.

Yes, the plugin is deployed by the VBS script in Active Directory. In "C:\Program Files" folder.

> You should find it under the perl\bin folder into the installation folder.

I found him in this directory.

gbougard · 2021-07-23 11:50:55

It really seems to me the agent is not running the dmidecode related modules on the computers where you now find "Physical Memory" instead of "DDR".

You should enable the debug=2 level in the agent configuration (change it in registry and restart the agent) on one of these computers and check the log file to confirm Dmidecode related modules are disabled.
If you have a confirmation, you must understand why the system is not running dmidecode as expected.

You can also first try to just run dmidecode from an administrative console on a concerned computer to confirm it still works as expected.

glpiabuser · 2021-07-29 07:58:10

Hello, dmidecode is running. I reinstalled FI on these computers and removed them from assets on GLPI site. The first inventory went fine, but then glpi changed the memory type and number of threads again.

Albager · 2022-01-17 16:22:58

It seems I am experiencing the same problem on some of my clients. Any idea why this is happening? (taken from the histroy of one of the clients with "Physical Memory" instead of DDR)

22962 2022-01-17 14:17 Plugin_FusionInventory (23) Memory Add a component: Physical Memory (13)
22959 2022-01-17 14:17 Plugin_FusionInventory (23) Memory Add a component: Physical Memory (13)
22958 2022-01-17 14:17 Plugin_FusionInventory (23) Memory Delete a component: DDR4 - DIMM (6)
22957 2022-01-17 14:17 Plugin_FusionInventory (23) Memory Delete a component: DDR4 - DIMM (6)

Oviously, dmidecode is running fine first, but then the correct DDR Memory value component is deleted by Plugin_FusionInventory and added again as "physical memory"??

Last edited by Albager (2022-01-17 16:24:47)

Forum GLPI-Project

Announcement

#1 2021-07-15 08:00:43

Problems detecting memory type and number of threads on some PCs

#2 2021-07-21 10:40:18

Re: Problems detecting memory type and number of threads on some PCs

#3 2021-07-22 13:13:38

Re: Problems detecting memory type and number of threads on some PCs

#4 2021-07-22 13:14:23

Re: Problems detecting memory type and number of threads on some PCs

#5 2021-07-22 14:44:20

Re: Problems detecting memory type and number of threads on some PCs

#6 2021-07-23 08:29:17

Re: Problems detecting memory type and number of threads on some PCs

#7 2021-07-23 11:50:55

Re: Problems detecting memory type and number of threads on some PCs

#8 2021-07-29 07:58:10

Re: Problems detecting memory type and number of threads on some PCs

#9 2022-01-17 16:22:58

Re: Problems detecting memory type and number of threads on some PCs

Board footer