You are not logged in.
I'm using the windows agent for x86.
It is installed as a service and recognized in services management.
But each time I'm sending a task to it (discovery - esx hosts - ...)
>> service crash and should be re-install from zero.
Even if I reboot or restart manually the agent, it just doesn't restart his webserver and contact with GLPI even if service is running.
But if I just let him send some data to GLPI automatically (basic data about itself),
it doesn't crash.
Tested with version : 2.3.4 - 2.3.5 - 2.3.6 - 2.4
Windows 7 x86, fresh install
Offline
Not really normal, have you infos about the crash? debug log?
Offline
I've test it a bit more, it's running since yesterday evening without problems.
I've just send an esx-discovery task and than it has seems to crash.
From GLPI: Agent is not reachable
From Windows: Nothing, just the webserver from the agent which is eturning a 404 error page not found but the services is still running. If I try to kill it than restart it manually, the webserver doesn't come back and still 404 not found :-/
Offline
Not this "crash" problem with Network discovery,
only with "esx discovery" for now
Offline
Perhaps a problem with https, is agent contact glpi on https?
Offline
No, it contacts it via classical http way
Offline
Problem "solved"
The agent doesn't crash after esx-discovery and succed tasks.
>>>> Catching bug
>> Had removed stable version
>> Installed Dev version
>>>> same bug
>> Removed it
>> Replaced last stable version
>>>> no more troubles (for now)
really strange, probably something more due to Windows itself than the agent
Offline
And than it crash again....
again during esx-discovering process
Offline
Ah attends, ca me dis un truc, je crois que ca arrive quand tu essaye d'inventorier plusieurs serveurs ESX (apparement ca serait un soucis dans la gestion du SSL)
Offline
Enfet, je ne fais l'inventaire que d'un seul serveur ESX.
Cependant, il a su le découvrir complètement une fois, deux fois,...
puis à la énieme fois (4 ou 5), il a planté.
Il y a des logs quelques parts que je pourrais te ressortir ?
Offline
Les logs de l'agent en étant en debug=3 ou (--debug --debug --debug)
Offline
Sous Windows, tu le met comment en mode débug ?
Sinon, il à fait le même soucis durant une découverte réseau (et là, il freeze toujorus),
lorsqu'il est tombé sur le serveur vmware égallement.
Offline
base de registre, HKLM/SOFTWARES/FusionInventory-agent et c'est la clé debug
Offline
je n'ai pas trouvé cette base "FusionInventory-agent" malgré un scan complet de HK Local Machine :-/
Offline