Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Change Hostname Zimbra 7.0

  1. #1
    gustavocearasc is offline Intermediate Member
    Join Date
    Apr 2010
    Posts
    16
    Rep Power
    5

    Default Change Hostname Zimbra 7.0

    Hello, I have a zimbra server with the name and mail.teste.com.br need to change the name of it to zimbra2.teste.com.br.
    I used some of the methods and zmsetservername errors occurred in LDAP.
    Any suggestions?

  2. #2
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,491
    Rep Power
    56

    Default

    Quote Originally Posted by gustavocearasc View Post
    Hello, I have a zimbra server with the name and mail.teste.com.br need to change the name of it to zimbra2.teste.com.br.
    You should have changed the domain name when you were asked during the initial otherwise it defaults to the FQDN of the server (as you've now found out).

    Quote Originally Posted by gustavocearasc View Post
    I used some of the methods and zmsetservername errors occurred in LDAP.
    Any suggestions?
    Posting 'it doesn't work' really does not give us any information with which to advise you of a solution - you need to give the exact errors you see in the log files.

    Using zmsetservername is the correct procedure (if you follow the details in the wiki article) or you can completely remove the install and reinstall ZCS the set the correct domain name as I mentioned above. Details of this installation procedure are in the Quick Start Installation Guide and all over the forums.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    gustavocearasc is offline Intermediate Member
    Join Date
    Apr 2010
    Posts
    16
    Rep Power
    5

    Default

    when I run the zmsetservername -n zimbra2.teste.com.br the following error occurs:

    Starting ldap ... done.

    Unable to contact ldap: / / mail.teste.com.br: 389: Invalid argument
    Unable to contact ldap: / / mail.teste.com.br: 389: Invalid argument
    Services:
    Getting local config = 389 LDAP_PORT
    Reinitializing the mta config ... done.
    Reinitializing the snmp config ... done.

  4. #4
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,491
    Rep Power
    56

  5. #5
    gustavocearasc is offline Intermediate Member
    Join Date
    Apr 2010
    Posts
    16
    Rep Power
    5

    Default

    Now the following error occurs:

    antispam Running
    Running antivirus
    Running ldap
    Running logger
    mailbox Stopped
    mysql.server is not running.
    Running mta
    Running snmp
    Running spell
    stats Stopped

  6. #6
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,491
    Rep Power
    56

    Default

    Quote Originally Posted by gustavocearasc View Post
    Now the following error occurs:

    antispam Running
    Running antivirus
    Running ldap
    Running logger
    mailbox Stopped
    mysql.server is not running.
    Running mta
    Running snmp
    Running spell
    stats Stopped
    That tells us nothing other than a service is not running. You need to look in the log files and see exactly what the errors are when you start Zimbra. When you've got the errors, look in the forums to see what exactly is causing the problem(s).
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  7. #7
    gustavocearasc is offline Intermediate Member
    Join Date
    Apr 2010
    Posts
    16
    Rep Power
    5

    Default Error mailbox.log

    2011-11-21 13:39:14,212 WARN [main] [] misc - Could not establish a connection to the database. Retrying in 5 seconds.
    com.zimbra.common.service.ServiceException: system failure: getting database connection
    ExceptionId:main:1321893554212:7935f6e55e23f3d9
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
    at com.zimbra.cs.db.DbPool.getConnection(DbPool.java: 314)
    at com.zimbra.cs.db.DbPool.getConnection(DbPool.java: 278)
    at com.zimbra.cs.db.DbPool.waitForDatabase(DbPool.jav a:200)
    at com.zimbra.cs.db.DbPool.startup(DbPool.java:191)
    at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:157)
    at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:123)
    at com.zimbra.soap.SoapServlet.init(SoapServlet.java: 128)
    at javax.servlet.GenericServlet.init(GenericServlet.j ava:241)
    at org.mortbay.jetty.servlet.ServletHolder.initServle t(ServletHolder.java:440)
    at org.mortbay.jetty.servlet.ServletHolder.doStart(Se rvletHolder.java:263)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
    at org.mortbay.jetty.servlet.ServletHandler.initializ e(ServletHandler.java:685)
    at org.mortbay.jetty.servlet.Context.startContext(Con text.java:140)
    at org.mortbay.jetty.webapp.WebAppContext.startContex t(WebAppContext.java:1254)
    at org.mortbay.jetty.handler.ContextHandler.doStart(C ontextHandler.java:517)
    at org.mortbay.jetty.webapp.WebAppContext.doStart(Web AppContext.java:471)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
    at org.mortbay.jetty.handler.HandlerCollection.doStar t(HandlerCollection.java:152)
    at org.mortbay.jetty.handler.ContextHandlerCollection .doStart(ContextHandlerCollection.java:156)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
    at org.mortbay.jetty.handler.HandlerCollection.doStar t(HandlerCollection.java:152)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
    at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
    at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
    at org.mortbay.jetty.handler.DebugHandler.doStart(Deb ugHandler.java:127)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
    at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:130)
    at org.mortbay.jetty.Server.doStart(Server.java:224)
    at org.mortbay.setuid.SetUIDServer.doStart(SetUIDServ er.java:158)
    at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:50)
    at org.mortbay.xml.XmlConfiguration.main(XmlConfigura tion.java:985)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.mortbay.start.Main.invokeMain(Main.java:194)
    at org.mortbay.start.Main.start(Main.java:534)
    at org.mortbay.start.Main.start(Main.java:441)
    at org.mortbay.start.Main.main(Main.java:119)
    Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientC onnectionException: Could not create connection to database server. Attempted reconnect 3 times. Giving up.
    at sun.reflect.GeneratedConstructorAccessor16.newInst ance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newI nstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Construc tor.java:513)
    at com.mysql.jdbc.Util.handleNewInstance(Util.java:40 9)
    at com.mysql.jdbc.Util.getInstance(Util.java:384)
    at com.mysql.jdbc.SQLError.createSQLException(SQLErro r.java:1015)
    at com.mysql.jdbc.SQLError.createSQLException(SQLErro r.java:989)
    at com.mysql.jdbc.SQLError.createSQLException(SQLErro r.java:984)
    at com.mysql.jdbc.SQLError.createSQLException(SQLErro r.java:929)
    at com.mysql.jdbc.ConnectionImpl.connectWithRetries(C onnectionImpl.java:2226)
    at com.mysql.jdbc.ConnectionImpl.createNewIO(Connecti onImpl.java:2127)
    at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImp l.java:774)
    at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connect ion.java:49)
    at sun.reflect.GeneratedConstructorAccessor14.newInst ance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newI nstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Construc tor.java:513)
    at com.mysql.jdbc.Util.handleNewInstance(Util.java:40 9)
    at com.mysql.jdbc.ConnectionImpl.getInstance(Connecti onImpl.java:375)
    at com.mysql.jdbc.NonRegisteringDriver.connect(NonReg isteringDriver.java:289)
    at java.sql.DriverManager.getConnection(DriverManager .java:582)
    at java.sql.DriverManager.getConnection(DriverManager .java:154)
    at org.apache.commons.dbcp.DriverManagerConnectionFac tory.createConnection(DriverManagerConnectionFacto ry.java:78)
    at com.zimbra.cs.db.ZimbraConnectionFactory.createCon nection(ZimbraConnectionFactory.java:64)
    at org.apache.commons.dbcp.PoolableConnectionFactory. makeObject(PoolableConnectionFactory.java:582)
    at org.apache.commons.pool.impl.GenericObjectPool.bor rowObject(GenericObjectPool.java:1158)
    at org.apache.commons.dbcp.PoolingDataSource.getConne ction(PoolingDataSource.java:106)
    at com.zimbra.cs.db.DbPool.getConnection(DbPool.java: 295)
    ... 39 more
    Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsExce ption: Communications link failure

    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    at sun.reflect.GeneratedConstructorAccessor12.newInst ance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newI nstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Construc tor.java:513)
    at com.mysql.jdbc.Util.handleNewInstance(Util.java:40 9)
    at com.mysql.jdbc.SQLError.createCommunicationsExcept ion(SQLError.java:1118)
    at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:343)
    at com.mysql.jdbc.ConnectionImpl.connectWithRetries(C onnectionImpl.java:2168)
    ... 56 more
    Caused by: java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:351)
    at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:213)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:200)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
    at java.net.Socket.connect(Socket.java:529)
    at java.net.Socket.connect(Socket.java:478)
    at java.net.Socket.<init>(Socket.java:375)
    at java.net.Socket.<init>(Socket.java:218)
    at com.mysql.jdbc.StandardSocketFactory.connect(Stand ardSocketFactory.java:256)
    at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:292)
    ... 57 more

  8. #8
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,491
    Rep Power
    56

    Default

    That just tells us that it can't connect to the MySQL server, you need to look in the other log files for the reason the mailbox isn't starting.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  9. #9
    gustavocearasc is offline Intermediate Member
    Join Date
    Apr 2010
    Posts
    16
    Rep Power
    5

    Default

    I stopped the zimbra service and restored the backup to start again from scratch.
    when I run zmsetservername-n error follows below:

    ./zmsetservername -n zimbra2.teste.com.br
    Getting local config zimbra_home=/opt/zimbra
    Getting local config zimbra_server_hostname=mail.teste.com.br
    Getting local config ldap_is_master=true
    Getting local config zimbra_ldap_userdn=uid=zimbra,cn=admins,cn=zimbra
    Getting local config zimbra_ldap_password=YU5ObJ6j8
    Getting local config ldap_master_url=ldap://mail.teste.com.br:389
    Getting local config ldap_starttls_supported=1
    Getting global config zimbraLogHostname=ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException mail.teste.com.br:389)

    Renaming mail.teste.com.br to zimbra2.teste.com.br
    Shutting down zimbra...done.
    Setting local config ldap_master_url=ldap://zimbra2.teste.com.br:389
    Getting local config ldap_url=ldap://mail.teste.com.br:389
    Setting local config ldap_url=ldap://zimbra2.teste.com.br:389
    Getting local config ldap_host=mail.teste.com.br
    Setting local config ldap_host=zimbra2.teste.com.br
    Getting local config av_notify_user=admin@mail.teste.com.br
    Setting local config av_notify_user=admin@zimbra2.teste.com.br
    Getting local config av_notify_domain=mail.teste.com.br
    Setting local config av_notify_domain=zimbra2.teste.com.br
    Getting local config snmp_trap_host=mail.teste.com.br
    Setting local config snmp_trap_host=zimbra2.teste.com.br
    Getting local config smtp_source=admin@mail.teste.com.br
    Setting local config smtp_source=admin@zimbra2.teste.com.br
    Getting local config smtp_destination=admin@mail.teste.com.br
    Setting local config smtp_destination=admin@zimbra2.teste.com.br
    Setting local config zimbra_server_hostname=zimbra2.teste.com.br
    Starting ldap...done.

    Unable to contact ldap://mail.teste.com.br:389: Connection timed out
    Unable to contact ldap://mail.teste.com.br:389: Connection timed out
    Services:
    Getting local config ldap_port=389
    Reinitializing the mta config...done.
    Reinitializing the snmp config...done.

  10. #10
    cloudmafia is offline Junior Member
    Join Date
    Mar 2012
    Location
    Earth
    Posts
    7
    Rep Power
    3

    Lightbulb [Solved] Change Zimbra Hostname ;)

    I think i can help you in this...


    First of all...

    If you are using local dns then configure DNS for new hostname and make changes in resolv.conf and hosts file... confirm dns is resolving your queries...
    use dig,nslookup and host commands...Reboot the system...

    Note - Before Processding for next step make sure that your dns server is resolving you hostname A record and MX record.

    Login with root.
    follow the below instructions.

    # su - zimbra

    $ zmcontrol stop

    $ /opt/zimbra/libexec/zmsetservername -force -n new.hostname.com
    (you will receive some errors but ignore them)

    $ /opt/zimbra/libexec/zmsetservername -o old.hostname.com -n new.hostname.com

    (it will not show any error and work fine)


    Set Default Domain-
    $ zmprov -l mcf zimbraDefaultDomainName newdomain.com


    Generate New ssh key for zimbra and update it

    $ zmsshkeygen

    $ zmupdateauthkeys

    $ zmcontrol start


    (it should start your zimbra successfully)


    Now if you are using self signed certificate so you have to create new certificate following below instruction...but before that make sure you system
    timezone and you zimbra server timezones are same.

    $ exit

    # su - zimbra -c 'zmcontrol stop'

    # rm -rf /opt/zimbra/ssl/*

    # rm -rf /opt/zimbra/ssl/.rnd

    # /opt/zimbra/java/bin/keytool -delete -alias my_ca -keystore /opt/zimbra/java/jre/lib/security/cacerts -storepass changeit

    # /opt/zimbra/java/bin/keytool -delete -alias jetty -keystore /opt/zimbra/mailboxd/etc/keystore -storepass `su - zimbra -c 'zmlocalconfig -s -m nokey mailboxd_keystore_password'`

    # vim /opt/zimbra/bin/zmcertmgr

    Find line
    SUBJECT="/C=US/ST=N\/A/L=N\/A/O=Zimbra Collaboration Suite/OU=Zimbra Collaboration Suite/CN=${zimbra_server_hostname}"
    and change to your company name

    then find and change you want value days expire cert validation_days=365 to validation_days=3650

    (save & exit)

    # /opt/zimbra/bin/zmcertmgr createca -new

    # /opt/zimbra/bin/zmcertmgr deployca -localonly

    # /opt/zimbra/bin/zmcertmgr createcrt self -new

    # /opt/zimbra/bin/zmcertmgr deploycrt self

    # su - zimbra -c 'zmcontrol start'

    It should start all the services successfully without any error.



    # /opt/zimbra/bin/zmcertmgr deploycrt self

    # /opt/zimbra/bin/zmcertmgr deployca

    # su - zimbra -c 'zmupdateauthkeys'

    # /opt/zimbra/bin/zmcertmgr viewdeployedcrt


    Login to Web link and check whether everything is working well or not.
    Check newly installed certificates and running services.


    https://<ip address> >>> web mail login

    https://<ip address>:7071/zimbraAdmin >>> Admin console login


    Enjoy...
    Cheers

    ------
    Neo

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. ZCS7 Beta only Listens on IPv6
    By tobru in forum Installation
    Replies: 2
    Last Post: 03-25-2011, 03:31 AM
  2. [SOLVED] Error Installing Zimbra on RHEL 5
    By harris7139 in forum Installation
    Replies: 10
    Last Post: 09-25-2007, 11:39 AM
  3. 4.5 Upgrade failure
    By brained in forum Installation
    Replies: 9
    Last Post: 03-03-2007, 03:30 PM
  4. svn version still won't start
    By kinaole in forum Developers
    Replies: 0
    Last Post: 10-04-2006, 06:47 AM
  5. Fedora Core 3, Clean Install - Not working!
    By pcjackson in forum Installation
    Replies: 17
    Last Post: 03-05-2006, 07:38 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
  •