修改docker中superset 可以匿名访问

最新推荐文章于 2024-08-26 17:33:29 发布
原创 最新推荐文章于 2024-08-26 17:33:29 发布 · 705 阅读 · 9 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#docker #容器 #运维

本文详细描述了如何在Docker容器中以root权限修改Superset配置，允许匿名访问并设置Gamma角色，同时移除X-Frame-Options限制和禁用CSRF保护。通过这些步骤，用户可以确保分享的链接直接进入Public界面。

修改docker中superset 可以匿名访问

以root形式进入容器

docker exec -it -u root my_superset /bin/bash

下载vim

apt-get update
apt-get install vim

修改配置文件

进入superset，找到config.py

cd superset
  1. 修改config.py配置文件，将PUBLIC_ROLE_LIKE 设置为Gamma
PUBLIC_ROLE_LIKE: Optional[str] = “Gamma”
  1. 去掉X-Frame-Options限制
HTTP_HEADERS = {}
  1. WTF_CSRF_ENABLED设置为False
WTF_CSRF_ENABLED = False
  1. 保存文件后执行init
superset init

在这里插入图片描述
在次进入后发现public权限与gamme一致
在这里插入图片描述
此时分享的链接可以直接进入

Aoeding
关注
Superset docker最新版的匿名访问iframe和汉化教程
manfulshark的博客
08-09 1032
这时将会发现iframe上面显示xxxx地址拒绝访问,这是由于superset自己设置了跨域拒绝访问,在请求中强制设置了。然而Public用户(属于匿名用户)是没有id属性的,Gamma用户中部分权限需要使用到该属性,此时将会报错。注意: 由于最后并未手动去个个排查究竟是哪个权限导致,大致范围在menu以及Log方面。若但设置HTTP_HEADERS无效,则可以试试其他的HEADERS。superset的官方汉化要么是翻译不准确,要么是不完全翻译。解决方法: 在superset的config文件中,将。
superset2.x开启匿名分享
第一片心意的博客
06-20 1103
superset2.x开启匿名分享
【Superset】匿名访问Dashboad
flyincyclone的博客
06-14 827
这通常意味着匿名用户将默认获得名为 “Viewer”（可设置为其他角色名称） 的角色的权限。这个 “Viewer” 角色通常被设置为只能查看数据，而不能对数据进行编辑、删除或执行其他敏感操作。配置与匿名访问或公共访问的默认角色设置相关。这个配置项允许管理员定义当用户没有登录（即匿名访问）时，应该赋予他们哪个角色的权限。目的是对角色和权限进行初始化。初始化完成后，刚才的改动才有效。目录下的config.py中找到。默认为None，表示不能匿名访问。按照文档的方法，首先在。
Docker部署Superset 2.1.0+开发环境+汉化+匿名访问+创建自定义图表（二次开发）+集成echarts+echarts百度地图
weixin_43219396的博客
04-23 1万+
Docker部署Superset 2.1.0+开发环境+汉化+匿名访问+创建自定义图表（二次开发）+集成echarts+echarts百度地图
设置superset可以匿名访问图表
热门推荐
water Wang
09-16 1万+
目标：匿名（不需要登录）即可访问superset图表
docker：容器中修改superset配置文件，避免iframe跨站访问问题
不花的花和尚的博客
05-20 6011
以上定位到superset容器： 然后以root帐户进入容器： 执行docker exec -it --user root 5dd1c0bc2d60 /bin/bash 注意空格问题，否则容易报错 如： 找配置文件进行修改： find./-typef-nameconfig.py 进入目录： cd /usr/local/lib/pyth...
使用docker compose 方式启动superset,superset的操作前端页面没有正常显示，如何处理
02-25
确认 `docker-compose.yml` 中 Superset 端口映射正确（默认端口 `8088`）： ```yaml services: superset: ports: - "8088:8088" # 确保左侧主机端口未被占用 ``` - **验证端口占用**： ```bash lsof -i :8088 ...
数据可视化平台Superset 简介
坏小子❤的专栏
09-19 4004
数据可视化平台Superset简介 Superset 简介 Superset是Airbnb开源BI数据分析与可视化平台（曾用名Caravel、Panoramix），该工具主要特点是可自助分析、自定义仪表盘、分析结果可视化（导出）、用户/角色权限控制，还集成了一个SQL编辑器，可以进行SQL编辑查询等，原来是用于支持...
gapinyc@DESKTOP-9QS7RL5:~/superset-prod$ docker logs superset_app [2025-10-21 10:01:33 +0000] [1] [INFO] Starting gunicorn 23.0.0 [2025-10-21 10:01:33 +0000] [1] [INFO] Listening at: http://0.0.0.0:8088 (1) [2025-10-21 10:01:33 +0000] [1] [INFO] Using worker: gevent [2025-10-21 10:01:33 +0000] [7] [INFO] Booting worker with pid: 7 [2025-10-21 10:01:33 +0000] [8] [INFO] Booting worker with pid: 8 [2025-10-21 10:01:33 +0000] [9] [INFO] Booting worker with pid: 9 [2025-10-21 10:01:33 +0000] [10] [INFO] Booting worker with pid: 10 Loaded your LOCAL configuration at [/etc/superset/superset_config.py] Loaded your LOCAL configuration at [/etc/superset/superset_config.py] Loaded your LOCAL configuration at [/etc/superset/superset_config.py] Loaded your LOCAL configuration at [/etc/superset/superset_config.py] 2025-10-21 10:01:38,497:INFO:superset.initialization:Setting database isolation level to READ COMMITTED 2025-10-21 10:01:38,499:INFO:superset.initialization:Setting database isolation level to READ COMMITTED 2025-10-21 10:01:38,500:INFO:superset.initialization:Setting database isolation level to READ COMMITTED /app/.venv/lib/python3.10/site-packages/flask_limiter/extension.py:333: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend. warnings.warn( /app/.venv/lib/python3.10/site-packages/flask_limiter/extension.py:333: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend. warnings.warn( /app/.venv/lib/python3.10/site-packages/flask_limiter/extension.py:333: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend. warnings.warn( 2025-10-21 10:01:38,513:INFO:superset.initialization:Setting database isolation level to READ COMMITTED /app/.venv/lib/python3.10/site-packages/flask_limiter/extension.py:333: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend. warnings.warn( 2025-10-21 10:01:38,606:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (pymysql.err.OperationalError) (1050, "Table 'ab_permission' already exists") [SQL: CREATE TABLE ab_permission ( id INTEGER NOT NULL AUTO_INCREMENT, name VARCHAR(100) NOT NULL, PRIMARY KEY (id), UNIQUE (name) ) ] (Background on this error at: https://sqlalche.me/e/14/e3q8) 2025-10-21 10:01:38,606:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (pymysql.err.OperationalError) (1050, "Table 'ab_permission' already exists") [SQL: CREATE TABLE ab_permission ( id INTEGER NOT NULL AUTO_INCREMENT, name VARCHAR(100) NOT NULL, PRIMARY KEY (id), UNIQUE (name) ) ] (Background on this error at: https://sqlalche.me/e/14/e3q8) 2025-10-21 10:01:38,606:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (pymysql.err.OperationalError) (1050, "Table 'ab_permission' already exists") [SQL: CREATE TABLE ab_permission ( id INTEGER NOT NULL AUTO_INCREMENT, name VARCHAR(100) NOT NULL, PRIMARY KEY (id), UNIQUE (name) ) ] (Background on this error at: https://sqlalche.me/e/14/e3q8) [2025-10-21 10:01:38 +0000] [9] [INFO] Worker exiting (pid: 9) [2025-10-21 10:01:38 +0000] [7] [INFO] Worker exiting (pid: 7) [2025-10-21 10:01:38 +0000] [10] [INFO] Worker exiting (pid: 10) 2025-10-21 10:01:39,148:INFO:superset.utils.screenshots:No PIL installation found [2025-10-21 10:01:39 +0000] [1] [ERROR] Worker (pid:7) exited with code 1 [2025-10-21 10:01:39 +0000] [1] [ERROR] Worker (pid:7) exited with code 1. [2025-10-21 10:01:39 +0000] [1] [ERROR] Worker (pid:9) exited with code 1 [2025-10-21 10:01:39 +0000] [1] [ERROR] Worker (pid:9) exited with code 1. [2025-10-21 10:01:39 +0000] [1] [ERROR] Worker (pid:10) exited with code 1 [2025-10-21 10:01:39 +0000] [1] [ERROR] Worker (pid:10) exited with code 1. [2025-10-21 10:01:39 +0000] [111] [INFO] Booting worker with pid: 111 [2025-10-21 10:01:39 +0000] [112] [INFO] Booting worker with pid: 112 [2025-10-21 10:01:39 +0000] [113] [INFO] Booting worker with pid: 113 2025-10-21 10:01:39,780:INFO:superset.utils.pdf:No PIL installation found 2025-10-21 10:01:40,883:WARNING:root:Failed to add user to db session: Class 'werkzeug.local.LocalProxy' is not mapped 2025-10-21 10:01:40,891:ERROR:root:DBEventLogger failed to log event(s) 2025-10-21 10:01:40,891:ERROR:root:(pymysql.err.ProgrammingError) (1146, "Table 'superset.logs' doesn't exist") [SQL: INSERT INTO logs (action, json, dttm, duration_ms) VALUES (%(action)s, %(json)s, %(dttm)s, %(duration_ms)s)] [parameters: {'action': 'welcome', 'json': '{"path": "/superset/welcome/", "object_ref": "Superset.welcome"}', 'dttm': datetime.datetime(2025, 10, 21, 10, 1, 40, 888732), 'duration_ms': 0}] (Background on this error at: https://sqlalche.me/e/14/f405) Traceback (most recent call last): File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1910, in _execute_context self.dialect.do_execute( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute cursor.execute(statement, parameters) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 153, in execute result = self._query(query) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 322, in _query conn.query(q) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 575, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 826, in _read_query_result result.read() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 1203, in read first_packet = self.connection._read_packet() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 782, in _read_packet packet.raise_for_error() File "/app/.venv/lib/python3.10/site-packages/pymysql/protocol.py", line 219, in raise_for_error err.raise_mysql_exception(self._data) File "/app/.venv/lib/python3.10/site-packages/pymysql/err.py", line 150, in raise_mysql_exception raise errorclass(errno, errval) pymysql.err.ProgrammingError: (1146, "Table 'superset.logs' doesn't exist") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/app/superset/utils/log.py", line 406, in log db.session.bulk_save_objects(logs) File "<string>", line 2, in bulk_save_objects File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3705, in bulk_save_objects self._bulk_save_mappings( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3912, in _bulk_save_mappings with util.safe_reraise(): File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ compat.raise_( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3901, in _bulk_save_mappings persistence._bulk_insert( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/persistence.py", line 107, in _bulk_insert _emit_insert_statements( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/persistence.py", line 1097, in _emit_insert_statements c = connection._execute_20( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1710, in _execute_20 return meth(self, args_10style, kwargs_10style, execution_options) File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/sql/elements.py", line 334, in _execute_on_connection return connection._execute_clauseelement( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1577, in _execute_clauseelement ret = self._execute_context( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1953, in _execute_context self._handle_dbapi_exception( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 2134, in _handle_dbapi_exception util.raise_( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1910, in _execute_context self.dialect.do_execute( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute cursor.execute(statement, parameters) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 153, in execute result = self._query(query) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 322, in _query conn.query(q) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 575, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 826, in _read_query_result result.read() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 1203, in read first_packet = self.connection._read_packet() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 782, in _read_packet packet.raise_for_error() File "/app/.venv/lib/python3.10/site-packages/pymysql/protocol.py", line 219, in raise_for_error err.raise_mysql_exception(self._data) File "/app/.venv/lib/python3.10/site-packages/pymysql/err.py", line 150, in raise_mysql_exception raise errorclass(errno, errval) sqlalchemy.exc.ProgrammingError: (pymysql.err.ProgrammingError) (1146, "Table 'superset.logs' doesn't exist") [SQL: INSERT INTO logs (action, json, dttm, duration_ms) VALUES (%(action)s, %(json)s, %(dttm)s, %(duration_ms)s)] [parameters: {'action': 'welcome', 'json': '{"path": "/superset/welcome/", "object_ref": "Superset.welcome"}', 'dttm': datetime.datetime(2025, 10, 21, 10, 1, 40, 888732), 'duration_ms': 0}] (Background on this error at: https://sqlalche.me/e/14/f405) Loaded your LOCAL configuration at [/etc/superset/superset_config.py] Loaded your LOCAL configuration at [/etc/superset/superset_config.py] Loaded your LOCAL configuration at [/etc/superset/superset_config.py] 2025-10-21 10:01:43,495:INFO:superset.initialization:Setting database isolation level to READ COMMITTED /app/.venv/lib/python3.10/site-packages/flask_limiter/extension.py:333: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend. warnings.warn( 2025-10-21 10:01:43,515:INFO:superset.initialization:Setting database isolation level to READ COMMITTED /app/.venv/lib/python3.10/site-packages/flask_limiter/extension.py:333: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend. warnings.warn( 2025-10-21 10:01:43,528:INFO:superset.initialization:Setting database isolation level to READ COMMITTED /app/.venv/lib/python3.10/site-packages/flask_limiter/extension.py:333: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend. warnings.warn( 2025-10-21 10:01:43,621:INFO:superset.utils.screenshots:No PIL installation found 2025-10-21 10:01:43,644:INFO:superset.utils.screenshots:No PIL installation found 2025-10-21 10:01:43,649:INFO:superset.utils.screenshots:No PIL installation found 2025-10-21 10:01:44,102:INFO:superset.utils.pdf:No PIL installation found 2025-10-21 10:01:44,105:INFO:superset.utils.pdf:No PIL installation found 2025-10-21 10:01:44,121:INFO:superset.utils.pdf:No PIL installation found 2025-10-21 10:02:17,194:WARNING:root:Failed to add user to db session: Class 'werkzeug.local.LocalProxy' is not mapped 2025-10-21 10:02:17,203:ERROR:root:DBEventLogger failed to log event(s) 2025-10-21 10:02:17,203:ERROR:root:(pymysql.err.ProgrammingError) (1146, "Table 'superset.logs' doesn't exist") [SQL: INSERT INTO logs (action, json, dttm, duration_ms) VALUES (%(action)s, %(json)s, %(dttm)s, %(duration_ms)s)] [parameters: {'action': 'welcome', 'json': '{"path": "/superset/welcome/", "object_ref": "Superset.welcome"}', 'dttm': datetime.datetime(2025, 10, 21, 10, 2, 17, 200564), 'duration_ms': 0}] (Background on this error at: https://sqlalche.me/e/14/f405) Traceback (most recent call last): File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1910, in _execute_context self.dialect.do_execute( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute cursor.execute(statement, parameters) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 153, in execute result = self._query(query) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 322, in _query conn.query(q) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 575, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 826, in _read_query_result result.read() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 1203, in read first_packet = self.connection._read_packet() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 782, in _read_packet packet.raise_for_error() File "/app/.venv/lib/python3.10/site-packages/pymysql/protocol.py", line 219, in raise_for_error err.raise_mysql_exception(self._data) File "/app/.venv/lib/python3.10/site-packages/pymysql/err.py", line 150, in raise_mysql_exception raise errorclass(errno, errval) pymysql.err.ProgrammingError: (1146, "Table 'superset.logs' doesn't exist") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/app/superset/utils/log.py", line 406, in log db.session.bulk_save_objects(logs) File "<string>", line 2, in bulk_save_objects File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3705, in bulk_save_objects self._bulk_save_mappings( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3912, in _bulk_save_mappings with util.safe_reraise(): File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ compat.raise_( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3901, in _bulk_save_mappings persistence._bulk_insert( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/persistence.py", line 107, in _bulk_insert _emit_insert_statements( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/persistence.py", line 1097, in _emit_insert_statements c = connection._execute_20( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1710, in _execute_20 return meth(self, args_10style, kwargs_10style, execution_options) File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/sql/elements.py", line 334, in _execute_on_connection return connection._execute_clauseelement( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1577, in _execute_clauseelement ret = self._execute_context( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1953, in _execute_context self._handle_dbapi_exception( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 2134, in _handle_dbapi_exception util.raise_( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1910, in _execute_context self.dialect.do_execute( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute cursor.execute(statement, parameters) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 153, in execute result = self._query(query) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 322, in _query conn.query(q) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 575, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 826, in _read_query_result result.read() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 1203, in read first_packet = self.connection._read_packet() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 782, in _read_packet packet.raise_for_error() File "/app/.venv/lib/python3.10/site-packages/pymysql/protocol.py", line 219, in raise_for_error err.raise_mysql_exception(self._data) File "/app/.venv/lib/python3.10/site-packages/pymysql/err.py", line 150, in raise_mysql_exception raise errorclass(errno, errval) sqlalchemy.exc.ProgrammingError: (pymysql.err.ProgrammingError) (1146, "Table 'superset.logs' doesn't exist") [SQL: INSERT INTO logs (action, json, dttm, duration_ms) VALUES (%(action)s, %(json)s, %(dttm)s, %(duration_ms)s)] [parameters: {'action': 'welcome', 'json': '{"path": "/superset/welcome/", "object_ref": "Superset.welcome"}', 'dttm': datetime.datetime(2025, 10, 21, 10, 2, 17, 200564), 'duration_ms': 0}] (Background on this error at: https://sqlalche.me/e/14/f405) 2025-10-21 10:02:22,645:WARNING:root:Failed to add user to db session: Class 'werkzeug.local.LocalProxy' is not mapped 2025-10-21 10:02:22,655:ERROR:root:DBEventLogger failed to log event(s) 2025-10-21 10:02:22,655:ERROR:root:(pymysql.err.ProgrammingError) (1146, "Table 'superset.logs' doesn't exist") [SQL: INSERT INTO logs (action, json, dttm, duration_ms) VALUES (%(action)s, %(json)s, %(dttm)s, %(duration_ms)s)] [parameters: {'action': 'welcome', 'json': '{"path": "/superset/welcome/", "object_ref": "Superset.welcome"}', 'dttm': datetime.datetime(2025, 10, 21, 10, 2, 22, 652530), 'duration_ms': 1}] (Background on this error at: https://sqlalche.me/e/14/f405) Traceback (most recent call last): File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1910, in _execute_context self.dialect.do_execute( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute cursor.execute(statement, parameters) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 153, in execute result = self._query(query) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 322, in _query conn.query(q) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 575, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 826, in _read_query_result result.read() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 1203, in read first_packet = self.connection._read_packet() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 782, in _read_packet packet.raise_for_error() File "/app/.venv/lib/python3.10/site-packages/pymysql/protocol.py", line 219, in raise_for_error err.raise_mysql_exception(self._data) File "/app/.venv/lib/python3.10/site-packages/pymysql/err.py", line 150, in raise_mysql_exception raise errorclass(errno, errval) pymysql.err.ProgrammingError: (1146, "Table 'superset.logs' doesn't exist") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/app/superset/utils/log.py", line 406, in log db.session.bulk_save_objects(logs) File "<string>", line 2, in bulk_save_objects File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3705, in bulk_save_objects self._bulk_save_mappings( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3912, in _bulk_save_mappings with util.safe_reraise(): File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ compat.raise_( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3901, in _bulk_save_mappings persistence._bulk_insert( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/persistence.py", line 107, in _bulk_insert _emit_insert_statements( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/orm/persistence.py", line 1097, in _emit_insert_statements c = connection._execute_20( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1710, in _execute_20 return meth(self, args_10style, kwargs_10style, execution_options) File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/sql/elements.py", line 334, in _execute_on_connection return connection._execute_clauseelement( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1577, in _execute_clauseelement ret = self._execute_context( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1953, in _execute_context self._handle_dbapi_exception( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 2134, in _handle_dbapi_exception util.raise_( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/util/compat.py", line 211, in raise_ raise exception File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1910, in _execute_context self.dialect.do_execute( File "/app/.venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute cursor.execute(statement, parameters) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 153, in execute result = self._query(query) File "/app/.venv/lib/python3.10/site-packages/pymysql/cursors.py", line 322, in _query conn.query(q) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 575, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 826, in _read_query_result result.read() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 1203, in read first_packet = self.connection._read_packet() File "/app/.venv/lib/python3.10/site-packages/pymysql/connections.py", line 782, in _read_packet packet.raise_for_error() File "/app/.venv/lib/python3.10/site-packages/pymysql/protocol.py", line 219, in raise_for_error err.raise_mysql_exception(self._data) File "/app/.venv/lib/python3.10/site-packages/pymysql/err.py", line 150, in raise_mysql_exception raise errorclass(errno, errval) sqlalchemy.exc.ProgrammingError: (pymysql.err.ProgrammingError) (1146, "Table 'superset.logs' doesn't exist") [SQL: INSERT INTO logs (action, json, dttm, duration_ms) VALUES (%(action)s, %(json)s, %(dttm)s, %(duration_ms)s)] [parameters: {'action': 'welcome', 'json': '{"path": "/superset/welcome/", "object_ref": "Superset.welcome"}', 'dttm': datetime.datetime(2025, 10, 21, 10, 2, 22, 652530), 'duration_ms': 1}] (Background on this error at: https://sqlalche.me/e/14/f405) gapinyc@DESKTOP-9QS7RL5:~/superset-prod$
最新发布
10-22
修复 `logs` 表缺失 | `docker exec superset_app superset db upgrade` | | 2. 安装 Pillow 支持截图/PDF | 修改 Dockerfile 加 `Pillow` 并重建 | | 3. 防止重复初始化 | 使用 `.initialized` 标记文件控制 `...
开源BI分析工具 -- superset安装
臭臭猫
04-11 3159
本文章主要介绍superset的安装，用于连接到kylin数据库，做可视化数据分析用。superset连接kylin的案例分析将在下篇博客中介绍。本人kylin安装节点是 6、7、8superset安装节点为8，8的资源利用率最少，安装时为最新版，下面参考文档中有些配置已经过时，因此写下此博客供最新版本的安装。OS: centos7Superset版本：0.22.1Python版本：2.7 vir...
如何将Superset图表嵌入html
11-22
superset配置图表免登陆访问，之后可将图表嵌入到html系统中
Superset集成到iframe 跨域 无需账号登录
软件工程小施同学 的专栏
03-15 7163
一、安装superset 二、嵌入到iframe 1. 设置匿名用户权限 找到superset容器 docker ps -a | grep superset 然后以root帐户进入容器的工作目录： docker exec -it --user root cc04 /bin/bash 找到配置文件config.py /usr/local/python3/lib/python3.6/site-packages/superset/config.py 修改config.py配..
superset安全与权限（3）
京河小蚁的博客
12-22 2519
目录 提供的角色 Admin Alpha Gamma Sql_lab Public 管理每个数据源访问的Gamma 自定义 权限 限制对数据源子集的访问 Superset中的安全性由Flask AppBuilder（FAB）处理。FAB是一个“简单快速的应用程序开发框架，建立在Flask之上”。FAB提供身份验证、用户管理、权限和角色。请阅读其安全文件https://flas...
Superset从配置到使用系列之四：集成Superset到自己的前端项目中
m0_47448095的博客
10-17 6212
需求描述 数据看板页面如果不用登录就可以访问 集成进来的页面，样式如何修改？比如隐藏头部菜单 数据看板去除登录 分享面板，拿到链接，如果此时直接在其他浏览器访问，就会直接跳转到登录页面 解决思路 1、权限不够就需要赋予权限，找到需要赋权的对象 通过查看源代码可以发现这些访问都是通过public角色的； 2、角色权限 Admin：拥有所有权限； Alpha：能访问所有数据源，增加或者更改数据源，但不能更改其他用户权限； Gamma：必须结合其他能访问数据源的角色才能访问数据。这个角色所能访问
Superset 无需登录访问分享的图表
weixin_53185499的博客
08-26 1544
在浏览器新打开superset分享的链接，不需要登录就可以看到，即设置成功。环境变量没有正确设置，指向Flask应用的入口点。可以看到public和gamma权限一致。superset init 执行前执行。
superset权限管理
小小北漂
12-27 3480
Superset支持用户自定义创建一个角色，例如：您可以创建一个角色Financial Analyst，该角色将由一组数据源（表）和/或数据库组成。然后用户将被授予Gamma，sql_lab，或者自定义角色都可以。 Superset的默认角色有：Admin、Alpha、Gamma、sql_lab、Public，下面介绍一下详细介绍一下每个角色的权限： 1、Admin 管理员有所有的权利，其中...
云主机superset接入redis缓存
微电子学与固体电子学-俞驰
09-20 2583
环境 环境 版本 Ubuntu 18.04 apache-superset (pip install apache-superset) 0.37.1 Mysql 5.7 redis-cli 4.0.9 调研 [1]提到了二级缓存 [4]提到如果配置cache成功会有相关信息 准备工作 apt install redis (virtualenv环境)pip installredis 编辑 ...
Superset免登录访问分享的仪表（设置SUPERSET可以匿名访问图表）
DraGon_HooRay的博客
10-15 5696
目标：匿名（不需要登录）即可访问superset图表（我的环境是在docker中） 一，superset角色介绍 角色权限介绍 Admin：拥有所有权限。 Alpha：能访问所有数据源，增加或者更改数据源，但不能给更改其他用户权限。 Gamma：必须结合其他能访问数据源的角色才能访问数据。这个角色所能访问的切片和看板，也是基于能访问数据源所创建的切片和看板。 sql_lab：能访问SQL Lab菜单。 Public：默认没有任何权限。 二、具体实现 1.最终目标：使grama和public权限一致（默.
配置superset
qq_40104240的博客
10-26 1181
配置superset 配置 在配置应用之前，你需要创建一个配置文件：superset_config.py，并将其添加到PythonPath中(python路径)。以下有一些参数，你可以配置到该文件中： # Superset specific config # 行数限制、web服务端口配置 ROW_LIMIT = 5000 SUPERSET_WEBSERVER_PORT = 8088 # Flask App Builder configuration # Your App secret key # 密钥
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值