Hsphere 2.4.3 and clamav

[ladylinux]

Hi,

Oh yes before the migration this same server's disk filled up because of clamd files in /var/hsphere/XXXX

Francesca

[ghost]

Is this server running Centos5 and the latest mail package?

I just checked some boxes running Hsphere 3.3 and theirs is listed:

clamd daemon 0.95.2 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64)

The problem is with clamd daemon 0.94 only From all my Hsphere 3.3 server they are running 0.95.2 and this issue with filling up disk space doesn't happen.

So either 1 this server was never updated with the lates mail rpms for whatever reason or 2 it is happening with certain OS or version that for some reason never had clam update like FreeBSD or Centos3.

All servers I checked are Centos5 64Bit running the latest mail package hsphere-mail-service-5-9.

[ghost]

Sorry I missed in your reply where you listed the mail package and that it is installed by default.

Unfortunately I have to disagree.
http://64.131.90.141/shiv/HS/release...33.0P1/pkglist

lists the latest mail packages as 5-9 So I feel that possible you have hsphere-mail-service disabled in the updater.
What I find very odd though is mail package 4-44 was not ever used in a in an Hsphere 3.3 release. They started at 5-3. Hsphere 3.2 is using 4-44.

[ladylinux]

Jeffery,

No I do not have it disabled .. anyhow I just migrated this a couple weeks ago and that is what is loaded on this 32 bit Centos 5.X box.

I would not be such a idiot to force load the 4-44 package so its some sort of weirdness with this server.

I would reload again but then I would find myself having to scramble to disable the cron job and also then replace the corrupt dbs with ones that don't cause exceptions.

You do see up a bit that Steve West also see's this issue (3.2 patch 2) as well as I think Marksys.

And despite asking one hundred times here including actual support tickets put into Parallels support. (They told us to wait until Sept for a 3.3 update to Clamav to fix this)

Anyhow .. we would not be debating this had Parallels supplied a mail service package newer that over a year ago.

Francesca

[ghost]

I understand it happens with 3.2 also, my post orginially started at 2.4.3 but for Hsphere 3.3P1 it can't be possible based on the pkglist listed. There is some weirdness with the install on that server or the wrong package updater was used, or maybe the server hosts file points to an incorrect ip for the download, there are a bunch of other causes. I just did a 3.3 mail install and the latest packages are installed 5-9. I have did many updates all to get the 5-9 package.

I understand parallels caused the whole issue by not releasing updates for all clam but for every versions under Hsphere 3.3 but you can manually load that 4-46 (which you know) that fixes it but for 3.1 and 3.2 this would be done manual ofcourse.

I know you know your shit I am not doubting you on anything but there has to be some reason for you to get mailpackage 4-44 on a Hsphere 3.3P1 cluster. I can't duplicate that on any cluster. This is not saying you are nuts or incorrect. But there has to be a reason you get that and I dont, I am happy to help brainstorm with you to try and figure it out but I also understand you are very busy as well as I.


For everyone that comes across clamd filling up the drive with crap in a matter of minutes. We are talking gigs and gigs in under 3minutes.

For parallels to fix this they need to update 2 package lists with 4-46 mail server
http://64.131.90.141/shiv/HS/release...32.0P2/pkglist
http://64.131.90.141/shiv/HS/release...31.0P1/pkglist

For anyone on Hsphere 3.1 or 3.2 download the new mail files which have new clam and install it manually.
http://64.131.90.141/shiv/HS/RHES5/h...rvice-4-46.rpm
http://64.131.90.141/shiv/HS/RHES5_6...rvice-4-46.rpm
http://64.131.90.141/shiv/HS/RHES4/h...rvice-4-46.rpm
http://64.131.90.141/shiv/HS/RHES4_6...rvice-4-46.rpm

For Hsphere 3.3P1 just download:
wget http://64.131.90.141/shiv/HS/release...33.0P1/U33.0P1
run the file:
sh U33.0P1
Then run the hspackages to update the system:
hspackages ip=x.x.x.x
x.x.x.x being the ip for the mailserver