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

issue: warning "Cannot invoke 'uname` to get architecture type" emitted #104

Closed
MarioninD opened this issue Oct 9, 2024 · 8 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@MarioninD
Copy link

MarioninD commented Oct 9, 2024

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

Attaching to revolt_api_1
api_1            |  INFO  revolt_config > Starting revolt-delta@0.7.16
api_1            |  WARN  revolt_config > No Captcha key specified! Remember to add hCaptcha key.
api_1            |  **ERROR os_info::architecture > Cannot invoke 'uname` to get architecture type: Os { code: 2, kind: NotFound, message: "No such file or directory" }**
api_1            |  INFO  revolt_database::models::admin_migrations::ops::mongodb > Migrating the database.



createbuckets_1  | mc: <ERROR> Couldn't construct anonymous client for `minio`. No valid configuration found for 'minio' host alias.
createbuckets_1  | Waiting minio...
@MarioninD MarioninD added the bug Something isn't working label Oct 9, 2024
@github-project-automation github-project-automation bot moved this to 🆕 Untriaged in Revolt Project Oct 9, 2024
@JoCat
Copy link

JoCat commented Oct 9, 2024

Check to see if you can invoke the uname command on the system console

@Sirse
Copy link

Sirse commented Oct 9, 2024

Same issue. uname and uname -a works fine in host machine

@Deswolrd
Copy link

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).

@Sirse
Copy link

Sirse commented Oct 10, 2024

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.

@JVT038
Copy link

JVT038 commented Oct 13, 2024

Same error here, on Synology DS918+.

@Macarthurval
Copy link

Same issue here.

uname -a
Linux revolt-chat 5.14.0-513.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Sep 27 07:50:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

@brownian-motion
Copy link

brownian-motion commented Nov 10, 2024

I'm hosting on Linux/Ubuntu and ran into the same problem.

The error message is created in the os_info library, when i tries to run uname: https://github.com/stanislav-tkach/os_info/blob/master/os_info/src/architecture.rs#L10
Because the revolt image is stripped-down and has no executables, this library call fails to execute uname and fails.

I was able to work around it by modifying my compose.yml to manually copy uname from the original image used to build revolt in the first place.

Specifically, I made this change to my compose.yml:

BEFORE

  # API server (delta)
  api:
    image: ghcr.io/revoltchat/server:20240929-1

AFTER

  # API server (delta)
  api:
    build:
      dockerfile_inline: |
        FROM rust:1.77.2-slim-bookworm AS builder
        FROM ghcr.io/revoltchat/server:20240929-1 AS target
        COPY --from=builder /bin/uname /usr/bin/uname

@insertish insertish changed the title ?bug: Cannot invoke 'uname` to get architecture type issue: warning "Cannot invoke 'uname` to get architecture type" emitted Nov 13, 2024
@insertish insertish moved this from 🆕 Untriaged to 🕒 Backlog in Revolt Project Nov 13, 2024
@github-project-automation github-project-automation bot moved this from 🕒 Backlog to ✅ Done in Revolt Project Dec 12, 2024
@IAmTomahawkx
Copy link
Member

This is fixed in build 20241212-1

@IAmTomahawkx IAmTomahawkx self-assigned this Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

8 participants