On 06/18/2014 05:17 PM, JohnG wrote:
gelmjw@voyager /var/www/sqlite3/finviz $ sqlite3 -version
3.7.9 2011-11-01 00:52:41 c7c6050ef060877ebe77b41d959e9df13f8c9b5e
gelmjw@voyager /var/www/sqlite3/finviz $
gelmjw@voyager /var/www/sqlite3/finviz $ uname -a
Linux voyager 3.2.0-23-generic #36-Ubuntu S
On Wed, Jun 18, 2014 at 6:17 PM, JohnG <4par...@gmail.com> wrote:
> gelmjw@voyager /var/www/sqlite3/finviz $ cd /var/www/sqlite3/finviz/;
> sqlite3 -init finviz.init finviz.db
> ~SNIP~
> How do I clear this lock condition?
>
>
Maybe try it like this instead:
gelmjw@voyager /var/www/sqlite3/finvi
gelmjw@voyager /var/www/sqlite3/finviz $ sqlite3 -version
3.7.9 2011-11-01 00:52:41 c7c6050ef060877ebe77b41d959e9df13f8c9b5e
gelmjw@voyager /var/www/sqlite3/finviz $
gelmjw@voyager /var/www/sqlite3/finviz $ uname -a
Linux voyager 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC
2012 x86_6
On 22 Apr 2012, at 1:55pm, 田晶 wrote:
> Is there any temp solutions for this case? As we need some time to change our
> plan on this,thanks!
Don't do multi-user, multi-process, or multi-thread access for a file accessed
using NFS.
It is not possible for the SQLite team to fix this: the thing
On Sun, 22 Apr 2012 02:36:24 +, ?? wrote:
> I using the -o nolock option when I mount nfs storage,
> and it works, but I am not sure what will cause by this option in future...
In that case database corruption will occur if you happen to update
(insert, update, delete rows) the database from
On 21 Apr 2012, at 7:05pm, Kit wrote:
> 2012/4/21 田晶 :
>> Hi all,
>> I have a question when using sqlite on redhat6, I put the sqlite file on nfs
>> storage(this storage is shared by isilion), the client using redhat 6 x64.
>> Tianjing
>
> Never use SQLite on NFS storage.
Slightly longer answ
2012/4/21 田晶 :
> Hi all,
> I have a question when using sqlite on redhat6, I put the sqlite file on nfs
> storage(this storage is shared by isilion), the client using redhat 6 x64.
> Tianjing
Never use SQLite on NFS storage.
--
Kit
___
sqlite-users mai
Hi all,
I have a question when using sqlite on redhat6, I put the sqlite file on nfs
storage(this storage is shared by isilion), the client using redhat 6 x64.
When I search the database, I got the following error:
[root@3-1 yubiao]# sqlite3 .UPLOAD.db
SQLite version 3.6.20
Enter ".help" for in
> Thanks for clarification. I assumed the error message of error code
> > SQLITE_BUSY is something like "databased is busy".
>
> http://www.sqlite.org/c3ref/c_abort.html
> Also in sqlite3.h file - comments on the right are almost exactly
> reflect the corresponding error message.
>
You are totall
e even through they are not
>> > shared?
>> > I tend to use short-lived database connections locally defined within
>> each
>> > function. Though it is not shared, it seems there may be cases where more
>> > than 1 database connections are held (in nested f
n calls). Will
> this
> > cause any issue?
> >
> > On Wed, Mar 17, 2010 at 11:05 AM, Pavel Ivanov
> wrote:
> >
> >> http://www.sqlite.org/faq.html#q5
> >> http://www.sqlite.org/lockingv3.html
> >>
> >> Pavel
> >>
> >&
11:05 AM, Pavel Ivanov wrote:
>
>> http://www.sqlite.org/faq.html#q5
>> http://www.sqlite.org/lockingv3.html
>>
>> Pavel
>>
>> On Wed, Mar 17, 2010 at 11:46 AM, imin imup wrote:
>> > Hello users,
>> >
>> > I'm using sqlite 3.6.
11:46 AM, imin imup wrote:
> > Hello users,
> >
> > I'm using sqlite 3.6.12 in muti-threaded application. I'm getting sqlite
> > errors occasionally.
> > The error message is
> >
> > *sqlite error: database is locked*
> >
> > could someone explai
http://www.sqlite.org/faq.html#q5
http://www.sqlite.org/lockingv3.html
Pavel
On Wed, Mar 17, 2010 at 11:46 AM, imin imup wrote:
> Hello users,
>
> I'm using sqlite 3.6.12 in muti-threaded application. I'm getting sqlite
> errors occasionally.
> The error message is
&g
Hello users,
I'm using sqlite 3.6.12 in muti-threaded application. I'm getting sqlite
errors occasionally.
The error message is
*sqlite error: database is locked*
could someone explain to me what happened and what to be done? or point me
to a document on how to fix this?
al Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 21, 2006 6:43 PM
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] SQLite error: Database is locked
Hi Denis,
Thanks to your reply.
Iam using the Linux 2.6.9.34 EL and sqlite version 3.3.6.
your solution is good ,
NFS. The same test works fine in /tmp, which is apparently local. I'll
report the problem to the host. Thanks for the help.
On 9/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
"Jay Johnston" <[EMAIL PROTECTED]> wrote:
> Yes, the directory is writable. No, there is no journal file -- th
"Jay Johnston" <[EMAIL PROTECTED]> wrote:
> Yes, the directory is writable. No, there is no journal file -- this
> happens even when creating a new database.
>
>
> [barranca]$ whoami
> jpj
> [barranca]$ ls -dl ./
> drwxr-x--x 38 jpj pg547368 4096 2006-09-15 09:25 ./
> [barranca]$ ec
Yes, the directory is writable. No, there is no journal file -- this
happens even when creating a new database.
[barranca]$ whoami
jpj
[barranca]$ ls -dl ./
drwxr-x--x 38 jpj pg547368 4096 2006-09-15 09:25 ./
[barranca]$ echo "create table foo(x varchar(12));" | ~/src/sqlite3-
3.3.
"Jay Johnston" <[EMAIL PROTECTED]> wrote:
> Yes, I can open the file created on the server on my laptop. No, I haven't
> changed anything on the server that would have caused this. Even when I run
> the static binary from sqlite.org I receive the same error, so it doesn't
> seem to be a library i
Yes, I can open the file created on the server on my laptop. No, I haven't
changed anything on the server that would have caused this. Even when I run
the static binary from sqlite.org I receive the same error, so it doesn't
seem to be a library issue.
On 9/15/06, Jay Sprenkle <[EMAIL PROTECTED
On 9/15/06, Jay Johnston <[EMAIL PROTECTED]> wrote:
No trac.db in the results of lsof. Also, no processes owned by me in
/proc/locks.
can you open the file created on the server on your laptop?
if you're dynamically linking it may be loading the wrong shared libs.
Have you installed anything o
No trac.db in the results of lsof. Also, no processes owned by me in
/proc/locks.
On 9/15/06, Jay Sprenkle <[EMAIL PROTECTED]> wrote:
On 9/14/06, Jay Johnston <[EMAIL PROTECTED]> wrote:
> I'm having a strange problem since earlier today where all sqlite tables
on
> my shared webserver seem to
On 9/14/06, Jay Johnston <[EMAIL PROTECTED]> wrote:
I'm having a strange problem since earlier today where all sqlite tables on
my shared webserver seem to be locked. I have a trac installation using
sqlite that started giving me "database is locked" errors earlier today and
continues to do so.
I'm having a strange problem since earlier today where all sqlite tables on
my shared webserver seem to be locked. I have a trac installation using
sqlite that started giving me "database is locked" errors earlier today and
continues to do so. This is not an intermittent problem -- since it bega
25 matches
Mail list logo
