Problem with starting core - problem getting a lock on something
Unfortunately our mailman-core-container doesn't start anymore correctly. We updated lately to v0.4.5 and it ran smoothly for the last 4 weeks. This morning the RAM crashed and I then had to restore some things since the RAID was affected. Anyway, the container doesn't get up anymore although we didn't change anything in the setup. Does anybody know what the error means and how we could fix that?
"Could not acquire the lock" normally means that some permissions aren't right ... right? Actually I don't know where to start.
What I already did: remove the container completely and rebuild it.
Thank you in advance! Jens.
Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 125, in acquire_lock_1 lock.lock(timedelta(seconds=0.1)) File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 386, in lock raise TimeOutError('Could not acquire the lock') flufl.lock._lockfile.TimeOutError: Could not acquire the lock
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 237, in details lockfile, hostname, pid, random_ignored = filename.split( ValueError: not enough values to unpack (expected 4, got 1)
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File "/usr/bin/master", line 8, in <module> sys.exit(main()) File "/usr/lib/python3.10/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3.10/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/usr/lib/python3.10/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3.10/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 580, in main lock = acquire_lock(force) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 151, in acquire_lock lock = acquire_lock_1(force) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 131, in acquire_lock_1 hostname, pid, tempfile = lock.details File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 241, in details raise NotLockedError('Details are unavailable') from error flufl.lock._lockfile.NotLockedError: Details are unavailable
I'm sorry for the too early answer, I found the solution myself:
- since the server crashed, it probably didn't shut down correctly and the "master.lck" was still open
- here I found the solution: https://github.com/maxking/docker-mailman/issues/401
- so I removed the lock from the volume of the container: rm ../var/locks/master.lck
- restart the container and it works
Thanks anyway :-D
Am 06.04.23 um 23:06 schrieb Jens Günther:
Unfortunately our mailman-core-container doesn't start anymore correctly. We updated lately to v0.4.5 and it ran smoothly for the last 4 weeks. This morning the RAM crashed and I then had to restore some things since the RAID was affected. Anyway, the container doesn't get up anymore although we didn't change anything in the setup. Does anybody know what the error means and how we could fix that?
"Could not acquire the lock" normally means that some permissions aren't right ... right? Actually I don't know where to start.
What I already did: remove the container completely and rebuild it.
Thank you in advance! Jens.
Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 125, in acquire_lock_1 lock.lock(timedelta(seconds=0.1)) File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 386, in lock raise TimeOutError('Could not acquire the lock') flufl.lock._lockfile.TimeOutError: Could not acquire the lock
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 237, in details lockfile, hostname, pid, random_ignored = filename.split( ValueError: not enough values to unpack (expected 4, got 1)
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File "/usr/bin/master", line 8, in <module> sys.exit(main()) File "/usr/lib/python3.10/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3.10/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/usr/lib/python3.10/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3.10/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 580, in main lock = acquire_lock(force) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 151, in acquire_lock lock = acquire_lock_1(force) File "/usr/lib/python3.10/site-packages/mailman/bin/master.py", line 131, in acquire_lock_1 hostname, pid, tempfile = lock.details File "/usr/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 241, in details raise NotLockedError('Details are unavailable') from error flufl.lock._lockfile.NotLockedError: Details are unavailable
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to jens.guenther@posteo.de
参加者 (1)
-
Jens Günther