Superset not up

[krishanthvs]

Bug description

superset is not up. It gets stuck in the loading page.Please find the screenshot for the same.
(superset-env) [root@ip-192-168-3-20 superset]# superset run -h 0.0.0.0 -p 8088
Loaded your LOCAL configuration at [/home/ec2-user/superset/superset_config.py]

• Serving Flask app 'superset.app:create_app()'
• Debug mode: on
  2024-10-22 12:37:01,203:INFO:werkzeug:WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
• Running on all addresses (0.0.0.0)
• Running on http://127.0.0.1:8088
• Running on http://192.168.3.20:8088
  2024-10-22 12:37:01,203:INFO:werkzeug:Press CTRL+C to quit
  2024-10-22 12:37:01,204:INFO:werkzeug: * Restarting with stat
  Loaded your LOCAL configuration at [/home/ec2-user/superset/superset_config.py]
  2024-10-22 12:37:03,146:DEBUG:superset.utils.logging_configurator:logging was configured successfully
  2024-10-22 12:37:03,151:DEBUG:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
  2024-10-22 12:37:05,185:WARNING:werkzeug: * Debugger is active!
  2024-10-22 12:37:05,188:INFO:werkzeug: * Debugger PIN: 314-530-554
  2024-10-22 12:38:33,701:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:33] "GET / HTTP/1.1" 302 -
  2024-10-22 12:38:34,044:WARNING:root:Class 'werkzeug.local.LocalProxy' is not mapped
  2024-10-22 12:38:34,045:DEBUG:superset.stats_logger:[stats_logger] (incr) welcome
  2024-10-22 12:38:34,057:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /superset/welcome/ HTTP/1.1" 302 -
  2024-10-22 12:38:34,406:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /login/ HTTP/1.1" 200 -
  2024-10-22 12:38:34,526:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /static/appbuilder/css/bootstrap.min.css HTTP/1.1" 200 -
  2024-10-22 12:38:34,638:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /static/appbuilder/css/fontawesome/v4-shims.min.css HTTP/1.1" 200 -
  2024-10-22 12:38:34,656:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /static/appbuilder/css/ab.css HTTP/1.1" 200 -
  2024-10-22 12:38:34,664:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /static/appbuilder/js/jquery-latest.js HTTP/1.1" 200 -
  2024-10-22 12:38:34,716:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /static/appbuilder/js/ab_filters.js HTTP/1.1" 200 -
  2024-10-22 12:38:34,736:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /static/appbuilder/js/ab_actions.js HTTP/1.1" 200 -
  2024-10-22 12:38:34,739:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /static/appbuilder/js/bootstrap.min.js HTTP/1.1" 200 -
  2024-10-22 12:38:34,754:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /static/appbuilder/js/bootstrap-datepicker/bootstrap-datepicker.min.js HTTP/1.1" 200 -
  2024-10-22 12:38:34,834:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /static/appbuilder/js/ab.js HTTP/1.1" 200 -
  2024-10-22 12:38:34,838:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:34] "GET /static/appbuilder/js/select2/select2.min.js HTTP/1.1" 200 -
  2024-10-22 12:38:55,603:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:55] "POST /login/ HTTP/1.1" 302 -
  2024-10-22 12:38:55,675:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:55] "GET / HTTP/1.1" 302 -
  2024-10-22 12:38:56,067:DEBUG:superset.stats_logger:[stats_logger] (incr) welcome
  2024-10-22 12:38:56,083:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:38:56] "GET /superset/welcome/ HTTP/1.1" 200 -
  2024-10-22 12:50:41,189:DEBUG:superset.stats_logger:[stats_logger] (incr) welcome
  2024-10-22 12:50:41,209:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:50:41] "GET /superset/welcome/ HTTP/1.1" 200 -
  2024-10-22 12:50:50,035:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:50:50] "GET / HTTP/1.1" 302 -
  2024-10-22 12:50:50,173:DEBUG:superset.stats_logger:[stats_logger] (incr) welcome
  2024-10-22 12:50:50,182:INFO:werkzeug:106.51.85.80 - - [22/Oct/2024 12:50:50] "GET /superset/welcome/ HTTP/1.1" 200 -
  

Screenshots/recordings

The superset is not up. Its in loading state continuously.

Superset version

master / latest-dev

Python version

3.11

Node version

I don't know

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[krishanthvs]

@dosu can you please check on this

[dosubot]

I found a similar open issue titled Async queries and Cache not working as expected, which was last updated on October 21, 2024. This issue might be related to your problem of Superset being stuck in a loading state. Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Redis Configuration: Ensure that your Redis configuration is correctly set up in the superset_config.py file. Check that the CACHE_CONFIG and DATA_CACHE_CONFIG are correctly pointing to your Redis instance and that the CACHE_TYPE is set to 'RedisCache'.

2. Async Queries Configuration: Verify that the GLOBAL_ASYNC_QUERIES feature flag is enabled and that the GLOBAL_ASYNC_QUERIES_TRANSPORT is set to 'polling' or 'ws' as per your setup.

3. Celery Configuration: Make sure that the Celery broker and result backend are correctly configured to use Redis, and that the Celery workers are running properly.

4. JWT Secret: Ensure that the GLOBAL_ASYNC_QUERIES_JWT_SECRET is set correctly, as this is crucial for async query authentication.

If the issue persists, you might want to look into the specific error messages or logs related to async queries and caching in Superset 4.0.2, which can provide more detailed insights into what might be going wrong ^[1].

To continue talking to Dosu, mention @dosu.

[krishanthvs]

@dosu its not a similar issue

[dosubot]

If the issue with Superset being stuck in a loading state is not related to async queries and caching, consider checking the following areas:

1. Static Assets: Ensure that static assets are loading correctly. Superset preloads static assets using <link rel="preload" as="style"> tags, and these need to be correctly set up. If the assets_prefix is not set correctly or the assets are not available at the specified paths, it could cause loading issues ^[1].

2. Session Management: Verify that session management is configured properly. Misconfigurations in session settings, such as SESSION_COOKIE_SECURE being set to True without HTTPS, can cause issues. Also, check if server-side sessions are enabled and if there are any issues with the session backend, like Redis ^[2].

3. Browser Console: Check the browser's developer console for any JavaScript errors or failed network requests that might indicate what is causing the loading issue.

4. Logs: Review the Superset logs for any errors or warnings that could provide more insight into the problem.

These steps should help identify the root cause of the loading issue. If you have specific error messages or logs, they could provide more clues.

To continue talking to Dosu, mention @dosu.

[krishanthvs]

@rusackas can you please help me on this

[tshallenberger]

At first glance, it doesn't look the UI was built properly. See:
https://superset.apache.org/docs/contributing/development/#frontend
Once you have ran the npm commands listed, try again and report back.

[krishanthvs]

@tshallenberger It was fixed using the npm commands. Thank you

[gongyuanze111]

@tshallenberger It was fixed using the npm commands. Thank you

@krishanthvs May I ask which commands did u use and how did you fix the problem. Same issue here and I tried purging npm and rebuilding. Didn't solve the problem.