[Fusioninventory-user] Container OpenVZ (Proxmox) and UUID

Mon Jul 13 18:59:14 UTC 2015

Hi, I ran the debug command twice.
Below are the results. What do I need to do for the account info file? Please tell me , what I need to do next.

[root at lxasstmgmpoc fusioninventory-agent]# service fusioninventory-agent stop
Stopping fusioninventory-agent:                            [  OK  ]
[root at lxasstmgmpoc fusioninventory-agent]# fusioninventory-agent  --user=glpi --password=glpi --debug --debug
[debug] FusionInventory unified agent for UNIX, Linux, Windows and MacOSX 2.1.14
[debug] Log system initialised (1)
[debug] --scan-homedirs missing. Don't scan user directories
[debug] vardir: /var/lib/fusioninventory-agent/http:__xxxx _glpi_plugins_fusioninventory_
[debug] [http://xxxx /glpi/plugins/fusioninventory/] Next server contact planned for Mon Jul 13 15:25:24 2015
[debug] No accountinfo file defined
[debug] Time to call Proc::Daemon

-----Original Message-----
From: Fusioninventory-user [mailto:fusioninventory-user-bounces+fsahmed=beckman.com at lists.alioth.debian.org] On Behalf Of Ahmed, Fnu S
Sent: Monday, July 13, 2015 11:17 AM
To: FusionInventory User discussion
Subject: Re: [Fusioninventory-user] Container OpenVZ (Proxmox) and UUID

Hi,
How do I run it? Do I need to type  fusioninventory-agent --debug ---debug   ? Please help

-----Original Message-----
From: Fusioninventory-user [mailto:fusioninventory-user-bounces+fsahmed=beckman.com at lists.alioth.debian.org] On Behalf Of David DURIEUX
Sent: Monday, July 13, 2015 8:57 AM
To: fusioninventory-user at lists.alioth.debian.org
Subject: Re: [Fusioninventory-user] Container OpenVZ (Proxmox) and UUID

Run with --debug --debug (yes 2 times) and see the agent logs

David
++

Le Mon, 13 Jul 2015 15:49:53 +0000
"Ahmed, Fnu S" <FSAHMED at beckman.com> a écrit:

>Hi David,
>Yes, I have tried http://xxxx /glpi/plugins/fusioninventory/ and it is
>the same result. Please help me. My time is running out :(
>
>-----Original Message-----
>From: Fusioninventory-user
>[mailto:fusioninventory-user-bounces+fsahmed=beckman.com at lists.alioth.d
>ebian.org] On Behalf Of David DURIEUX Sent: Monday, July 13, 2015 8:47
>AM To:
>fusioninventory-user at lists.alioth.debian.org Subject: Re:
>[Fusioninventory-user] Container OpenVZ (Proxmox) and UUID
>
>Le Mon, 13 Jul 2015 15:38:23 +0000
>"Ahmed, Fnu S" <FSAHMED at beckman.com> a écrit:
>
>>Hello,
>>These are the commands
>>ps -ef | grep fusion
>>root     19647     1  0 14:04 ?
>>00:00:00 /usr/bin/perl /usr/bin/fusioninventory-agent
>>--server=http://xxxx /glpi/plugins/fusioninventory --user=glpi
>>--password=glpi --basevardir=/var/log/fusioninventory-agent -stdout
>>After this, when I start the service fusioninventory start, it says
>>that it is running. But, cannot see the module in the agent management
>>module. If it is communicating, what is it communicating with? Also
>>the URL http://xxx /glpi/plugins/fusioninventory takes me to the not
>>found page and " The requested URL
>>/glpi/plugins/fusioninventory/front/wizard.php was not found on this
>>server." Page. Is it possible for you to check  and set everything
>>right remotely? Or else, please advice what to do. Please help.
>
>Try with url --server=http://xxxx /glpi/plugins/fusioninventory/ So
>with the / at the end
>
>David
>++
>
>>Thanks,
>>Shabena.
>>
>>
>>-----Original Message-----
>>From: Fusioninventory-user
>>[mailto:fusioninventory-user-bounces+fsahmed=beckman.com at lists.alioth.
>>d ebian.org] On Behalf Of Guillaume Rousse Sent: Friday, July 10, 2015
>>1:57 PM To:
>>fusioninventory-user at lists.alioth.debian.org Subject: Re:
>>[Fusioninventory-user] Container OpenVZ (Proxmox) and UUID
>>
>>Le 03/06/2015 16:28, Guillaume Rousse a écrit :
>>> Le 02/06/2015 12:26, Guillaume Rousse a écrit :
>>>> So I'd rather first define our expected semantic first, before
>>>> asserting anyone practice if wrong, and here is my suggested
>>>> definition:
>>>> - HARDWARE/UUID should be physical host identifier, unique among
>>>> all other physical hosts (and should eventually get renamed as
>>>> PHYSICAL_HOST_ID)
>>>> - HARDWARE/VMID should be virtual host identifier, unique among all
>>>> other virtual hosts from the same hypervisor only (and should
>>>> eventually get renamed as VIRTUAL_HOST_ID)
>>> So, is HARDWARE/UUID supposed to be a physical host identifier or a
>>> global host identifier ?
>>>
>>> In the first case, it should be unique among physical hosts only,
>>> virtual hosts should have same UUID than their physical host, and
>>> should change UUID when they are migrated to another physical host.
>>>
>>> In the second case, it should be unique among all hosts (either
>>> physical or virtual), but what's the usefulness of additioanl
>>> virtual-machine specific HARDWARE/VMID identifier ?
>>Hello.
>>
>>After some discussion with other developpers, we agreed on the
>>following plan:
>>- ensure HARDWARE/UUID is really unique among all machines, either
>>physical or virtual
>>- drop HARDWARE/VMID as confusing
>>- ensure hosts know their guests UUIDs, to allow relationships to be
>>established on GLPI
>>
>>Our specification
>>(http://www.fusioninventory.org/documentation/dev/spec/protocol/invent
>>o
>>ry) has been updated, and the following commits implements the change:
>>-
>>https://github.com/fusioninventory/fusioninventory-agent/commit/e6a6cb
>>1
>>271b02145cdc0ad31ce7998151077c47d
>>-
>>https://github.com/fusioninventory/fusioninventory-agent/commit/99fbd4
>>1
>>a4d3fc0249ecfbc1a703612d4d80f268b
>>-
>>https://github.com/fusioninventory/fusioninventory-agent/commit/ab41a4
>>2
>>7fd54ab6265175ec2e09e1c0350072100
>>-
>>https://github.com/fusioninventory/fusioninventory-agent/commit/43b373
>>e
>>d3db163d6439a65d4945f87755686b550
>>
>>Please test those changes, if possible.
>>--
>>Guillaume
>>
>>_______________________________________________
>>Fusioninventory-user mailing list
>>Fusioninventory-user at lists.alioth.debian.org
>>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/fusioninventor
>>y -user Please be advised that this email may contain confidential
>>information. If you are not the intended recipient, please notify us
>>by email by replying to the sender and delete this message. The sender
>>disclaims that the content of this email constitutes an offer to enter
>>into, or the acceptance of, any agreement; provided that the foregoing
>>does not invalidate the binding effect of any digital or other
>>electronic reproduction of a manual signature that is included in any
>>attachment.
>>
>>_______________________________________________
>>Fusioninventory-user mailing list
>>Fusioninventory-user at lists.alioth.debian.org
>>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/fusioninventor
>>y
>>-user
>
>_______________________________________________
>Fusioninventory-user mailing list
>Fusioninventory-user at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/fusioninventory
>-user Please be advised that this email may contain confidential
>information. If you are not the intended recipient, please notify us by
>email by replying to the sender and delete this message. The sender
>disclaims that the content of this email constitutes an offer to enter
>into, or the acceptance of, any agreement; provided that the foregoing
>does not invalidate the binding effect of any digital or other
>electronic reproduction of a manual signature that is included in any
>attachment.
>
>_______________________________________________
>Fusioninventory-user mailing list
>Fusioninventory-user at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/fusioninventory
>-user

_______________________________________________
Fusioninventory-user mailing list
Fusioninventory-user at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/fusioninventory-user
Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.