Public bug reported:
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.
** Affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1445191
Title:
There may be a bug in the --force
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1445191/+subscriptions
_______________________________________________
Mailman-coders mailing list
[email protected]
https://mail.python.org/mailman/listinfo/mailman-coders
