| Summary: | clamd causes shutdown/reboot to hang, forcing hard poweroff. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Greg McGee <gjmcgee> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | thomas |
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | clamd-0.97.8-1.mga3 | CVE: | |
| Status comment: | |||
|
Description
Greg McGee
2013-06-23 09:28:10 CEST
still hangs up with clamd uninstalled, system hangs trying to run the clamav update daemon.(strange it works just killing clamd... but it does) Thomas, can you (as maintainer of this package) have a look at this please? Might it be related to a faulty systemd unit file perhaps? CC:
(none) =>
thomas Whatever it is, the issue persisted even after uninstalling clamav etc, just did a clean reinstall to clean it up forcibly. (have to love fast USB sticks and having /home on its own partition, done with updates and a load of add-ons in ~20 minutes) I can snarf an image of the current clean install before doing any diagnostics if directed as to what needs to be done. The strangest thing was it would shut down or reboot clean _once_ after doing a fsck to unbork itself, then hang again on the next cycle. It was working fine prior to installing clamav, no malware concerns, I just like to have it handy to make a first pass on badly infested Windows drives when trying to unbork a freinds machine on occasion. I will look at it. I haven't experienced the problem on my VB, but before I left I tried to shut down my wife's box with mga3 and I had to use the power button after half way shut down. It doesn't have any clam related packages installed. rpm -qa |grep clam yields nothing. Just got back from a camping trip with no phone service close by and no data service within 100 miles. (So much for the great ads of our top-notch service providers) I checked at several installations all 64 bit and cannot reproduce this problem: 64 bit laptop using magaia3 64 bit Virtualbox using mga3 64 bit Virtualbox using cauldron I also cannot get it to repeat on a fresh install, must have been some mild corruption of some setup/config file, or possibly some other package update that has since been corrected. So I close this as invalid, resp. resolved/worksforme Status:
NEW =>
RESOLVED |