[Mailman-Users] qrunner locks timestamped in the future?

[Jo Brooks]

First, the particulars: Solaris 7, Python 2.1, mailman 2.0.6

I have recently encountered a very strange problem.  It started today.

First symptom, was that this one list wasn't sending out messages.
Second symptom, I was no longer able to access the admin webpages.
Sometimes I could log in and check the configs, most of the time I
could not.  The pages would hang.

So I thought it was a permission problem, but check_perms said all
was well.

As far as I can tell, this started sometime this morning, based on
all the messages in the qfiles directory for this list.

After I went on to check the qrunner and the locks, I discovered
something strange.  The timestamps in the lock directory are dated 
ahead of current time.

root at lists:/home/mailman/locks #> date
Wed Aug 29 14:44:01 MST 2001

root at lists:/home/mailman/locks #> ls -l
total 20
-rw-rw-r--   2 mailman  mailman       44 Aug 30  2001 qrunner.lock
-rw-rw-r--   2 mailman  mailman       44 Aug 30  2001
qrunner.lock.lists.19707
-rw-rw-r--   2 mailman  mailman       48 Aug 29  2001 nnnnn_staff.lock
-rw-rw-r--   2 mailman  mailman       48 Aug 29  2001
nnnnn_staff.lock.lists.19707
-rw-rw-r--   1 nobody   mailman       48 Aug 29  2001
nnnnn_staff.lock.lists.19757
-rw-rw-r--   1 nobody   mailman       48 Aug 29  2001
nnnnn_staff.lock.lists.19771
-rw-rw-r--   1 nobody   mailman       48 Aug 29  2001
nnnnn_staff.lock.lists.19785
-rw-rw-r--   1 nobody   mailman       48 Aug 29  2001
nnnnn_staff.lock.lists.19798
-rw-rw-r--   1 nobody   mailman       48 Aug 29  2001
nnnnn_staff.lock.lists.19801
-rw-rw-r--   1 nobody   mailman       48 Aug 29  2001
nnnnn_staff.lock.lists.19871


I modified the timestamps manually, but....

root at lists:/home/mailman/locks #> touch -am *
root at lists:/home/mailman/locks #> ls -l
total 20
-rw-rw-r--   2 mailman  mailman       44 Aug 29 14:44 qrunner.lock
-rw-rw-r--   2 mailman  mailman       44 Aug 29 14:44
qrunner.lock.lists.19707
-rw-rw-r--   2 mailman  mailman       48 Aug 29 14:44 nnnnn_staff.lock
-rw-rw-r--   2 mailman  mailman       48 Aug 29 14:44
nnnnn_staff.lock.lists.19707
-rw-rw-r--   1 nobody   mailman       48 Aug 29 14:44
nnnnn_staff.lock.lists.19757
-rw-rw-r--   1 nobody   mailman       48 Aug 29 14:44
nnnnn_staff.lock.lists.19771
-rw-rw-r--   1 nobody   mailman       48 Aug 29 14:44
nnnnn_staff.lock.lists.19785
-rw-rw-r--   1 nobody   mailman       48 Aug 29 14:44
nnnnn_staff.lock.lists.19798
-rw-rw-r--   1 nobody   mailman       48 Aug 29 14:44
nnnnn_staff.lock.lists.19801
-rw-rw-r--   1 nobody   mailman       48 Aug 29 14:44
nnnnn_staff.lock.lists.19871

but within a few minutes, the timestamps go out of whack again.

This list is the only one that's not working...all the other lists
on this server (about 25) are behaving just fine.  And the qrunner
does manage to continue to timestamp itself oddly.  And every now
and then, I'll see a qrunner process that's several minutes old.
I saw one earlier today that was several hours old.  Killing the
hung qrunner doesn't seem to help much.

I'm tempted to remove the list and recreate it, but I don't know 
what that would do to the messages they've missed...if this causes 
the messages to be lost, I don't want to do that.

Any ideas?  This is quickly becoming urgent.


----
JoJo Brooks
DHL Worldwide Express