flufl.lock._lockfile.NotLockedError: Already unlocked
![](https://secure.gravatar.com/avatar/4a0c604d04f340969c4dcfb0f8434031.jpg?s=120&d=mm&r=g)
I have started working on this pr. It is regarding various bounce_process functions. Strange behaviour is observed which I am not so sure what or why is happening. Unexpected Traceback error pops up in my terminal.
File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 580, in main loop.loop() File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 401, in loop self._pause() File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 391, in _pause signal.pause() File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 267, in sigalrm_handler self._lock.refresh() File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/flufl.lock-3.2-py3.7.egg/flufl/lock/_lockfile.py", line 184, in refresh flufl.lock._lockfile.NotLockedError: <Lock /home/aaryan/mailman/mailman/var/locks/master.lck [unlocked: 1 day, 6:00:00] pid=7596 at 0x7f54af802320x>: None
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 583, in main os.remove(config.PID_FILE) FileNotFoundError: [Errno 2] No such file or directory: '/home/aaryan/mailman/mailman/var/master.pid'
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/home/aaryan/mailman/venv3/bin/master", line 11, in <module> load_entry_point('mailman', 'console_scripts', 'master')() File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/Click-7.0-py3.7.egg/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/Click-7.0-py3.7.egg/click/core.py", line 717, in main rv = self.invoke(ctx) File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/Click-7.0-py3.7.egg/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/Click-7.0-py3.7.egg/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 585, in main lock.unlock() File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/flufl.lock-3.2-py3.7.egg/flufl/lock/_lockfile.py", line 287, in unlock flufl.lock._lockfile.NotLockedError: Already unlocked
I think some configuration of mailman is conflicting. One point to mention is the var
was created when I was working on some other branch.
Maybe deleting the var and running mailman start
will solve it?
Not many leads are there hence I though best asking this.
Pointers to this problem are appreciated
Am I missing something here?
![](https://secure.gravatar.com/avatar/8c8c6e35ec7ca5c708a6049152b2bedd.jpg?s=120&d=mm&r=g)
On Sat, Jul 20, 2019, at 7:15 AM, Aaryan Bhagat wrote:
I have started working on this pr. It is regarding various bounce_process functions. Strange behaviour is observed which I am not so sure what or why is happening. Unexpected Traceback error pops up in my terminal.
File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 580, in main loop.loop() File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 401, in loop self._pause() File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 391, in _pause signal.pause() File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 267, in sigalrm_handler self._lock.refresh() File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/flufl.lock-3.2-py3.7.egg/flufl/lock/_lockfile.py", line 184, in refresh flufl.lock._lockfile.NotLockedError: <Lock /home/aaryan/mailman/mailman/var/locks/master.lck [unlocked: 1 day, 6:00:00] pid=7596 at 0x7f54af802320x>: None
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 583, in main os.remove(config.PID_FILE) FileNotFoundError: [Errno 2] No such file or directory: '/home/aaryan/mailman/mailman/var/master.pid'
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/home/aaryan/mailman/venv3/bin/master", line 11, in <module> load_entry_point('mailman', 'console_scripts', 'master')() File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/Click-7.0-py3.7.egg/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/Click-7.0-py3.7.egg/click/core.py", line 717, in main rv = self.invoke(ctx) File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/Click-7.0-py3.7.egg/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/Click-7.0-py3.7.egg/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/home/aaryan/mailman/mailman/src/mailman/bin/master.py", line 585, in main lock.unlock() File "/home/aaryan/mailman/venv3/lib/python3.7/site-packages/flufl.lock-3.2-py3.7.egg/flufl/lock/_lockfile.py", line 287, in unlock flufl.lock._lockfile.NotLockedError: Already unlocked
I think some configuration of mailman is conflicting. One point to mention is the
var
was created when I was working on some other branch.
This seems to be because you removed the var/ directory without stopping Mailman Core. Note that var/ directory is continuously needed by Mailman Core when running since it stores it's runtime information there. If you remove the var/ directory without stopping Mailman Core, you'll end up in weird situations like this.
Make sure you always do mailman stop
and only then remove the
var/ directory.
Maybe deleting the var and running
mailman start
will solve it? Not many leads are there hence I though best asking this. Pointers to this problem are appreciated Am I missing something here?
Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-leave@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3
Security Policy: https://wiki.list.org/x/QIA9
-- thanks, Abhilash Raj (maxking)
![](https://secure.gravatar.com/avatar/4a0c604d04f340969c4dcfb0f8434031.jpg?s=120&d=mm&r=g)
This seems to be because you removed the var/ directory without stopping Mailman Core. Note that var/ directory is continuously needed by Mailman Core when running since it stores it's runtime information there. If you remove the var/ directory without stopping Mailman Core, you'll end up in weird situations like this.
Make sure you always do mailman stop and only then remove the var/ directory.
Ok thanks, I understood it!
participants (2)
-
Aaryan Bhagat
-
Abhilash Raj