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

Proposal for additional Fedora info in the wiki FAQ #3281

Closed
1 of 3 tasks
DandelionSprout opened this issue Jun 22, 2021 · 2 comments
Closed
1 of 3 tasks

Proposal for additional Fedora info in the wiki FAQ #3281

DandelionSprout opened this issue Jun 22, 2021 · 2 comments
Assignees
Milestone

Comments

@DandelionSprout
Copy link
Contributor

DandelionSprout commented Jun 22, 2021

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • I am running the latest version (v0.107.0-b.2, installed from GitHub)
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed

Problem Description

While I set off the entirety of Tuesday on doing one proper setup of Fedora Workstation 34 aarch64, I had far more problems getting systemctl to recognise AGH on Fedora boot, than on any other distro I had tried.

After some 5 hours did I come across #765 (comment), but I had to do one additional thing to fix the problem on my end:

It turns out that SELinux is extremely overzealous in its firewall protection and its anti-/home/ behaviour. It's not merely enough to copy an existing installation from /home/username/Documents to /usr/local/bin and reinstall the service from there. AGH's initial setup must've occured from a clean slate in /usr/local/bin, which finally seems to have made AGH start as a service on boot.

This allowed me to avoid the dreaded (and honestly bewilderingly non-verbose) "203 exited-code" status, so I can only presume that it's nice info to add to the FAQ and to the Fedora section's title.

Proposed Solution

In the wiki pages, add info on SELinux and various causes of status '203 / exited-code' in Fedora, and to add them more prominently if possible. Probably also add info in "Getting Started" on that AGH is completely unable to run as a service from /home/ on distros that use SELinux.

Alternatives Considered

None that I can't think of.

Additional Information

I know I did a lot to try to fix the problem, including forking=1; setting AdGuardHome/data to be writeable by all users (In one instance I failed to reproduce later on, the data folder was write-protected for non-root users); and extending StartLimitInterval and StartLimitBurst in /etc/systemd/system/AdGuardHome.service to 15 and 30 respectively.

@ainar-g ainar-g self-assigned this Jun 23, 2021
@ainar-g ainar-g added this to the v0.107.0 milestone Jun 23, 2021
@ainar-g
Copy link
Contributor

ainar-g commented Dec 16, 2021

@DandelionSprout, sorry for the long wait. We've added your suggestions to the Getting Started and the FAQ entries. Do you think that the information we've added is enough?

@ainar-g
Copy link
Contributor

ainar-g commented Dec 21, 2021

I'll close this issue for now. Feel free to report new documentation issues!

@ainar-g ainar-g closed this as completed Dec 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants