Perforce repository indexing fails due to message "Disallowed by policy"

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

症状

Fisheye has been trying to index a Perforce repository, and the following error appears in the atlassian-fisheye-<date>.log:

2014-08-27 14:20:26,774 DEBUG [InitPing3 P4Repo ] fisheye P4CliUtils-dumpCommandLine - [perforce:1666//P4Repo/main] Executing p4 -p perforce:1666 -u fisheye -ztag fixes //P4Repo/main/...@914531,915986 
2014-08-27 14:20:26,805 DEBUG [InitPing3 P4Repo ] fisheye P4Exec-getProcessStatusMessage - Exception processing P4 command - returning as status
com.atlassian.utils.process.ProcessException: Non-zero exit code: 1
	at com.atlassian.utils.process.PluggableProcessHandler.complete(PluggableProcessHandler.java:69)
	at com.atlassian.utils.process.ExternalProcessImpl.wrapUpProcess(ExternalProcessImpl.java:509)
	at com.atlassian.utils.process.ExternalProcessImpl.finish(ExternalProcessImpl.java:423)
	at com.atlassian.utils.process.ExternalProcessImpl.execute(ExternalProcessImpl.java:378)
	at com.cenqua.fisheye.perforce.client.P4Exec.rawProcessCommand(P4Exec.java:214)
	at com.cenqua.fisheye.perforce.client.P4Exec.processCommand(P4Exec.java:176)
	at com.cenqua.fisheye.perforce.client.P4Exec.executeWithInput(P4Exec.java:286)
	at com.cenqua.fisheye.perforce.client.P4Exec.executeZTagCommand(P4Exec.java:279)
	at com.cenqua.fisheye.perforce.client.P4Client.addFixes(P4Client.java:217)
	at com.cenqua.fisheye.perforce.client.P4Client.addChangeFileInfo(P4Client.java:198)
	at com.cenqua.fisheye.perforce.client.P4Client.getChangeLists(P4Client.java:162)
	at com.cenqua.fisheye.perforce.P4Scanner.slurpRevisionBlock(P4Scanner.java:192)
	at com.cenqua.fisheye.perforce.P4Scanner.processRevisions(P4Scanner.java:1198)
	at com.cenqua.fisheye.rep.LifecycleRepositoryScanner.slurpRepository(LifecycleRepositoryScanner.java:81)
	at com.cenqua.fisheye.rep.LifecycleRepositoryScanner.doSlurpTransaction(LifecycleRepositoryScanner.java:48)
	at com.cenqua.fisheye.perforce.P4Scanner.doSlurpTransaction(P4Scanner.java:1081)
	at com.cenqua.fisheye.rep.BaseRepositoryScanner.ping(BaseRepositoryScanner.java:73)
	at com.cenqua.fisheye.rep.BaseRepositoryEngine.doSlurp(BaseRepositoryEngine.java:86)
	at com.cenqua.fisheye.rep.RepositoryEngine.slurp(RepositoryEngine.java:414)
	at com.cenqua.fisheye.rep.ping.IndexingPingRequest.doRequest(IndexingPingRequest.java:27)
	at com.cenqua.fisheye.rep.ping.IncrementalPingRequest.doRequest(IncrementalPingRequest.java:30)
	at com.cenqua.fisheye.rep.ping.PingRequest$1.run(PingRequest.java:55)
	at com.cenqua.fisheye.util.NamedExecution.run(NamedExecution.java:27)
	at com.cenqua.fisheye.rep.ping.PingRequest.process(PingRequest.java:52)
	at com.cenqua.fisheye.rep.RepositoryHandle.processPingRequests(RepositoryHandle.java:213)
	at com.cenqua.fisheye.rep.RepositoryHandle.access$100(RepositoryHandle.java:57)
	at com.cenqua.fisheye.rep.RepositoryHandle$2.run(RepositoryHandle.java:169)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
2014-08-27 14:20:26,805 DEBUG [InitPing3 P4Repo ] fisheye P4Exec-processCommand - [perforce:1666//P4Repo/main] Command failed with status = com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | Disallowed by policy
 - retrying with fresh login
2014-08-27 14:20:26,977 ERROR [InitPing3 P4Repo ] fisheye BaseRepositoryScanner-handleSlurpException - Problem processing revisions from repo P4Repo due to class com.cenqua.fisheye.perforce.client.P4ClientException - com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | Disallowed by policy
com.cenqua.fisheye.perforce.client.P4ClientException: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | Disallowed by policy
	at com.cenqua.fisheye.perforce.client.P4Client.addFixes(P4Client.java:233)
	at com.cenqua.fisheye.perforce.client.P4Client.addChangeFileInfo(P4Client.java:198)
	at com.cenqua.fisheye.perforce.client.P4Client.getChangeLists(P4Client.java:162)
	at com.cenqua.fisheye.perforce.P4Scanner.slurpRevisionBlock(P4Scanner.java:192)
	at com.cenqua.fisheye.perforce.P4Scanner.processRevisions(P4Scanner.java:1198)
	at com.cenqua.fisheye.rep.LifecycleRepositoryScanner.slurpRepository(LifecycleRepositoryScanner.java:81)
	at com.cenqua.fisheye.rep.LifecycleRepositoryScanner.doSlurpTransaction(LifecycleRepositoryScanner.java:48)
	at com.cenqua.fisheye.perforce.P4Scanner.doSlurpTransaction(P4Scanner.java:1081)
	at com.cenqua.fisheye.rep.BaseRepositoryScanner.ping(BaseRepositoryScanner.java:73)
	at com.cenqua.fisheye.rep.BaseRepositoryEngine.doSlurp(BaseRepositoryEngine.java:86)
	at com.cenqua.fisheye.rep.RepositoryEngine.slurp(RepositoryEngine.java:414)
	at com.cenqua.fisheye.rep.ping.IndexingPingRequest.doRequest(IndexingPingRequest.java:27)
	at com.cenqua.fisheye.rep.ping.IncrementalPingRequest.doRequest(IncrementalPingRequest.java:30)
	at com.cenqua.fisheye.rep.ping.PingRequest$1.run(PingRequest.java:55)
	at com.cenqua.fisheye.util.NamedExecution.run(NamedExecution.java:27)
	at com.cenqua.fisheye.rep.ping.PingRequest.process(PingRequest.java:52)
	at com.cenqua.fisheye.rep.RepositoryHandle.processPingRequests(RepositoryHandle.java:213)
	at com.cenqua.fisheye.rep.RepositoryHandle.access$100(RepositoryHandle.java:57)
	at com.cenqua.fisheye.rep.RepositoryHandle$2.run(RepositoryHandle.java:169)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
2014-08-27 14:20:26,977 ERROR [InitPing3 P4Repo ] fisheye RepositoryEngine-startPause - Repository scanner paused.

Running the command below directly in the Command Prompt / Terminal of the Fisheye server returns the same "Disallowed by policy" message:

p4 -p perforce:1666 -u fisheye -ztag fixes //P4Repo/main/...@914531,915986

Running the same command above on the P4 server works.

原因

The "p4 fixes" command has been failing because the broker is not allowing it.

ソリューション

  • Make sure that the broker is allowing "p4 fixes".
    OR 
  • If "p4 fixes" is not being used by your company, configure Fisheye to run directly to the Perforce server.
最終更新日 2018 年 7 月 31 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.