Error: redis not ready: exit status 1

[juan-vilas]

Describe the bug

Everything was working fine but since a couple of days ago the project stopped working with the following message:
redis not ready is preventing the project to start.
Logs:

...
[mongo] {"t":{"$date":"2026-04-11T19:07:59.712+00:00"},"s":"I",  "c":"CONTROL",  "id":23138,   "ctx":"SignalHandler","msg":"Shutting down","attr":{"exitCode":0}}

Error:
 > redis not ready: exit status 1

I was using version 1.3.1-2026-02-16. I tried to update to version 1.4.1-2026-03-25 to see if it was fixed but no luck.

To Reproduce

I run this script in a VPS:

docker run -d \
    -e ANY_SYNC_BUNDLE_INIT_EXTERNAL_ADDRS="example.com“ \
    -e ANY_SYNC_BUNDLE_INIT_S3_BUCKET="my-bucket-0000“ \
    -e ANY_SYNC_BUNDLE_INIT_S3_ENDPOINT=“https://s3.eu-central-003.backblazeb2.com“ \
    -e ANY_SYNC_BUNDLE_INIT_S3_REGION="eu-central-003“ \
    -e AWS_ACCESS_KEY_ID="<my-access-key>“ \
    -e AWS_SECRET_ACCESS_KEY="<my-secret-key>“ \
    -p 33010:33010 \
    -p 33020:33020/udp \
    -v $(pwd)/data:/data \
    --restart unless-stopped \
  ghcr.io/grishy/any-sync-bundle:1.4.1-2026-03-25

Expected behavior

run the project

Actual behavior

...
[mongo] {"t":{"$date":"2026-04-11T19:07:59.712+00:00"},"s":"I",  "c":"CONTROL",  "id":23138,   "ctx":"SignalHandler","msg":"Shutting down","attr":{"exitCode":0}}

Error:
 > redis not ready: exit status 1

Environment

• Deployment: minimal container with external Backblaze file storage
• Version/tag: 1.4.1-2026-03-25
• OS/Arch: Ubuntu 24.04.3 LTS

[grishy]

Thank you, can you collect more logs above?
redis not ready: exit status 1 - this is only the final result, not the logs.

Also note that the start parameters work only on the first start. This is why *_INIT_* is used. So, you also need to check the bundle-config.yml file.

[juan-vilas]

I fixed it by adding start-bundle at the end 🎉
It was using start-all-in-one.
Final command in case it helps anyone:

docker run -d \
    -e ANY_SYNC_BUNDLE_INIT_EXTERNAL_ADDRS="example.com“ \
    -e ANY_SYNC_BUNDLE_INIT_S3_BUCKET="my-bucket-0000“ \
    -e ANY_SYNC_BUNDLE_INIT_S3_ENDPOINT=“https://s3.eu-central-003.backblazeb2.com“ \
    -e ANY_SYNC_BUNDLE_INIT_S3_REGION="eu-central-003“ \
    -e AWS_ACCESS_KEY_ID="<my-access-key>“ \
    -e AWS_SECRET_ACCESS_KEY="<my-secret-key>“ \
    -p 33010:33010 \
    -p 33020:33020/udp \
    -v $(pwd)/data:/data \
    --restart unless-stopped \
  ghcr.io/grishy/any-sync-bundle:1.3.1-2026-02-16 \
  start-bundle

But now it's showing the following error: connection refused, any idea what is happening?
Thanks in advance, this is a super project! 😁

2026-04-13T19:37:03.367Z        INFO    cli     ✓ service initialized   {"name": "coordinator"}
2026-04-13T19:37:03.367Z        INFO    cli     ▶ initializing service  {"name": "consensus"}
2026-04-13T19:37:03.367Z        INFO    cli     ✓ service initialized   {"name": "consensus"}
2026-04-13T19:37:03.367Z        INFO    cli     ▶ initializing service  {"name": "filenode"}
2026-04-13T19:37:03.375Z        INFO    cli     ✓ service initialized   {"name": "filenode"}
2026-04-13T19:37:03.375Z        INFO    cli     ▶ initializing service  {"name": "sync"}
2026-04-13T19:37:03.376Z        INFO    cli     ✓ service initialized   {"name": "sync"}
2026-04-13T19:37:03.377Z        INFO    cli     ✓ all services initialized, all DRPC handlers registered
2026-04-13T19:37:03.377Z        INFO    cli     ━━━ Phase 2: Running all services ━━━
2026-04-13T19:37:03.377Z        INFO    cli     ▶ running service       {"name": "coordinator"}
2026-04-13T19:37:23.368Z        INFO    coordinator.acl GC: removed 0; cache size: 0
2026-04-13T19:37:23.368Z        INFO    consensus.stream.consensus.stream       GC: removed 0; cache size: 0
2026-04-13T19:37:33.367Z        INFO    common.net.pool GC: removed 0; cache size: 0
2026-04-13T19:37:33.367Z        INFO    common.net.pool GC: removed 0; cache size: 0
2026/04/13 19:37:33 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 7168 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
2026-04-13T19:37:33.382Z        INFO    net.transport.yamux     yamux listener started  {"localAddr": "[::]:33010"}
2026-04-13T19:37:33.382Z        WARN    common.nodeconf periodic call error     {"error": "server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: 127.0.0.1:27017, Type: Unknown, Last error: dial tcp 127.0.0.1:27017: connect: connection refused }, ] }"}
2026-04-13T19:37:33.384Z        INFO    net.transport.quic      quic listener started   {"localAddr": "[::]:33020"}
2026-04-13T19:37:43.367Z        INFO    coordinator.acl GC: removed 0; cache size: 0
2026-04-13T19:37:43.368Z        INFO    consensus.stream.consensus.stream       GC: removed 0; cache size: 0

[grishy]

start-bundle requires that you have Redis outside of the container.
start-all-in-one starts Redis inside the container next to any-sync-bundle, also with MongoDB.

So you need to start Redis externally with a Bloom filter configured now and provide address to any-sync-bundle 🙂

[grishy]

Can you share initial logs start-all-in-one? I think you didn't clean up data/ dir. while changing parameters

[juan-vilas]

Okay I think what is happening is that the container restarted and created a new client-config.yml.
Now I have to import this new client configuration (I have to logout for this). But I have some files that did not sync, is there a way to tell the server to use the previous client-config so that I don't lose these files?