stoatchat/self-hosted
1
0
Fork 0
mirror of https://github.com/stoatchat/self-hosted.git synced 2026-07-21 04:25:24 -04:00
Code Issues 42 Packages Projects Releases Wiki Activity

bug: bonfire minio/mc eqalpha/keydb can't start #66

New Issue
Closed
opened 2026-02-16 12:51:18 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 12:51:18 -05:00
Owner
Copy Link
Copy Source

Originally created by @nyamuch1 on GitHub (Jul 27, 2024).

What happened?

image

revolt_events_1

la02@la02:~/docker/revolt$ docker logs revolt_events_1
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 INFO  revolt_config > Starting revolt-bonfire@0.7.14
thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

revolt_createbuckets_1

la02@la02:~/docker/revolt$ docker logs revolt_createbuckets_1
Added `minio` successfully.
The cluster is ready
mc: <ERROR> Unable to make bucket `minio/attachments`. Your previous request to create the named bucket succeeded and you already own it.
mc: <ERROR> Unable to make bucket `minio/avatars`. Your previous request to create the named bucket succeeded and you already own it.
mc: <ERROR> Unable to make bucket `minio/backgrounds`. Your previous request to create the named bucket succeeded and you already own it.
mc: <ERROR> Unable to make bucket `minio/icons`. Your previous request to create the named bucket succeeded and you already own it.
mc: <ERROR> Unable to make bucket `minio/banners`. Your previous request to create the named bucket succeeded and you already own it.
mc: <ERROR> Unable to make bucket `minio/emojis`. Your previous request to create the named bucket succeeded and you already own it.

revolt_redis_1 did not generate any logs

la02@la02:~/docker/revolt$ docker logs revolt_redis_1
la02@la02:~/docker/revolt$
Originally created by @nyamuch1 on GitHub (Jul 27, 2024). ### What happened? ![image](https://github.com/user-attachments/assets/213b419c-0075-4068-98b0-18b8055e4188) ## revolt_events_1 ``` la02@la02:~/docker/revolt$ docker logs revolt_events_1 INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace INFO revolt_config > Starting revolt-bonfire@0.7.14 thread 'main' panicked at 'Redis connection: FailedConnection', /home/rust/src/crates/core/presence/src/lib.rs:166:43 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` ## revolt_createbuckets_1 ``` la02@la02:~/docker/revolt$ docker logs revolt_createbuckets_1 Added `minio` successfully. The cluster is ready mc: <ERROR> Unable to make bucket `minio/attachments`. Your previous request to create the named bucket succeeded and you already own it. mc: <ERROR> Unable to make bucket `minio/avatars`. Your previous request to create the named bucket succeeded and you already own it. mc: <ERROR> Unable to make bucket `minio/backgrounds`. Your previous request to create the named bucket succeeded and you already own it. mc: <ERROR> Unable to make bucket `minio/icons`. Your previous request to create the named bucket succeeded and you already own it. mc: <ERROR> Unable to make bucket `minio/banners`. Your previous request to create the named bucket succeeded and you already own it. mc: <ERROR> Unable to make bucket `minio/emojis`. Your previous request to create the named bucket succeeded and you already own it. ``` ## revolt_redis_1 did not generate any logs ``` la02@la02:~/docker/revolt$ docker logs revolt_redis_1 la02@la02:~/docker/revolt$ ```
yindo added the bug label 2026-02-16 12:51:18 -05:00
yindo closed this issue 2026-02-16 12:51:18 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
good first issue
help wanted
improvement
pull-request
Mirrored from GitHub Pull Request
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#66
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?