On 02/08/2016 08:42 AM, Aditya Divekar wrote: > I got the following error when I was trying to start the mailman service > today - > > master: error: The master lock could not be acquired. It appears as > though there is a stale master lock
The service was not gracefully stopped the last time it was running and left the master lock behind. The FAQ at <http://wiki.list.org/x/17891756> describes how locks are implemented in Mailman 2.1, but Mailman 3 is similar. There is a var/locks/ directory in your Mailman hierarchy. In it you will see two files. in MM 2.1, they would be named master-qrunner and master-qrunner.hostname.pid. In MM 3 they will be similar. Assuming there is no process with PID = pid running on hostname, you can safely remove those files. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
