I think I have a similar problem here in my company. We use Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) and Artifactory 2.3.4.1 (rev. 13021).
I've configured the release and snapshot repositories in the distributionManagement of the pom. In the maven settings I've added the username and password for artifactory. I trigger a maven deploy and maven is deploying artifacts. But for some artifacts I reproducably get the following maven error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy (default-deploy) on project cmzwo-serviceorchestration.core: Failed to retrieve remote metadata de.zdf.cmzwo:cmzwo-serviceorchestration.core:1.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata de.zdf.cmzwo:cmzwo-serviceorchestration.core:1.0-SNAPSHOT/maven-metadata.xml from/to cmzwoelf-internal-snapshots (http://ffmzdfcmzwo02.sdm.de:8081/artifactory/cmzwoelf-internal-snapshots): Access denied to: http://ffmzdfcmzwo02.sdm.de:8081/artifactory/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.core/1.0-SNAPSHOT/maven-metadata.xml -> [Help 1] Notice that this is on project where maven could deploy douzens of artifacts before in this run. So I cannot understand why maven is getting an "access denied" in the middle of the deployment operations. I should mention that I ran Artifactory 2.0.8 before and got the same error on the same artifacts. So I decided to setup a completely new out-of-the-box Artifactory. So I'm running the latest version, as mentioned above. I find a lot of PUT requests in the request.log: 20110907162853|1|REQUEST|80.90.108.99|exbldeploy|GET|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/1.0-SNAPSHOT/maven-metadata.xml.sha1|HTTP/1.1|200|40 20110907162853|215|REQUEST|80.90.108.99|exbldeploy|PUT|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/1.0-SNAPSHOT/cmzwo-serviceorchestration.parent-1.0-20110907.142853-2.pom|HTTP/1.1|201|17183 20110907162853|11|REQUEST|80.90.108.99|exbldeploy|PUT|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/1.0-SNAPSHOT/cmzwo-serviceorchestration.parent-1.0-20110907.142853-2.pom.sha1|HTTP/1.1|200|40 20110907162853|29|REQUEST|80.90.108.99|exbldeploy|PUT|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/1.0-SNAPSHOT/cmzwo-serviceorchestration.parent-1.0-20110907.142853-2.pom.md5|HTTP/1.1|200|32 20110907162853|3|REQUEST|80.90.108.99|exbldeploy|GET|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/maven-metadata.xml|HTTP/1.1|200|371 20110907162853|1|REQUEST|80.90.108.99|exbldeploy|GET|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/maven-metadata.xml.sha1|HTTP/1.1|200|40 20110907162853|2|REQUEST|80.90.108.99|exbldeploy|PUT|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/1.0-SNAPSHOT/maven-metadata.xml|HTTP/1.1|202|618 20110907162853|1|REQUEST|80.90.108.99|exbldeploy|PUT|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/1.0-SNAPSHOT/maven-metadata.xml.sha1|HTTP/1.1|200|40 20110907162853|2|REQUEST|80.90.108.99|exbldeploy|PUT|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/1.0-SNAPSHOT/maven-metadata.xml.md5|HTTP/1.1|200|32 20110907162853|21|REQUEST|80.90.108.99|exbldeploy|PUT|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/maven-metadata.xml|HTTP/1.1|201|337 20110907162853|2|REQUEST|80.90.108.99|exbldeploy|PUT|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/maven-metadata.xml.sha1|HTTP/1.1|200|40 20110907162854|2|REQUEST|80.90.108.99|exbldeploy|PUT|/cmzwoelf-internal-snapshots/de/zdf/cmzwo/cmzwo-serviceorchestration.parent/maven-metadata.xml.md5|HTTP/1.1|200|32 20110907162855|1205|REQUEST|80.90.108.99|exbldeploy|GET|/repo/org/apache/cxf/cxf-codegen-plugin/2.4.1/cxf-codegen-plugin-2.4.1.pom|HTTP/1.1|200|5372 The artifact that maven cannot deploy is not specific in any way that I can think of. It has not a large size, no special name, it's included as module in a parent pom like all other artifacts that were successfully deployed before. Maybe anyone has an idea of what is wrong here. Yoav Landman wrote: > > The request.log file should be under $ARTIFACTORY_HOME/logs. You may also > see an error in the artifactory.log when this happens or a "denied" > indication in the access.log file. You would need to wait for the new logs > entries to be outputted. > > If you ran out of space, I would also suggest rebuilding the > index<http://wiki.jfrog.org/confluence/display/RTF/Dealing+with+Broken+Index> > to > make sure the errors are not a manifestation of a broken index. > > > On Thu, Aug 25, 2011 at 7:52 PM, pradeep <[email protected]> > wrote: > >> We had an issue with disk space sometime ago and the logs were not >> generated. >> Tomcat's stdout log had contents similar to Artifactory.log, but not >> anything that looks like request log. Is there any other way to look for >> the >> information you are looking for? Or do we have to wait until the error >> comes >> back again. >> >> -- >> View this message in context: >> http://forums.jfrog.org/Maven-fails-to-deploy-occationally-Could-not-transfer-metadata-Access-denied-to-error-tp6713183p6725208.html >> Sent from the Artifactory - Users mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> EMC VNX: the world's simplest storage, starting under $10K >> The only unified storage solution that offers unified management >> Up to 160% more powerful than alternatives and 25% more efficient. >> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev >> _______________________________________________ >> Artifactory-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/artifactory-users >> > > ------------------------------------------------------------------------------ > EMC VNX: the world's simplest storage, starting under $10K > The only unified storage solution that offers unified management > Up to 160% more powerful than alternatives and 25% more efficient. > Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev > _______________________________________________ > Artifactory-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/artifactory-users > -- View this message in context: http://forums.jfrog.org/Maven-fails-to-deploy-occationally-Could-not-transfer-metadata-Access-denied-to-error-tp6713183p6768208.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
