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

make an acme-dns log when used via systemd #87

Open
jvanasco opened this issue May 30, 2018 · 5 comments
Open

make an acme-dns log when used via systemd #87

jvanasco opened this issue May 30, 2018 · 5 comments

Comments

@jvanasco
Copy link
Contributor

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.

@joohoi
Copy link
Owner

joohoi commented 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.

@cbricart
Copy link

cbricart commented 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

@LinuxCuba
Copy link

`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)`

@LinuxCuba
Copy link

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`

@LinuxCuba
Copy link

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

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

4 participants