Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Core container won't up after upgrade #401

Closed
danil-smirnov opened this issue Sep 10, 2020 · 2 comments
Closed

[BUG] Core container won't up after upgrade #401

danil-smirnov opened this issue Sep 10, 2020 · 2 comments
Labels

Comments

@danil-smirnov
Copy link
Contributor

danil-smirnov commented Sep 10, 2020

Tag/version of Container Images
Core 0.3.7

I've discovered that after some recent release Mailman Core container won't docker-compose up after its version has upgraded in the docker-compose.yaml file.

The container fails to start with an error:

lists-mailman-core | Postgres is up - continuing
lists-mailman-core | Using Postfix configuration
lists-mailman-core | Found configuration file at /opt/mailman/mailman-extra.cfg
lists-mailman-core | Traceback (most recent call last):
lists-mailman-core |   File "/usr/lib/python3.8/site-packages/mailman/bin/master.py", line 125, in acquire_lock_1
lists-mailman-core |     lock.lock(timedelta(seconds=0.1))
lists-mailman-core |   File "/usr/lib/python3.8/site-packages/flufl/lock/_lockfile.py", line 364, in lock
lists-mailman-core |     raise TimeOutError('Could not acquire the lock')
lists-mailman-core | flufl.lock._lockfile.TimeOutError: Could not acquire the lock
lists-mailman-core |
lists-mailman-core | During handling of the above exception, another exception occurred:
lists-mailman-core |
lists-mailman-core | Traceback (most recent call last):
lists-mailman-core |   File "/usr/bin/master", line 8, in <module>
lists-mailman-core |     sys.exit(main())
lists-mailman-core |   File "/usr/lib/python3.8/site-packages/click/core.py", line 829, in __call__
lists-mailman-core |     return self.main(*args, **kwargs)
lists-mailman-core |   File "/usr/lib/python3.8/site-packages/click/core.py", line 782, in main
lists-mailman-core |     rv = self.invoke(ctx)
lists-mailman-core |   File "/usr/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
lists-mailman-core |     return ctx.invoke(self.callback, **ctx.params)
lists-mailman-core |   File "/usr/lib/python3.8/site-packages/click/core.py", line 610, in invoke
lists-mailman-core |     return callback(*args, **kwargs)
lists-mailman-core |   File "/usr/lib/python3.8/site-packages/mailman/bin/master.py", line 572, in main
lists-mailman-core |     lock = acquire_lock(force)
lists-mailman-core |   File "/usr/lib/python3.8/site-packages/mailman/bin/master.py", line 146, in acquire_lock
lists-mailman-core |     lock = acquire_lock_1(force)
lists-mailman-core |   File "/usr/lib/python3.8/site-packages/mailman/bin/master.py", line 131, in acquire_lock_1
lists-mailman-core |     lock.disown()
lists-mailman-core | AttributeError: 'Lock' object has no attribute 'disown'

A workaround is rm -f core/var/locks/master.lck* but I suppose it should not happen.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.93. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@danil-smirnov
Copy link
Contributor Author

Seems I can not reproduce it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant