I’ve been attempting to set up ScyllaDB on Fly.io using the following command:
fly deploy --image scylladb/scylla:latest
Unfortunately, I’m encountering a recurring error:
Scylla version 5.2.2-0.20230521.9dd70a58c3f9 with build-id d692f21f4fc0ee40fac88d4bdef5d4f0999127ba starting ...
command used: "/usr/bin/scylla --log-to-syslog 0 --log-to-stdout 1 --default-log-level info --network-stack posix --developer-mode=1 --overprovisioned --listen-address 2605:4c40:42:c3f1:0:11c8:67b4:1 172.19.132.66 --rpc-address 2605:4c40:42:c3f1:0:11c8:67b4:1 172.19.132.66 --seed-provider-parameters seeds=2605:4c40:42:c3f1:0:11c8:67b4:1 172.19.132.66 --alternator-address 2605:4c40:42:c3f1:0:11c8:67b4:1 172.19.132.66 --blocked-reactor-notify-ms 999999999"
error: too many positional options have been specified on the command line
Try --help.
This error suggests that too many positional options have been specified on the command line. Despite numerous attempts over the last couple of days, which also included creating my own Dockerfile, I’ve been unable to rectify this issue.
Has anyone here successfully set up ScyllaDB or Cassandra on Fly.io and can provide some guidance on this? Any insights or suggestions would be greatly appreciated.
I haven’t however … if the cause is simply the command is too long (too many options), you could avoid that by using a scylla.yml file. I’m thinking if you specify all the flags/params in there, the command would not need to be so long .
Starts the docker image as expected and awaits connections. An issue I’m running into now is actually connecting, I assigned a ipv4 address to the machine and when I connect from my localhost, the following is printed to console:
2023-06-10T16:49:22.653 proxy[32874430c76485] atl [error] instance refused connection. is your app listening on 0.0.0.0:9042? make sure it is not only listening on 127.0.0.1 (hint: look at your startup logs, servers often print the address they are listening on)
I’ve even tried fly proxy 9042:9042 --app scylla-dev but when connecting from localhost times out w/ no console logs.
Given that error message, a few random things you could try. Once again: total guesses!
Try changing 0.0.0.0 to :: Fly uses IPv6 internally and so I wonder if your local machine can connect to the proxy, but maybe it can’t connect to the app. Shouldn’t be the case but can’t hurt.
I’ve seen commands where they use e.g --port 9042:9042. Should be equivalent, but hey, can’t hurt.