Subject: The mailing list for listmasters using Sympa
List archive
- From: Steve Shipway <address@concealed>
- To: Michael Kuriger <address@concealed>, "address@concealed" <address@concealed>
- Subject: RE: [sympa-users] sympa issues
- Date: Tue, 2 Dec 2014 19:59:44 +0000
Are you able to post the error message here? Have you checked in your web server and sympa logs to see if there is any relevant error message that can be posted to give us some
idea? Check database logs, slow query logs, sympa logs, and general logs as well as web server error logs.
There is a known issue that happens for list searches in the web interface when you have a very large number of lists (though the latest Sympa versions - 6.1.19 and later I think - include the Riseup code which mitigates this). Very large numbers of lists (many thousands) can result in timeouts while performing searches.
If the problem is a database search timeout, then you should check into --
1. Increase the FCGI timeouts as defined in your apache conf
2. Do tuning to ensure enough memory is given to your database instance, so that it may perform in-memory index searches
3. Check the database slow query logs - possibly an index is missing and needs to be reinstated
4. Upgrade to a more recent Sympa, so that it makes proper use of the searches
5. Check for resource exhaustion on your Sympa server - does it have enough CPU and memory available for the number of messages and throughput it is experiencing? Check for filesystem space for temporary work files and database growth.
6. Maybe re-create the list table in the database (use the sympa.pl command with appropriate options), and if necessary, perform any database health checks andtests to check for and remove any corruption that may have been introduced.
There is a known issue that happens for list searches in the web interface when you have a very large number of lists (though the latest Sympa versions - 6.1.19 and later I think - include the Riseup code which mitigates this). Very large numbers of lists (many thousands) can result in timeouts while performing searches.
If the problem is a database search timeout, then you should check into --
1. Increase the FCGI timeouts as defined in your apache conf
2. Do tuning to ensure enough memory is given to your database instance, so that it may perform in-memory index searches
3. Check the database slow query logs - possibly an index is missing and needs to be reinstated
4. Upgrade to a more recent Sympa, so that it makes proper use of the searches
5. Check for resource exhaustion on your Sympa server - does it have enough CPU and memory available for the number of messages and throughput it is experiencing? Check for filesystem space for temporary work files and database growth.
6. Maybe re-create the list table in the database (use the sympa.pl command with appropriate options), and if necessary, perform any database health checks andtests to check for and remove any corruption that may have been introduced.
Steve Shipway
University of Auckland ITS
UNIX Systems Design Lead
Ph: +64 9 373 7599 ext 86487
From: address@concealed [address@concealed] on behalf of Michael Kuriger [address@concealed]
Sent: Saturday, 8 November 2014 7:53 a.m.
To: address@concealed
Subject: [sympa-users] sympa issues
Sent: Saturday, 8 November 2014 7:53 a.m.
To: address@concealed
Subject: [sympa-users] sympa issues
Hello! We are experiencing an issue since yesterday. When looking through the logs, it looks like the issue we’re seeing started shortly after a new list was added. At any rate, the problem is that we cannot so any type of list search. Either by clicking
the search button, or trying to get a list of lists. Eventually it times out and prints an error on the screen. Where can we start looking to see what the issue is?
we’re on version 6.1.7
Thanks,
Michael Kuriger
address@concealed
818-649-7235
MikeKuriger (IM)
-
[sympa-users] sympa issues,
Michael Kuriger, 11/07/2014
- RE: [sympa-users] sympa issues, Steve Shipway, 12/02/2014
Archive powered by MHonArc 2.6.19+.