openerp-india team mailing list archive
-
openerp-india team
-
Mailing list archive
-
Message #09023
[Bug 949907] Re: could not obtain lock on row in relation "res_users"
Thinking back, this happened around the time a number of other issues
were happening. Is it possible that the db was in an inconsistent
state? I start out with a fresh db now when unsure.
What's the tool to "verify' (openerp-wise) the structure and contents of
a db ?
Again, if it crops up again, I'll try to decorticate the problem a bit
more.
--
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/949907
Title:
could not obtain lock on row in relation "res_users"
Status in OpenERP Server:
Incomplete
Bug description:
I received a number of these with the
2012-03-08 13:00:58,104 18563 ERROR ? openerp.sql_db: bad query: SELECT id from res_users
WHERE login='admin' AND password='admin'
AND active FOR UPDATE NOWAIT
Traceback (most recent call last):
File "/home/richard/src/openerp/server/6.1/openerp/sql_db.py", line 212, in execute
res = self._obj.execute(query, params)
OperationalError: could not obtain lock on row in relation "res_users"
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/949907/+subscriptions
References