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 jan.m.daniels...@gmail.com 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

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

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 sgb...@googlemail.com: On Tue, Jun 16, 2015 at 5:44 PM, Jacek Cała jacek.c...@gmail.com wrote: works perfectly fine. It's not

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 jacek.c...@gmail.com 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

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 jacek.c...@gmail.com wrote: As stated in the original question 'ssh SERVERNAME' works fine,

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

2015-06-17 Thread jungle Boogie
On 17 June 2015 at 06:06, Jacek Cała jacek.c...@gmail.com 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:

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

2015-06-17 Thread Stephan Beal
On Wed, Jun 17, 2015 at 3:15 PM, bch brad.har...@gmail.com 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

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 jacek.c...@gmail.com: 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)

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

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 jan.nijtm...@gmail.com: 2015-06-17 15:56 GMT+02:00 Jacek Cała jacek.c...@gmail.com:

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