Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Condor-users] Quill errors again
- Date: Wed, 26 Jul 2006 14:58:34 +0100
- From: "Dr Ian C. Smith" <i.c.smith@xxxxxxxxxxxxxxx>
- Subject: [Condor-users] Quill errors again
Hi,
I'm getting exactly the same errors with Quill as
reported in:
https://lists.cs.wisc.edu/archive/condor-users/2005-December/msg00005.shtml
Namely, that the condor_q with quill stops reporting
after a while. It also starts to print out records like:
--- ???? ---
--- ???? ---
--- ???? ---
before this. Looking at the postgresql log there are
whole load of errors of the form:
ERROR: duplicate key violates unique constraint "procads_str_pkey"
ERROR: duplicate key violates unique constraint "procads_num_pkey"
I've noticed that there are several instances of condor_quill running
so is it the case that these are trying to write to the DB at the same
time causing a contention problem ?
The condor_config file contains a comment that seem to pertain to this:
# The Postgreql server requires usernames that can manipulate tables. This
will
# be the username associated with this instance of the quill daemon
mirroring
# a schedd's job queue. Each quill daemon must have a unique username
# associated with it otherwise multiple quill daemons will corrupt the data
# held under an indentical user name.
QUILL_DB_NAME = quill_db
although I can't quite see what it means. Should each condor_quill write to
a separate postgresql DB or use a separate username ? If only a single
quill daemon runs would this solve the problem (how is this configured ?).
Presumably this would just move the bottleneck to the RDMS though ?
Any thoughts,
-ian.
-----------------------------------
Dr Ian C. Smith,
e-Science team,
University of Liverpool
Computing Services Department