Replies: 4 comments 1 reply
-
Just random advice that you probably don't need that. Since systemd v240 (2018Q2) the default should be |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Tried it, no delta - thinking it may be that coredns needs to wait until the network connection is up? It says to wait on |
Beta Was this translation helpful? Give feedback.
-
Not sure sorry, I don't write systemd service configs often. You'd want to try look through logs to try identify what could be causing the issue. You could try introducing a delay like 5-10 sec and if that consistently starts then it's probably a race condition and you need that extra dependency identified. |
Beta Was this translation helpful? Give feedback.
-
|
Will give it a try, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
lgtm, not sure if working directory ~ is valid thou that's what I use cat <<'EOF' > /etc/systemd/system/coredns.service
[Unit]
After=network.target
Description=coredns server
Documentation=http://coredns.io
[Service]
User=coredns
Type=simple
EnvironmentFile=/etc/sysconfig/coredns
ExecStart=/usr/bin/coredns --conf=/etc/coredns/Corefile $EXTRA_ARGS
ExecReload=/bin/kill -HUP $MAINPID
Restart=on-failure
RestartSec=10
SuccessExitStatus=0
[Install]
WantedBy=multi-user.target
EOF
echo 'EXTRA_ARGS=' > /etc/sysconfig/coredns
mkdir -p /etc/systemd/system/coredns.service.d/
cat <<'EOF' > /etc/systemd/system/coredns.service.d/override.conf
[Service]
AmbientCapabilities=CAP_NET_BIND_SERVICE
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
NoNewPrivileges=true
EOFcould it be selinux? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have coredns set up to start on systemd, as a service. The service file is,
But ... after reboot, it always fails - does not start up. Manually restart it, no issues. Thinking perhaps it's a dependency of sorts? Any thoughts?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions