Zimbra not starting

[FunkyPenguin]

[quote user="tbullock"]What are the details in the /var/log/zimbra.log ?
It should give specifics on why it is not working.

[/QUOTE]

Here is an extract of my zimbra.log:

Aug 30 16:59:52 vulcan postfix/smtpd[20189]: SSL_accept:SSLv3 flush data

Aug 30 16:59:52 vulcan postfix/smtpd[20189]: TLS connection established from vm04-bcn-london.deploy.xenoserver.org[217.147.82.229]: TLSv1 with cipher AES256-SHA (256/256 bits)

Aug 30 16:59:52 vulcan postfix/smtpd[20189]: 656F9E109: client=vm04-bcn-london.deploy.xenoserver.org[217.147.82.229]

Aug 30 16:59:52 vulcan postfix/cleanup[20193]: 656F9E109: message-id=

Aug 30 16:59:52 vulcan postfix/qmgr[17281]: 656F9E109: from=, size=3373, nrcpt=1 (queue active)

Aug 30 16:59:52 vulcan amavis[16267]: (16267-02) ESMTP::10024 /opt/zimbra/amavisd/tmp/amavis-20060830T164136-16267:  ->  Received: SIZE=3373 from mail.forcev.net ([127.0.0.1]) by localhost (mail.forcev.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16267-02 for ; Wed, 30 Aug 2006 16:59:52 +0100 (BST)

Aug 30 16:59:52 vulcan amavis[16267]: (16267-02) Checking: SDV1tlQZci9d [217.147.82.229]  -> 

Aug 30 16:59:52 vulcan postfix/smtpd[20189]: disconnect from vm04-bcn-london.deploy.xenoserver.org[217.147.82.229]

Aug 30 16:59:55 vulcan postfix/smtpd[20199]: initializing the server-side TLS engine

Aug 30 16:59:55 vulcan postfix/smtpd[20199]: connect from localhost[127.0.0.1]

Aug 30 16:59:55 vulcan postfix/smtpd[20199]: 49C841C77C: client=localhost[127.0.0.1]

Aug 30 16:59:55 vulcan postfix/cleanup[20193]: 49C841C77C: message-id=

Aug 30 16:59:55 vulcan postfix/qmgr[17281]: 49C841C77C: from=, size=3947, nrcpt=1 (queue active)

Aug 30 16:59:55 vulcan postfix/smtpd[20199]: disconnect from localhost[127.0.0.1]

Aug 30 16:59:55 vulcan amavis[16267]: (16267-02) FWD via SMTP:  -> , 250 2.6.0 Ok, id=16267-02, from MTA([127.0.0.1]:10025): 250 Ok: queued as 49C841C77C

Aug 30 16:59:55 vulcan amavis[16267]: (16267-02) Passed CLEAN, [217.147.82.229] [82.133.102.210]  -> , Message-ID: , mail_id: SDV1tlQZci9d, Hits: -2.699, 2883 ms

Aug 30 16:59:55 vulcan amavis[16267]: (16267-02) extra modules loaded: Net/LDAP/Bind.pm

Aug 30 16:59:55 vulcan postfix/smtp[20195]: 656F9E109: to=, relay=127.0.0.1[127.0.0.1], delay=3, status=sent (250 2.6.0 Ok, id=16267-02, from MTA([127.0.0.1]:10025): 250 Ok: queued as 49C841C77C)

Aug 30 16:59:55 vulcan postfix/qmgr[17281]: 656F9E109: removed

Aug 30 16:59:55 vulcan postfix/lmtp[20200]: 49C841C77C: to=, relay=mail.forcev.net[192.168.0.10], delay=0, status=deferred (host mail.forcev.net[192.168.0.10] said: 451 4.0.0 Temporary message delivery failure try again (in reply to end of DATA command))

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: connect from vm04-bcn-london.deploy.xenoserver.org[217.147.82.229]

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: setting up TLS connection from vm04-bcn-london.deploy.xenoserver.org[217.147.82.229]

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: SSL_accept:before/accept initialization

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: read from 0816D318 [0815C8E8] (11 bytes => -1 (0xFFFFFFFF))

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: SSL_accept:error in SSLv2/v3 read client hello A

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: read from 0816D318 [0815C8E8] (11 bytes => 11 (0xB))

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: 0000 16 03 01 00 43 01 00 00|3f 03 01                 ....C... ?..

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: read from 0816D318 [0815C8F3] (61 bytes => -1 (0xFFFFFFFF))

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: SSL_accept:error in SSLv3 read client hello B

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: SSL_accept:error in SSLv3 read client hello B

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: read from 0816D318 [0815C8F3] (61 bytes => 61 (0x3D))

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: 0000 44 f5 b6 6d e5 4b ec fe|78 3d fd ee 83 f4 4a 81  D..m.K.. x=....J.

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: 0010 fe cc 6e 5b 78 5b 88 cb|c7 89 d2 a6 d1 08 dd d6  ..n[x[.. ........

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: 0020 00 00 18 00 35 00 2f 00|0a 00 05 00 04 00 38 00  ....5./. ......8.

Aug 30 16:59:59 vulcan postfix/smtpd[20189]: 0030 32 00 13 00 66 00 39 00|33 00 16 01              2...f.9. 3...

[quote user="tbullock"]

Do you have a MX record that resolves to your Zimbra machine?

[/QUOTE]
That I do.
[quote user="tbullock"]

What does your hosts file look like after your rebuild?[/QUOTE]

[/QUOTE]
My hosts file is:

127.0.0.1       localhost
# special IPv6 addresses

::1             localhost ipv6-localhost ipv6-loopback
fe00::0         ipv6-localnet
ff00::0         ipv6-mcastprefix

ff02::1         ipv6-allnodes

ff02::2         ipv6-allrouters

ff02::3         ipv6-allhosts

192.168.0.10    vulcan.forcev.net vulcan

I've got this far running on ZCS 3.1.4 as version 4 wasn't getting me very far with the install. I'll try another upgrade.

[FunkyPenguin]

This time the upgrade went smoothly, but I still have the same issue - cant view mail as I get the network service error.

[tbullock]

[quote user="FunkyPenguin"]This time the upgrade went smoothly, but I still have the same issue - cant view mail as I get the network service error.[/QUOTE]
Is your QUEUE still backlogging as well?
Have you changed or disabled the default ssh port on your Zimbra machine?

[FunkyPenguin]

Travis,
I haven't changed the ssh port on the machine.
The queue is still growing, all messages are getting deferred. I've done zmfixperms/reboot and tried flushing the queue from both the Admin UI and CLI, but no joy. From what I can see and in my simple mind, tomcat appears to have broken and I'm just missing one or two little steps to fix it - I jjust don't know what the heck those steps are.

[FunkyPenguin]

I've tried to re-index the account using the steps found here , but it looks like I've scrambled the heck out of the AdminUI.
All accounts are affected by this problem rendering me without mail.

[tbullock]

Are there any other moderators who would like to weigh in on this one?

[phoenix]

What state are you at now with ZImbra? You've done an upgrade to version 4 but you're getting the 'missing blob' message and the admin ui is screwed-up, is that about it?

[adobrin]

why did you ask about the default ssh port? is that used for anything other than the statistics in the admin ui in 4.0?

[adobrin]

my opinion is you need to go back to your non-working backup. its not fun to recover once you've had a failed installation.
hit the backup, fix the ldap authentication, and then upgrade again.

[FunkyPenguin]

In a nutshell yes.
I am running Release 4.0.0_GA_303.SuSE10_20060829130819 SuSE10 FOSS edition; I am unable to send or recieve mail from any account all inbound mail is put into the deferred queue; the Admin UI is scrambled and unuseable; my own account is stuck in maintanence mode.
I think thats about all the fun I have at the moment. I'm all ears to any ideas on how to fix this.