hi. Nope, didn't touch the configuration after the latest update. Glad
Mark led me to the root cause. Working just fine now that I ran the
database check.
Great support!
On Jul 23, 2014 8:37 PM, "Stephen J. Turnbull" wrote:
> Chad Rebuck writes:
>
> > Here is additional information. The log
Chad Rebuck writes:
> Here is additional information. The log entries for "lifetime has
> expired" started happening much more frequently after upgrading to
> 2.1.18-1.
Did you enable any of the features that require querying the DNS for
DMARC policy (eg, Privacy | Sender Filters | dmarc_mode
Just to provide closure here, after a bit more off list communication,
it was determined that the list's request.pck was huge (1.3 MB) with
probably thousands of held messages and the admindb CGI was being timed
out by the web server before it could process the whole file which was
leaving the list
On 07/23/2014 09:15 AM, Chad Rebuck wrote:
> Here ya go
>
> [root@pogo locks]# ll
> total 16K
> -rw-rw-r-- 2 httpmailman 52 Jul 23 2014 a2-16v-list.lock
> -rw-rw-r-- 2 httpmailman 52 Jul 23 2014 a2-16v-list.lock.pogo.25890.0
> -rw-rw-r-- 2 mailman mailman 48 Jul 24 2014 master-qrunner
>
Here is additional information. The log entries for "lifetime has expired"
started happening much more frequently after upgrading to 2.1.18-1.
This is the most recent complete log entry for the "lifetime has expired":
Jul 23 03:47:28 2014 (21881) a2-16v-list.lock lifetime has expired, breaking
J
I installed it with a package on my arch system using
pacman -Syu
[root@pogo chadr]# ll /var/lib/mailman/locks/
total 16K
-rw-rw-r-- 1 httpmailman 52 Jul 23 03:52 a2-16v-list.lock.pogo.22018.0
-rw-rw-r-- 1 httpmailman 52 Jul 23 04:45 a2-16v-list.lock.pogo.22205.0
-rw-rw-r-- 2 mailman mail
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@pogo locks]# ll
> total 16K
> -rw-rw-r-- 1 httpmailman 52 Jul 23 2014 a2-16v-list.lock
> -rw-rw-r-- 1 httpmailman 52 Jul 23 2
http://mail.a2-16v.com/mailman/listinfo/a2-16v-list
http://mail.a2-16v.com/mailman/admin/a2-16v-list
web access
144.160.5.25 - - [22/Jul/2014:16:38:40 -0400] "GET
/mailman/admin/a2-16v-list HTTP/1.1" 504 247
web error
[Tue Jul 22 16:40:40.374934 2014] [cgi:warn] [pid 187:tid 1098904624]
[client
On 07/22/2014 01:16 PM, Chad Rebuck wrote:
> thanks for the help
>
> 1. yes, I am able to access the list info page fine, then I click on the
> admin interface from that page. All the pages are http, not https from
> what I see.
What is the exact URL of the listinfo page you are accessing and
thanks for the help
1. yes, I am able to access the list info page fine, then I click on the
admin interface from that page. All the pages are http, not https from
what I see.
2. yes
3. yes, I can access other pages on the same server using the same domain
name even when the admin page is not re
Chad Rebuck writes:
> I'm not able to access the admin interface. I don't reach the page
> where I can enter my admin password. The mailman error log doesn't
> show anything.
> I'm running mailman 2.1.18-1.
>
> This message appears:
>
> Gateway Timeout
>
> The gateway did not recei
I'm not able to access the admin interface. I don't reach the page where I
can enter my admin password. The mailman error log doesn't show anything.
I'm running mailman 2.1.18-1.
This message appears:
Gateway Timeout
The gateway did not receive a timely response from the upstream server or
ap
12 matches
Mail list logo
