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

[Chad Rebuck]

Here ya go

[root at pogo locks]# ll
total 16K
-rw-rw-r-- 2 http    mailman 52 Jul 23  2014 a2-16v-list.lock
-rw-rw-r-- 2 http    mailman 52 Jul 23  2014 a2-16v-list.lock.pogo.25890.0
-rw-rw-r-- 2 mailman mailman 48 Jul 24  2014 master-qrunner
-rw-rw-r-- 2 mailman mailman 48 Jul 24  2014 master-qrunner.pogo.25683
[root at pogo locks]# ps -fww 25890
UID        PID  PPID  C STIME TTY      STAT   TIME CMD
http     25890   378 95 12:12 ?        R      0:11 /usr/bin/python2 -S
/usr/lib/mailman/scripts/driver admindb




On Wed, Jul 23, 2014 at 12:05 PM, Mark Sapiro <mark at msapiro.net> wrote:

> On 07/23/2014 08:39 AM, Chad Rebuck wrote:
> >
> > I stopped mailman, confirmed no python processes exist, and deleted all
> > files from the locks dir.  I could access the admin page, but not the
> > pending moderator requests.
> >
> > [root at pogo locks]# ll
> > total 8.0K
> > -rw-rw-r-- 2 http mailman 52 Jul 23  2014 a2-16v-list.lock
> > -rw-rw-r-- 2 http mailman 52 Jul 23  2014 a2-16v-list.lock.pogo.25650.0
> > [root at pogo locks]#
>
>
> First, ignore my prior remark about time stamps in the future. This is
> expected. It is the way locking determines when a lock expires.
>
> What happens if you do something like the above, but before the CGI
> times out you look at the locks and then look for the PID?
>
> I.e., if you looked at the locks and saw the above, do
>
> ps -fww 25650
>
> to see some detail about the process that has the lock while it's still
> there.
>
> It appears that the CGI is not responding for some other reason and when
> killed by the web server, it leaves the list locked. So locked lists are
> not the cause of the problem, but another symptom of the problem
> whatever that might be.
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>