[Mailman-Users] {Disarmed} Re: unable to access admin interface

[Mark Sapiro]

On 07/22/2014 01:56 PM, Chad Rebuck wrote:
> I see a related email from a google seach where you pointed someone to
> the lock files directory.  I suppose this isn't normal?  Too many lock
> files?
> 
> [root at pogo locks]# pwd
> /var/lib/mailman/locks
> [root at pogo locks]# ll
> total 100K
> -rw-rw-r-- 2 http    mailman 52 Jul 22  2014 a2-16v-list.lock
> -rw-rw-r-- 1 http    mailman 52 Jul 20 18:10 a2-16v-list.lock.pogo.19620.0
> -rw-rw-r-- 2 http    mailman 52 Jul 22  2014 a2-16v-list.lock.pogo.20307.0
> -rw-rw-r-- 1 http    mailman 52 Jul 22  2014 a2-16v-list.lock.pogo.20309.0
> -rw-rw-r-- 1 http    mailman 52 Jul 22  2014 a2-16v-list.lock.pogo.20311.0
> -rw-rw-r-- 1 http    mailman 52 Jul 22  2014 a2-16v-list.lock.pogo.20312.0
> -rw-rw-r-- 1 http    mailman 52 Jul 22  2014 a2-16v-list.lock.pogo.20313.0
> -rw-rw-r-- 1 http    mailman 52 Jul 22  2014 a2-16v-list.lock.pogo.20316.0
> -rw-rw-r-- 1 http    mailman 52 Jul 22  2014 a2-16v-list.lock.pogo.20323.0
> -rw-rw-r-- 1 http    mailman 52 Jul 22  2014 a2-16v-list.lock.pogo.20351.0
> -rw-rw-r-- 1 http    mailman 52 Jul 22  2014 a2-16v-list.lock.pogo.20519.0
> -rw-rw-r-- 1 http    mailman 52 Jul 22  2014 a2-16v-list.lock.pogo.20598.0
> -rw-rw-r-- 1 http    mailman 52 Jul 20 22:38 a2-16v-list.lock.pogo.20648.0
> -rw-rw-r-- 1 http    mailman 52 Jul 20 22:40 a2-16v-list.lock.pogo.20663.0
> -rw-rw-r-- 1 http    mailman 52 Jul 20 22:44 a2-16v-list.lock.pogo.20674.0
> -rw-rw-r-- 1 http    mailman 52 Jul 20 22:48 a2-16v-list.lock.pogo.20699.0
> -rw-rw-r-- 1 http    mailman 52 Jul 20 22:57 a2-16v-list.lock.pogo.20827.0
> -rw-rw-r-- 1 http    mailman 52 Jul 20 23:16 a2-16v-list.lock.pogo.20980.0
> -rw-rw-r-- 1 http    mailman 52 Jul 20 23:19 a2-16v-list.lock.pogo.20989.0
> -rw-rw-r-- 1 http    mailman 52 Jul 20 23:54 a2-16v-list.lock.pogo.21944.0
> -rw-rw-r-- 1 http    mailman 50 Jul 21 00:16 a2-16v-list.lock.pogo.406.0
> -rw-rw-r-- 1 http    mailman 50 Jul 21 00:20 a2-16v-list.lock.pogo.435.0
> -rw-rw-r-- 1 http    mailman 50 Jul 21 00:31 a2-16v-list.lock.pogo.484.0
> -rw-rw-r-- 2 mailman mailman 46 Jul 23  2014 master-qrunner
> -rw-rw-r-- 2 mailman mailman 46 Jul 23  2014 master-qrunner.pogo.341


There is definitely a locking issue. It's not that there are too many
per se, it's that the list is locked by a defunct process and the lock
will never be relinquished.

If you

cat /var/lib/mailman/locks/a2-16v-list.lock

the contents will be the file name of the active lock. Judging from the
link count, it's this one

-rw-rw-r-- 2 http    mailman 52 Jul 22  2014 a2-16v-list.lock.pogo.20307.0



do 'ps -fww 20307' or whatever the PID of the active lock is. If that
PID doesn't exist, do

rm /var/lib/mailman/locks/a2-16v-list.lock.pogo.19620.0

and wait a few seconds. If all the locks don't clear, repeat until they do.

If a PID with the lock does exist, ps -fww will show what it is which
may help identfy why it is hung with the list locked.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan