locked files problem after reboot
hey, I have got a problem with flufl.lock in mailman3. When my server is rebooted, locked files seems to stay and cause errors so mailman3 core wont start (it is started automatically by supervisord service):
PermissionError: [Errno 1] Operation not permitted Traceback (most recent call last): File "/home/user/.local/lib/python3.6/site-packages/mailman/bin/master.py", line 146, in acquire_lock lock = acquire_lock_1(force) File "/home/user/.local/lib/python3.6/site-packages/mailman/bin/master.py", line 125, in acquire_lock_1 lock.lock(timedelta(seconds=0.1)) File "/home/user/.local/lib/python3.6/site-packages/flufl/lock/_lockfile.py", line 259, in lock raise TimeOutError('Could not acquire the lock') flufl.lock._lockfile.TimeOutError: Could not acquire the lock
I have to remove the files in var/locks manually to go forward. Is there a configuration error for my setup? Or is it just a not fixed bug?
Greetsn, jekyl
On 5/23/19 5:36 AM, mailman3@malevil.cc wrote:
hey, I have got a problem with flufl.lock in mailman3. When my server is rebooted, locked files seems to stay and cause errors so mailman3 core wont start (it is started automatically by supervisord service): ... I have to remove the files in var/locks manually to go forward. Is there a configuration error for my setup? Or is it just a not fixed bug?
Add the --force option to the 'mailman start' command in your startup
script. i.e. mailman start --force
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I'm running into a "stale master lock" error when mailman is trying to start, in this case from an image I created of a working setup. The server was off when I made the image. I've tried running mailman start with the --force option and it times out. Any thoughts on how I can clear this lock manually? I'm testing failure/restore scenarios so I'd like to know that I can bring my system back from an imaged backup.
~Kelly
On 6/19/20 1:53 PM, kelly.close@lrewater.com wrote:
I'm running into a "stale master lock" error when mailman is trying to start, in this case from an image I created of a working setup. The server was off when I made the image. I've tried running mailman start with the --force option and it times out. Any thoughts on how I can clear this lock manually? I'm testing failure/restore scenarios so I'd like to know that I can bring my system back from an imaged backup.
Just remove var/locks/master.lck*
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
kelly.close@lrewater.com
-
mailman3@malevil.cc
-
Mark Sapiro