Open datafoo opened 7 months ago
It is probably worth specifying the output of nixops check
which shows some special:
[me@laptop:~/dev/mydeployments/deployment1.example.com]$ nixops check -d deployment1.example.com --include mymachine
Machines state:
+-----------+--------+----+-----------+----------+-----------+-------+-------+
| Name | Exists | Up | Reachable | Disks OK | Load avg. | Units | Notes |
+-----------+--------+----+-----------+----------+-----------+-------+-------+
| mymachine | Yes | No | N/A | N/A | | | |
+-----------+--------+----+-----------+----------+-----------+-------+-------+
Non machines resources state:
+------+--------+
| Name | Exists |
+------+--------+
+------+--------+
mux_client_request_session: read from master failed: Broken pipe
[me@laptop:~/dev/mydeployments/deployment1.example.com]$ no such identity: /tmp/nix-shell.hgG5u9/nixops-tmp8cuxc17o/id_nixops-mymachine: No such file or directory
root@mymachine.deployment1.example.com: Permission denied (publickey).
The no such identity: /tmp/nix-shell.hgG5u9/nixops-tmp8cuxc17o/id_nixops-mymachine: No such file or directory root@mymachine.deployment1.example.com: Permission denied (publickey).
part is not something I type myself, it just pops up in the console after 1 second or 2.
When running
nixops check
, I sometime observe theConnection closed by authenticating user root
log on the target machines. When this happensnixops check
displays Up = No for the corresponding machines. But the real problem is that, if I retry multiple times, fail2ban bans my IP address because ofConnection closed by authenticating user root
:This was done running NixOps 2.0.0-pre-fc9b55c
Why is NixOps closing the SSH connection?
I have not been able to consistently reproduce the problem but I can say that it happens very often when the target machine is a Hetzner Cloud CX11 virtual machine.