Re: [fossil-users] SQLITE_BUSY ?

2015-06-17 Thread Joerg Sonnenberger
On Wed, Jun 17, 2015 at 12:10:36PM -0400, Richard Hipp wrote: > On 6/17/15, Jan Danielsson wrote: > > On 17/06/15 11:38, Joerg Sonnenberger wrote: > > [---] > >> Sadly, a plain pull is not 100% read-only, so WAL doesn't help avoiding > >> such problems. > > > >Out of curiosity; why aren't pull

Re: [fossil-users] SQLITE_BUSY ?

2015-06-17 Thread Andy Bradford
Thus said Joerg Sonnenberger on Wed, 17 Jun 2015 11:38:46 +0200: > It's possible to hit one of the hidden master -> public repo pushes, > they can take a bit as the disks are generally busy in the machine > with other conversions :) If I'm not mistaken, some changes were made to help with l

Re: [fossil-users] SQLITE_BUSY ?

2015-06-17 Thread Richard Hipp
On 6/17/15, Jan Danielsson wrote: > On 17/06/15 11:38, Joerg Sonnenberger wrote: > [---] >> Sadly, a plain pull is not 100% read-only, so WAL doesn't help avoiding >> such problems. > >Out of curiosity; why aren't pulls 100% read-only on the server? > The server might decide to create a new c

Re: [fossil-users] SQLITE_BUSY ?

2015-06-17 Thread Jan Danielsson
On 17/06/15 11:38, Joerg Sonnenberger wrote: [---] > Sadly, a plain pull is not 100% read-only, so WAL doesn't help avoiding > such problems. Out of curiosity; why aren't pulls 100% read-only on the server? -- Kind Regards, Jan ___ fossil-users mail

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Jacek Cała
Thank you Jan for clarifying the problem. BTW, perhaps that's a reason why on the download page there could also be a linux-x64 version available. Cheers, Jacek 2015-06-17 15:17 GMT+01:00 Jan Nijtmans : > 2015-06-17 15:56 GMT+02:00 Jacek Cała : > > Hi, > > > > Please find below some detail

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Jan Nijtmans
2015-06-17 15:56 GMT+02:00 Jacek Cała : > Hi, > > Please find below some details about the software running in my container: > > - fossil version -v says: > This is fossil version 1.33 [9c65b5432e] 2015-05-23 11:11:31 UTC > Compiled on Jun 10 2015 22:28:08 using gcc-4.6.3 (32-bit) > SQLite 3.8.10.2

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Jacek Cała
Hi, Please find below some details about the software running in my container: - fossil version -v says: This is fossil version 1.33 [9c65b5432e] 2015-05-23 11:11:31 UTC Compiled on Jun 10 2015 22:28:08 using gcc-4.6.3 (32-bit) SQLite 3.8.10.2 2015-05-20 18:17:19 2ef4f3a5b1 Schema version 2015-01

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Jan Nijtmans
2015-06-16 17:44 GMT+02:00 Jacek Cała : > Hi, > > I'm running fossil 1.33 in a docker container and found an issue when > cloning my repo. If I run it like: > > $ fossil clone http://USERNAME@SERVERNAME/REPONAME repo.fossil What does "fossil version -v" say? Or "file fossil"? Is the fossil binar

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Stephan Beal
On Wed, Jun 17, 2015 at 3:15 PM, bch wrote: > You're ignoring that ssh has extensive configuration options and could be > configured to use an alias. Stephan is probably trying to get a more > definitive test to help. > LOL! Yeah, what Brad said ;). Plus... i did skip over the original post's men

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread jungle Boogie
On 17 June 2015 at 06:06, Jacek Cała wrote: > As stated in the original question 'ssh SERVERNAME' works fine, which means > 'ping SERVERNAME' can also resolve the name ok. Paste your /etc/resolve.conf file Are ssh servername and clone server name the same? -- --- inum: 883510009027723 si

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread bch
You're ignoring that ssh has extensive configuration options and could be configured to use an alias. Stephan is probably trying to get a more definitive test to help. On Jun 17, 2015 6:06 AM, "Jacek Cała" wrote: > As stated in the original question 'ssh SERVERNAME' works fine, which > means 'pin

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Jacek Cała
As stated in the original question 'ssh SERVERNAME' works fine, which means 'ping SERVERNAME' can also resolve the name ok. 2015-06-17 13:44 GMT+01:00 Stephan Beal : > On Tue, Jun 16, 2015 at 5:44 PM, Jacek Cała wrote: > >> works perfectly fine. It's not urgent for me because I can work using IP

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Stephan Beal
On Tue, Jun 16, 2015 at 5:44 PM, Jacek Cała wrote: > works perfectly fine. It's not urgent for me because I can work using IP > but I'd appreciate any hints how it may be solved. > Try: ping SERVERNAME If that results in the same error then the problem is your DNS config or access to the DNS s

Re: [fossil-users] SQLITE_BUSY ?

2015-06-17 Thread Joerg Sonnenberger
On Tue, Jun 16, 2015 at 11:04:07PM -0700, Matt Welland wrote: > We see these (or similar) occasionally when the filesystem gets slow. The > problem is exacerbated with large repos. It's possible to hit one of the hidden master -> public repo pushes, they can take a bit as the disks are generally b