[Mailman-Users] unable to access admin interface

[Mark Sapiro]

On 07/22/2014 07:25 PM, Chad Rebuck wrote:
> I didn't remove it until now, but I saw it seemed to update itself when I
> tried to access the admin page.
> 
> [root at pogo locks]# ll
> total 16K
> -rw-rw-r-- 1 http    mailman 52 Jul 23  2014 a2-16v-list.lock
> -rw-rw-r-- 1 http    mailman 52 Jul 23  2014 a2-16v-list.lock.pogo.21765.0
> -rw-rw-r-- 2 mailman mailman 46 Jul 24  2014 master-qrunner
> -rw-rw-r-- 2 mailman mailman 46 Jul 24  2014 master-qrunner.pogo.341
> 
> [root at pogo locks]# rm -rf a2-16v-list.lock*
> 
> [root at pogo locks]# ll
> total 8.0K
> -rw-rw-r-- 2 mailman mailman 46 Jul 24  2014 master-qrunner
> -rw-rw-r-- 2 mailman mailman 46 Jul 24  2014 master-qrunner.pogo.341
> 
> 
> I was then able to access the admin page, but when I clicked on "tend to
> pending requests" I got the 504 error after a couple minutes
> 
> [root at pogo locks]# tail -2 /var/log/httpd/error_log
> [Tue Jul 22 22:22:30.721677 2014] [cgi:error] [pid 378:tid 1143579696]
> [client 144.160.5.25:34507] Script timed out before returning headers:
> admindb, referer: http://mail.a2-16v.com/mailman/admin/a2-16v-list
> [Tue Jul 22 22:23:30.781402 2014] [cgi:warn] [pid 378:tid 1143579696]
> [client 144.160.5.25:34507] AH01220: Timeout waiting for output from CGI
> script /usr/lib/mailman/cgi-bin/admindb, referer:
> http://mail.a2-16v.com/mailman/admin/a2-16v-list
> [root at pogo locks]# tail -2 /var/log/httpd/access_log
> 144.160.5.25 - - [22/Jul/2014:22:21:14 -0400] "GET
> /mailman/admin/a2-16v-list HTTP/1.1" 200 20748
> 144.160.5.25 - - [22/Jul/2014:22:21:30 -0400] "GET
> /mailman/admindb/a2-16v-list HTTP/1.1" 504 247
> 
> now the lock folder is as follows
> 
> [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.21828.0
> -rw-rw-r-- 2 mailman mailman 46 Jul 24  2014 master-qrunner
> -rw-rw-r-- 2 mailman mailman 46 Jul 24  2014 master-qrunner.pogo.341
> [root at pogo locks]#


So PID 21828 has the list lock. It looks like the admindb CGI, PID 378
timed out, presumably because it couldn't get the lock, but its request
would be a file named a2-16v-list.lock.pogo.378.0, and that doesn't seem
to be there.

What if anything is in Mailman's 'error' log and 'locks' log?

Locking may be the underlying issue, but it's not just stale locks
because even after they're cleared, you still have issues.

How did you install 2.1.18-1?

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