[SOLVED] Zimbra NE Backup Issue - session.xml.tmp was not renamed to session.xml

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
bsaxon
Posts: 27
Joined: Fri Sep 12, 2014 10:38 pm

[SOLVED] Zimbra NE Backup Issue - session.xml.tmp was not renamed to session.xml

Postby bsaxon » Sat May 08, 2010 9:04 am

I've tried running a full backup and I am getting the following error. I applied 6.0.6.1 patch last night. Not sure if this has anything to do w/ it. I've tried running the back up again with the same error. Anyone have any clues or know what's going?


Label: * full-20100508.060003.411

Type: * *unknown

Status: *missing, incomplete, or invalid

Started: Sat, 2010/05/08 01:00:03.411 CDT

Number of accounts: 0 out of 0 completed

Number of errors: 1

Error: incomplete backup full-20100508.060003.411: /opt/zimbra/backup/sessions/full-20100508.060003.411/session.xml.tmp was not renamed to session.xml; backup did not complete successfully

com.zimbra.cs.backup.BackupServiceException: incomplete backup full-20100508.060003.411: /opt/zimbra/backup/sessions/full-20100508.060003.411/session.xml.tmp was not renamed to session.xml; backup did not complete successfully

ExceptionId:btpool0-648://localhost:7071/service/admin/soap/BackupQueryRequest:1273320795617:4d45080e7455f190

Code:backup.INCOMPLETE_BACKUP

at com.zimbra.cs.backup.BackupServiceException.INCOMPLETE_BACKUP(BackupServiceException.java:70)

at com.zimbra.cs.backup.FileBackupTarget$FileBackupSet.(FileBackupTarget.java:792)

at com.zimbra.cs.backup.FileBackupTarget.getBackupSet(FileBackupTarget.java:216)

at com.zimbra.cs.backup.FileBackupTarget.getBackupSets(FileBackupTarget.java:236)

at com.zimbra.cs.service.backup.BackupQuery.handle(BackupQuery.java:71)

at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:419)

at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:273)

at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:157)

at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)

at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:182)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)

at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)

at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)

at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:155)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)

at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)

at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)

at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

at org.mortbay.jetty.Server.handle(Server.java:326)

at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543)

at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939)

at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)

at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)

at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)

at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)


uxbod
Ambassador
Ambassador
Posts: 7811
Joined: Fri Sep 12, 2014 10:21 pm

[SOLVED] Zimbra NE Backup Issue - session.xml.tmp was not renamed to session.xml

Postby uxbod » Sat May 08, 2010 9:16 am

Check /opt/zimbra/log/mailbox.log, around the time the backup kicked off, and see if any errors were reported.
bsaxon
Posts: 27
Joined: Fri Sep 12, 2014 10:38 pm

[SOLVED] Zimbra NE Backup Issue - session.xml.tmp was not renamed to session.xml

Postby bsaxon » Sat May 08, 2010 7:12 pm

The backup starts:
2010-05-08 19:03:39,144 INFO  [FullBackupThread] [] io - AsyncFileCopier is starting

2010-05-08 19:03:39,145 INFO [FullBackupThread] [] backup - Full backup started for backup set; label: full-20100509.000338.757

2010-05-08 19:03:39,360 INFO [FullBackupThread] [name=user@ourdomain.com;mid=560;] backup - redo log file sequence is 6559 at full backup for youngstown@southerncareinc.com

2010-05-08 19:03:39,417 INFO [FullBackupThread] [name=user@ourdomain;mid=560;] backup - Full backup started for account user@ourdomain.com (3a373c26-4e8d-44d4-831d-6ca6e327c947) mailbox 560

2010-05-08 19:03:39,418 INFO [FullBackupThread] [name=user@ourdomain.com;mid=560;] mailbox - Locking mailbox 560 for maintenance.

2010-05-08 19:03:39,431 INFO [FullBackupThread] [name=user@ourdomain.com;mid=560;] backup - Number of blobs to backup for mailbox 560: 3364

2010-05-08 19:03:39,431 INFO [FullBackupThread] [name=user@ourdomain.com;mid=560;] mailbox - Ending maintenance on mailbox 560.

2010-05-08 19:03:39,431 INFO [FullBackupThread] [name=user@ourdomain.com;mid=560;] mbxmgr - Mailbox 560 account 3a373c26-4e8d-44d4-831d-6ca6e327c947 AVAILABLE

And then the following error:

2010-05-08 19:04:09,991 ERROR [ZipCopier-mbox560-2] [] backup - Unable to write to zip file

java.io.IOException: No space left on device

at java.io.FileOutputStream.writeBytes(Native Method)

at java.io.FileOutputStream.write(FileOutputStream.java:260)

at com.zimbra.common.util.zip.ZipOutputStream.writeOut(ZipOutputStream.java:903)

at com.zimbra.common.util.zip.ZipOutputStream.write(ZipOutputStream.java:513)

at com.zimbra.cs.backup.util.ParallelZipCopier$ZipCopierThread.run(ParallelZipCopier.java:213)

2010-05-08 19:04:09,991 ERROR [ZipCopier-mbox560-2] [] backup - Error reported by FileCopier: No space left on device

java.io.IOException: No space left on device

at java.io.FileOutputStream.writeBytes(Native Method)

at java.io.FileOutputStream.write(FileOutputStream.java:260)

at com.zimbra.common.util.zip.ZipOutputStream.writeOut(ZipOutputStream.java:903)

at com.zimbra.common.util.zip.ZipOutputStream.write(ZipOutputStream.java:513)

at com.zimbra.cs.backup.util.ParallelZipCopier$ZipCopierThread.run(ParallelZipCopier.java:213)


I'm out of disk space!
Klug
Elite member
Elite member
Posts: 2365
Joined: Mon Dec 16, 2013 11:35 am
Contact:

[SOLVED] Zimbra NE Backup Issue - session.xml.tmp was not renamed to session.xml

Postby Klug » Sun May 09, 2010 10:10 am

I happened to me once.

As long as you don't remove the temporary file, you won't be able to do any more backups.
(I edited the previous post just to change the BBcode from "PHP" to "code")

Return to “Administrators”

Who is online

Users browsing this forum: No registered users and 6 guests