On 6/23/20 4:53 AM, Adam Goryachev wrote: > I wrote the above intending to have another go at this later, and so > now I have san5 back online, and have rebooted both castle and san6, > now my status on all three is: > linstor n l > ╭───────────────────────────────────────────────────────────╮ > ┊ Node ┊ NodeType ┊ Addresses ┊ State ┊ > ╞═══════════════════════════════════════════════════════════╡ > ┊ castle ┊ SATELLITE ┊ 192.168.5.204:3366 (PLAIN) ┊ Unknown ┊ > ┊ san5 ┊ SATELLITE ┊ 192.168.5.205:3366 (PLAIN) ┊ Unknown ┊ > ┊ san6 ┊ SATELLITE ┊ 192.168.5.206:3366 (PLAIN) ┊ Unknown ┊ > ╰───────────────────────────────────────────────────────────╯ >
I suggest to check whether you can open a TCP connection from the controller to those satellite ports, e.g. just telnet from 192.168.5.204 port 3366 and see what happens. If it says "connection refused" or just hangs, then it's commonly either a network issue or a misconfigured firewall. IPv4 vs. IPv6 could also be an issue, try changing the listen addresses from ::0 to 0.0.0.0, cause sometimes on some distributions/kernels, listening on IPv6 does not implicitly listen von IPv4 as well (or alternatively, use the IPv6 global scope addresses instead of the IPv4 addresses). br, Robert _______________________________________________ Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list [email protected] https://lists.linbit.com/mailman/listinfo/drbd-user
