Yes, over 40Gb free on the server. ________________________________________ From: [email protected] [[email protected]] On Behalf Of Deng Ching [[email protected]] Sent: Saturday, October 02, 2010 12:06 AM To: [email protected] Subject: Re: HTTP code 500 when trying to access a artifact.
Hi, Did you check if there is enough disk space in your server? Thanks, Deng On Sat, Oct 2, 2010 at 1:13 AM, Michael Delaney <[email protected]> wrote: > > I'm not seeing any exceptions but I am seeing the entries in request log > that contain the 500 error codes. > > On 9/30/2010 7:19 PM, Brett Porter wrote: >> >> Do you see anything in the archiva server log that would correspond to the >> return of the 500 code? >> >> - Brett >> >> On 01/10/2010, at 1:13 AM, Michael Delaney wrote: >> >>> All, >>> >>> Our Archiva 1.1.2 server has started to act up a lot as of late. We're >>> seeing some 500 error codes when trying to deply our artifacts. We're also >>> seeing some behavior where an artifact is uploaded to Archiva (any type: >>> pom, zip, jar, war; of varying size) but build freezes during the "upload" >>> process. The newly updated file is accessible via WGET/HTTP calls but the >>> build doesn't progress. >>> >>> I assume this requires me to bump a logging value in log4j but I'm not >>> sure which ones I should bump; or just brute force it and bump all of them. >>> >>> [ Error Snippet ] >>> [INFO] Error deploying artifact: Failed to transfer file: >>> http://archiva:8080/archiva/repository/snapshot/groupId/myProject/1.0.0-SNAPSHOT/myProject-1.0.0-20100930.010002-48-config.jar. >>> Return code is: 500 >>> >>> >> -- >> Brett Porter >> [email protected] >> http://brettporter.wordpress.com/ >> >> >> >> >> >
