Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 09-03-2010, 04:06 AM
Active Member
 
Posts: 26
Default Install zcs 6.0.8 on SLESS 10 32 bits

Hi,

I try install zcs-6.0.8_GA_2661.SuSEES10.20100820055003. I can't get Mainmenu that displays showing the default entries for the Zimbra component i am installing.

Code:
Do you agree with the terms of the software license agreement? [N] Y

Checking for prerequisites...
     FOUND: NPTL
     FOUND: sudo-1.6.8p12-18.14
     FOUND: libidn-0.6.0-14.2
     FOUND: gmp-4.1.4-20.10
     FOUND: /usr/lib/libstdc++.so.6
Checking for suggested prerequisites...
    FOUND: perl-5.8.8
    FOUND: sysstat
Prerequisite check complete.
Checking current number of databases...

Do you want to verify message store database integrity? [Y] N

Checking for installable packages

Found zimbra-core
Found zimbra-ldap
Found zimbra-logger
Found zimbra-mta
Found zimbra-snmp
Found zimbra-store
Found zimbra-apache
Found zimbra-spell
Found zimbra-memcached
Found zimbra-proxy


The Zimbra Collaboration Suite appears already to be installed.
It can be upgraded with no effect on existing accounts,
or the current installation can be completely removed prior
to installation for a clean install.

Do you wish to upgrade? [Y]

Select the packages to install
    Upgrading zimbra-core
    Upgrading zimbra-ldap
    Upgrading zimbra-logger
    Upgrading zimbra-mta
    Upgrading zimbra-snmp
    Upgrading zimbra-store
    Upgrading zimbra-apache
    Upgrading zimbra-spell

Install zimbra-memcached [Y]
    Upgrading zimbra-proxy
Checking required space for zimbra-core
checking space for zimbra-store

Installing:
    zimbra-core
    zimbra-ldap
    zimbra-logger
    zimbra-mta
    zimbra-snmp
    zimbra-store
    zimbra-apache
    zimbra-spell
    zimbra-memcached
    zimbra-proxy

The system will be modified.  Continue? [N] Y

Shutting down zimbra mail

Removing existing packages

   zimbra-ldap...done
   zimbra-logger...done
   zimbra-mta...done
   zimbra-snmp...done
   zimbra-store...done
   zimbra-spell...done
   zimbra-proxy...done
   zimbra-apache...done
   zimbra-core...done

Removing deployed webapp directories
Installing packages

    zimbra-core......zimbra-core-6.0.8_GA_2661.SuSEES10-20100820055003.i386.rpm...done
    zimbra-ldap......zimbra-ldap-6.0.8_GA_2661.SuSEES10-20100820055003.i386.rpm...done
    zimbra-logger......zimbra-logger-6.0.8_GA_2661.SuSEES10-20100820055003.i386.rpm...done
    zimbra-mta......zimbra-mta-6.0.8_GA_2661.SuSEES10-20100820055003.i386.rpm...done
    zimbra-snmp......zimbra-snmp-6.0.8_GA_2661.SuSEES10-20100820055003.i386.rpm...done
    zimbra-store......zimbra-store-6.0.8_GA_2661.SuSEES10-20100820055003.i386.rpm...done
    zimbra-apache......zimbra-apache-6.0.8_GA_2661.SuSEES10-20100820055003.i386.rpm...done
    zimbra-spell......zimbra-spell-6.0.8_GA_2661.SuSEES10-20100820055003.i386.rpm...done
    zimbra-memcached......zimbra-memcached-6.0.8_GA_2661.SuSEES10-20100820055003.i386.rpm...done
    zimbra-proxy......zimbra-proxy-6.0.8_GA_2661.SuSEES10-20100820055003.i386.rpm...done

Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
   HOSTNAME=localhost
   LDAPHOST=
   LDAPPORT=
   SNMPTRAPHOST=
   SMTPSOURCE=
   SMTPDEST=
   SNMPNOTIFY=0
   SMTPNOTIFY=0
   LDAPROOTPW=zimbra
   LDAPZIMBRAPW=zimbra
   LDAPPOSTPW=zmpostfix
   LDAPREPPW=zmreplica
   LDAPAMAVISPW=zmamavis
   LDAPNGINXPW=zmnginx
Restoring existing configuration file from /opt/zimbra/.saveconfig/localconfig.xml...done
Operations logged to /tmp/zmsetup.09032010-125248.log
Installing LDAP configuration database...done.
ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
Setting defaults...ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
done.
Setting defaults from existing config...done.
Checking for port conflicts
ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
Saving config in /opt/zimbra/config.8588...done.
Operations logged to /tmp/zmsetup.09032010-125248.log
Setting local config values...done.
Setting up CA...done.
Deploying CA to /opt/zimbra/conf/ca ...done.
Warning: No valid SSL certificates were found.
New self-signed certificates will be generated and installed.
Creating SSL certificate...done.
Creating SSL certificate...done.
Creating SSL certificate...done.
Creating SSL certificate...done.
Installing mailboxd SSL certificates...done.
Setting replication password...done.
Setting Postfix password...done.
Setting amavis password...done.
Setting nginx password...done.
Creating server entry for localhost...failed.
Saving CA in ldap ...done.
Saving SSL Certificate in ldap ...done.
Setting spell check URL...failed.
Setting service ports on localhost...done.
Adding localhost to zimbraMailHostPool in default COS...failed. Couldn't find a server entry for localhost
Installing webclient skins...
        bare...failed.
        beach...failed.
        bones...failed.
        hotrod...failed.
        lake...failed.
        lavender...failed.
        lemongrass...failed.
        oasis...failed.
        pebble...failed.
        sand...failed.
        sky...failed.
        smoke...failed.
        steel...failed.
        tree...failed.
        twilight...failed.
        waves...failed.
        yahoo...failed.
        zmail...failed.
Finished installing webclient skins.
Setting Keyboard Shortcut Preferences...failed.
Setting zimbraFeatureIMEnabled=FALSE...failed.
Setting zimbraFeatureTasksEnabled=FALSE...failed.
Setting zimbraFeatureBriefcasesEnabled=FALSE...failed.
Setting zimbraFeatureNotebookEnabled=TRUE...failed.
Setting MTA auth host...failed.
Setting TimeZone Preference...failed.
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException localhost:389)
prov> Initializing mta config...done.
Setting services on localhost...done.
Creating domain sistemas.gruposame.net...failed.
Setting default domain name...failed.
Creating user spam.j4rs1ktlty@.. ...failed.
Creating user ham.ouz_9ekt@.... ...failed.
Setting spam training accounts...failed.
Initializing store sql database...done.
Setting zimbraSmtpHostname for localhost...failed.
Configuring SNMP...done.
Checking for default IM conference room...not present.
Initializing default IM conference room...failed.
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 (6.0.8_GA_2661_SuSEES10)
        The ADMIN EMAIL ADDRESS created (admin@........net)

Notify Zimbra of your installation? [Yes] No
Notification skipped
Starting servers...Unable to determine enabled services from ldap.
done.
Checking for deprecated zimlets...failed.
Removing convertd mime tree from ldap...failed. This may impact system functionality.
Installing common zimlets...
        com_zimbra_adminversioncheck...failed. This may impact system functionality.
        com_zimbra_bulkprovision...failed. This may impact system functionality.
        com_zimbra_cert_manager...failed. This may impact system functionality.
        com_zimbra_date...failed. This may impact system functionality.
        com_zimbra_dnd...failed. This may impact system functionality.
        com_zimbra_email...failed. This may impact system functionality.
        com_zimbra_phone...failed. This may impact system functionality.
        com_zimbra_url...failed. This may impact system functionality.
        com_zimbra_ymemoticons...failed. This may impact system functionality.
Finished installing common zimlets.
Initializing Documents...failed to initialize documents...see logfile for details.
Restarting mailboxd...done.
Setting up zimbra crontab...cp: cannot stat `/var/spool/cron/tabs/zimbra': No such file or directory
done.


Moving /tmp/zmsetup.09032010-125248.log to /opt/zimbra/log


Configuration complete - press return to exit
I can't understand. Some advise?

Thanks a lot.
Reply With Quote
  #2 (permalink)  
Old 09-03-2010, 04:19 AM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

This looks like an upgrade, according to that log file, what are you upgrading from? If this is a single server why do you have memcached & proxy installed? It also looks like you've run the upgrade/install several times, that's why the following entries are all empty:

Code:
Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
   HOSTNAME=localhost
   LDAPHOST=
   LDAPPORT=
   SNMPTRAPHOST=
   SMTPSOURCE=
   SMTPDEST=
   SNMPNOTIFY=0
   SMTPNOTIFY=0
   LDAPROOTPW=zimbra
   LDAPZIMBRAPW=zimbra
   LDAPPOSTPW=zmpostfix
   LDAPREPPW=zmreplica
   LDAPAMAVISPW=zmamavis
   LDAPNGINXPW=zmnginx
You can find information in the forums on how to recover from that error (basically you'll need to restore the defaults).
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 10-21-2010, 02:16 PM
Active Member
 
Posts: 28
Default

Above problem happened to me several times, untill I started doing the following:

First, use install.sh with --softwareonly. This prevents the installer to go into configuration mode. The problem as far as I can see is a broken ldap. So with --softwareonly it installs but does not upgrade.

Then, fix the ldap database. In my case, I had to upgrade from 32 bit to 64 bit and reconstruct the database. There is a post in the forum Exporting and Importing Zimbra LDAP Data » Zimbra :: Blog how to do that.

If it's not 32->64 bit, then recover the database.
I think (as root) doing
/opt/zimbra/bdb/bin/db_recover -v -h /opt/zimbra/data/ldap/hdb/db
will fix it. Sometimes you get an error (something about wrong version) and then you have to use the other db_recover that is in /opt/zimbra/bdb-SOMEVERSIONNUMBER. ..

After you fixed ldap, then run /opt/zimbra/libexec/zmsetup.pl

Good luck
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.