On 5/3/16, Steve Schow <st...@bstage.com> wrote: > I am wondering what I have done wrong in my setup to get this error shown > below. This is the first repo I created on a “server” box. Its running in > server mode. I cloned it on other machines, but I did not clone it on this > server machine. Occasionally I get on the server box command line and add > some files directly to this server repo. when I do, the commit seems to > attempt to do sync stuff with itself and generates these errors: > > me@myhost:[/home/me/fossil]: fossil commit -m “this is how you do it" > Autosync: http://me@myhost:8090/myrepo/ > Round-trips: 1 Artifacts sent: 0 received: 0 > Pull done, sent: 343 received: 2565 ip: 192.168.1.80 > New_Version: f1867a08ba9d7117498e123d51e6c4dff5ce1755 > Autosync: http://me@myhost:8090/myrepo/ > Round-trips: 1 Artifacts sent: 1 received: 0 > Error: Database error: SQL error: database is locked
Perhaps on the server, run "fossil all rebuild --wal" to put all your repositories in WAL mode for better concurrency. (This is a guess.) > Round-trips: 1 Artifacts sent: 1 received: 0 > Sync done, sent: 2876 received: 277 ip: 192.168.1.80 > Autosync failed. > > Do I have something configured wrong or is it an error to try to run fossil > commands directly against a repo that is currently running in server mode? > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- 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
