Public bug reported:
I've configured danted to be startup automatically during system bootup.
Hower, it fails with the following error:
---8<---
Jun 04 17:20:47 max systemd[1]: Starting SOCKS (v4 and v5) proxy daemon
(danted)...
Jun 04 17:20:47 max systemd[1]: Started SOCKS (v4 and v5) proxy daemon (danted).
Jun 04 17:20:47 max danted[3209]: warning: int_ifname2sockaddr(): interface
"enp0s31f6" has no usable IP-addresses configured
Jun 04 17:20:47 max danted[3209]: error: /etc/danted.conf: problem on line 53
near token "enp0s31f6": could not resolve hostname "enp0s31f6": Temporary
failure in name re>
Jun 04 17:20:47 max danted[3209]: alert: mother[1/1]: shutting down
Jun 04 17:20:47 max systemd[1]: danted.service: Main process exited,
code=exited, status=1/FAILURE
Jun 04 17:20:47 max systemd[1]: danted.service: Failed with result 'exit-code'.
--->8---
When I later try to start it manually using 'systemctl' it starts up
without issues.
I was able to fix it using this patch:
---8<---
--- /lib/systemd/system/danted.service 2021-06-06 16:05:47.208029695 +0200
+++ /lib/systemd/system/danted.service~ 2021-06-06 16:05:38.000000000 +0200
@@ -1,7 +1,7 @@
[Unit]
Description=SOCKS (v4 and v5) proxy daemon (danted)
Documentation=man:danted(8) man:danted.conf(5)
-After=network-online.target
+After=network.target
[Service]
Type=simple
--->8---
This suggests that when "network.target" is reached, not all required
services are set up yet.
IMHO dependency needs to be changed to "network-online.target" or
something more appropriate.
Please note that I'm running this computer as a permanently LAN
connected stationary desktop workstation. If it's a mobile computer
using WiFi, UMTS or something, "network-online.target" might not be the
best choice (I'm judging this by the label "network-online" without
knowing in detail what that target means).
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: dante-server 1.4.2+dfsg-7build3 [modified:
lib/systemd/system/danted.service]
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sun Jun 6 16:01:00 2021
InstallationDate: Installed on 2019-11-25 (559 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: dante
UpgradeStatus: Upgraded to hirsute on 2021-06-04 (1 days ago)
modified.conffile..etc.danted.conf: [modified]
mtime.conffile..etc.danted.conf: 2019-11-25T21:46:38.038876
** Affects: dante (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute
** Summary changed:
- danted does not start on system startup as systemd dependency is wrong
+ danted does not start on system startup as systemd dependency seems to be
wrong
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931019
Title:
danted does not start on system startup as systemd dependency seems to
be wrong
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dante/+bug/1931019/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
