archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qian, Yi" <>
Subject Re: archiva not response
Date Thu, 11 Aug 2011 14:51:16 GMT
Hello, Wendy

Set security.policy.unlockable.accounts=guest in file
did not solve the problem, how do I set up logging level to debug, so more
trace can be logged?


On 8/9/11 8:24 AM, "Wendy Smoak" <> wrote:

>On Mon, Aug 8, 2011 at 3:22 PM, Qian, Yi <> wrote:
>> We are using archiva as our local maven repository for over a year,
>>today we having problem of accessing our local archiva repository.
>>Browser window returns unable connected message. archiva status command
>>returns Apache Archiva is running (31951). But archiva stop command does
>>not stop the server, I have to use kill the procedure and start it,  The
>>archiva.log has following messages -
>> WARN  org.apache.maven.archiva.web.action.DeleteArtifactAction  - User
>>guest(Guest) is locked.
>> User
>>guest(Guest) is locked.
>> But no one uses guest account.  I looked at all the logs, could not
>>find any clue about the problem. Our archiva runs as standalone on RHL
>>enterprise 5.4 server.
>Try making the guest account un-lockable in and
>see if that helps...
>can be specified multiple times to ensure that password policies never
>lock the specified account(s) (eg.
>security.policy.unlockable.accounts=guest )

View raw message