Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34328 - [darkstat] fails to start as systemd service
Attached to Project:
Community Packages
Opened by Darko Pantić (pdarko) - Friday, 15 March 2013, 19:24 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 18 March 2013, 12:17 GMT
Opened by Darko Pantić (pdarko) - Friday, 15 March 2013, 19:24 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 18 March 2013, 12:17 GMT
|
DetailsDescription:
Darkstat service fails to start during boot process Additional info: * package version(s) 3.0.715-7 * config and/or log files etc. # systemctl status darkstat darkstat.service - Network statistics gatherer (packet sniffer) Loaded: loaded (/usr/lib/systemd/system/darkstat.service; enabled) Active: failed (Result: exit-code) since Fri 2013-03-15 17:17:55 AZOT; 8min ago Process: 208 ExecStopPost=/bin/rm -f /var/darkstat/darkstat.pid (code=exited, status=0/SUCCESS) Process: 193 ExecStart=/usr/sbin/darkstat --user darkstat --chroot /var/darkstat --import darkstat.dat --export darkstat.dat --pidfile /var/darkstat/darkstat.pid -b 0.0.0.0 -i $DARKSTAT_IFACE $DARKSTAT_ARGS (code=exited, status=1/FAILURE) Mar 15 17:17:57 arch darkstat[193]: 201: error: pcap_open_live(): eth0: That device is not up Steps to reproduce: After installing darkstat (# pacman -S darkstat) enable darkstat service (# systemctl enable darkstat) and reboot. As you can see from service status (# systemctl status darkstat) service failed because network is not up, which means darkstat is started before network. This problem can be fixed by ensuring that network is up before darkstat service is started. Hence adding After=network.target to darkstat.service will fix it. |
This task depends upon