Just like the subject says, since installing 6.304 we have been getting alerts just about every hour saying that clamd isn't running and has been restarted.
Astaro re-rolled 6.304, I'm sure in part to fix this issue.
I am waiting for my co-worker to get in to see if he got a response from Astaro support on how to resolve this issue on machines running the old 6.304.
Astaro, you seriously need to rethink your update process when things break like this.
If you added a minor version number to releases (6.304.1, etc) then you could release minor updates without any manual intervention.
Machines running 6.303 would upgrade directly to 6.304.1 (any minor releases supersede the previous). Machines running 6.304 would get a special update to get them up to 6.304.1.
Edit: There is a note in the middle of the 6.304 release notes which indicate that rebooting the server should fix the issue. What about servers where I am unable to reboot the server to maintain uptime?
Astaro re-rolled 6.304, I'm sure in part to fix this issue.
I am waiting for my co-worker to get in to see if he got a response from Astaro support on how to resolve this issue on machines running the old 6.304.
Astaro, you seriously need to rethink your update process when things break like this.
If you added a minor version number to releases (6.304.1, etc) then you could release minor updates without any manual intervention.
Machines running 6.303 would upgrade directly to 6.304.1 (any minor releases supersede the previous). Machines running 6.304 would get a special update to get them up to 6.304.1.
Edit: There is a note in the middle of the 6.304 release notes which indicate that rebooting the server should fix the issue. What about servers where I am unable to reboot the server to maintain uptime?
