Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed to start Ajenti panel.

See original GitHub issue

I can’t start the Ajenti panel after I install it. System: CentOS 8.0 64bit

● ajenti.service - Ajenti panel
   Loaded: loaded (/usr/lib/systemd/system/ajenti.service; enabled; vendor preset: disabled)
   Active: failed (Result: protocol) since Thu 2020-11-05 20:54:47 CST; 13s ago
  Process: 113903 ExecStart=/bin/python3 -d (code=exited, status=0/SUCCESS)

Nov 05 20:54:47 shino systemd[1]: Starting Ajenti panel...
Nov 05 20:54:47 shino systemd[1]: ajenti.service: Can't open PID file /var/run/ajenti.pid (yet?) after start: No such file or directory
Nov 05 20:54:47 shino systemd[1]: ajenti.service: Failed with result 'protocol'.
Nov 05 20:54:47 shino systemd[1]: Failed to start Ajenti panel.

Issue Analytics

State:
Created 3 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

kiarncommented, Nov 10, 2020

I think the reason why systemctl fail is because /usr/local/bin is not in $PATH in CentOS 8 anymore. The automated install write the ouput of which ajenti-panel in the Systemd Unit file, but this output is empty.

So, I guess that a solution would be to replace the line

ExecStart=/bin/python3 -d

through

ExecStart=/bin/python3 /usr/local/bin/ajenti-panel -d

in /lib/systemd/system/ajenti.service and then run a systemctl daemon-reload to reload the unit file. Then systemctl start ajenti.service should work, I hope. Please let me know.

0reactions

Decem6ercommented, Nov 11, 2020

@kiarn Thank you for your help. That works.

I think the reason why systemctl fail is because /usr/local/bin is not in $PATH in CentOS 8 anymore. The automated install write the ouput of which ajenti-panel in the Systemd Unit file, but this output is empty.

So, I guess that a solution would be to replace the line

ExecStart=/bin/python3 -d

through

ExecStart=/bin/python3 /usr/local/bin/ajenti-panel -d

in /lib/systemd/system/ajenti.service and then run a systemctl daemon-reload to reload the unit file. Then systemctl start ajenti.service should work, I hope. Please let me know.