Hello @romaric we are running into a similar issue.
We changed the settings as required (I think). For us, ScyllaDB got corrupted somehow. We had to remove a bunch of the scylladb system tables to even get ScyllaDB to start up:
e[36mscylladb_1 |e[0m ERROR 2021-03-02 14:30:02,459 [shard 0] database - Exception while populating keyspace 'system_schema' with column family 'dropped_columns' from file '/var/lib/scylla/data/system_schema/dropped_columns-5e7583b5f3f43af19a39b7e1d6f5f11f': sstables::malformed_sstable_exception (invalid version for file md-1591-big-TOC.txt. Name doesn't match any known version.)
e[36mscylladb_1 |e[0m ERROR 2021-03-02 14:30:02,459 [shard 0] database - Exception while populating keyspace 'system_schema' with column family 'types' from file '/var/lib/scylla/data/system_schema/types-5a8b1ca866023f77a0459273d308917a': sstables::malformed_sstable_exception (invalid version for file md-19530-big-TOC.txt. Name doesn't match any known version.)
e[36mscylladb_1 |e[0m ERROR 2021-03-02 14:30:02,459 [shard 0] database - Exception while populating keyspace 'system_schema' with column family 'indexes' from file '/var/lib/scylla/data/system_schema/indexes-0feb57ac311f382fba6d9024d305702f': sstables::malformed_sstable_exception (invalid version for file md-1543-big-Data.db. Name doesn't match any known version.)
e[36mscylladb_1 |e[0m ERROR 2021-03-02 14:30:02,459 [shard 0] database - Exception while populating keyspace 'system_schema' with column family 'triggers' from file '/var/lib/scylla/data/system_schema/triggers-4df70b666b05325195a132b54005fd48': sstables::malformed_sstable_exception (invalid version for file md-19530-big-TOC.txt. Name doesn't match any known version.)
e[36mscylladb_1 |e[0m ERROR 2021-03-02 14:30:02,459 [shard 0] database - Exception while populating keyspace 'system_schema' with column family 'views' from file '/var/lib/scylla/data/system_schema/views-9786ac1cdd583201a7cdad556410c985': sstables::malformed_sstable_exception (invalid version for file md-1158-big-Index.db. Name doesn't match any known version.)
e[36mscylladb_1 |e[0m ERROR 2021-03-02 14:30:02,459 [shard 0] database - Exception while populating keyspace 'system_schema' with column family 'keyspaces' from file '/var/lib/scylla/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6': sstables::malformed_sstable_exception (invalid version for file md-1718-big-Statistics.db. Name doesn't match any known version.)
After removing all offending files as per ScyllaDB docs ScyllaDB at least was able to start again.
However, we are now at the same point that @moreno is. Our ScyllaDB does show up at the IP you suggested. Some relevant parts from docker inspect:
"PortBindings": {
"9042/tcp": [
{
"HostIp": "",
"HostPort": "9042"
}
]
},
...
"IPAddress": "172.18.0.2",
Using the command that @moreno posted, ScyllaDB seems to report it is working:
docker exec -it twake_scylladb_1 nodetool status
Datacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns Host ID Rack
UN 172.18.0.2 199.33 KB 256 ? 023db100-54f4-45f9-8f1e-93bff347865e rack1
Note: Non-system keyspaces don't have the same replication settings, effective ownership information is meaningless
However, using your curl suggestion appears to provide the same problem for us:
$ curl 127.0.0.1:9042
curl: (1) Received HTTP/0.9 when not allowed
The migrate script then also does not work as intended of course:
yarn run v1.22.5
$ tsc && node dist/start.js
NoHostAvailableError: All host(s) tried for query failed. First host tried, 172.18.0.2:9042: DriverError: Connection timeout
at Socket.connectTimedOut (/usr/src/app/node_modules/cassandra-driver/lib/connection.js:205:19)
at Object.onceWrapper (events.js:420:28)
at Socket.emit (events.js:314:20)
at Socket._onTimeout (net.js:483:8)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7) {
info: 'Cassandra Driver Error'
}. See innerErrors.
at ControlConnection._borrowFirstConnection (/usr/src/app/node_modules/cassandra-driver/lib/control-connection.js:301:15)
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
info: 'Represents an error when a query cannot be performed because no host is available or could be reached by the driver.',
innerErrors: {
'172.18.0.2:9042': DriverError: Connection timeout
at Socket.connectTimedOut (/usr/src/app/node_modules/cassandra-driver/lib/connection.js:205:19)
at Object.onceWrapper (events.js:420:28)
at Socket.emit (events.js:314:20)
at Socket._onTimeout (net.js:483:8)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7) {
info: 'Cassandra Driver Error'
}
}
}
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
It would seem that there is something else broken or misconfigured on our end.