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

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 01-05-2012, 05:09 PM
New Member
 
Posts: 3
Default Problems after changing domain with zmsetservername

Hello,

I have followed the instructions here to change the hostname of a server, but am running into problems after running 'zmcontrol restart'. It looks like some services are not starting correctly, and I cannot access the webmail or admin (port 7071) interfaces.

Here is the output of 'zmcontrol restart'

Code:
Host zimbra-6279-jamescuzella.testapp.standingcloud.com
        Stopping zmconfigd...Done.
        Stopping stats...Done.
        Stopping mta...Done.
        Stopping spell...Done.
        Stopping snmp...Done.
        Stopping cbpolicyd...Done.
        Stopping archiving...Done.
        Stopping antivirus...Done.
        Stopping antispam...Done.
        Stopping imapproxy...Done.
        Stopping memcached...Done.
        Stopping mailbox...Done.
        Stopping logger...Done.
        Stopping ldap...Done.
Host zimbra-6279-jamescuzella.testapp.standingcloud.com
        Starting ldap...Done.
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
        Starting zmconfigd...Done.
        Starting logger...Failed.
Starting logswatch...ERROR: service.FAILURE (system failure: unable to lookup server by name: zimbra-6279-jamescuzella.testapp.standingcloud.com message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
zimbra logger service is not enabled!  failed.


        Starting mailbox...Done.
        Starting memcached...Done.
        Starting imapproxy...Done.
        Starting antispam...Done.
        Starting antivirus...Done.
        Starting snmp...Done.
        Starting spell...Done.
        Starting mta...Done.
        Starting stats...Done.
Reply With Quote
  #2 (permalink)  
Old 01-05-2012, 05:22 PM
Elite Member
 
Posts: 334
Default

Quote:
Originally Posted by jcuzella View Post
Hello,
...
Code:
...
Host zimbra-6279-jamescuzella.testapp.standingcloud.com
        Starting ldap...Done.
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Please paste the relevant log on /opt/zimbra/log/mailbox.log. It seems that your LDAP has an incorrect settings.

Quote:
Originally Posted by jcuzella View Post
Hello,
...
Starting logswatch...ERROR: service.FAILURE (system failure: unable to lookup server by name: zimbra-6279-jamescuzella.testapp.standingcloud.com message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
zimbra logger service is not enabled! failed.
[/CODE]
Invalid credentials means something wrong with your LDAP user name & password. Did you modify LDAP settings in addition Zimbra hostname?
__________________
Best Regards
---
Masim "Vavai" Sugianto
Vavai Personal Blog
Personal Blog [ID]

Release 7.1.3_GA_3346.SLES11_64_20110930001521 SLES11_64 FOSS edition.
Reply With Quote
  #3 (permalink)  
Old 01-05-2012, 08:55 PM
Intermediate Member
 
Posts: 22
Default

you changed hostname. so you will need to tell other server the new hostname or IP.
Reply With Quote
  #4 (permalink)  
Old 01-06-2012, 09:00 AM
New Member
 
Posts: 3
Default

Quote:
Originally Posted by vavai View Post
Please paste the relevant log on /opt/zimbra/log/mailbox.log. It seems that your LDAP has an incorrect settings.



Invalid credentials means something wrong with your LDAP user name & password. Did you modify LDAP settings in addition Zimbra hostname?
Perhaps I should reveal that there is more going on here than just a changed domain. This is a second zimbra server instance (server B) that is freshly installed and being restored with snapshot backups from another (server A). Both are single server installs of the Open Source edition.

To be most clear... My goal is to restore Server A onto a new install on Server B with these constraints:
  • Backups from Server A must be small
  • Hostname of Server B must be different
  • LDAP password of Server B must be different

When the new instance (server B) is being installed, it is configured with a new hostname, and new LDAP password (I can't set the same password for both for security reasons). Afterwards, I restore the snapshot backup from server A on top of this, then run zmsetservername to ensure the old config files are changed back.

So to answer the question, yes... the LDAP password for the second instance ends up being different perhaps than what is stored in the post-restored server state.

Here's the mailbox.log: Zimbra mailbox.log - Pastebin.com

Last edited by jcuzella; 01-06-2012 at 09:45 AM.. Reason: Added explanation of restore constraints
Reply With Quote
  #5 (permalink)  
Old 01-11-2012, 02:13 PM
New Member
 
Posts: 3
Default

Hmm... after considering the wiki, it looks like the way I've been trying to backup & restore is not the right way.

I'll try some of the other open source edition backup scripts and start a new thread in case I have problems ;-)
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.