Your message dated Mon, 13 Apr 2020 18:40:31 +0200
with message-id <91cbe842571db08b35e7b3b7b927c9e3e6a0f48e.camel@jff.email>
and subject line Re: openvpn: systemd does not start openvpn after upgrade from
stretch tu buster
has caused the Debian Bug report #939903,
regarding openvpn: systemd does not start openvpn after upgrade from stretch tu
buster
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
939903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openvpn
Version: 2.4.7-1
Severity: normal
Dear Maintainer,
I am running openvpn in a Linux container. I have upgraded openvpn from stretch
to buster version. I have tried to start openvpn with "systemctl start
openvpn". The error in the syslog is:
Sep 10 00:31:17 vpn systemd[1]: Starting OpenVPN connection to server...
Sep 10 00:31:17 vpn systemd[3766]: openvpn@server.service: Failed to set up
mount namespacing: Permission denied
Sep 10 00:31:17 vpn systemd[3766]: openvpn@server.service: Failed at step
NAMESPACE spawning /usr/sbin/openvpn: Permission denied
Sep 10 00:31:17 vpn systemd[1]: openvpn@server.service: Main process exited,
code=exited, status=226/NAMESPACE
Sep 10 00:31:17 vpn systemd[1]: openvpn@server.service: Failed with result
'exit-code'.
Sep 10 00:31:17 vpn systemd[1]: Failed to start OpenVPN connection to server.
I would expect openvpn to start normally without errors.
I have tried to add the following lines to the systemd unit, but it has not
helped:
PrivateTmp=false
NoNewPrivileges=yes
I have tried to manually run openvpn with these commands:
/usr/sbin/openvpn --daemon ovpn-server --status /run/openvpn/server.status 10
--cd /etc/openvpn --config /etc/openvpn/server.conf --writepid
/run/openvpn/server.pid
openvpn --config /etc/openvpn/server.conf
Both commands were successful.
Regards,
Mikolaj Menke
-- System Information:
Debian Release: 10.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.18-16-pve (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8),
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages openvpn depends on:
ii debconf [debconf-2.0] 1.5.71
ii iproute2 4.20.0-2
ii libc6 2.28-10
ii liblz4-1 1.8.3-1
ii liblzo2-2 2.10-0.1
ii libpam0g 1.3.1-5
ii libpkcs11-helper1 1.25.1-1
ii libssl1.1 1.1.1c-1
ii libsystemd0 241-7~deb10u1
ii lsb-base 10.2019051400
Versions of packages openvpn recommends:
ii easy-rsa 3.0.6-1
Versions of packages openvpn suggests:
ii openssl 1.1.1c-1
pn openvpn-systemd-resolved <none>
pn resolvconf <none>
-- debconf information:
openvpn/create_tun: false
--- End Message ---
--- Begin Message ---
Hello Mikolaj,
thank you for spending your time helping to make Debian better with
this bug report.
Niklas Miller has described the solution. I therefore close this bug.
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key : 8CA1D25D
CAcert Key S/N : 0E:D4:56
Old pgp Key: BE581B6E (revoked since 2014-12-31).
Jörg Frings-Fürst
D-54470 Lieser
git: https://jff.email/cgit/
Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst
My wish list:
- Please send me a picture from the nature at your home.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
