Celigo · On-premise agent
On-premise agent service not running
Short answer
The Celigo on-premise agent service fails or stops when the agent is already running in another mode, because only one instance can run at a time. Determine whether the agent is running in Background mode or through the UI.
VerifiedLast verified
01Error text
On-premise agent service not running02Likely causes
- The agent can run through the agent UI, in the background, or as a Windows service. The service fails or stops if the agent is running in another mode.
03How to fix it
- Determine whether the agent is running in Background mode or through the UI.
- Make sure the agent is not running and terminate any running instances.
- Restart the service.
04Official documentation
→Related errors
- On-premise agent: Offline (red) statusAn Offline (red) status for a Celigo on-premise agent means the agent is not running, its token does not match, or a firewall or proxy is blocking it. Check that the agent is running, that its token matches the token in integrator.io, and that no firewall or proxy blocks it.
- On-premise agent: No logs or empty log filesMissing or empty log files for a Celigo on-premise agent mean the agent is running with incorrect permissions, or the log path is misconfigured or inaccessible. Determine whether the log files exist on the machine.
- On-premise agent: Failed to uninstall old application filesThis Celigo on-premise agent error means the Windows system PATH environment variable is corrupted or inconsistent after the agent auto-update. Restart the system.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Celigo work:Open Celigo jobsCeligo rates and salaries