flufl.lock._lockfile.NotLockedError: Already unlocked

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.
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?

On Sat, Jul 20, 2019, at 7:15 AM, Aaryan Bhagat wrote:
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.
-- thanks, Abhilash Raj (maxking)

On Sat, Jul 20, 2019, at 7:15 AM, Aaryan Bhagat wrote:
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.
-- thanks, Abhilash Raj (maxking)
participants (2)
-
Aaryan Bhagat
-
Abhilash Raj