You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/10/12 16:40:24 UTC
[GitHub] [superset] misumme-pg opened a new issue, #21786: superset-worker CrashLoopBackOff
misumme-pg opened a new issue, #21786:
URL: https://github.com/apache/superset/issues/21786
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Pulling 58m kubelet Pulling image "apache/superset:latest"
Normal Pulled 57m kubelet Successfully pulled image "apache/superset:latest" in 18.904111192s
Normal Created 55m (x5 over 57m) kubelet Created container superset
Normal Started 55m (x5 over 57m) kubelet Started container superset
Normal Pulled 55m (x4 over 57m) kubelet Container image "apache/superset:latest" already present on machine
Warning BackOff 3m8s (x246 over 57m) kubelet Back-off restarting failed container
Logs of the superset worker
kubectl logs -f superset-worker-867678fb57-jnkgd
Defaulted container "superset" out of: superset, wait-for-postgres (init)
Requirement already satisfied: psycopg2-binary==2.9.1 in /usr/local/lib/python3.8/site-packages (2.9.1)
Requirement already satisfied: redis==3.5.3 in /usr/local/lib/python3.8/site-packages (3.5.3)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
WARNING: You are using pip version 22.0.4; however, version 22.2.2 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
logging was configured successfully
2022-10-12 16:13:34,609:INFO:superset.utils.logging_configurator:logging was configured successfully
2022-10-12 16:13:34,612:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
2022-10-12 16:13:34,616:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
2022-10-12 16:13:34,623:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
2022-10-12 16:13:34,626:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.OperationalError) could not translate host name "CMW2gha7yrg@superset-postgresql" to address: Name or service not known
(Background on this error at: https://sqlalche.me/e/14/e3q8)
Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
Can anyone help what to do about this error???
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] superset-worker CrashLoopBackOff [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #21786: superset-worker CrashLoopBackOff
URL: https://github.com/apache/superset/issues/21786
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] superset-worker CrashLoopBackOff [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #21786:
URL: https://github.com/apache/superset/issues/21786#issuecomment-1939784279
Closing this as stale since it's been silent for so long, and we're trying to steer toward a more actionable Issues backlog. If people are still encountering this in current versions (currently 3.x) please open a new Issue or a PR to address the problem.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org