Hello all,
I'm working on upgrading our mailman3 instance. The current running instance is 3.1.0, and I am attempting to move to 3.2.0a1. Partially because La Villa Strangiato is a better song than Between the Wheels, but mostly because we want some of the bug fixes, and we are nailing down our upgrade process for the future.
Initially after updating when I ran the "mailman info" command, I got this:
Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 7, in <module> from mailman.bin.mailman import main File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/bin/mailman.py", line 19, in <module> import click ModuleNotFoundError: No module named 'click'
So I went and installed click - easy enough to do. But then I get this error:
"Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 11, in <module> sys.exit(main()) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 696, in main with self.make_context(prog_name, args, **extra) as ctx: File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 621, in make_context self.parse_args(ctx, args) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 1018, in parse_args rest = Command.parse_args(self, ctx, args) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 880, in parse_args value, args = param.handle_parse_result(ctx, opts, args) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 1404, in handle_parse_result self.callback, ctx, self, value) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 78, in invoke_param_callback return callback(ctx, param, value) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/bin/mailman.py", line 93, in initialize_config initialize(value) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/core/initialize.py", line 219, in initialize initialize_2(propagate_logs=propagate_logs) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/core/initialize.py", line 178, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/database/factory.py", line 54, in create database.initialize() File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/database/base.py", line 107, in initialize url, isolation_level='READ UNCOMMITTED', pool_pre_ping=True) File "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/engine/__init__.py", line 387, in create_engine return strategy.create(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/engine/strategies.py", line 160, in create engineclass.__name__)) TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), using configuration PGDialect_psycopg2/QueuePool/Engine. Please check that the keyword arguments are appropriate for this combination of components."
Anyone able to point me where to go to look for a solution for this?
We're running postgresql as the database, and psycopg2 has been installed.
Thoughts?
-Darren
On 04/16/2018 10:12 AM, Darren Smith wrote:
"/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/engine/strategies.py", line 160, in create engineclass.__name__)) TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), using configuration PGDialect_psycopg2/QueuePool/Engine. Please check that the keyword arguments are appropriate for this combination of components."
Anyone able to point me where to go to look for a solution for this?
You need to update SQLAlchemy to >= 1.2 for this, but there is another issue that requires at least 1.2.3 (current is 1.2.6)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Boy howdy did that work...
Thanks!
On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark@msapiro.net> wrote:
On 04/16/2018 10:12 AM, Darren Smith wrote:
"/opt/mailman3/conda/lib/python3.6/site-packages/ sqlalchemy/engine/strategies.py", line 160, in create engineclass.__name__)) TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), using configuration PGDialect_psycopg2/QueuePool/Engine. Please check that the keyword arguments are appropriate for this combination of components."
Anyone able to point me where to go to look for a solution for this?
You need to update SQLAlchemy to >= 1.2 for this, but there is another issue that requires at least 1.2.3 (current is 1.2.6)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Nice...spoke too soon.
Mailman info works, but when attempting to start mailman I'm now getting this:
Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 11, in <module> sys.exit(main()) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 676, in main _verify_python3_env() File "/opt/mailman3/conda/lib/python3.6/site-packages/click/_unicodefun.py", line 118, in _verify_python3_env 'for mitigation steps.' + extra) RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps.
This system lists a couple of UTF-8 supporting locales that you can pick from. The following suitable locales where discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, (followed by a bijillion others)
-Darren
On Mon, Apr 16, 2018 at 11:25 AM, Darren Smith <silas.crutherton@gmail.com> wrote:
Boy howdy did that work...
Thanks!
On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark@msapiro.net> wrote:
On 04/16/2018 10:12 AM, Darren Smith wrote:
"/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/ engine/strategies.py", line 160, in create engineclass.__name__)) TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), using configuration PGDialect_psycopg2/QueuePool/Engine. Please check that the keyword arguments are appropriate for this combination of components."
Anyone able to point me where to go to look for a solution for this?
You need to update SQLAlchemy to >= 1.2 for this, but there is another issue that requires at least 1.2.3 (current is 1.2.6)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
By the way, in reading the URL in the error, I attempted to set the LANG and LC_ALL to en_US.utf8 (as was found in the error) but it still does not work.
On Mon, Apr 16, 2018 at 11:26 AM, Darren Smith <silas.crutherton@gmail.com> wrote:
Nice...spoke too soon.
Mailman info works, but when attempting to start mailman I'm now getting this:
Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 11, in <module> sys.exit(main()) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 676, in main _verify_python3_env() File "/opt/mailman3/conda/lib/python3.6/site-packages/click/_unicodefun.py", line 118, in _verify_python3_env 'for mitigation steps.' + extra) RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps.
This system lists a couple of UTF-8 supporting locales that you can pick from. The following suitable locales where discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, (followed by a bijillion others)
-Darren
On Mon, Apr 16, 2018 at 11:25 AM, Darren Smith <silas.crutherton@gmail.com
wrote:
Boy howdy did that work...
Thanks!
On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark@msapiro.net> wrote:
On 04/16/2018 10:12 AM, Darren Smith wrote:
"/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/ engine/strategies.py", line 160, in create engineclass.__name__)) TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), using configuration PGDialect_psycopg2/QueuePool/Engine. Please check that the keyword arguments are appropriate for this combination of components."
Anyone able to point me where to go to look for a solution for this?
You need to update SQLAlchemy to >= 1.2 for this, but there is another issue that requires at least 1.2.3 (current is 1.2.6)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Further debugging - using the python3.6 from the virtual environment where mailman is running, it looks like it is trying to use utf-8:
import locale import codecs print(locale.getpreferredencoding()) UTF-8 print(codecs.lookup(locale.getpreferredencoding()).name) utf-8
Thoughts?
On Mon, Apr 16, 2018 at 11:29 AM, Darren Smith <silas.crutherton@gmail.com> wrote:
By the way, in reading the URL in the error, I attempted to set the LANG and LC_ALL to en_US.utf8 (as was found in the error) but it still does not work.
On Mon, Apr 16, 2018 at 11:26 AM, Darren Smith <silas.crutherton@gmail.com
wrote:
Nice...spoke too soon.
Mailman info works, but when attempting to start mailman I'm now getting this:
Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 11, in <module> sys.exit(main()) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 676, in main _verify_python3_env() File "/opt/mailman3/conda/lib/python3.6/site-packages/click/_unicodefun.py", line 118, in _verify_python3_env 'for mitigation steps.' + extra) RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps.
This system lists a couple of UTF-8 supporting locales that you can pick from. The following suitable locales where discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, (followed by a bijillion others)
-Darren
On Mon, Apr 16, 2018 at 11:25 AM, Darren Smith < silas.crutherton@gmail.com> wrote:
Boy howdy did that work...
Thanks!
On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark@msapiro.net> wrote:
On 04/16/2018 10:12 AM, Darren Smith wrote:
"/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/ engine/strategies.py", line 160, in create engineclass.__name__)) TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), using configuration PGDialect_psycopg2/QueuePool/Engine. Please check that the keyword arguments are appropriate for this combination of components."
Anyone able to point me where to go to look for a solution for this?
You need to update SQLAlchemy to >= 1.2 for this, but there is another issue that requires at least 1.2.3 (current is 1.2.6)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 04/16/2018 10:26 AM, Darren Smith wrote:
Nice...spoke too soon.
Mailman info works, but when attempting to start mailman I'm now getting this: ... RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps.
Are you starting Mailman from an init script. If so, add
export LANG=en_US.UTF-8
to the script. See <http://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html#running-mailman-3>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
And as usual, Mark to the rescue. Works like a charm...thank you!
By the way, whose idea was it to use Rush songs for the release names? I whole-heartedly approve.
-Darren
On Mon, Apr 16, 2018 at 11:52 AM, Mark Sapiro <mark@msapiro.net> wrote:
On 04/16/2018 10:26 AM, Darren Smith wrote:
Nice...spoke too soon.
Mailman info works, but when attempting to start mailman I'm now getting this: ... RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps.
Are you starting Mailman from an init script. If so, add
export LANG=en_US.UTF-8
to the script. See <http://mailman.readthedocs.io/en/latest/src/mailman/docs/ install.html#running-mailman-3>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
participants (2)
-
Darren Smith -
Mark Sapiro