Originally from the User Slack
@Sujay_KS: hey team, we have scylla 4.6.3 running as a docker container, in ec2-server with IMDSV2 enabled, but scylla is unable to access metadata and giving error, but it works if i disable IMDS v2 has anyone faced this ? , is there any fix for this
https://stackoverflow.com/questions/71884350/using-imds-v2-with-token-inside-docker-on-ec2-or-ecs
I have also configured hop as 2 in ec2-server but still facing the error
Stack Overflow: Using IMDS (v2) with token inside docker on EC2 or ECS
error log:
INFO 2024-12-23 14:36:52,056 [shard 0] init - starting prometheus API server
INFO 2024-12-23 14:36:52,057 [shard 0] init - starting tokens manager
INFO 2024-12-23 14:36:52,057 [shard 0] init - starting migration manager notifier
INFO 2024-12-23 14:36:52,057 [shard 0] init - starting lifecycle notifier
INFO 2024-12-23 14:36:52,057 [shard 0] init - creating tracing
INFO 2024-12-23 14:36:52,057 [shard 0] init - creating snitch
scylla: locator/ec2_snitch.cc:25: auto locator::ec2_snitch::load_config()::(anonymous class)::operator()(seastar::sstring) const: Assertion `az.size()' failed.
Aborting on shard 0.
Backtrace:
0x3dbe2f8
0x3def152
0x7fab29b7fa1f
/opt/scylladb/libreloc/libc.so.6+0x3d2a1
/opt/scylladb/libreloc/libc.so.6+0x268a3
/opt/scylladb/libreloc/libc.so.6+0x26788
/opt/scylladb/libreloc/libc.so.6+0x35a15
0x2b328e3
0x2b34ac9
0x3dd0cc4
0x3dd20b7
0x3dd12fc
0x3d7aaae
0x3d79e26
0xf41135
/opt/scylladb/libreloc/libc.so.6+0x27b74
0xf3e2ed
2024-12-23 14:36:53,059 INFO success: scylla entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-12-23 14:40:15,322 INFO exited: scylla (terminated by SIGABRT (core dumped); not expected)
2024-12-23 14:40:16,325 INFO spawned: 'scylla' with pid 1027
Scylla version 4.6.3-0.20220414.8bf149fdd with build-id 8d16d8972498cc769071ff25309b009eb77bf77a 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 172.18.0.2 --rpc-address 172.18.0.2 --seed-provider-parameters seeds=10.68.10.132,10.68.11.173 --broadcast-address 10.68.10.238 --broadcast-rpc-address 10.68.10.238 --alternator-address 172.18.0.2 --blocked-reactor-notify-ms 999999999"
parsed command line options: [log-to-syslog, (positional) 0, log-to-stdout, (positional) 1, default-log-level, (positional) info, network-stack, (positional) posix, developer-mode: 1, overprovisioned, listen-address: 172.18.0.2, rpc-address: 172.18.0.2, seed-provider-parameters: seeds=10.68.10.132,10.68.11.173, broadcast-address: 10.68.10.238, broadcast-rpc-address: 10.68.10.238, alternator-address: 172.18.0.2, blocked-reactor-notify-ms, (positional) 999999999]
@Felipe_Cardeneti_Mendes: IMDsv2 support started in 5.2 — latest Scylla is 6.2 you must upgrade
@Sujay_KS: cool got it