[Bug 1624262] Re: clamav unable to create pid file using systemd
[Expired for clamav (Ubuntu) because there has been no activity for 60 days.] ** Changed in: clamav (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624262 Title: clamav unable to create pid file using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1624262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624262] Re: clamav unable to create pid file using systemd
The systemd service these days doesn't use a pidfile at all anymore. It uses "normal" systemd handling of a single process service which will poulate $MAINPID that can be referenced from associated systemd services. You can fetch those via: systemctl show -p MainPID clamav-daemon Actually it was that way in Xenial already and I'm not sure how much that is an issue to SRU to trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624262 Title: clamav unable to create pid file using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1624262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624262] Re: clamav unable to create pid file using systemd
I came by cleanin gup bugs that were dormant for too long, and I beg your pardon for thise being that way. Yet I hope my explanation helps. If you think this is really needed for former releases or if I missed sometihng plese set back to new. ** Changed in: clamav (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624262 Title: clamav unable to create pid file using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1624262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624262] Re: clamav unable to create pid file using systemd
** Tags added: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624262 Title: clamav unable to create pid file using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1624262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624262] Re: clamav unable to create pid file using systemd
Same here and in conjunction with Monit, causes lots of error log entries -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624262 Title: clamav unable to create pid file using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1624262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624262] Re: clamav unable to create pid file using systemd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: clamav (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624262 Title: clamav unable to create pid file using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1624262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624262] Re: clamav unable to create pid file using systemd
I forgot to mention that the above solution works within our LXC guest environments, but it is not sufficient when running on physical hardware. It seems, that the clamav startup scripts are executed a bit too early. When they are started, the folder /run or /var/run is not yet a tmpfs. So the PID files will be written to the harddisk instead of the tmpfs. When the system is now putting the tmpfs over /run the PIDs are virtually gone and the monitoring service is unable to see them. The systemd scripts clamav-daemon.service and clamav-freshclam.service both require clamav-daemon.socket, so it is necessary to postpone the execution of it a little bit. I have added the following line to /lib/systemd/system/clamav-daemon.socket: After=network.target Honestly I don't know which service is the best one to wait for here. I just chose network.target, because I knew it is going to be late enough. Maybe someone has a better idea here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624262 Title: clamav unable to create pid file using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1624262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
