Project

General

Profile

Bug #635

again the locked DB issue

Added by natlus over 15 years ago. Updated over 15 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/19/2009
Due date:
% Done:

0%

Estimated time:
Version:
0.4.0+
OS:
Linux

Description

Sorry, I don't know what's going on. The solution of #621 does not seem to clear the 'locked DB error'. And it's surprising me that apparently I am the only one who gets this error.

But again: accessing the DB throws "DB Message: database is locked". In contrast to prior bug reports, I can now say that this is not necessarily dependent on a client connection. See the attached log.
Also, this issue also seems to prevent clients to connect.

Circumstances:
- statically linked quasselcore from todays git
- QT4.5 on linux
- 3 users with more than one network each and of course several channels each
- I got just one cup of coffee right now

quasselcore.log11 (4.54 KB) quasselcore.log11 natlus, 03/19/2009 08:38 AM

History

#1 Updated by sph over 15 years ago

Might be useful to add that you are using the SQlite backend (I assume).

#2 Updated by sph over 15 years ago

Actually, for a multiuser core, you better use the PostgreSQL backend. SQLite isn't the best solution for a threading environment.

#3 Updated by EgS over 15 years ago

First of all: were you unable to reopen bug #621?

2nd: where is that statically linked Core from as the static nightly core we provide isn't up to date

#4 Updated by natlus over 15 years ago

Yes I use the SQLite backend.

EgS wrote:

First of all: were you unable to reopen bug #621?

Um, sorry I had your last line of comment in #621 different in mind. I didn't try to reopen it.

2nd: where is that statically linked Core from as the static nightly core we provide isn't up to date

I built it from a git clone of yesterdays head.

#5 Updated by EgS over 15 years ago

I guess the error is still present... ;) Very strange though...

Ok so we've got a couple of options here. Since you're compiling the core yourself we're a bit better off.
I'm going to create a special debugging branch for this issue. But this is going to take a bit as it's tedious work... :/

#6 Updated by EgS over 15 years ago

From now on please use this debug branch:

http://git.quassel-irc.org/?p=quassel.git;a=shortlog;h=refs/heads/sqlitedebug

Make sure you start the core with --loglevel=Debug option set.

Also available in: Atom PDF