Zimbra an Centos 4.2 fail to start

[eaperezh]

Hi, I installed zimbra on a centos 4.2 with 756 mb ram and 80 gig disk VM.

When the centos boots, it fails to start zimbra and this is the only thing reflected on the system.

zmcontrol status: cannot determine services

and ps ax reveals that only slapd is running.

what other info can I post here?

Thanks,

[eaperezh]

BTW I also happen to have thounsands of "Too many open files" error message.

[marcmac]

Search the forums for "utf8" and i18n to find the change to /etc/sysconfig/i18n.

[eaperezh]

That solved the problem.
The lines that start with # are the original ones.
BTW, given the fact that I didnt find an explanation, what does this change mean?

LANG="en_US"
#LANG="en_US.UTF-8"
SUPPORTED="en_US:en:es_MX:es:es_PA:es:es_ES:es"
#SUPPORTED="en_US.UTF-8:en_US:en:es_MX.UTF-8:es_MX:es:es_PA.UTF-8:es_PA:es:es_ES.UTF-8:es_ES:es"
SYSFONT="latarcyrheb-sun16"

thanks,

[marcmac]

What does it mean? I don't know, actually (other than, zimbra on a VM works)

[slayer]

I checked my RHEL4 and it also has the "UTF-8" but i don't see any post regarding unicode issues unlike with CentOS. Any explaination?

[marcmac]

Any explanation for what? It's seems less connected to OS than to running on a virtual machine (vmware is where I've seen it).

[mubley]

FYI...the UTF8 problem is not just limited to virtual machines. The problem can be duplicated on real hardware (no VM) with Fedora Core 4 or CentOS 4.2 if you choose a Minimal OS installation (no GUI). I'm not sure what the difference is in the minimal OS installation that creates the UTF8 problem. In any case, the fix listed above resolves the issue.

[slayer]

Yup, taking out UTF8 on i18n does fix the problem.

[KevinH]

http://wiki.zimbra.com/index.php?tit..._unicode_start

If you have anything to add or other recommendations please update the wiki.