There may be a bug in the --force

Bug #1445191 reported by Aurélien Bompard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU Mailman
Undecided
Unassigned

Bug Description

When installing Mailman3 on a new host, a previous start of Mailman had to be killed because of memory issues.
After getting more RAM, starting mailman failed with a message that kinda looked like: "these are not the pidfiles you are looking for". It also suggested us to use the --force.

Being rather in the dark (side) about this, we tried. Apparently, we must do it, or do it not, but there is no try. Mailman didn't start this time either.

This felt like a great disturbance in the --force, which may require some investigation.

We hope this is unrelated to the millenium bug in Falcon.

Barry Warsaw (barry)
tags: added: mailman3
Revision history for this message
Abhilash Raj (raj-abhilash1) wrote :

This bug has been moved to the new gitlab repo here: https://gitlab.com/mailman/mailman/issues/111

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers