Repository paused with - The filesystem 'P4LOG' has only 0MB free, but the server configuration requires at least 10MB available.
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
The Perforce repository in Fisheye is paused and in the UI the following error can be seen:
The following also appears in the atlassian-fisheye-YYYY-MM-DD.log:
Log Error
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
{noformat}
2015-03-16 03:03:53,956 ERROR - Unable to initialise repository FE-TEST due to com.cenqua.fisheye.config.ConfigException:Problem communicating with repository : Unable to get repository info: Unable to login: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | The filesystem 'P4LOG' has only 0MB free, but the server configuration requires at least 10MB available.
com.cenqua.fisheye.config.ConfigException: Problem communicating with repository : Unable to get repository info: Unable to login: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | The filesystem 'P4LOG' has only 0MB free, but the server configuration requires at least 10MB available.
at com.cenqua.fisheye.perforce.P4ScmConfig.testConnection(P4ScmConfig.java:169)
at com.cenqua.fisheye.perforce.P4RepositoryInfo.testConnection(P4RepositoryInfo.java:120)
at com.cenqua.fisheye.perforce.P4Scanner.validateRepository(P4Scanner.java:177)
at com.cenqua.fisheye.rep.LifecycleRepositoryScanner.startRepository(LifecycleRepositoryScanner.java:132)
at com.cenqua.fisheye.rep.LifecycleRepositoryScanner.doSlurpTransaction(LifecycleRepositoryScanner.java:39)
at com.cenqua.fisheye.rep.BaseRepositoryScanner.ping(BaseRepositoryScanner.java:75)
at com.cenqua.fisheye.rep.BaseRepositoryEngine.doSlurp(BaseRepositoryEngine.java:86)
at com.cenqua.fisheye.rep.RepositoryEngine.slurp(RepositoryEngine.java:397)
at com.cenqua.fisheye.rep.ping.IndexingPingRequest.doRequest(IndexingPingRequest.java:25)
at com.cenqua.fisheye.rep.ping.IncrementalPingRequest.doRequest(IncrementalPingRequest.java:30)
at com.cenqua.fisheye.rep.ping.PingRequest.process(PingRequest.java:54)
at com.cenqua.fisheye.rep.RepositoryHandle.processPingRequests(RepositoryHandle.java:219)
at com.cenqua.fisheye.rep.RepositoryHandle.access$100(RepositoryHandle.java:56)
at com.cenqua.fisheye.rep.RepositoryHandle$2.run(RepositoryHandle.java:175)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.cenqua.fisheye.perforce.client.P4ClientException: Unable to get repository info: Unable to login: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | The filesystem 'P4LOG' has only 0MB free, but the server configuration requires at least 10MB available.
at com.cenqua.fisheye.perforce.client.P4Client.info(P4Client.java:83)
at com.cenqua.fisheye.perforce.P4ScmConfig.testConnection(P4ScmConfig.java:161)
... 16 more
{noformat}Cause
By default, the Perforce Server rejects commands when free space on the filesystems housing the P4ROOT, P4JOURNAL, P4LOG, or TEMP falls below 10 megabytes.
Solution
Use the p4 diskspace command to monitor the disk space, this will display the amount of free space, diskspace used, and total capacity of any filesystem used by Perforce.
To change this behaviour alter the default values (10mb) for filesys.P4ROOT.min, filesys.P4JOURNAL.min, filesys.P4LOG.min, filesys.TEMP.min, filesys.depot.min values, also increase the amount of disk space available on the server.
Was this helpful?