Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Bus access error" on "glances -w" #2821

Open
bcutter opened this issue Jun 8, 2024 · 7 comments
Open

"Bus access error" on "glances -w" #2821

bcutter opened this issue Jun 8, 2024 · 7 comments

Comments

@bcutter
Copy link

bcutter commented Jun 8, 2024

Describe the bug
32 bit OS and 64 bit kernel results in Bus-Zugriffsfehler ("bus access error") when running glances -w.
Was working fine before with 32 bit kernel, after switching to 64 bit kernel web refuses to start.

To Reproduce
Steps to reproduce the behavior:

  1. Start Glances with the following options '-w'
  2. See error
Glances Web User Interface started on http://0.0.0.0:61208/
INFO:     Started server process [13762]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:61208 (Press CTRL+C to quit)
Bus-Zugriffsfehler

Expected behavior
start web itnerface

Screenshots

Environement (please complete the following information)

  • Operating System (lsb_release -a or OS name/version):
Description:    Raspbian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye
  • Glances & psutil versions:
Glances version:        4.0.8
Glances API version:    4
PsUtil version:         5.9.8
Log file:               /home/pi/.local/share/glances/glances.log
  • How do you install Glances (Pypi package, script, package manager, source): pip install --user 'glances[web]'
  • Glances test (only available with Glances 3.1.7 or higher): /
Everything [OK]

Additional context

You can also pastebin:

@nicolargo
Copy link
Owner

Any relevant message in the Glances log file ? (/home/pi/.local/share/glances/glances.log)

@bcutter
Copy link
Author

bcutter commented Jun 8, 2024

No:

2024-06-08 19:50:21,050 -- INFO -- Start Glances 4.0.8
2024-06-08 19:50:21,052 -- INFO -- CPython 3.9.2 (/usr/bin/python3) and psutil 5.9.8 detected
2024-06-08 19:50:23,914 -- INFO -- Start GlancesWebServer mode
2024-06-08 19:50:23,966 -- WARNING -- Missing Python Lib (No module named 'pynvml'), Nvidia GPU plugin is disabled
2024-06-08 19:50:23,974 -- WARNING -- Missing Python Lib (No module named 'netifaces'), IP plugin is disabled
2024-06-08 19:50:23,980 -- WARNING -- Sparklines module not found (No module named 'sparklines')
2024-06-08 19:50:23,995 -- WARNING -- Missing Python Lib (No module named 'pymdstat'), Raid plugin is disabled
2024-06-08 19:50:24,360 -- WARNING -- Missing Python Lib (No module named 'pySMART'), HDD Smart plugin is disabled
2024-06-08 19:50:24,366 -- WARNING -- Error loading Docker deps Lib. Docker plugin is disabled (No module named 'docker')
2024-06-08 19:50:24,368 -- WARNING -- Error loading Podman deps Lib. Podman feature in the Containers plugin is disabled (No module named 'podman')
2024-06-08 19:50:24,961 -- INFO -- Glances RESTful API Server started on http://0.0.0.0:61208/api/4
2024-06-08 19:50:24,963 -- INFO -- Get WebUI in /home/pi/.local/lib/python3.9/site-packages/glances/outputs/static/public
2024-06-08 19:50:24,963 -- INFO -- Glances Web User Interface started on http://0.0.0.0:61208/

But I have to update my description: the error only occurs one a web browser actually tries to access glances (on http://0.0.0.0:61208), then the error is thrown immediately (visible on the console, not logged) and glances crashes.

Copy link

github-actions bot commented Sep 7, 2024

This issue is stale because it has been open for 3 months with no activity.

@RazCrimson
Copy link
Collaborator

@bcutter Did this get resolved or is the issue still present?

@bcutter
Copy link
Author

bcutter commented Sep 8, 2024

No change. No workaround, no update, nothing. Still exists.

@github-actions github-actions bot removed the inactive label Sep 9, 2024
Copy link

github-actions bot commented Dec 8, 2024

This issue is stale because it has been open for 3 months with no activity.

@bcutter
Copy link
Author

bcutter commented Dec 8, 2024

Still broken.

@github-actions github-actions bot removed the inactive label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants