What is the cause of 'superset db upgrade' exiting with code 132 due CACHE_TYPE set to null?
Asked Answered
W

1

0

I try to install superset on Fedora 31, I've followed the official document site.

I have this error when I execute superset db upgrade

  • logging was configured successfully
  • INFO:superset.utils.logging_configurator:logging was configured successfully /home/mos/Workspace/superset/venv37/lib64/python3.7/site-packages/flask_caching/init.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
  • "Flask-Caching: CACHE_TYPE is set to null, "
  • Illegal instruction (core dumped)

with exit code 132

Wildlife answered 24/4, 2020 at 7:42 Comment(1)
I encounter same issue on Ubuntu 18.04Wildlife
W
2

I figure it out. It caused by the absence of AVX(Advanced Vector Extensions) support in the CPU.

Wildlife answered 29/4, 2020 at 10:15 Comment(2)
can you tell me more about it? how to resolve this issue?Lytle
@Lytle presumably use a CPU that has AVX support.Merca

© 2022 - 2024 — McMap. All rights reserved.