![]() May 23 16:32:30 us yum: Updated: clamav-scanner-systemd-0.99.noarch May 23 16:32:30 us yum: Updated: clamav-server-systemd-0.99.noarch The upgrade went like this: May 23 16:32:29 us yum: Updated: clamav-filesystem-0.99.noarch Soo - I tried upgrading it once more after the downgrade - and it's the same result. Loading mirror speeds from cached hostfileĬlamav.x86_64 0.99. 0.99. 0.99. 0.99. 0.99. 0.99. 0.99. 0.99. 0.99. 0.99. PackagesĬlamav-data-empty.noarch 0.99. virtualminĬlamav-debuginfo.x86_64 0.99. virtualminĬlamav-milter.x86_64 0.99. virtualminĬlamav-milter-systemd.noarch 0.99. virtualminĬlamav-milter-sysvinit.noarch 0.99. virtualminĬlamav-scanner-sysvinit.noarch 0.99. virtualminĬlamav-server-sysvinit.noarch 0.99. virtualmin This what I get from yum list clam*: # yum list clamav\* ![]() Virtualmin-universal Virtualmin Distribution Neutral Packages 65 Virtualmin/7/x86_64 RHEL/CentOS/Scientific 7 - x86_64 - Virtualmin 150 Yum repolist yields: repo id repo name status For now I've solved it by rolling back to 0.98 with yum and it works perfectly again. I did the changes suggested in your edit, but it didn't change anything when trying to start clamav from Webmin. These are the defaults we ship in our packages. You'll also need to edit /etc/clamd.d/nf to have LocalSocket set to /var/run/clamd.scan/clamd.sock and LocalSocketGroup set to clamscan). rpmnew config files over the existing ones, or edit them to remove the "Example" line. You need those (but given your command example above, it seems like you do have them).Įdit2: And I guess I wasn't clear about what you should do about it. ![]() rpmnew config files to see if that's what happened.Įdit: There is a bug in our installer, however, recently, where the clamav-scanner and clamav-scanner-systemd packages don't get installed and they need to be for Virtualmin to function with clamd. But, if you've gotten other packages from other sources along the way, it may have replaced our working configs with broken configs. In short: Our packages have been tested to work in the general case for Virtualmin (though it's possible uncommon cases might break). I've filed tickets repeatedly about that package shipping with broken configuration, but they've always been closed without action.so I keep packaging clamav. ![]() If you've enabled the EPEL repository, without being explicit about what packages you want to get from it, you could have gotten their ClamAV package, which is distributed with broken config files all around (all of them have "Example" in them, and the clamd configuration does not enable a socket or port for communication, so it won't start at all). Because it is a config file, it's possible for it to not get replaced when upgrading it, so even if you have our package now, you wouldn't necessarily get the nf distributed in our package. :(Īre you sure you haven't had other clamav packages (from sources other than us) installed at some point? nf as we distribute it has never had "Example" in it, so it had to come from some other package. Not sure where to go from here to get clamav to run properly from webmi. ![]() May 23 14:01:20 us systemd: Unit clamav-daemon.socket entered failed state.Īlso - not sure if that's a problem local to our system, but when trying to update with freshclam the "Example" line wasn't commented out in the conf, so that wouldn't run either - commented it out freshclam can run now. May 23 14:01:20 us systemd: Job rvice/start failed with result 'dependency'. May 23 14:01:20 us systemd: Dependency failed for Clam AntiVirus userspace daemon. May 23 14:01:20 us systemd: Failed to listen on Socket for Clam AntiVirus userspace daemon. May 23 14:01:20 us systemd: clamav-daemon.socket control process exited, code=exited status=217 May 23 14:01:20 us systemd: Failed to chown socket at step USER: No such process May 23 14:01:20 us systemd: Starting Socket for Clam AntiVirus userspace daemon. I still can't run it from webmin though - I get this in /var/log/messages: May 23 14:01:20 us systemd: Cannot add dependency job for unit rvice, ignoring: Unit rvice is masked. Now I can run clamd as /usr/sbin/clamd -c /etc/clamd.d/nf -nofork=yes and it can start. In order to try and start it manually I had to rename the database (main.cvd). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |