The mailing list for listmasters using Sympa

["Silvers, Tim" <address@concealed>]

The 500 error seemed to be some leftover data from the file corruption that hadn’t been cleansed from the system. A while later, everything was fine. Thanks, Soji, fo your assistance.

Tim

On Aug 16, 2016, at 1:24 PM, Silvers, Tim <address@concealed> wrote:

We have an hourly job that runs this, which I hadn’t tracked down until I did more digging this morning. The log showed there was an error regarding a hash reference. So I edited List.pm to include a print statement in the function that inserts data into the list_table so I could see on which list it was having a problem. That allowed us to trace the issue to one list directory that must have had some sort of file corruption or something. The directory has been saved for analysis, but we archived the directory then removed it from the data directory and then re-ran the —sync_list_db option, which rebuilt the list_table. The index of lists is working now as well.

We now have a new problem, which is that some functions submitted via the Web UI are returning a 500 error. The changes being made (e.g., ownership changes, send options, etc.) are recorded, but users are not returned to the page from which they came and they see the error page. Not all changes within the Web UI cause this error, however. For instance, modifying subscribers and general navigation. We’re still looking at this, but I wonder if we just need to restart services (apache in particular)?

Tim

On Aug 16, 2016, at 5:14 AM, IKEDA Soji <address@concealed> wrote:

Hi Tim,

Though you may already found out the solution, list_table in the
database can be rebuilt entirely by running:

# sympa.pl --sync_list_db

It empties and reloads list_table.


Regards,

-- Soji

Attachment: smime.p7s
Description: S/MIME cryptographic signature