error about failure to take lock printed to smart server protocol socket
Bug #484315 reported by
Alexandre Garnier
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
High
|
Unassigned | ||
Bug Description
When there is a lock, I get this message :
bzr: ERROR: Received bad protocol version marker: "Unable to obtain lock chroot-
Not really readable with \n ...
I have this on concurrent commit on a shared repository accessed with bzr:// by a lightweight checkout.
Revision history for this message
| Andrew Bennetts (spiv) wrote | #1 |
| tags: | added: hpss |
| Changed in bzr: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
Revision history for this message
| Alexandre Garnier (zigarn) wrote | #2 |
| summary: |
- Formatting problem of lock message + error about failure to take lock printed to smart server protocol socket |
| tags: | added: check-for-breezy |
| tags: | removed: check-for-breezy |
To post a comment you must log in.
Huh, that's weird. At a guess, the bzr:// server is launched via inetd (and thus run with the --inet option)? If so, then I suspect that the server is erroneously emitting that text to stderr, which is then being relayed over the TCP socket, and screwing up the proper communication of errors between client and server.
This may be a dupe of an existing bug report, this does sound familiar.