I think this is a bug I fixed recently - on startup, zimbra tries to read it's config, and there's some bad code (mine) that will basically hang forever trying to read it if the system's busy. I fixed that, I hope, and it should show up in the next release.
(This is a hard bug to reproduce, since you have to reboot the server to make it happen. I think it's related to JVM initialization on startup being kinda slow) |