Re: [fossil-users] database locked on sync

[Martin S. Weber]

On 08/06/11 12:47, Kevin Quick wrote:
> $ fossil sync PATH-TO-REPO
>   Bytes  Cards  Artifacts Deltas
> Sent:3897 82  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: 2225 bytes sent, 813 bytes received
> $
>
> This happens every time.  I found the suggestion for "PRAGMA
> journal_mode=WAL;" in sqlite mode, but that had no effect.

Actually, I've found that that happens when you have/try to open the same 
.fossil multiple times?

I.e. I have a server (fossil server ...) on host server; I use clients 
typically on boxens clientX (for X in ...); The procedure always was:
- fossil clone http://user@server:port/repo ~/open/repo.fossil
- mkdir ~/open/repo
- cd ~/open/repo
- fossil open ~/open/repo.fossil
- setup fossil remote-url (again;so that fossil actually asks for the pwd).

No problem ever. Auto-sync in all directions works charms.

But when I open the original fossil on server (say, it's lying in ~/fossilien, 
so I do:
- mkdir ~/open/repo
- cd ~/open/repo
- fossil open ~/fossilien/repo.fossil ) the open works fine, but any sync / 
update / whatever afterwards either comes up with COMMIT : DB locked or
the sql you have above: DB locked.

If, on the other hand, on the server, I replicate the clientX approach (that 
is, fossil clone http://user@localhost:port/repo ~/open/repo.fossil; fossil 
open repo.fossil) everything is fine.

So I think it's an issue with having file:/// level access open to a fossil 
repository multiple times / from multiple fossil instances? I'm just fishing 
the muddy waters here, but it's pretty obvious how to force the "Database 
error: database is locked" to appear to me.

Regards,

-Martin
___
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] database locked on sync

[Lluís Batlle i Rossell]

On Mon, Aug 08, 2011 at 03:36:29PM -0400, Martin S. Weber wrote:
> On 08/06/11 12:47, Kevin Quick wrote:
> > $ fossil sync PATH-TO-REPO
> >   Bytes  Cards  Artifacts Deltas
> > Sent:3897 82  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: 2225 bytes sent, 813 bytes received
> > $
> >
> > This happens every time.  I found the suggestion for "PRAGMA
> > journal_mode=WAL;" in sqlite mode, but that had no effect.
> 
> So I think it's an issue with having file:/// level access open to a fossil 
> repository multiple times / from multiple fossil instances? I'm just fishing 
> the muddy waters here, but it's pretty obvious how to force the "Database 
> error: database is locked" to appear to me.

I have fossil repositories opened in multiple directories each, and I only hit
"database locked" troubles if I'm really running at the same time two fossil
operations on the same repository.

So, I don't understand what happens in your situation.
___
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] database locked on sync

[Stephan Beal]

2011/8/8 Lluís Batlle i Rossell 

> I have fossil repositories opened in multiple directories each, and I only
> hit
> "database locked" troubles if I'm really running at the same time two
> fossil
> operations on the same repository.
>
> So, I don't understand what happens in your situation.


He's running a server on that same repo concurrently, and the server
apparently locks the db for its whole life. The workaround is simply to use
HTTP over localhost.

-- 
- 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] database locked on sync

[Martin S. Weber]

On 08/08/11 16:16, Stephan Beal wrote:
> 2011/8/8 Lluís Batlle i Rossell  >
>
> I have fossil repositories opened in multiple directories each, and
> I only hit
> "database locked" troubles if I'm really running at the same time
> two fossil
> operations on the same repository.
>
> So, I don't understand what happens in your situation.
>
>
> He's running a server on that same repo concurrently, and the server
> apparently locks the db for its whole life. The workaround is simply to
> use HTTP over localhost.

Actually, there seems to be more at play here. I tried replicating the problem 
on a toy (empty) repo, but failed. I mean I know how to handle myself (now ;)) 
without facing problems; if I succeed in having a nice clinical test-case that 
exhibits the same problems I'll let you know.

Regards,
-Martin
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Unable to sign manifest

[tpero...@compumation.com]

fossil branch new Test 5947928ba

'gpg' is not recognized as an internal or external command, operable program or 
batch file.
unable to sign manifest. continue (Y/N)? n

fossil unset pgp-command

fossil branch new Test 5947928ba

'in-B1C64C8EF29A42586A91' is not recognized as an internal or external command,
operable program or batch file.
unable to sign manifest.  continue (y/N)? n

Why?

Thanks.
___
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] Unable to sign manifest

[Stephan Beal]

On Mon, Aug 8, 2011 at 11:43 PM, tpero...@compumation.com <
tpero...@compumation.com> wrote:

> fossil unset pgp-command
>
> ** **
>
> fossil branch new Test 5947928ba
>
> ** **
>
> 'in-B1C64C8EF29A42586A91' is not recognized as an internal or external
> command,
>

That's weird, but you can try:

fossil set clearsign 0

as a workaround for the time being.

-- 
- 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] Unable to sign manifest

[Richard Hipp]

On Mon, Aug 8, 2011 at 5:43 PM, tpero...@compumation.com <
tpero...@compumation.com> wrote:

> fossil branch new Test 5947928ba
>
> ** **
>
> 'gpg' is not recognized as an internal or external command, operable
> program or batch file.
>
> unable to sign manifest. continue (Y/N)? n
>
> ** **
>
> fossil unset pgp-command
>
> ** **
>
> fossil branch new Test 5947928ba
>
> ** **
>
> 'in-B1C64C8EF29A42586A91' is not recognized as an internal or external
> command,
>
> operable program or batch file.
>
> unable to sign manifest.  continue (y/N)? n
>
> ** **
>
> Why?
>

Probably because when you unset pgp-command it still trys to call system()
to do the pgp signing, but leaves off the name of the command since that is
now unset.

Try:  fossil set clearsign off




> 
>
> ** **
>
> Thanks.
>
> ___
> 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