nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problem backing up data for the null plugiP

Adnan_aa2oxg

An Error occurred while we are taking the xml backup.

Error: "There was a problem backing up data for the null plugin"

But the XML backup file created with above error. when we are going to restore it gives the below Error.

Error importing from zip file: "/var/application-data/jira/import/2016-Sep-30--0100.zip". Error: archive is not a ZIP archive

At location "/application-data/jira/export\" we have observed a folder with name "corrupted" i attached this folder I hope it will help out you to diagnose the exact problem.

Please investigate and resolve the issue.

Thanks

Adnan Haider250backup error.jpg

corrupted.rar

backup error.jpg

Accepted answers

All comments

Nic Brough -Adaptavist-

Best guess is that you've got an invalid or removed add-on that still has data lying around.

Have a look at the list of add-ons you have - any showing as broken, invalid or disabled? What does the log file say at the time of the backup failure? I'd expect it to tell us what classes are failing, which would at least lead us to the right add-on.

Adnan_aa2oxg

i have checked there is no any add-ons showing as broken , invalid or disabled. i have attached the Atlassian-jira.log file. please have look into it.

atlassian-jira.rar

Nic Brough -Adaptavist-

I don't have the time or energy to guess my way throgh your whole log file.

What does it say at the time of the backup failure?

Adnan_aa2oxg

We observed that the following Errors occurred whenever the auto backup service of JIRA executed.

2016-10-17 09:02:12,960 Caesium-1-3 ERROR anonymous    Backup Service [c.a.j.bc.dataimport.DefaultExportService] Error during Active Objects Backup

com.atlassian.activeobjects.spi.ActiveObjectsImportExportException: There was an error during import/export with <unknown plugin>:

        at com.atlassian.activeobjects.backup.ImportExportErrorServiceImpl.newImportExportSqlException(ImportExportErrorServiceImpl.java:26)

        at com.atlassian.dbexporter.jdbc.JdbcUtils.withNoAutoCommit(JdbcUtils.java:57)

        at com.atlassian.dbexporter.exporter.DataExporter$1.call(DataExporter.java:52)

        at com.atlassian.dbexporter.exporter.DataExporter$1.call(DataExporter.java:49)

        at com.atlassian.dbexporter.jdbc.JdbcUtils.withConnection(JdbcUtils.java:28)

        at com.atlassian.dbexporter.exporter.DataExporter.export(DataExporter.java:49)

        at com.atlassian.dbexporter.DbExporter.exportData(DbExporter.java:49)

        at com.atlassian.activeobjects.backup.ActiveObjectsBackup.save(ActiveObjectsBackup.java:110)

        at com.atlassian.jira.bc.dataimport.DefaultExportService.exportActiveObjects(DefaultExportService.java:184)

        at com.atlassian.jira.bc.dataimport.DefaultExportService.export(DefaultExportService.java:86)

        at com.atlassian.jira.bc.dataimport.DefaultExportService.export(DefaultExportService.java:67)

        at com.atlassian.jira.service.services.export.ExportService.performBackup(ExportService.java:123)

        at com.atlassian.jira.service.services.export.ExportService.run(ExportService.java:111)

        at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)

        at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:62)

        at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:44)

        at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:32)

        at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)

        at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)

        at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:401)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:396)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:349)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:255)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:252)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)

        at java.lang.Thread.run(Thread.java:745)

Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 28,800,010 milliseconds ago.  The last packet sent successfully to the server was 28,802,419 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.

        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

        at java.lang.reflect.Constructor.newInstance(Constructor.java:422)

        at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)

        at com.mysql.jdbc.MysqlIO.readPacket(MysqlIO.java:628)

        at com.mysql.jdbc.MysqlIO.getResultSet(MysqlIO.java:415)

        at com.mysql.jdbc.MysqlIO.readResultsForQueryOrUpdate(MysqlIO.java:3040)

        at com.mysql.jdbc.MysqlIO.readAllResults(MysqlIO.java:2288)

        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2681)

        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2547)

        at com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:4874)

        at org.apache.commons.dbcp.DelegatingConnection.setAutoCommit(DelegatingConnection.java:371)

        at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.setAutoCommit(PoolingDataSource.java:328)

        at org.ofbiz.core.entity.jdbc.interceptors.connection.DelegatingConnection.setAutoCommit(DelegatingConnection.java:56)

        ... 3 filtered

        at java.lang.reflect.Method.invoke(Method.java:497)

        at net.java.ao.DelegateConnectionHandler.delegate(DelegateConnectionHandler.java:79)

        at net.java.ao.DelegateConnectionHandler.invoke(DelegateConnectionHandler.java:54)

        at com.sun.proxy.$Proxy2823.setAutoCommit(Unknown Source)

        ... 2 filtered

        at java.lang.reflect.Method.invoke(Method.java:497)

        at com.atlassian.activeobjects.spi.ConnectionHandler.delegate(ConnectionHandler.java:38)

        at com.atlassian.activeobjects.spi.ConnectionHandler.invoke(ConnectionHandler.java:33)

        at com.sun.proxy.$Proxy3034.setAutoCommit(Unknown Source)

        at com.atlassian.dbexporter.jdbc.JdbcUtils.withNoAutoCommit(JdbcUtils.java:54)

        ... 27 more

Caused by: java.io.EOFException: Can not read response from server. Expected to read 7,171,939 bytes, read 159,943 bytes before connection was unexpectedly lost.

at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:2957)

        at com.mysql.jdbc.MysqlIO.readPacket(MysqlIO.java:598)

        ... 50 more

2016-10-17 09:02:12,961 Caesium-1-3 ERROR anonymous    Backup Service [c.a.j.s.services.export.ExportService] An exception while running the export service "Backup Service": There was a problem backing up data for the null plugin.

com.atlassian.core.AtlassianCoreException: There was a problem backing up data for the null plugin.

        at com.atlassian.jira.service.services.export.ExportService.performBackup(ExportService.java:125)

        at com.atlassian.jira.service.services.export.ExportService.run(ExportService.java:111)

        at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)

        at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:62)

        at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:44)

        at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:32)

        at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)

        at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)

        at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:401)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:396)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:349)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:255)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:252)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)

        at java.lang.Thread.run(Thread.java:745)

2016-10-17 09:02:13,071 Caesium-1-3 WARN anonymous    Backup Service [c.a.j.s.services.export.ExportService] The corrupted backup file '/var/application-data/jira/export/2016-Oct-17--0100.zip' was moved to '/var/application-data/jira/export/corrupted/2016-Oct-17--0100.zip'.

2016-10-17 09:02:13,071 Caesium-1-3 WARN anonymous    Backup Service [c.a.j.s.services.export.ExportService] A backup failure reason file was written to '/var/application-data/jira/export/corrupted/2016-Oct-17--0100.zip.failure.txt'.

2016-10-17 09:02:13,073 Caesium-1-3 WARN ServiceRunner     [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: replaced => count=-1; marks=[-2-0]; pool=7/20

java.lang.AssertionError: Explicit stack trace requested

        at com.atlassian.jira.util.log.RateLimitingLogger.warnWithTrace(RateLimitingLogger.java:141)

        at com.atlassian.jira.ofbiz.ConnectionPoolHealthSqlInterceptor$CountHolder.logWarn(ConnectionPoolHealthSqlInterceptor.java:240)

        at com.atlassian.jira.ofbiz.ConnectionPoolHealthSqlInterceptor$CountHolder.replaced(ConnectionPoolHealthSqlInterceptor.java:269)

        at com.atlassian.jira.ofbiz.ConnectionPoolHealthSqlInterceptor.onConnectionReplaced(ConnectionPoolHealthSqlInterceptor.java:98)

        at com.atlassian.jira.ofbiz.ChainedSQLInterceptor.lambda$onConnectionReplaced$330(ChainedSQLInterceptor.java:70)

        at com.atlassian.jira.ofbiz.ChainedSQLInterceptor$$Lambda$11/473184174.accept(Unknown Source)

        at com.atlassian.jira.ofbiz.ChainedSQLInterceptor.forEach(ChainedSQLInterceptor.java:93)

        at com.atlassian.jira.ofbiz.ChainedSQLInterceptor.onConnectionReplaced(ChainedSQLInterceptor.java:69)

        at org.ofbiz.core.entity.jdbc.interceptors.connection.SafeDelegatingSqlConnectionInterceptor.onConnectionReplaced(SafeDelegatingSqlConnectionInterceptor.java:47)

        at org.ofbiz.core.entity.jdbc.interceptors.connection.ConnectionTracker$DelegatingConnectionImpl.close(ConnectionTracker.java:99)

        at org.ofbiz.core.entity.jdbc.SQLProcessor.closeConnection(SQLProcessor.java:330)

        at org.ofbiz.core.entity.jdbc.SQLProcessor.close(SQLProcessor.java:271)

        at org.ofbiz.core.entity.EntityListIterator.close(EntityListIterator.java:156)

        at com.atlassian.jira.ofbiz.DefaultOfBizListIterator.close(DefaultOfBizListIterator.java:69)

        at com.atlassian.jira.ofbiz.WrappingOfBizListIterator.close(WrappingOfBizListIterator.java:48)

        at com.atlassian.jira.entity.SelectQueryImpl$ExecutionContextImpl.forEach(SelectQueryImpl.java:234)

        at com.atlassian.jira.entity.SelectQueryImpl$ExecutionContextImpl.asList(SelectQueryImpl.java:164)

        at com.atlassian.jira.scheduler.OfBizRunDetailsDao.getAllIdsForJob(OfBizRunDetailsDao.java:139)

        at com.atlassian.jira.scheduler.OfBizRunDetailsDao.addRunDetails(OfBizRunDetailsDao.java:111)

        at com.atlassian.scheduler.core.AbstractSchedulerService.addRunDetails(AbstractSchedulerService.java:151)

        at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:98)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:401)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:396)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:349)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:255)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:252)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)

        at java.lang.Thread.run(Thread.java:745)

Colin McDermott_GLiNTECH

As per https://community.atlassian.com/t5/Jira-questions/There-was-a-problem-backing-up-data-for-the-null-plugin/qaq-p/935204

The max_allowed_packets may be your culprit here.

Take a look at your mysql logs and see if you are getting issues.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software