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://[email protected] ... 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 [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
