# Survivor site-x-a after the 04:39:22 kill of site-x-b, BEFORE site-x's LocalDb was replicated.
# Key lines, transcribed from `docker logs scadabridge-env2-site-x-a` (the container was recreated
# at 04:42:52 to turn replication on, which discarded its docker log).
[04:39:50 WRN] [leader-auto-down] DOWNING akka.tcp://scadabridge@scadabridge-env2-site-x-b:8082: unreachable for 00:00:15 and this node (...site-x-a:8082) is leader
[04:39:51 INF] Younger observed OldestChanged: [akka.tcp://scadabridge@scadabridge-env2-site-x-b:8082 -> myself]
[04:39:51 INF] Singleton manager started singleton actor [akka://scadabridge/user/deployment-manager-singleton/deployment-manager]
[04:39:51 INF] DeploymentManagerActor starting — loading deployed configs from SQLite...
[04:39:51 INF] Loaded 1 deployed configs (1 enabled) from SQLite        <- a stale MxAlarmDemo-1 row from an earlier env2 seeding; env-soak-1 / env-galaxy-1 were never on this node
[04:39:51 INF] All 1 Instance Actors created
[04:39:51 WRN] No connection actor for ScadaBridge Site X during alarm subscribe
[04:39:51 WRN] Native alarm subscription failed for GalaxyAlarms on MxAlarmDemo-1: Unknown connection: ScadaBridge Site X; retrying in 5000ms
... repeated every 5-40 s until 04:41:06; no script runs, site_data_connections 0/0 (see seeded-unreplicated-site-x-active-kill.metrics)
