Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: Error during installling zimbra-spell-3.0.0_M2_740.FC3-20051114171941.i386.rpm

  1. #11
    xtremetoonz is offline Active Member
    Join Date
    Nov 2005
    Posts
    33
    Rep Power
    9

    Default

    I had added the actual host name line in the /etc/hosts file like this:
    Code:
    127.0.0.1       localhost.localdomain localhost
    223.200.200.13  zimbra.domain.com zimbra
    so I changed it to:
    Code:
    127.0.0.1       localhost.localdomain localhost zimbra.domain.com
    192.168.0.13  zimbra.domain.com zimbra
    still get:
    Code:
    Adding testrh.power1.com to zimbraMailHostPool in default COS
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException zimbra.domain.com:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException zimbra.domain.com:389)
    Done
    then further down the install process:
    Code:
    *** Running as zimbra user: /opt/zimbra/bin/zmcontrol start
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException zimbra.domain.com:389)

    so now I'm gonna try removing the line with the non-localhost IP in the /etc/hosts and see if that works
    Last edited by xtremetoonz; 11-16-2005 at 04:13 PM.

  2. #12
    xtremetoonz is offline Active Member
    Join Date
    Nov 2005
    Posts
    33
    Rep Power
    9

    Cool

    I am also just realizing I have a few default services I'm stopping while this next intall is going through. Iptables and portmap being the two suspicious ones.

  3. #13
    xtremetoonz is offline Active Member
    Join Date
    Nov 2005
    Posts
    33
    Rep Power
    9

    Default

    No Soup:
    Code:
    Adding localhost.localdomain to zimbraMailHostPool in default COS
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost.localdomain:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost.localdomain:389)
    Done
    Attached Files Attached Files

  4. #14
    marcmac is offline Expert Member
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    13

    Default version

    Aren't you installing on a 2.4 kernel, RH3 box?

    That's not supported by the ZCS software, as was pointed out in another thread - you should consider upgrading to RHEL4 or FC3

  5. #15
    Emperor Angel is offline Junior Member
    Join Date
    Nov 2005
    Posts
    5
    Rep Power
    9

    Default

    I'm using FC3 that is full updated with the yum command
    I'm using kernel 2.6.12 and I get the following error
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException testrh.power1.com:389)

    My /etc/host looks like this:
    127.0.0.1 localhost.localdomain localhost
    #172.16.0.32 Zimbra.Zimbra.nl FedoraCore3
    127.0.0.1 Zimbra.Zimbra.nl FedoraCore3


    Any help is welcome

  6. #16
    raj's Avatar
    raj
    raj is offline Moderator
    Join Date
    Oct 2005
    Location
    USA, Canada and India
    Posts
    777
    Rep Power
    10

    Default

    there is some problem with this version of Zimbra..iam very sure.
    previous version worked flawlessly during installed and no isssues no matter what you ran.

    i reinstalled this version 6 times and no luck same error..
    then i did complete reinstall of OS and yum update and installed worked but my MTA dont start as

    So iam giving it a rest for a day till someone really figure out this port 389 problem..if you search fourm there are atleast 4-5 diff threads with same error.

    Raj

  7. #17
    Emperor Angel is offline Junior Member
    Join Date
    Nov 2005
    Posts
    5
    Rep Power
    9

    Default

    Thanks Raj for this explenation.

    I shall try the previous version

  8. #18
    xtremetoonz is offline Active Member
    Join Date
    Nov 2005
    Posts
    33
    Rep Power
    9

    Default

    I'm gonna start over. Downloading ES4 now, will try the ES4 ZCS package.

  9. #19
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    18

    Default

    Quote Originally Posted by raj
    there is some problem with this version of Zimbra..iam very sure.
    previous version worked flawlessly during installed and no isssues no matter what you ran.

    i reinstalled this version 6 times and no luck same error..
    then i did complete reinstall of OS and yum update and installed worked but my MTA dont start as

    So iam giving it a rest for a day till someone really figure out this port 389 problem..if you search fourm there are atleast 4-5 diff threads with same error.

    Raj
    Raj, Did you run yum update? Can you post your error logs? If it's a problem with LDAP did you try to start it in debug mode ? There may be a problem but 100's of people have got this version working so there must be something that you guys are doing different.

Page 2 of 2 FirstFirst 12

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Removing hostname from hosts file fixed prob.
    By lemur in forum Installation
    Replies: 10
    Last Post: 06-13-2007, 06:29 PM
  2. zmtlsctl give LDAP error
    By sourcehound in forum Administrators
    Replies: 5
    Last Post: 03-11-2007, 03:48 PM
  3. 4.5 Upgrade failure
    By brained in forum Installation
    Replies: 9
    Last Post: 03-03-2007, 03:30 PM
  4. Unable to start tomcat
    By chanck in forum Administrators
    Replies: 11
    Last Post: 06-11-2006, 12:58 AM
  5. FC3 Install and no zimbra ?
    By aws in forum Installation
    Replies: 10
    Last Post: 10-09-2005, 04:19 PM

Posting Permissions

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