'zmmailboxdctl is not running'

[cd084]

HELP!!!!

Just got back from my Christy Hol's to have my server go down in flames... As it turned out some bad memory, that fixed the server is now running... but NOT Zimbra. I have gone back several days worth of backups and always get the same when starting Zimbra 'zmmailboxdctl is not running' and I can not access it via the gui/http. I have gone through the forums and found references to a possible java memory problem and have increased the memory usage from 30 to 50 with out success. Can anybody possibly point me in the right direction, I have been looking at logs, but unsure at what I should be looking for, or were.
The only other thing that I have noticed is a large increase in the zimbra directory size, where it averaged around 5Gb its now 8.5Gb.

[mmorse]

Post some snips from /opt/zimbra/log/mailbox.log & zmmailboxd.out after a stop/start.

[cd084]

The mailbox.log has not received anything new, its last entry is from the backup at 1am on the 25dec.
The zmmailboxd.out is not time stamped so I have just pasted the last 20 or so lines:

Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Invalid initial heap size: -Xms4441m
The specified size exceeds the maximum representable size.
Could not create the Java virtual machine.
Invalid initial heap size: -Xms4441m
The specified size exceeds the maximum representable size.
Could not create the Java virtual machine.
Invalid initial heap size: -Xms4441m
The specified size exceeds the maximum representable size.
Could not create the Java virtual machine.
Invalid initial heap size: -Xms4441m
The specified size exceeds the maximum representable size.
Could not create the Java virtual machine.
Invalid initial heap size: -Xms4441m
The specified size exceeds the maximum representable size.
Could not create the Java virtual machine.
Invalid initial heap size: -Xms4441m
The specified size exceeds the maximum representable size.
Could not create the Java virtual machine.
Invalid initial heap size: -Xms4441m
The specified size exceeds the maximum representable size.
Could not create the Java virtual machine.
Invalid initial heap size: -Xms4441m
The specified size exceeds the maximum representable size.
Could not create the Java virtual machine.

[cd084]

Maybe I should be a little more details... After I got the machine up and going again zimbra would not start at all. I tried the previous several days (I only have a seven day rotation) and all were the same 'zmmailboxdctl is not running', but at least it sort of started. I am currently trying to work with my "last successfully backup" NOT the version that was running at the time of the crash. In my frustration I may have done a fopar and upgraded from 5.0.10 to 5.0.11.. how ever the problem is the same.

[jeeves]

Maybe I should be a little more details... After I got the machine up and going again zimbra would not start at all. I tried the previous several days (I only have a seven day rotation) and all were the same 'zmmailboxdctl is not running', but at least it sort of started. I am currently trying to work with my "last successfully backup" NOT the version that was running at the time of the crash. In my frustration I may have done a fopar and upgraded from 5.0.10 to 5.0.11.. how ever the problem is the same.

How much RAM do you have? You shud reduce the java heap memory percentage in my opinion .

[cd084]

How much RAM do you have? You shud reduce the java heap memory percentage in my opinion .

8.7Gb

I have set it back to 37 percent after trying everything from 30 - 75.

[jeeves]

Try something between 15 - 20 %. At 37 % you are probably over allocating the amount of memory required.

[cd084]

Try something between 15 - 20 %. At 37 % you are probably over allocating the amount of memory required.

jeeves... You are the man!!!
Thanks mate, 15% did the trick. I can now start trying to glue all the hair back onto my head ;-)