Re: [fossil-users] intermittent "db is locked" messages...
On Fri, Oct 28, 2011 at 8:10 PM, Richard Hipp wrote:
> The statement appears to be purely defensive, so I'm guessing we could take
> it out . But it would also be good to understand what is going on.
>
> When you do the auto-sync, are you doing it from an account that is
> read-only ("anonymous")? Maybe we are opening the database in read-only
> mode for a pull and hence this attempt to clean up a table in the database
> is failing - just a guess.
>
Every time i've seen it has been with a r/w account, and i _think_ i've only
seen it on the main repo. i've always attributed it to other activity going
on concurrently in the main repo, but now that i see it's a local error i
have no idea what might cause it, especially since fossil doesn't use any
threads or forked processes in a sync operation (from what i understand
fork() is only used in server mode).
It's nothing tragic, just something that pops up every couple of weeks or
so.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] intermittent "db is locked" messages...
On Fri, Oct 28, 2011 at 7:26 AM, Stephan Beal wrote:
> Hi, all,
>
> Occasionally (maybe once every two weeks or so) i'm seeing the following
> when pulling/pushing the main fossil repo:
>
> [stephan@cheyenne:~/cvs/fossil/fossil-json]$ f up
> Autosync: http://step...@fossil-scm.org
> ...
> Sent:1634 33 0 0
> Error: Database error: database is locked
> DELETE FROM unclustered WHERE rid IN (SELECT rid FROM private)
>
> Has anyone out there got an explanation (or theory!) for what might be
> causing this?
>
>
The offending SQL seems to be from here:
http://www.fossil-scm.org/fossil/artifact/4631dc5d0c0?ln=642-646
The statement appears to be purely defensive, so I'm guessing we could take
it out . But it would also be good to understand what is going on.
When you do the auto-sync, are you doing it from an account that is
read-only ("anonymous")? Maybe we are opening the database in read-only
mode for a pull and hence this attempt to clean up a table in the database
is failing - just a guess.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil Repository Does Not Exist Error
On Fri, Oct 28, 2011 at 6:21 PM, Stephan Beal wrote: > LOL: no matter what order the COMMAND lines are in, help still shows > test-move-repository: > Doh, of course it does because it's hard-coded: ** COMMAND: switch ** COMMAND: test-move-repository ** ** Usage: %fossil test-move-repository PATHNAME ** -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil Repository Does Not Exist Error
On Fri, Oct 28, 2011 at 6:05 PM, Brian Smith wrote: > There's a "test-move-repository" command that does just this. > Perhaps it should be promoted to a proper command. > All you have to do to enable that is add this line: ---> ** COMMAND: switch ** COMMAND: test-move-repository LOL: no matter what order the COMMAND lines are in, help still shows test-move-repository: [stephan@cheyenne:~/cvs/fossil/fossil]$ ./fossil help switch Usage: ./fossil test-move-repository PATHNAME Change the location of the repository database on a local check-out. Use this command to avoid having to close and reopen a checkout when relocating the repository database. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil Repository Does Not Exist Error
There's a "test-move-repository" command that does just this. Perhaps it should be promoted to a proper command. On Oct 28, 2011 8:49 AM, "Konstantin Khomoutov" < flatw...@users.sourceforge.net> wrote: > On Fri, 28 Oct 2011 07:00:41 -0700 > Matt Welland wrote: > > > I usually open the _FOSSIL_ file with sqlite3 and update the pointer > > to the repo db. A "repodb reset" command or some such would be nice > > to have. > fossil switch NEW_LOCATION > > That would make Subversion users feel at home. > Though I personally like the name "retarget" or "rebind". > "reset" sounds a bit too scary. > > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil Repository Does Not Exist Error
On Fri, 28 Oct 2011 07:00:41 -0700 Matt Welland wrote: > I usually open the _FOSSIL_ file with sqlite3 and update the pointer > to the repo db. A "repodb reset" command or some such would be nice > to have. fossil switch NEW_LOCATION That would make Subversion users feel at home. Though I personally like the name "retarget" or "rebind". "reset" sounds a bit too scary. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil Repository Does Not Exist Error
On Fri, Oct 28, 2011 at 07:00:41AM -0700, Matt Welland wrote: > I usually open the _FOSSIL_ file with sqlite3 and update the pointer to the > repo db. A "repodb reset" command or some such would be nice to have. > > matt@hermes> sqlite3 > _FOSSIL_ > ~/data/opensrc > SQLite version 3.7.5 > Enter ".help" for instructions > Enter SQL statements terminated with a ";" > sqlite> update vvar set value='/home/matt/fossils/mattsmisc.fossil' where > name='repository'; Ah, that would be nice for a command, yes. I've found myself painfully closing and opening checkouts, while I'd better have used this. > On Fri, Oct 28, 2011 at 5:36 AM, Konstantin Khomoutov < > flatw...@users.sourceforge.net> wrote: > > > On Fri, 28 Oct 2011 13:56:21 +0200 > > Stephan Beal wrote: > > > > > > > Or if you DO have uncommitted changes you can also try: > > > > > > > > > > rm _FOSSIL_ > > > > > > > > Dangerous if you have stashed changes ;-) > > > > > > > > > Aha - THAT explains why i lost my stash the last time i did > > > that ... ;) > > > > For the record (more for the original poster to read), these things > > are documented in [1]. > > > > 1. http://www.sqlite.org/debug1/doc/trunk/www/tech_overview.wiki > > ___ > > fossil-users mailing list > > fossil-users@lists.fossil-scm.org > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil Repository Does Not Exist Error
I usually open the _FOSSIL_ file with sqlite3 and update the pointer to the repo db. A "repodb reset" command or some such would be nice to have. matt@hermes> sqlite3 _FOSSIL_ ~/data/opensrc SQLite version 3.7.5 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> update vvar set value='/home/matt/fossils/mattsmisc.fossil' where name='repository'; On Fri, Oct 28, 2011 at 5:36 AM, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote: > On Fri, 28 Oct 2011 13:56:21 +0200 > Stephan Beal wrote: > > > > > Or if you DO have uncommitted changes you can also try: > > > > > > > > rm _FOSSIL_ > > > > > > Dangerous if you have stashed changes ;-) > > > > > > Aha - THAT explains why i lost my stash the last time i did > > that ... ;) > > For the record (more for the original poster to read), these things > are documented in [1]. > > 1. http://www.sqlite.org/debug1/doc/trunk/www/tech_overview.wiki > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil Repository Does Not Exist Error
On Fri, 28 Oct 2011 13:56:21 +0200 Stephan Beal wrote: > > > Or if you DO have uncommitted changes you can also try: > > > > > > rm _FOSSIL_ > > > > Dangerous if you have stashed changes ;-) > > > Aha - THAT explains why i lost my stash the last time i did > that ... ;) For the record (more for the original poster to read), these things are documented in [1]. 1. http://www.sqlite.org/debug1/doc/trunk/www/tech_overview.wiki ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil Repository Does Not Exist Error
On Fri, Oct 28, 2011 at 1:33 PM, Dmitry Chestnykh wrote: > On Fri, 28 Oct 2011 13:31:47 +0200 Stephan Beal > wrote: > > > Or if you DO have uncommitted changes you can also try: > > > > rm _FOSSIL_ > > Dangerous if you have stashed changes ;-) Aha - THAT explains why i lost my stash the last time i did that ... ;) -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil Repository Does Not Exist Error
On Fri, 28 Oct 2011 13:31:47 +0200 Stephan Beal wrote: > Or if you DO have uncommitted changes you can also try: > > rm _FOSSIL_ Dangerous if you have stashed changes ;-) -- Dmitry Chestnykh http://www.codingrobots.com ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil Repository Does Not Exist Error
On Fri, Oct 28, 2011 at 1:14 PM, Dmitry Chestnykh wrote: > Make sure you don't have uncommited changes. > > fossil close > fossil open new/path/to/your/repository > Or if you DO have uncommitted changes you can also try: rm _FOSSIL_ fossil open /new/path/... --keep --keep tells the open command not to overwrite any same-named files which exist in both the local filesystem and the repo. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] intermittent "db is locked" messages...
Hi, all, Occasionally (maybe once every two weeks or so) i'm seeing the following when pulling/pushing the main fossil repo: [stephan@cheyenne:~/cvs/fossil/fossil-json]$ f up Autosync: http://step...@fossil-scm.org ... Sent:1634 33 0 0 Error: Database error: database is locked DELETE FROM unclustered WHERE rid IN (SELECT rid FROM private) Received: 118 1 0 0 Total network traffic: 1523 bytes sent, 2059 bytes received f: Autosync failed -- updated-to: 11373d5bb8f40c23433677ffa8a2df38b43a74e1 2011-10-22 16:36:13 UTC tags: json-multitag-test, json comment: Removed an old warning comment. Removed an incorrect perms check in /json/user/save. Added a TODO. (user: stephan) Every time i have seen this, the following has applied: a) i have no other running instances of fossil which would be locking my local repo db. b) running update again works as expected, without the locking error. it is not 100% clear to me whether the locking error is coming from my local db (the DELETE suggests it is local) or the remote (in which case i could understand an occasional locking error). As far as i'm concerned this is strictly a "cosmetic problem," but i say that because (A) it only happens very rarely and (B) i don't have any automation which would be broken by this. Has anyone out there got an explanation (or theory!) for what might be causing this? -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil Repository Does Not Exist Error
On Fri, 28 Oct 2011 18:49:56 +0800 "David Baxendale (GMail - Singapore)" wrote: > I have recently moved all my files to a new machine and the directory > structure is slightly different under Windows 7. Now when I execute a > fossil status command, fossil reports the repository does not exist > or is in an unreadable directory, followed by the old directory name. > > How do I fix this? Make sure you don't have uncommited changes. fossil close fossil open new/path/to/your/repository -- Dmitry Chestnykh http://www.codingrobots.com ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Fossil Repository Does Not Exist Error
I have recently moved all my files to a new machine and the directory structure is slightly different under Windows 7. Now when I execute a fossil status command, fossil reports the repository does not exist or is in an unreadable directory, followed by the old directory name. How do I fix this? -- Regards, David Baxendale Email: david.baxend...@gmail.com ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Bug showing commit in the ui, on permissions
Hello, I'm using delta manifests, with fossil 1.20. And when by chance fossil created a new base manifest in a checkin, that checkin ui info page shows a big list about the execute permissions, either cleared or set. I've not touched any permissions in that checkin; I think there is some error in getting the differences between checkins about permissions, related to delta/base manifests. Anyone wanting to take a look? I don't know that code at all. Regards, Lluís. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
