Open MarioninD opened 5 days ago
Check to see if you can invoke the uname
command on the system console
Same issue. uname and uname -a works fine in host machine
Not sure if it's the same issue, but looks quite the same for me. Happens when trying to connect WebSocket
events-1 | INFO revolt_config > Starting revolt-bonfire@0.7.16
events-1 | ERROR os_info::architecture > Cannot invoke 'uname` to get architecture type: Os { code: 2, kind: NotFound, message: "No such file or directory" }
Right after that, main thread collapses
events-1 | thread 'main' panicked at /home/rust/src/crates/core/presence/src/lib.rs:166:43:
events-1 | Redis connection: FailedConnection
events-1 | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
uname in host machine looks good as far as I can tell
uname -a
Linux debian 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux
Fresh setup with .env / Revolt.toml changes for external access via reverse proxy (curl and wscat from local machine directly provides the same results). Used mongo version (4.4 for older CPU as guide says).
Not sure if it's the same issue, but looks quite the same for me. Happens when trying to connect WebSocket
events-1 | INFO revolt_config > Starting revolt-bonfire@0.7.16 events-1 | ERROR os_info::architecture > Cannot invoke 'uname` to get architecture type: Os { code: 2, kind: NotFound, message: "No such file or directory" }
Right after that, main thread collapses
events-1 | thread 'main' panicked at /home/rust/src/crates/core/presence/src/lib.rs:166:43: events-1 | Redis connection: FailedConnection events-1 | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
uname in host machine looks good as far as I can tell
uname -a Linux debian 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux
Fresh setup with .env / Revolt.toml changes for external access via reverse proxy (curl and wscat from local machine directly provides the same results). Used mongo version (4.4 for older CPU as guide says).
Yes, absolutely same issue (Ubuntu 24.04.1 LTS), old homelab Intel NUC with mongo 4.4.
Same error here, on Synology DS918+.
What happened?
I can't quite understand what the error is related to, I think I did everything according to the instructions :)
docker-compose logs api and minio/mc