Hello :-) We have worked around this situation by modifying /usr/share/fusioninventory/lib/FusionInventory/Agent/Task/Inventory/Generic/Domains.pm to use `hostname -f` instead of the hostname function from perl module Sys::Hostname.
Best Charles Blue Light free and open source service and research On 13/06/15 15:07, Blue Light wrote: > Hello :-) > > I have inherited a GLPI, Fusioninventory Agent and Plugin setup. In GLPI's > Assets > > Computers, some of the Domain column is populated and some is not. > > Auditing a selection of computers running Fusioninventory Agent shows no > apparent link between > Fusioninventory Agent versions, places the domain name could be taken from > and what GLPI displays: > > +---------+---------------+---------+-----------------+---------+--------+-------------+------------+ > | | | | | | | > | Canonical | > | Domain | | | | | | > Domain in | /etc/hosts | > | in GLPI | Computer | OS | Repo | Version | Run by | > resolv.conf | 127.0.1.1 | > +---------+---------------+---------+-----------------+---------+--------+-------------+------------+ > | N | ac001.acur.av | Precise | Ubuntu | 2.1.10 | cron | N > | Y | > | N | asyncto2 | Wheezy | Debian | 2.2.3 | cron | N > | N | > | N | backup | Wheezy | fusioninventory | 2.3.15 | daemon | N > | N | > | N | ltsp2 | Precise | fusioninventory | 2.1.10 | daemon | N > | N | > | N | rose | Precise | Ubuntu | 2.1.10 | cron | N > | Y | > | Y | LS1 | Squeeze | Debian | 2.0.6 | cron | N > | N | > | Y | ac002.acur.av | Precise | fusioninventory | 2.3.4 | cron | N > | Y | > | Y | housing | Precise | fusioninventory | 2.3.15 | cron | N > | Y | > +---------+---------------+---------+-----------------+---------+--------+-------------+------------+ > > In case that table is line-wrapped, there is a copy at > http://pastebin.com/M1pQJpKL > > Table notes: > * "Domain in GLPI": Shows if GLPI's Assets > Computers > Domain column is > populated. > * "Domain in resolv.conf": having a "search" line with the domain is a > workaround. > * "Canonical /etc/hosts 127.0.1.1" is explained below. > > Examining Fusioninventory Agent's perl suggests (I am not a perl programmer) > that it uses the hostname > function from the Sys::Hostname module. Its documentation > (http://search.cpan.org/~scott/Sys-Hostname-Long-1.5/lib/Sys/Hostname/Long.pm) > says: > > ==== quote begins ==== > Most unix systems have trouble working out the fully qualified domain name as > it to be configured > somewhere in the system correctly. For example in most linux systems (debian, > ?) the fully qualified name > should be the first entry next to the ip number in /etc/hosts > > 192.168.0.1 fred.somwhere.special fred > > If it is the other way around, it will fail. > ==== quote ends ==== > > Hence the "Canonical /etc/hosts 127.0.1.1" table column. > > Insofar as Fusioninventory Agent uses a perl module to get the domain name, > this is not a Fusioninventory > Agent problem but maybe readers of this list have found a solution. > > Best > _______________________________________________ Glpi-user mailing list Glpi-user@gna.org https://mail.gna.org/listinfo/glpi-user