| 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.
|  | | 
09-13-2007, 03:44 PM
| | Former Zimbran | |
Posts: 5,606
| | Check your private messages. | 
09-13-2007, 07:48 PM
| | | To summarize, FQDN/hostname is changing in his case (not just like moving everything to a dedicated co-loc somewhere) + a domain name change (while hosting several other domains as well)
No split dns for him at present-so thankfully that's didn't add to the mix or anything.
His ZCS is up and running fine, but waiting for mx record switchovers to receive mail.
----
A bit of warning to others who come later:
IP's will obviously change in dns/mx/hostfile/resolve-but your server name should stay the same till your comfortable running the change name script-after a good backup, because people have mixed results.
(see all the fun in that: ZmSetServerName - ZimbraWiki)
----
Will you be changing operating system versions as well?: Quote: |
Originally Posted by phoenix Backup the /opt/zimbra directory on your current server (check the gid & uid of zimbra and make a note of it) then disconnect it from your LAN. Install the same release on the new Zimbra server as you had on the old server, make sure it's all working the shutdown zimbra and copy the directory from your old server to the new one, make sure the uid & gid is changed to the ones you had on the old server - run zmfixperms and also make sure the LDAP password is set (check the wiki or forum for details). Do an upgrade install (./install.sh -s) on the new server and you should be good to go. I'm assuming that your new server will have the same IP & FQDN as the old server. That should be about it. | It's being revised-but if your changing from 32>64bit: Network Edition: Moving from 32-bit to 64-bit Server - ZimbraWiki
NE users just see the different methods of using zmbackup>zmrestore /docs/ne/latest/administration_guide/10_Backup_Restore.13.1.html#1079525 | 
09-26-2007, 09:06 AM
| | | Well, After a 3 hour session & with the help of jholder, managed to get server data transfered and pointed all relevant domain mx records to new dedicated server. Now i can't send any email from any account! I've had no emails come in the last 2 days due mx records now pointing to a server with Zimbra which is not working!. So i have no email and a server i'm paying money for which don't work!. How many times in posts have I said "I'M DONE WITH THIS?" I JUST CAN'T BELIEVE THAT THIS IS SOOOO HARD TO CONFIGURE? I'TS GOTTA BE ME?
WHEN'S THE BOOK COMING OUT GUYS!!!
THE BAD THING IS I'VE GOT 12 CLIENTS (APPX 120+ EMAIL ACCOUNTS) WAITING FOR ME TO SET THEM UP!!. ITS NOT GONNA HAPPEN NOW !!
ANYONE GOT A HOSTED SERVICE THAT WORKS? | 
09-26-2007, 09:23 AM
| | | Actually, several people DO have books in the works. On topics ranging from basic single server aspects > multi-server setups, some on clustering, and books just dedicated to zimlets.
List of HSP's if you should decide to go that route: http://www.zimbra.com/partners/zimbra_hosting.html
UPDATE: john's pm'ing back and forth - someone may post details on the current error shortly
Last edited by mmorse; 09-26-2007 at 09:46 AM..
| 
09-26-2007, 09:32 AM
| | Former Zimbran | |
Posts: 5,606
| | Quote:
Originally Posted by derr1ck Well, After a 3 hour session & with the help of jholder, managed to get server data transfered and pointed all relevant domain mx records to new dedicated server. Now i can't send any email from any account! I've had no emails come in the last 2 days due mx records now pointing to a server with Zimbra which is not working!. So i have no email and a server i'm paying money for which don't work!. How many times in posts have I said "I'M DONE WITH THIS?" I JUST CAN'T BELIEVE THAT THIS IS SOOOO HARD TO CONFIGURE? I'TS GOTTA BE ME?
WHEN'S THE BOOK COMING OUT GUYS!!!
THE BAD THING IS I'VE GOT 12 CLIENTS (APPX 120+ EMAIL ACCOUNTS) WAITING FOR ME TO SET THEM UP!!. ITS NOT GONNA HAPPEN NOW !!
ANYONE GOT A HOSTED SERVICE THAT WORKS? | I think there might be some oversimplification here.
First your issue was that you had simply moved server names, and moved ips. . without updating Zimbra.
So, I fixed that for you (out of kindness might I add).
Then the issue was that your DNS was not correct.
You fixed that.
Now the issue is with an exception you have. I asked you to post it in the forms because I had never seen that before.
For being a FRRRREEEEEEEE service, I think our support for you has been outstanding.
I'm sure a hosting provider would be happy to help you, but keep in mind that it I specifically went out of my way to help you. . .and I did not have to.
Last edited by jholder; 09-26-2007 at 09:37 AM..
| 
09-26-2007, 09:35 AM
| | Former Zimbran | |
Posts: 5,606
| | For those interested in helping, here's the exception I asked Derrick to post: Code: root@zimbra1:~# tail -f /opt/zimbra/log/mailbox.log
2007-09-26 05:35:58,977 INFO [Thread-191] [] mailbox - Importing POP3 messages from DataSource: { id=c4c56fb3-41ff-4e38-b69f-f596aebbf716, type=pop3, isEnabled=true, name=info@Datasurvivor, host=mail.datasurvivor.com, port=110, connectionType=cleartext, username=info@datasurvivor.com, folderId=2 }
2007-09-26 05:35:58,992 INFO [Thread-189] [] mailbox - Importing POP3 messages from DataSource: { id=398b0236-f01b-4d52-a86b-160b9a9b004b, type=pop3, isEnabled=true, name=Info@mobec, host=mail.maildomain.com, port=110, connectionType=cleartext, username=info@maildomain.com, folderId=2 }
2007-09-26 05:35:58,995 INFO [Pop3Server-2] [] pop - connected
2007-09-26 05:35:59,007 INFO [Pop3Server-3] [] pop - connected
2007-09-26 05:35:59,021 INFO [Pop3Server-2] [ip=66.128.49.170;] cache - Initializing folder and tag caches for mailbox 13
2007-09-26 05:35:59,225 INFO [Pop3Server-3] [ip=66.128.49.170;] cache - Initializing folder and tag caches for mailbox 14
2007-09-26 05:35:59,235 INFO [Pop3Server-3] [name=info@maildomain.com;ip=66.128.49.170;] pop - quit from client
2007-09-26 05:35:59,235 INFO [Pop3Server-3] [name=info@maildomain.com;ip=66.128.49.170;] ProtocolHandler - Handler exiting normally
2007-09-26 05:35:59,237 INFO [Pop3Server-2] [name=support@maildomain.com;ip=66.128.49.170;] pop - quit from client
2007-09-26 05:35:59,237 INFO [Pop3Server-2] [name=support@maildomain.com;ip=66.128.49.170;] ProtocolHandler - Handler exiting normally
2007-09-26 05:36:32,876 INFO [http-80-Processor99] [name=derrick@maildomain.com;mid=3;ip=87.194.33.122;ua=ZimbraWebClient - FF2.0 (Win)/4.5.6_GA_1044.UBUNTU6;] SendMsg - LC(mbox=0833a4f9-a34b-4cef-b3d9-68a01a31a298, sessions=[8])
2007-09-26 05:36:33,010 INFO [http-80-Processor99] [name=derrick@maildomain.com;mid=3;ip=87.194.33.122;ua=ZimbraWebClient - FF2.0 (Win)/4.5.6_GA_1044.UBUNTU6;] mailbox - Added message id=13460 digest=9p7XXwrVkD5J1u85UsesPhmXpb4= mailbox=3 rcpt=:API:
2007-09-26 05:36:36,389 INFO [IndexWritersSweeperThread] [] MailboxIndex - open index writers sweep: before=1, closed=0, after=1 (1ms)
2007-09-26 05:36:54,292 WARN [http-80-Processor99] [name=derrick@maildomain.com;mid=3;ip=87.194.33.122;ua=ZimbraWebClient - FF2.0 (Win)/4.5.6_GA_1044.UBUNTU6;] MailSender - exception occurred during SendMsg
com.zimbra.cs.mailbox.MailSender$SafeMessagingException
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1270)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:370)
at javax.mail.Service.connect(Service.java:275)
at javax.mail.Service.connect(Service.java:156)
at javax.mail.Service.connect(Service.java:105)
at javax.mail.Transport.send0(Transport.java:168)
at javax.mail.Transport.send(Transport.java:98)
at com.zimbra.cs.mailbox.MailSender.sendMessage(MailSender.java:369)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:248)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:124)
at com.zimbra.cs.operation.SendMsgOperation.callback(SendMsgOperation.java:114)
at com.zimbra.cs.operation.Operation.schedule(Operation.java:190)
at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:140)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:270)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:168)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:90)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:223)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
2007-09-26 05:36:54,294 INFO [http-80-Processor99] [name=derrick@maildomain.com;mid=3;ip=87.194.33.122;ua=ZimbraWebClient - FF2.0 (Win)/4.5.6_GA_1044.UBUNTU6;] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: MessagingException
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:175)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:307)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:124)
at com.zimbra.cs.operation.SendMsgOperation.callback(SendMsgOperation.java:114)
at com.zimbra.cs.operation.Operation.schedule(Operation.java:190)
at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:140)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:270)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:168)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:90)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:223)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: com.zimbra.cs.mailbox.MailSender$SafeMessagingException
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1270)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:370)
at javax.mail.Service.connect(Service.java:275)
at javax.mail.Service.connect(Service.java:156)
at javax.mail.Service.connect(Service.java:105)
at javax.mail.Transport.send0(Transport.java:168)
at javax.mail.Transport.send(Transport.java:98)
at com.zimbra.cs.mailbox.MailSender.sendMessage(MailSender.java:369)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:248)
... 26 more | 
09-26-2007, 09:46 AM
| | | Hey John, my comment on "what I'm paying for" was reference to the fact That I'm shelling out money for a dedicated server specifically to host Zimbra on NOT Zimbra it self. And as for your support I have thanked you, and the support was fantastic, I agree
But i still don't have a working installation. So I think my points are valid.
Zimbra's installation process needs to be simplified and should have a procedure for transferring an installation from server-to-server with or without a domain name change!.
I have attached the output below.
I Would love to get this Zimbra back up and running as i have gone so far with this and had it working on a local server without problems, alot of money & time has gone by and I need to account for the missed deadlines on other stuff while devoting time to this. | 
09-26-2007, 09:55 AM
| | | | | Thread Tools | Search this Thread | | | | | Display Modes | Linear Mode | | Why Join? Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.  |