Is the Linux version of the Agent really a thing? I have tried this on multiple platforms (Windows WSL, Centos Stream 10, Stream 8, and now Fedora 41) and get the same error each time.
“Failed to start celigoagent.service: Unit celigoagent.service not found.”
The documentation does not clarify which releases of Fedora or Centos are supported. (Hint: not the current one.) It also doesn’t indicate Ubuntu is an officially supported OS, despite evidence that the AppImage was built on a machine from the /home/ubuntu directory.
Other things I’ve found the hard way:
The agent requires X virtual frame buffer support, which is not installable on some Linux distros because X has been kicked aside for Wayland.
The officially supported (by Celigo) release of Centos (8) hits EOL in December 2025. Current Centos is Stream 10.
Fedora 41 seems to be the best bet so far; it quietly loaded all the dependencies from a relatively lightweight network install. It throws the exact same error message as every other distro I’ve tried when I actually launch the Agent installer though.
I’m about to give up and resign myself to buying another Windows Server license just to host the Windows version of the agent on vSphere in our DMZ.
Anyone have this running? Any additional pointers?
@troythompson There could be different reasons why this might not be working. We have definitely tested this for various Linux system. Is it possible for you to provide the logs for our team to check where things may have gone wrong ? Also, it would be great if you could log a support ticket for this in order to share the logs securely for further troubleshooting.
Logs are created in /root/.config/agent/ folder of linux machine. Use this command to check if log files exists in ur root directory as .log files will get created for current timestamp in root and check for server-{{Current Date timestamp}} logs here ->
The /root/.config directory does not contain an agent subfolder; no logs were created during the agent-linux.run startup.
The /usr/local/bin/celigo-agent directory was created and contains the AppImage, yml file, installer script, and a temp.json file (0 bytes).
When I run the xvfb-run command seen inside the linux-install.sh script, to start up the agent-linux.AppImage, it returns no errors and exits silently. No logs are created.
Are there some debug command line parameters that would log more details?
I don’t have a solution for you right now, but I did want to let you know that I am gathering information on supported Linux versions. I will update you here (along with updating the documentation) once I have a list. I also want to point out a troubleshooting article for on-prem agents, although I didn’t see anything in the article that might help with your specific use case. Thank you for your patience!
I have a specific ticket opened for tracking this issue too.
I was able to get the agent running in a test VM on the Ubuntu 24 platform but had to manually patch around a dependency error to make it work. Since Ubuntu is not supported (per the documentation) I didn’t pursue that option further.
