堆栈内存溢出
  简体   繁体   English

Gradle 构建挂起没有失败，DefaultFileLockManager 获取和释放守护进程地址注册表上的锁定

[英]Gradle build is hanging without failure, DefaultFileLockManager acquiring and releasing lock on daemon addresses registry

 原文  2017-07-07 17:42:54  7   3    java/ gradle/ build/ artifactory/ gradlew

问题描述

I have several gradle-based projects and on all of them recently I've become unable to execute a ./gradlew clean build.我有几个基于 gradle 的项目，最近我都无法执行 ./gradlew clean build。 Upon running this, the When I run with the --debug flag, I get stuck on > Building 7% > :compileJava > Resolving dependencies ':compileClasspath' and it never moves forward.运行它时，当我使用 --debug 标志运行时，我卡在> Building 7% > :compileJava > Resolving dependencies ':compileClasspath'并且它永远不会前进。

When I ran with the --debug flag, I got this output regarding the DefaultFileLockManager acquiring and releasing a daemon lock, but this has been unhelpful.当我使用--debug标志运行时，我得到了关于DefaultFileLockManager获取和释放守护程序锁的输出，但这没有帮助。 Here is the last bit of the Gradle debug log that I see.这是我看到的 Gradle 调试日志的最后一点。

11:22:57.079 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection request: [route: {s}->https://maven.vaadin.com:443][total kept alive: 0; route allocated: 1 of 2; total allocated: 1 of 20]
11:22:57.080 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection leased: [id: 203][route: {s}->https://maven.vaadin.com:443][total kept alive: 0; route allocated: 2 of 2; total allocated: 2 of 20]
11:22:57.080 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Opening connection {s}->https://maven.vaadin.com:443
11:22:57.080 [DEBUG] [org.apache.http.impl.conn.DefaultHttpClientConnectionOperator] Connecting to maven.vaadin.com/54.86.23.48:443
11:22:57.080 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory] Connecting socket to maven.vaadin.com/54.86.23.48:443 with timeout 0
11:22:57.098 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory] Enabled protocols: [TLSv1, TLSv1.1, TLSv1.2]
11:22:57.098 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory] Enabled cipher suites:[TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
11:22:57.098 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory] Starting handshake
11:22:57.141 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory] Secure session established
11:22:57.141 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory]  negotiated protocol: TLSv1.2
11:22:57.142 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory]  negotiated cipher suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
11:22:57.142 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory]  peer principal: CN=*.vaadin.com, O=Vaadin Ltd, L=Turku, ST=Western Finland, C=FI
11:22:57.142 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory]  peer alternative names: [*.vaadin.com, vaadin.com]
11:22:57.142 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory]  issuer principal: CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US
11:22:57.142 [DEBUG] [org.apache.http.impl.conn.DefaultHttpClientConnectionOperator] Connection established 10.10.2.46:54773<->54.86.23.48:443
11:22:57.142 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Executing request HEAD /vaadin-addons/info/magnolia/magnolia-module-content-dependencies/1.6.1/magnolia-module-content-dependencies-1.6.1.pom HTTP/1.1
11:22:57.142 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Target auth state: UNCHALLENGED
11:22:57.142 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Proxy auth state: UNCHALLENGED
11:22:57.163 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-203: Close connection
11:22:57.166 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Connection discarded
11:22:57.166 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-203: Close connection
11:22:57.166 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection released: [id: 203][route: {s}->https://maven.vaadin.com:443][total kept alive: 0; route allocated: 1 of 2; total allocated: 1 of 20]
11:22:57.166 [INFO] [org.gradle.internal.resource.transport.http.HttpClientHelper] Resource missing. [HTTP HEAD: https://maven.vaadin.com/vaadin-addons/info/magnolia/magnolia-module-content-dependencies/1.6.1/magnolia-module-content-dependencies-1.6.1.pom]
11:22:57.167 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.DefaultExternalResourceArtifactResolver] Loading https://maven.vaadin.com/vaadin-addons/info/magnolia/magnolia-module-content-dependencies/1.6.1/magnolia-module-content-dependencies-1.6.1.jar
11:22:57.167 [DEBUG] [org.gradle.internal.resource.transport.http.HttpResourceAccessor] Constructing external resource metadata: https://maven.vaadin.com/vaadin-addons/info/magnolia/magnolia-module-content-dependencies/1.6.1/magnolia-module-content-dependencies-1.6.1.jar
11:22:57.167 [DEBUG] [org.gradle.internal.resource.transport.http.HttpClientHelper] Performing HTTP HEAD: https://maven.vaadin.com/vaadin-addons/info/magnolia/magnolia-module-content-dependencies/1.6.1/magnolia-module-content-dependencies-1.6.1.jar
11:22:57.167 [DEBUG] [org.apache.http.client.protocol.RequestAddCookies] CookieSpec selected: default
11:22:57.167 [DEBUG] [org.apache.http.client.protocol.RequestAuthCache] Auth cache not set in the context
11:22:57.167 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection request: [route: {s}->https://maven.vaadin.com:443][total kept alive: 0; route allocated: 1 of 2; total allocated: 1 of 20]
11:22:57.167 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection leased: [id: 204][route: {s}->https://maven.vaadin.com:443][total kept alive: 0; route allocated: 2 of 2; total allocated: 2 of 20]
11:22:57.167 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Opening connection {s}->https://maven.vaadin.com:443
11:22:57.167 [DEBUG] [org.apache.http.impl.conn.DefaultHttpClientConnectionOperator] Connecting to maven.vaadin.com/54.86.23.48:443
11:22:57.167 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory] Connecting socket to maven.vaadin.com/54.86.23.48:443 with timeout 0
11:22:57.186 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory] Enabled protocols: [TLSv1, TLSv1.1, TLSv1.2]
11:22:57.186 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory] Enabled cipher suites:[TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
11:22:57.186 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory] Starting handshake
11:22:57.207 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory] Secure session established
11:22:57.207 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory]  negotiated protocol: TLSv1.2
11:22:57.207 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory]  negotiated cipher suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
11:22:57.207 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory]  peer principal: CN=*.vaadin.com, O=Vaadin Ltd, L=Turku, ST=Western Finland, C=FI
11:22:57.207 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory]  peer alternative names: [*.vaadin.com, vaadin.com]
11:22:57.207 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory]  issuer principal: CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US
11:22:57.207 [DEBUG] [org.apache.http.impl.conn.DefaultHttpClientConnectionOperator] Connection established 10.10.2.46:54774<->54.86.23.48:443
11:22:57.207 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Executing request HEAD /vaadin-addons/info/magnolia/magnolia-module-content-dependencies/1.6.1/magnolia-module-content-dependencies-1.6.1.jar HTTP/1.1
11:22:57.207 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Target auth state: UNCHALLENGED
11:22:57.207 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Proxy auth state: UNCHALLENGED
11:22:57.230 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-204: Close connection
11:22:57.234 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Connection discarded
11:22:57.234 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-204: Close connection
11:22:57.234 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection released: [id: 204][route: {s}->https://maven.vaadin.com:443][total kept alive: 0; route allocated: 1 of 2; total allocated: 1 of 20]
11:22:57.234 [INFO] [org.gradle.internal.resource.transport.http.HttpClientHelper] Resource missing. [HTTP HEAD: https://maven.vaadin.com/vaadin-addons/info/magnolia/magnolia-module-content-dependencies/1.6.1/magnolia-module-content-dependencies-1.6.1.jar]
11:22:57.234 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.ExternalResourceResolver] No meta-data file or artifact found for module 'info.magnolia:magnolia-module-content-dependencies:1.6.1' in repository 'vaadin-addons'.
11:22:57.234 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.modulecache.DefaultModuleMetaDataCache] Recording absence of module descriptor in cache: info.magnolia:magnolia-module-content-dependencies:1.6.1 [changing = false]
11:22:57.235 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.DefaultExternalResourceArtifactResolver] Loading https://nexus.magnolia-cms.com/content/groups/enterprise/info/magnolia/magnolia-module-content-dependencies/1.6.1/magnolia-module-content-dependencies-1.6.1.pom
11:22:57.235 [DEBUG] [org.gradle.internal.resource.transfer.DefaultCacheAwareExternalResourceAccessor] Constructing external resource: https://nexus.magnolia-cms.com/content/groups/enterprise/info/magnolia/magnolia-module-content-dependencies/1.6.1/magnolia-module-content-dependencies-1.6.1.pom
11:22:57.235 [DEBUG] [org.gradle.internal.resource.transport.http.HttpResourceAccessor] Constructing external resource metadata: https://nexus.magnolia-cms.com/content/groups/enterprise/info/magnolia/magnolia-module-content-dependencies/1.6.1/magnolia-module-content-dependencies-1.6.1.pom
11:22:57.235 [DEBUG] [org.gradle.internal.resource.transport.http.HttpClientHelper] Performing HTTP HEAD: https://nexus.magnolia-cms.com/content/groups/enterprise/info/magnolia/magnolia-module-content-dependencies/1.6.1/magnolia-module-content-dependencies-1.6.1.pom
11:22:57.236 [DEBUG] [org.apache.http.client.protocol.RequestAddCookies] CookieSpec selected: default
11:22:57.236 [DEBUG] [org.apache.http.client.protocol.RequestAuthCache] Auth cache not set in the context
11:22:57.236 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection request: [route: {s}->https://nexus.magnolia-cms.com:443][total kept alive: 0; route allocated: 2 of 2; total allocated: 2 of 20]
11:23:06.177 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:23:06.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:06.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:06.178 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:23:06.178 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:06.178 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:06.178 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:23:16.177 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:23:16.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:16.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:16.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:23:16.178 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:16.178 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:16.178 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:23:26.179 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:23:26.179 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:26.179 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:26.179 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:23:26.179 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:26.179 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:26.180 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:23:36.180 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:23:36.180 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:36.180 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:36.180 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:23:36.180 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:36.181 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:36.181 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:23:46.176 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:23:46.176 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:46.176 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:46.176 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:23:46.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:46.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:46.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:23:56.179 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:23:56.180 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:56.180 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:56.180 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:23:56.181 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:23:56.181 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:23:56.181 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:06.177 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:24:06.178 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:06.178 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:06.178 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:06.178 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:06.179 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:06.179 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:16.176 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:24:16.176 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:16.176 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:16.176 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:16.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:16.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:16.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:26.176 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:24:26.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:26.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:26.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:26.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:26.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:26.177 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:36.175 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:24:36.175 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:36.176 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:36.176 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:36.176 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:36.176 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:36.176 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:46.173 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:24:46.174 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:46.174 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:46.174 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:46.175 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:46.175 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:46.175 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:56.172 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:24:56.173 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:56.173 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:56.173 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:24:56.173 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
11:24:56.174 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
11:24:56.174 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
11:25:06.175 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
11:25:06.175 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.

3 个解决方案

解决方案1
 0  2017-07-11 07:21:21

I had the same issue. 我遇到过同样的问题。 In my case setting proxy in ~/gradle/gradle.properties helped: 就我而言，在〜/ gradle / gradle.properties中设置代理有助于： 

systemProp.http.proxyHost=hostname
systemProp.http.proxyPort=8080
systemProp.http.proxyUser=user
systemProp.http.proxyPassword=password

解决方案2
 0  2018-07-02 03:37:56

In order for gradle work properly, you need to configure at least 3 kind of proxies on Linux/macOS which are 为了使gradle正常工作，您需要在Linux / macOS上至少配置3种代理：

  • gradle proxies - inside gradle.properties gradle代理-内部gradle.properties
  • maven proxies - inside ~/.m2/settings.xml Maven代理-〜/ .m2 / settings.xml内部
  • bash proxies - inside ~/.bashrc or ~/.bash_profile bash代理-〜/ .bashrc或〜/ .bash_profile内部

Apart from these proxy settings, you also need to double check your proxy settings of your OS, eg on mac, check "System Preferences" -> "Network" -> "Advanced..." -> "Proxies". 除了这些代理设置外，您还需要仔细检查操作系统的代理设置，例如在Mac上，选中“系统偏好设置”->“网络”->“高级...”->“代理”。 You may need try to turn on/off this system proxies. 您可能需要尝试打开/关闭此系统代理。

However, sometimes, like your case, it may not because of connectivity problems, but due to permission issues. 但是，有时，就像您的情况一样，可能不是由于连接问题，而是由于权限问题。 If you ever ran your gradle commands using "sudo" then some of the directories generated during executing the gradle commands may become owned by "root". 如果曾经使用“ sudo”运行gradle命令，则在执行gradle命令期间生成的某些目录可能会归“ root”所有。 Hence, when you try to run gralde commands using normal user, these directories are not accessible. 因此，当您尝试使用普通用户运行gralde命令时，将无法访问这些目录。 The bad thing is that gradle does not give you any information or even hints to "permission". 不好的是，gradle不会为您提供任何信息，甚至也不会提示您“许可”。

The solution to this is as below. 解决方法如下。

  • To find all the files and directories that are owned by root or belong to root group: 要查找所有由根拥有或属于根组的文件和目录：

    $ls -alR | $ ls -alR | grep -w root > list.txt grep -w root> list.txt

The result of this command will be output to file list.txt, open it to check all the files and directories. 该命令的结果将输出到文件list.txt，打开它以检查所有文件和目录。 For example you may see the output something as below: 例如，您可能会看到如下输出： 

drwxrwxr-x+ 86 root  admin   2.9K Jun 29 20:30 Applications/
drwxr-xr-x+ 65 root  wheel   2.2K May 19 00:19 ***/.gradle
drwxr-xr-x@  2 root  wheel    68B Nov 20  2016 ***/build
drwxr-xr-x@  4 root  wheel   136B Jun 29 20:31 .gradle
drwxr-xr-x    3 employee  staff   102B Nov 10  2015 Samsung/
drwxr-xr-x    7 employee  staff   238B Jul  6  2016 VirtualBox VMs/
drwxr-xr-x    3 employee  staff   102B Nov  4  2016 android-ndk/
drwxr-xr-x    3 employee  staff   102B Aug 31  2016 bin/

  • To find the exact location of those files or directories 查找这些文件或目录的确切位置

    $find "$PWD" | $ find“ $ PWD” | grep your-file-name grep您的文件名

  • Delete those files or directories. 删除那些文件或目录。

    $ sudo rm -rf your-file-name $ sudo rm -rf您的文件名

Usually, you need change your directory to below locations to perform above actions to delete all the files with root user. 通常，您需要将目录更改为以下位置，以执行上述操作，以root用户身份删除所有文件。

  • ~/.gradle – The .gradle cache under your user's “Home” directory 〜/ .gradle –用户“主”目录下的.gradle缓存
  • /.gradle – The .gradle cache under your project root directory /.gradle –项目根目录下的.gradle缓存
  • [project-root]/[module]/build – The .gradle cache under your gradle module directory. [project-root] / [module] / build – gradle模块目录下的.gradle缓存。
  • ~/.m2 – The Maven cache directory under your user's “Home” directory 〜/ .m2 –用户“主”目录下的Maven缓存目录

Then start over a gradle sync, the problem should be resolved. 然后重新开始gradle同步，该问题应得到解决。

You can find more detailed descriptions from below blogs: 您可以从以下博客中找到更详细的描述：

  1. gradle-sync-issue-on-debian-os-due-to-user-does-not-have-permission gradle这个-同步问题上，Debian的操作系统，由于对用户不-不具备许可权
  2. android-gradle-plugin-3-0-sync-issue Android的gradle这个-插件-3-0-同步问题
  3. gradle-proxy-configuration gradle这个代理配置

解决方案3
 0  2021-12-22 10:34:53

I am not sure what exactly caused this issue in my case, but the problem was a version of the Gradle wrapper that was too low.我不确定在我的情况下到底是什么导致了这个问题，但问题是 Gradle 包装器的版本太低了。 The version causing this issue was 4.0 , it was fixed by using 4.9 .导致这个问题的版本是4.0 ，它是通过使用4.9修复的。

You can change the version of the wrapper by first setting it in your build.gradle file:您可以通过首先在build.gradle文件中设置它来更改包装器的版本：

wrapper {
    gradleVersion '4.9'
}

To install the correct wrapper jar in your project, go to your project root directory and run要在您的项目中安装正确的包装器 jar，请转到您的项目根目录并运行

gradle wrapper

This will download the appropriate jar file into your gradle/wrapper folder and update the gradle-wrapper.properties .这会将相应的 jar 文件下载到您的gradle/wrapper文件夹中并更新gradle-wrapper.properties 。 Then you can run ./gradlew build as usual.然后你可以像往常一样运行./gradlew build 。

解决方案4
 0  2022-01-09 12:24:12

只需转到 pc c:/users/yourUsername/.gradle 中的 .gradle 文件夹并删除缓存文件夹

暂无
暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 锁定文件并删除它，而无需先释放锁定 - Lock a file and delete it without first releasing the lock 混淆获取和释放锁 - confusion in acquiring and releasing of locks 为什么不调用通知等待就释放锁 - why without calling the notify wait is releasing the lock Gradle 由于文件锁定超时，守护进程停止并行工作 - Gradle Daemon stopped working in parallel due to file lock timeouts 为Java 1.8启用jackOptions时，Gradle构建挂起 - Gradle build hanging when jackOptions is enabled for Java 1.8 FML Gradle - 失败：构建失败并出现异常 - FML Gradle - FAILURE: Build failed with an exception 释放“同步”锁 - Releasing a “synchronized” lock 一旦通过就释放锁 - Releasing a lock as soon as it is passed 构建 docker 映像 - Gradle 构建守护进程意外消失 - Building docker image - Gradle build daemon disappeared unexpectedly Build a project using gradle FAILURE: Build failed with an exception - Build a project using gradle FAILURE: Build failed with an exception
相关标签
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM