Services Stop Running Due To Lack Of Space In Database Server
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
All Services stop running. This affects outgoing mail queue, backup service and others. When these actions are performed manually, it works.
For example, the Mail Queue will not flush automatically but when flushed manually, all mails are sent
After generating a Support Zip, the following appears in the application.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
<services>
<service>
<name>Audit log cleaning service</name>
<delay>86400ms</delay>
<last-run>19/Dec/14 11:33 AM</last-run>
</service>
<service>
<name>Backup Service</name>
<delay>43200ms</delay>
<last-run>19/Dec/14 11:33 PM</last-run>
</service>
<service>
<name>Mail Queue Service</name>
<delay>60ms</delay>
<last-run>20/Dec/14 2:16 AM</last-run>
</service>
</services>
Cross checking the time the Service last ran, the following appears in the atlassian-jira.log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
2014-12-20 02:14:19,237 atlassian-scheduler-quartz1.local_Worker-3 ERROR ServiceRunner [org.quartz.core.JobRunShell] Job SchedulerServiceJobs.com.atlassian.jira.service.DefaultServiceManager threw an unhandled Exception:
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:RunDetails][jobId,com.atlassian.jira.service.JiraService:10000][runDuration,1][runOutcome,S][startTime,2014-12-20 02:14:19.228][id,918354][infoMessage,] (SQL Exception while executing the following:INSERT INTO public.rundetails (ID, JOB_ID, START_TIME, RUN_DURATION, RUN_OUTCOME, INFO_MESSAGE) VALUES (?, ?, ?, ?, ?, ?) (ERROR: could not extend file "base/18844/20965": wrote only 4096 of 8192 bytes at block 2
Hint: Check free disk space.))
at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:397)
at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.createValue(WrappingOfBizDelegator.java:219)
at com.atlassian.jira.entity.EntityEngineImpl.createValue(EntityEngineImpl.java:34)
at com.atlassian.jira.scheduler.OfBizRunDetailsDao.addRunDetails(OfBizRunDetailsDao.java:140)
at com.atlassian.scheduler.core.AbstractSchedulerService.addRunDetails(AbstractSchedulerService.java:145)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:81)
at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32)
at org.quartz.core.JobRunShell.run(JobRunShell.java:223)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Caused by: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:RunDetails][jobId,com.atlassian.jira.service.JiraService:10000][runDuration,1][runOutcome,S][startTime,2014-12-20 02:14:19.228][id,918354][infoMessage,] (SQL Exception while executing the following:INSERT INTO public.rundetails (ID, JOB_ID, START_TIME, RUN_DURATION, RUN_OUTCOME, INFO_MESSAGE) VALUES (?, ?, ?, ?, ?, ?) (ERROR: could not extend file "base/18844/20965": wrote only 4096 of 8192 bytes at block 2
Hint: Check free disk space.))
at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:200)
at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:165)
at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:83)
at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:554)
at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:98)
at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:392)
... 8
Cause
As per the error pointed, it is caused by lack of space in database server, the database could not add or alter more data into its table, thus this error is thrown. Other functions in JIRA might still work. However data might be corrupted already. This might cause lost work if a restore of a previous backup must be performed.
Resolution
Add more space on the database server or clean up some unused data to free up some space there
Was this helpful?