Zimbra fails to start after installation

[andreychek]

Originally Posted by Alex--

OK, found it...

I was installing on "minimal installation" CentOS 4.2 box. The installation manuall for Zimbra says "acceppt all default answers" (which means full Desktop install, are they out of their mind?) except for... So, after I did full Desktop install, then installed Zimbra, it started up just fine.

That's great, I'm glad it's working for you.

For the record (and anyone else who ends up trying CentOS), I did a basic server install, added a few extra packages (I forget which, they were unrelated to Zimbra), and it's working great for me... both the OSS and Network Edition.

So, there's something that's different in your new install that's allowing it to work.... but I don't think it's a requirement that one do a desktop install in order for Zimbra to function (regardless of what the instructions say :-)

It'd be interesting to learn what the difference between your original install and this new one are, that's allowing it to work. Either way, I'm glad that it is working though :-)

Have a good one,
-Eric

[Alex--]

Well, the only difference is the number of packages intalled (150 vs. 600). Everything else was absolutely the same.

[goetzi]

For the record too:

I also have sucessfully running Zimbra Network Edition on CentOS 4.2 (Server, the "one-cd-edition"). I only did a "Minimal-install". Then I ran "yum update", "yum install fetchmail", and "yum install xyz" for all think that ZCS wanted when running install.sh. I edited my /etc/hosts like this , finally I had to do this steps, but now it is running fine.

If some guys need it I can make a proper "step-by-step-howto", then I will do a new ZCS install on CentOS in a virtual machine.

[Eugênio Nassu]

Originally Posted by marcmac

Not everyone pays attention to the nsswitch.conf file when deciding how to resolve hostnames. I'm specifically referring to ldap and postfix - which is why I asked for the output of `host localhost`. If that returns 127.0.0.1, you're good.

So, if ldap starts (su - zimbra, ldap start) can you telnet to port 389?

ANything in /tmp/install.log or /tmp/zmsetup.log?

I followed almost every post about this error.
It seems that LDAP starts, but I can't reach the 329 port
/etc/hosts seems to be ok
what can I do ? I'm using Fedora 4 and it is all updated.

[marcmac]

Can you reach port 389?

[Eugênio Nassu]

Typo. I meant 389

[marcmac]

ps auxww | grep slapd - is it running?
su - zimbra
sh -x bin/ldap start - any errors?
remove loglevel 0 from conf/slapd.conf and restart - any errors in /var/log/zimbra.log?

[Eugênio Nassu]

Dec 5 16:16:28 isis zimbramon[2122]: 2122:info: Starting services
Dec 5 16:16:28 isis slapd[2143]: @(#) $OpenLDAP: slapd 2.2.28 (Nov 9 2005 13:38:12) $ root@build-fc4.liquidsys.com:/home/build/p4/main/ThirdParty/openldap/openldap-2.2.28/servers/slapd
Dec 5 16:16:28 isis slapd[2143]: bdb_db_init: Initializing BDB database
Dec 5 16:16:28 isis slapd[2143]: main: TLS init def ctx failed: -1
Dec 5 16:16:28 isis slapd[2143]: slapd stopped.
Dec 5 16:16:28 isis slapd[2143]: connections_destroy: nothing to destroy.

Excerpt from zimbra.log

[marcmac]

Search the forums for ldap and certificate problems, that's what's happening here.