backtrace when locking failed unexpectedly

Bug #594828 reported by Sven Oostenbrink
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned

Bug Description

See shell text below:

......
Committed revision 11.
maorozco@maorozco-laptop:~/projects/name/drivers$ bzr push
bzr: ERROR: No push location known or specified.
maorozco@maorozco-laptop:~/projects/name/drivers$ bzr push bzr+ssh://maorozco@server/projects/name/drivers --remember
bzr: ERROR: Cannot lock LockDir(chroot-44693520:///projects/name/drivers/.bzr/branch/lock): Permission denied: "/projects/name/drivers/.bzr/branch/lock/p1zpcjn3ms.tmp": [Errno 13] Permission denied: '/projects/name/drivers/.bzr/branch/lock/p1zpcjn3ms.tmp'
maorozco@maorozco-laptop:~/projects/name/drivers$ bzr push bzr+ssh://maorozco@server/projects/name/drivers --remember
bzr: ERROR: bzrlib.errors.ErrorFromSmartServer: Error received from smart server: ('error', '[Errno 1] Operation not permitted')

*** Bazaar has encountered an internal error. This probably indicates a
   bug in Bazaar. You can help us fix it by filing a bug report at
       https://bugs.launchpad.net/bzr/+filebug
   attaching the crash file
       /home/maorozco/.cache/crash/bzr-20100615015021-9689.crash
   and including a description of the problem.

   The crash file is plain text and you can inspect or edit it to remove
   private information.
maorozco@maorozco-laptop:~/projects/name/drivers$

Revision history for this message
Sven Oostenbrink (so-oostenbrink) wrote :
Revision history for this message
Robert Collins (lifeless) wrote :

I think you should be find if you just delete the lock dir and create it again with appropriate permissions. You'll need to make sure that your groups are set up appropriately on the server; I think our admin docs have something about this.

There isn't actually anything wrong in the bzr code related to this as far as I can tell.

Changed in bzr:
status: New → Invalid
Revision history for this message
Sven Oostenbrink (so-oostenbrink) wrote : Re: [Bug 594828] Re: Second bzr push to remote repo crashes after first bzr push failed due to permission denied on remote repo

Well, if its a locking problem, I'd say BZR should talk about locking, not
about crashes, should it? There is a crash, so something is off.. Anyway, I
didn't trust the repo anymore so we just pushed out to a new one, which also
fixed the problem..

Cheers,

Sven

On Thu, Jun 24, 2010 at 1:07 AM, Robert Collins
<email address hidden>wrote:

> I think you should be find if you just delete the lock dir and create it
> again with appropriate permissions. You'll need to make sure that your
> groups are set up appropriately on the server; I think our admin docs
> have something about this.
>
> There isn't actually anything wrong in the bzr code related to this as
> far as I can tell.
>
> ** Changed in: bzr
> Status: New => Invalid
>
> --
> Second bzr push to remote repo crashes after first bzr push failed due to
> permission denied on remote repo
> https://bugs.launchpad.net/bugs/594828
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Invalid
>
> Bug description:
> See shell text below:
>
> ......
> Committed revision 11.
> maorozco@maorozco-laptop:~/projects/name/drivers$ bzr push
> bzr: ERROR: No push location known or specified.
> maorozco@maorozco-laptop:~/projects/name/drivers$ bzr push
> bzr+ssh://maorozco@server/projects/name/drivers --remember
> bzr: ERROR: Cannot lock
> LockDir(chroot-44693520:///projects/name/drivers/.bzr/branch/lock):
> Permission denied: "/projects/name/drivers/.bzr/branch/lock/p1zpcjn3ms.tmp":
> [Errno 13] Permission denied:
> '/projects/name/drivers/.bzr/branch/lock/p1zpcjn3ms.tmp'
> maorozco@maorozco-laptop:~/projects/name/drivers$ bzr push
> bzr+ssh://maorozco@server/projects/name/drivers --remember
> bzr: ERROR: bzrlib.errors.ErrorFromSmartServer: Error received from smart
> server: ('error', '[Errno 1] Operation not permitted')
>
> *** Bazaar has encountered an internal error. This probably indicates a
> bug in Bazaar. You can help us fix it by filing a bug report at
> https://bugs.launchpad.net/bzr/+filebug
> attaching the crash file
> /home/maorozco/.cache/crash/bzr-20100615015021-9689.crash
> and including a description of the problem.
>
> The crash file is plain text and you can inspect or edit it to remove
> private information.
> maorozco@maorozco-laptop:~/projects/name/drivers$
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/bzr/+bug/594828/+subscribe
>

Changed in bzr:
status: Invalid → Won't Fix
status: Won't Fix → Confirmed
importance: Undecided → Medium
summary: - Second bzr push to remote repo crashes after first bzr push failed due
- to permission denied on remote repo
+ backtrace when locking failed unexpectedly
Jelmer Vernooij (jelmer)
tags: added: hpss locking
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.