Package: arpwatch Version: 2.1a15-1.3 Severity: important Hi, after an upgrade from wheezy to jessie on a QNAP TS-419P+ (armel), I've noticed that arpwatch fails to start during boot.
Starting arpwatch manually by ssh'ing in as root and running: >service arpwatch stop >service arpwatch start seems to work. Perhaps there is something with the new systemd setup that causes arpwatch to start too early, before the ethernet devices are configured? This is the output of "journalctl|grep arpwatch": Apr 05 21:54:57 hostname arpwatch[1056]: Running as uid=109 gid=105 Apr 05 21:54:57 hostname arpwatch[1056]: Link layer type 113 not ethernet or fddi Apr 05 21:54:58 hostname arpwatch[963]: Starting Ethernet/FDDI station monitor daemon: (chown arpwatch /var/lib/arpwatch/arp.dat) arpwatch. Apr 05 21:56:21 hostname arpwatch[1426]: Stopping Ethernet/FDDI station monitor daemon: arpwatch. Apr 05 21:56:22 hostname arpwatch[1449]: Starting Ethernet/FDDI station monitor daemon: (chown arpwatch /var/lib/arpwatch/arp.dat) arpwatch. Apr 05 21:56:22 hostname arpwatch[1454]: Running as uid=109 gid=105 Apr 05 21:56:22 hostname arpwatch[1454]: listening on eth0 Also, while manually starting after boot has worked 3-4 times after the upgrade, on the last reboot and manual stop+start, I started getting new host about every host on the LAN at once. Looking in /var/lib/arpwatch/, I saw "arp.dat" was 0 bytes (while an older "arp.dat-" had the old database. Cheers, -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 3.16.0-4-kirkwood Locale: LANG=en_US.UTF-8, LC_CTYPE=nb_NO.iso88591 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages arpwatch depends on: ii adduser 3.113+nmu3 ii libc6 2.19-17 ii libpcap0.8 1.6.2-2 arpwatch recommends no packages. arpwatch suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
