Results 1 to 4 of 4

Thread: [SOLVED] Upgrade error zcs 4.5.0_GA

  1. #1
    mutinda is offline Intermediate Member
    Join Date
    Dec 2006
    Posts
    23
    Rep Power
    8

    Default [SOLVED] Upgrade error zcs 4.5.0_GA

    Hi people.

    I have a zimbra installation running on Fedora Core 5 (zcs 4.5.0_GA_612.FC5). Just this afternoon I ran a repair (upgrade) for some reason or other using the same zimbra version and I got into some real trouble.

    Errors began when setting defaults from and existing config: see below-

    ------
    Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
    Operations logged to /tmp/zmsetup.log.27863
    Setting defaults...Setting defaults from existing config...Warning: null valued key

    'mysql_logger_root_password'
    Done
    Checking for port conflicts
    Starting ldap...Done
    Setting defaults from ldap...ERROR: service.FAILURE (system failure: getDirectContext) (cause:

    javax.naming.CommunicationException localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException

    localhost:389)
    Done

    Main menu

    1) Hostname: xxxx.or.ke
    2) Ldap master host: xxxx.or.ke
    3) Ldap port: 389
    4) Ldap password: set
    5) zimbra-ldap: Enabled
    6) zimbra-store: Enabled
    +Create Admin User: no
    +Enable automated spam training: yes
    ******* +Spam training user: UNSET
    ******* +Non-spam(Ham) training user: UNSET
    +Global Documents Account: wiki@xxxx.or.ke
    +SMTP host: xxxx.or.ke
    ******* +Web server HTTP port: UNSET
    ******* +Web server HTTPS port: UNSET
    +Web server mode: mixed
    +Enable POP/IMAP proxy: no
    ******* +IMAP server port: UNSET
    ******* +IMAP server SSL port: UNSET
    ******* +POP server port: UNSET
    ******* +POP server SSL port: UNSET
    +Use spell check server: yes
    +Spell server URL: http://xxxx.or.ke:7780/aspell.php

    7) zimbra-mta: Enabled
    8) zimbra-snmp: Enabled
    9) zimbra-logger: Enabled
    10) zimbra-spell: Enabled
    r) Start servers after configuration yes
    s) Save config to file
    x) Expand menu
    q) Quit

    It appears the installer is unable to read the ldap file. Why is this?

    I had (happily) just done a complete backup of my zimbra folder and also tried to recover using that and advice from this link Moving ZCS to Another Server » Zimbra :: Blog but there is no change.

    Help!

  2. #2
    mutinda is offline Intermediate Member
    Join Date
    Dec 2006
    Posts
    23
    Rep Power
    8

    Default Almost there, but not quite....

    After some bile-inducing moments, I managed to do an install with fewer errors. Part of the install dialogue is like so:

    ---
    Initializing Documents...failed to initialize documents...see logfile for details.
    Restarting tomcat...Done


    Operations logged to /tmp/zmsetup.log.12148


    Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
    Operations logged to /tmp/zmsetup.log.12148
    Setting defaults...Setting defaults from existing config...Done
    Checking for port conflicts
    Starting ldap...Done
    Setting defaults from ldap...Done
    Saving config in /opt/zimbra/config.12148...Done
    Operations logged to /tmp/zmsetup.log.12148
    Setting local config values...Done
    Stopping ldap...done
    Starting ldap...Done
    Saving CA in ldap...Done
    Installing SSL certificate...Done
    Creating server entry for XXXXX.or.ke...Done
    Setting spell check URL...Done
    Setting service ports on XXXXX.or.ke...Done
    Adding XXXXX.or.ke to zimbraMailHostPool in default COS...Done
    Installing skins...
    sky
    harvest
    lavender
    froggy
    rose
    vanilla
    steel
    bare
    sand
    Done
    Setting Keyboard Shortcut Preferences...done.
    Setting MTA auth host...Done
    Creating user spam.ztyskqxycp@XXXXX.or.ke...Done
    Creating user ham.os4m7sjsr@XXXXX.or.ke...Done
    Setting spam training accounts...Done
    Initializing mta config...Done
    Configuring SNMP...Done
    Setting services on XXXXX.or.ke...Done
    Setting up zimbra crontab...Done
    Setting up syslog.conf...Done

    You have the option of notifying Zimbra of your installation.
    This helps us to track the uptake of the Zimbra Collaboration Suite.
    The only information that will be transmitted is:
    The VERSION of zcs installed (4.5.0_GA_612_FC5)
    The ADMIN EMAIL ADDRESS created (admin@XXXXX.or.ke)

    Notify Zimbra of your installation? [Yes] n
    Notification skipped
    Starting servers...Done.
    Installing zimlets...
    com_zimbra_email
    com_zimbra_search
    com_zimbra_date
    com_zimbra_phone
    com_zimbra_url
    Done
    Initializing Documents...failed to initialize documents...see logfile for details.
    Restarting tomcat...Done


    Operations logged to /tmp/zmsetup.log.12148


    Configuration complete - press return to exit

    ---

    As you can see, the documents didn't initialize.

    The log file shows:

    ---
    Initializing Documents...
    Getting ldap default cos attribute zimbraFeatureNotebookEnabled from ldap.

    Global config attribute retrieved from ldap: zimbraNotebookAccount=wiki@XXXXX.or.ke
    *** Running as zimbra user: /opt/zimbra/bin/zmprov mc default zimbraFeatureNotebookEnabled TRUE

    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
    *** Running as zimbra user: /opt/zimbra/bin/zmprov mcf zimbraNotebookAccount wiki@XXXXX.or.ke

    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
    *** Running as zimbra user: /opt/zimbra/bin/zmprov in wiki@XXXXX.or.ke 'hP2Hvpgf' /opt/zimbra/wiki/Template Template

    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
    *** Running as zimbra user: /opt/zimbra/bin/zmprov mc default zimbraFeatureNotebookEnabled FALSE

    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
    failed to initialize documents...see logfile for details.

    *** Running as zimbra user: /opt/zimbra/bin/zmprov mc default zimbraFeatureNotebookEnabled TRUE

    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    [] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
    [] INFO: Retrying request
    ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)
    ---

    Checking server status:

    ---

    [root@XXXXX zcs]# su zimbra
    [zimbra@XXXXX zcs]$ zmcontrol status
    Host XXXXX.or.ke
    antispam Running
    antivirus Running
    ldap Running
    logger Running
    mailbox Stopped
    tomcat is not running
    mta Running
    snmp Running
    spell Running
    [zimbra@XXXXX zcs]$ tomcat restart
    [zimbra@XXXXX zcs]$ zmcontrol status
    Host XXXXX.or.ke
    antispam Running
    antivirus Running
    ldap Running
    logger Running
    mailbox Running
    mta Running
    snmp Running
    spell Running
    [zimbra@XXXXX zcs]$
    ---

    All looks well but the Admin console and user login pages don't load!

    After checking status again, the mailbox isn't running and tomcat is stopped.

    ---
    [zimbra@XXXXX zcs]$ zmcontrol status
    Host XXXXX.or.ke
    antispam Running
    antivirus Running
    ldap Running
    logger Running
    mailbox Stopped
    tomcat is not running
    mta Running
    snmp Running
    spell Running
    [zimbra@XXXXX zcs]$
    ---

    What's going on? Anyone out there, PLEASE!

  3. #3
    mutinda is offline Intermediate Member
    Join Date
    Dec 2006
    Posts
    23
    Rep Power
    8

    Default Missing blob

    1 a.m. and I'm still at it. Oh dear.
    I followed advice from here Mailbox Stopped about changing sql passwords and editing the mysql.server file. I did that plus chown zimbra:zimbra /opt/zimbra/store/* and zmfixperms which I read about here 3 testing: LDAP: 389 Failed when restore zimbra.

    After a reboot, my mailbox and tomcat behaved! Woo hoo!

    My services are all running, and I can log into the Admin and user pages. I can't view my email messages though; when the inbox loads I get an error saying:

    msg - system failure: missing blob for id: 4604, change: 12808
    com.zimbra.common.service.ServiceException: system failure: missing blob for id: 4604, change: 12808
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:175)
    at com.zimbra.cs.mailbox.MailItem.getBlob(MailItem.ja va:716)
    at com.zimbra.cs.mailbox.MessageCache.fetchFromStore( MessageCache.java:213)
    at com.zimbra.cs.mailbox.MessageCache.getMimeMessage( MessageCache.java:179)
    at com.zimbra.cs.mailbox.Message.getMimeMessage(Messa ge.java:287)
    at com.zimbra.cs.service.mail.ToXML.encodeMessageAsMP (ToXML.java:603)
    at com.zimbra.cs.service.mail.GetMsg.handle(GetMsg.ja va:75)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:262)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:162)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:223)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:162)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
    at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
    at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
    at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
    at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
    at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
    at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
    at java.lang.Thread.run(Thread.java:595)

    code - service.FAILURE
    method - ZmCsfeCommand.prototype.invoke
    detail - soap:Receiver

    The one thread I found that talks about missing blobs just kinda trails off. Hmph!

    Anyone want the glory of having helped me over this last hurdle? I can smell the victory...

  4. #4
    mutinda is offline Intermediate Member
    Join Date
    Dec 2006
    Posts
    23
    Rep Power
    8

    Default The storm is over

    Thank you all for not replying to my posts... I mean it. I was forced to really dig deep into the forums.

    I found very helpful posts about using zmltpinject plus a fabulous script by gitzc here that adds a date header to each message. RRREALLY saved my bacon.

    So that means I actually didn't repair the broken installation of zimbra; I just put in a new one and injected all the old email into it.

    Great forum this!

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Upgrade instructions in 5.0.10 too muddy to understand
    By johnshen in forum Installation
    Replies: 4
    Last Post: 12-06-2008, 06:19 AM
  2. Replies: 2
    Last Post: 10-04-2007, 03:20 PM
  3. M1 -> M2 Upgrade Scripts
    By KevinH in forum Announcements
    Replies: 57
    Last Post: 12-15-2005, 10:10 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •