starred/acme-dns
1
0
Fork 0
mirror of https://github.com/acme-dns/acme-dns.git synced 2026-04-27 04:45:48 +03:00
Code Issues 178 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #87] make an acme-dns log when used via systemd #34

New issue
Open
opened 2026-03-13 15:27:29 +03:00 by kerem · 5 comments
kerem commented 2026-03-13 15:27:29 +03:00
Owner
Copy link

Originally created by @jvanasco on GitHub (May 30, 2018).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/87

right now logging goes into syslog and can be a bit messy to parse/understand as many services output there. a dedicated log would be nice.

Originally created by @jvanasco on GitHub (May 30, 2018). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/87 right now logging goes into `syslog` and can be a bit messy to parse/understand as many services output there. a dedicated log would be nice.
kerem commented 2026-03-13 15:27:40 +03:00
Author
Owner
Copy link

@joohoi commented on GitHub (May 31, 2018):

This is very true, and it's on the TODO list in readme. Needs an (mental) priority bump for the stated reasons however. I'll leave this issue up for reminder.

<!-- gh-comment-id:393688893 --> @joohoi commented on GitHub (May 31, 2018): This is very true, and it's on the TODO list in readme. Needs an (mental) priority bump for the stated reasons however. I'll leave this issue up for reminder.
kerem commented 2026-03-13 15:27:45 +03:00
Author
Owner
Copy link

@cbricart commented on GitHub (Jun 8, 2018):

actually, when started under systemd any logging should got to stdout/stderr (that also applies to running containerized) - systemd will catch those outputs and send them to systemd-journald(8) which may then be comfortably queried with journalctl(1):
$> journalctl -u acme-dns.service

<!-- gh-comment-id:395675109 --> @cbricart commented on GitHub (Jun 8, 2018): actually, when started under systemd any logging should got to stdout/stderr (that also applies to running containerized) - systemd will catch those outputs and send them to `systemd-journald(8)` which may then be comfortably queried with `journalctl(1)`: `$> journalctl -u acme-dns.service`
kerem commented 2026-03-13 15:27:50 +03:00
Author
Owner
Copy link

@LinuxCuba commented on GitHub (Aug 13, 2018):

`root@certbot:/# systemctl status acme-dns.service

  • acme-dns.service - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely
    Loaded: loaded (/etc/systemd/system/acme-dns.service; enabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Mon 2018-08-13 12:22:01 UTC; 4s ago
    Process: 24577 ExecStart=/usr/local/bin/acme-dns (code=exited, status=1/FAILURE)
    Main PID: 24577 (code=exited, status=1/FAILURE)`
<!-- gh-comment-id:412500686 --> @LinuxCuba commented on GitHub (Aug 13, 2018): `root@certbot:/# systemctl status acme-dns.service * acme-dns.service - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely Loaded: loaded (/etc/systemd/system/acme-dns.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-08-13 12:22:01 UTC; 4s ago Process: 24577 ExecStart=/usr/local/bin/acme-dns (code=exited, status=1/FAILURE) Main PID: 24577 (code=exited, status=1/FAILURE)`
kerem commented 2026-03-13 15:27:55 +03:00
Author
Owner
Copy link

@LinuxCuba commented on GitHub (Aug 13, 2018):

Once that worked, a permissions problem prevented reading the encryption certificates of the domain in which the daemon runs.
* acme-dns.service - Limited DNS server with RESTful HTTP API to handle ACME DNS Loaded: loaded (/etc/systemd/system/acme-dns.service; enabled; vendor preset: Active: active (running) since Mon 2018-08-13 14:32:58 UTC; 4s ago Main PID: 25024 (acme-dns) Tasks: 4 (limit: 4915) CGroup: /system.slice/acme-dns.service -25024 /usr/local/bin/acme-dns

Aug 13 14:32:58 certbot systemd[1]: acme-dns.service: Failed to reset devices.li
Aug 13 14:32:58 certbot systemd[1]: Started Limited DNS server with RESTful HTTP
Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=info
Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=debug
Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=debug
Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=debug
Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=debug
Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=debug
Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=info
Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=inf`

<!-- gh-comment-id:412541046 --> @LinuxCuba commented on GitHub (Aug 13, 2018): Once that worked, a permissions problem prevented reading the encryption certificates of the domain in which the daemon runs. `* acme-dns.service - Limited DNS server with RESTful HTTP API to handle ACME DNS Loaded: loaded (/etc/systemd/system/acme-dns.service; enabled; vendor preset: Active: active (running) since Mon 2018-08-13 14:32:58 UTC; 4s ago Main PID: 25024 (acme-dns) Tasks: 4 (limit: 4915) CGroup: /system.slice/acme-dns.service `-25024 /usr/local/bin/acme-dns Aug 13 14:32:58 certbot systemd[1]: acme-dns.service: Failed to reset devices.li Aug 13 14:32:58 certbot systemd[1]: Started Limited DNS server with RESTful HTTP Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=info Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=debug Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=debug Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=debug Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=debug Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=debug Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=info Aug 13 14:32:59 certbot acme-dns[25024]: time="2018-08-13T14:32:58Z" level=inf`
kerem commented 2026-03-13 15:28:01 +03:00
Author
Owner
Copy link

@LinuxCuba commented on GitHub (Aug 13, 2018):

Despite being working, why this error?
systemd[1]: acme-dns.service: Failed to reset devices.list

<!-- gh-comment-id:412541631 --> @LinuxCuba commented on GitHub (Aug 13, 2018): Despite being working, why this error? systemd[1]: acme-dns.service: Failed to reset devices.list
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
fix_dockerhub
dockerhub
readme2.0
goreleaser_action
refactoring
linter_update_config
update_deps_122
dependabot/go_modules/github.com/valyala/fasthttp-1.34.0
deps_bump
update_goreleaser
update_golint
deps_update
update_dockerfile
v2.0.2
v2.0.1
v2.0
v1.1
v1.0
v0.8
v0.7.2
v0.7.1
v0.7
v0.6
v0.5
v0.4
v0.3.2
v0.3.1
v0.3
v0.2
v0.1
Labels
Clear labels   
Documentation

   
Documentation

   
bug

   
enhancement

   
feature request

   
feature request

   
help wanted

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
security

   
security

   
testing
No labels
Documentation
Documentation
bug
enhancement
feature request
feature request
help wanted
pull-request
question
security
security
testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/acme-dns#34
No description provided.