Problem with bk repository?
Hello
In the last few days and weeks, i'm seeing in increasing number of errors like this:
david@devil:/repository/linuxppc_2_4_devel>bk parent Parent repository is bk://ppc.bkbits.net/linuxppc_2_4_devel david@devil:/repository/linuxppc_2_4_devel>bk pull -ll ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
Is this something to worry about or just some kind of "bandwidth limitation"?
Dave
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 14 lines
david@devil:/repository/linuxppc_2_4_devel>bk parent Parent repository is bk://ppc.bkbits.net/linuxppc_2_4_devel david@devil:/repository/linuxppc_2_4_devel>bk pull -ll ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
I was it for the first time today too.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 14 lines · On Tue, Aug 06, 2002 at 08:46:50AM -0700, [email protected] wrote:
Quoted 13 lines
david@devil:/repository/linuxppc_2_4_devel>bk parent Parent repository is bk://ppc.bkbits.net/linuxppc_2_4_devel david@devil:/repository/linuxppc_2_4_devel>bk pull -ll ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
Quoted 1 line
I was it for the first time today too.
Are either of you still getting this? What seems to be happening is that when David Gibson pushes something to the tree, it never quite finishes and Bk ends up in a slightly wierd state. David, are you behind some sort of wierd network setup or anything?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 15 lines · Tom Rini
Quoted 14 lines · On Tue, Aug 06, 2002 at 08:46:50AM -0700, [email protected] wrote:
Quoted 13 lines
david@devil:/repository/linuxppc_2_4_devel>bk parent Parent repository is bk://ppc.bkbits.net/linuxppc_2_4_devel david@devil:/repository/linuxppc_2_4_devel>bk pull -ll ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
Quoted 6 lines
Quoted 1 line
I was it for the first time today too.
Are either of you still getting this? What seems to be happening is that when David Gibson pushes something to the tree, it never quite finishes and Bk ends up in a slightly wierd state. David, are you behind some sort of wierd network setup or anything?
Ah, crap. I did run into this the other day - I did a push which got interrupted (connection closed by foreign host - probably due to SOCKS). After that my pulls (and attempts to push again) complained that there was a lock. But paulus had a look at the parent repository where 'll' denied that there was any lock - at least it did the second time it was invoked. My pulls were still failing and I was going to send out a mail, but the next day it seemed to be working again, so I figured it was a once off breakage.
I guess I was wrong.
I'm not sure if my last push was interrupted, or whether there was some residual breakage from the earlier push in the repository which got triggered again by the later push.
Pulls are working again for me now, so I'm not sure what to do next to investigate this.
--
David Gibson | For every complex problem there is a
[email protected] | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
[root@bitmover cort-20010106071759-19793-5c81b698cda31832]# bk takepatch -avvLf PENDING/2002-08-05.01
Applying 1 revisions to ChangeSet Applying 2 revisions to new file drivers/mtd/maps/beech-mtd.c Applying 1 revisions to drivers/mtd/maps/Config.in Applying 1 revisions to drivers/mtd/maps/Makefile
takepatch: 5 new revisions, 3 conflicts in 4 files
bk: takepatch.c:268: getConfig: Assertion `exists(".." "/BitKeeper/etc/SCCS/s.config")' failed. Aborted
Looks like we have a busted tree, I'll see what I can do. --
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
There was a corrupted PPC logging tree and I have fixed that. I apologize for any problems, we are working on trying to make this stuff work better.
Quoted 19 lines · David M?ller (ELSOFT AG)
Hello
In the last few days and weeks, i'm seeing in increasing number of errors like this:
david@devil:/repository/linuxppc_2_4_devel>bk parent Parent repository is bk://ppc.bkbits.net/linuxppc_2_4_devel david@devil:/repository/linuxppc_2_4_devel>bk pull -ll ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
ERROR-Can't get read lock on the repository.
pull: remote locked, trying again...
Quoted 7 lines
Is this something to worry about or just some kind of "bandwidth limitation"?
Dave
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/