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 02-06-2012, 06:43 AM
Senior Member
 
Posts: 50
Default 32 to 64 bit Upgrade issue - BES Searcher password

I am trying to test out a move from Ubuntu 8.04 32 bit to 10.04 64 bit. Due to a hard drive failure, I am running the old version off a virtual machine while I do the tests, but I'd like to get up and running on the server ASAP.

Version of zimbra is current version (7.1.4) on all versions.

I followed the instructions on the wiki, but only afterwards realized that the mail port had been 81 on the old version, but set to 80 in the new version, which is why I assumed I got a zmmailboxdctl is not running error when I started up the new instance.

I tried to us zmprov to fix this, but I got the following error:
[] 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)


I decided to do an "upgrade" to redo the settings, but now when it gets to that part, it gives me the asterisks next to the ldap bes searcher password saying it is unverified, and nothing I try works.

Can anyone help get me over this hurdle to get back up and running?

Last edited by Cryophallion; 02-06-2012 at 06:48 AM..
Reply With Quote
  #2 (permalink)  
Old 02-06-2012, 04:25 PM
Zimbra Employee
 
Posts: 580
Default

Did you use the menu to set a password for it?
__________________
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
Reply With Quote
  #3 (permalink)  
Old 02-06-2012, 04:45 PM
Senior Member
 
Posts: 50
Default

I tried, but it kept labeling it "unverified" I believe. I'm trying for a third time tomorrow. I think that that may be the only password that is not in my old xml settings, but it is still extremely frustrating.
Reply With Quote
  #4 (permalink)  
Old 02-06-2012, 04:48 PM
Zimbra Employee
 
Posts: 580
Default

Ok, interesting. :/ Do you know what it is logging in the setup log in /tmp when you set a value for it? I thought this was fixed in 7.1.3 (bug#64401)
__________________
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
Reply With Quote
  #5 (permalink)  
Old 02-07-2012, 06:47 AM
Senior Member
 
Posts: 50
Default

Below is the output. I DID fix the main issue mentioned above (certs issues), but I decided to test if this bug still exists.

Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for ldap_starttls_supported=1.
Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for zimbra_require_interprocess_security=1.
Tue Feb 7 09:45:04 2012 Verified uid=zmamavis,cn=appaccts,cn=zimbra on mail.example.com.
Tue Feb 7 09:45:04 2012 Checking ldap on mail.example.com:389
Tue Feb 7 09:45:04 2012 Verified ldap running at ldap://mail.example.com:389
Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for ldap_url=ldap://mail.example.com:389.
Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for ldap_starttls_supported=1.
Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for zimbra_require_interprocess_security=1.
Tue Feb 7 09:45:04 2012 Verified uid=zimbra,cn=admins,cn=zimbra on mail.example.com.
Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for zimbra_ldap_password=maxum1.
Tue Feb 7 09:45:04 2012 Checking ldap on mail.example.com:389
Tue Feb 7 09:45:04 2012 Unable to bind to ldap://mail.example.com:389 with user uid=zmbes-searcher,cn=appaccts,cn=zimbra:
Tue Feb 7 09:45:04 2012 Couldn't bind to mail.example.com as uid=zmbes-searcher,cn=appaccts,cn=zimbra
Tue Feb 7 09:45:04 2012 Checking ldap on mail.example.com:389
Tue Feb 7 09:45:04 2012 Verified ldap running at ldap://mail.example.com:389
Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for ldap_url=ldap://mail.example.com:389.
Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for ldap_starttls_supported=1.
Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for zimbra_require_interprocess_security=1.
Tue Feb 7 09:45:04 2012 Verified uid=zmpostfix,cn=appaccts,cn=zimbra on mail.example.com.
Tue Feb 7 09:45:04 2012 Checking ldap on mail.example.com:389
Tue Feb 7 09:45:04 2012 Verified ldap running at ldap://mail.example.com:389
Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for ldap_url=ldap://mail.example.com:389.
Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for ldap_starttls_supported=1.
Tue Feb 7 09:45:04 2012 Skipping update of unchanged value for zimbra_require_interprocess_security=1.
Tue Feb 7 09:45:04 2012 Verified uid=zmamavis,cn=appaccts,cn=zimbra on mail.example.com.
Tue Feb 7 09:45:05 2012 checking isEnabled zimbra-ldap
Tue Feb 7 09:45:05 2012 zimbra-ldap is enabled
Reply With Quote
  #6 (permalink)  
Old 02-07-2012, 03:52 PM
Zimbra Employee
 
Posts: 580
Default

You can get around this for now by finding the following code block in zmsetup.pl:

Code:
  # check zmbes searcher binding to the master
  if ($config{LDAPHOST} eq $config{HOSTNAME}) {
    if ($config{ldap_bes_searcher_password} eq "") {
      detail ("BES searcher configuration not complete\n");
      $failedcheck++;
    }
    my $binduser = "uid=zmbes-searcher,cn=appaccts,$config{ldap_dit_base_dn_config}";
    if (checkLdapBind($binduser,$config{ldap_bes_searcher_password})) {
      detail ("Couldn't bind to $config{LDAPHOST} as $binduser\n");
      $config{LDAPBESSEARCHSET} = "Not Verified";
      $failedcheck++;
    } else {
      detail ("Verified $binduser on $config{LDAPHOST}.\n");
      $config{LDAPBESSEARCHSET} = "set";
    }
  }
Remove the if... through else ... lines, and the first } after the else line, that'll skip checking that it is valid, and let you proceed with the install.
__________________
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
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.