Package: fwknop-server Version: 2.6.9-1+b1 Severity: important Restarting the server using systemctl does not do anything:
See the command line: ----------------------------------------------------------- root@homebox /etc/fwknop# pidof fwknopd 27175 root@homebox /etc/fwknop# systemctl restart fwknop-server root@homebox /etc/fwknop# pidof fwknopd 27175 ----------------------------------------------------------- And the logs: ----------------------------------------------------------- Oct 20 17:10:29 homebox systemd[1]: Stopping LSB: start and stop fwknopd... Oct 20 17:10:29 homebox fwknop-server[27340]: Stopping FireWall KNock OPerator: fwknopd. Oct 20 17:10:29 homebox systemd[1]: Stopped LSB: start and stop fwknopd. Oct 20 17:10:29 homebox systemd[1]: Starting LSB: start and stop fwknopd... Oct 20 17:10:29 homebox fwknop-server[27345]: Starting FireWall KNock OPerator: fwknopd. Oct 20 17:10:29 homebox systemd[1]: Started LSB: start and stop fwknopd. Oct 20 17:10:29 homebox fwknop-server[27345]: [*] An instance of fwknopd is already running: (PID=27175). ----------------------------------------------------------- This is a major issue, especially if I modify the keys and restart the server, I could loose access to my server! -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fwknop-server depends on: ii iptables 1.6.0+snapshot20161117-6 ii libc6 2.24-11+deb9u3 pn libfko3 <none> ii libpcap0.8 1.8.1-3 ii lsb-base 9.20161125 fwknop-server recommends no packages. Versions of packages fwknop-server suggests: pn fwknop-apparmor-profile <none>
