Yeah.... the server sucks, it's high on my list of 'must replace' but currently its running in a VM on a Proliant server with two Xeon 900MHz chips and a whopping 1gb ram, of which around 650mb is available to the zimbra install. Yes, I know this is below spec but it worked ok on beta 3 (admittedly with the AV turned off for good measure).
I'll be replacing it with something sane really soon.
free -m shows:
Code:
total used free shared buffers cached
Mem: 627 585 42 0 15 358
-/+ buffers/cache: 210 416
Swap: 690 0 690
The os is debian etch updated as much as possible via aptitude upgrade, the native drives are raid 5 ultra scsi3's but as it's in a VM I doubt that's seen by the os.
Disk space is as follows
Code:
root@zimbra~ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 15G 7.1G 6.4G 53% /
tmpfs 314M 0 314M 0% /lib/init/rw
udev 10M 52K 10M 1% /dev
tmpfs 314M 0 314M 0% /dev/shm
Thanks for your help, it may well be a result of the server being under spec, and if that's the case then I'll increase the priority of replacing it, but perhaps a better error could be reported saying something like "Are you crazy, you cant run Zimbra on this!"
