Cannot use scheduled task with glpi agent

[waiwaikev38]

Bug reporting acknowledgment

Yes, I read it

Professional support

Yes, I know

Describe the bug

Hi,
i just planned a deployment task. But it seems agents are not wake up by my scheduled task.
Automatic tasks are goo, and i see nothin in php-error.log

But if i force a wake up from my asset menu, i can see task inventory,deploy... start. I just don't understand why ma scheduled task not.

I try to read again full documentation, and except my configuration with delaytime and lazy are in default, i don't see anything wrong in my configuration.

wakeupAgents and taskscheduler are in CLI mode.

To reproduce

Create scheduled task for deploy package with :
Scheduled start time [SET]
Preparing time slot [8 --> 18]
Agents' alarm clock interval (in minutes) [5minute]
Slot time of execution [8 --> 18]
Number of agents to wake up [10]

Expected behavior

I want scheduled tasks wakeup my remote agent (for deploy package) without force them one by one.

Operating system

Windows

GLPI Agent version

v1.15

GLPI version

Other (Details in additional context below), 10.0.x (Details in additional context below)

GLPIInventory plugin or other plugin version

GLPI Inventory v1.5.3

Additional context

GLPI Server is in 10.0.20

[g-bougard]

Hi @waiwaikev38

I converted your issue as a Q&A discussion as you didn't report any glpi-agent issue.

About your problem, wakeupAgents is a glpi-inventory-plugin task. To wake up an agent, it has to contact glpi-agent on its http interface on port 62354. You have to check a lot of things before being sure it can work. First, glpi-agent can't be contacted if it is behind a firewall in the network from glpi server perspective. Glpi-agent must not have been configured to not listen on port 62354 and it must trust GLPI server. It does by default if the request effectively comes from the ip behind the configured server hostname. If you enable debug=2 in glpi-agent, you can check if glpi-agent received a request and you can test manually from the asset page by manually requesting an inventory from there. If the manual test doesn't work, you may have a network issue. For example, if you setup a proxy so glpi can request marketplace, this may also be a reason.

[waiwaikev38]

Hello,

I can confirm that I can perfectly "wake up" an asset from its inventory page.
I haven't seen anything in the glpi php logs about errors sending requests, or maybe I'm not looking in the wrong place.
Best regards

[g-bougard]

If you can wake up agent manually, it means you may be in trouble with the wakeupAgents and taskscheduler GLPI automatic actions which, you said, are in CLI mode. Check them in GLPI Setup section, check first the status of the "Last run" field. There you can also force to execute to check it works. In the case, it is not run when expected, this may mean your schedule may not be correct.