Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to run judgedeamon as a service, documentation seems to be incorrect #2681

Open
niconaus opened this issue Sep 12, 2024 · 2 comments · May be fixed by #2767
Open

Unable to run judgedeamon as a service, documentation seems to be incorrect #2681

niconaus opened this issue Sep 12, 2024 · 2 comments · May be fixed by #2767

Comments

@niconaus
Copy link

Description of the problem

When trying to run the judgehost deamon as a service, I get an error.

Your environment

  • DOMjudge version 8.3.0
  • Operating system Ubuntu 24.04.1 LTS
  • Apache

Steps to reproduce

The manual states the following:

The judgedaemon can also be run as a service by running:

sudo systemctl enable --now domjudge-judgehost

This gives me:

Failed to enable unit: Unit file domjudge-judgehost.service does not exist.

Looking at the domjudge source files, it seems that the way to launch the judgedeamon as a service has changed to the following:

sudo systemctl enable --now domjudge-judgehost.target

This does launch, and the deamon becomes active after this. For me, the judgehost still does not show up in the domjudge web interface, but I'm assuming that's a separate issue.

@Kevinjil
Copy link
Contributor

Short on time to investigate, but possibly related to #2086

@vmcj
Copy link
Member

vmcj commented Oct 27, 2024

Short on time to investigate, but possibly related to #2086

Yes, that one was fixed in main with more documentation during the installation (See: ec7ca6c).

I think the problem here is that we need to update the documentation for 8.2 & 8.3 as in certain cases autocomplete does not pick this up.

vmcj added a commit that referenced this issue Oct 27, 2024
@vmcj vmcj linked a pull request Oct 27, 2024 that will close this issue
@vmcj vmcj linked a pull request Oct 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants