[03:31:05] PROBLEM - apt on db2002 is CRITICAL: APT CRITICAL: 3 packages available for upgrade (3 critical updates). [06:18:08] RECOVERY - apt on db2002 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [09:18:10] PROBLEM - apt on tools2002 is CRITICAL: APT CRITICAL: 3 packages available for upgrade (3 critical updates). [12:30:00] PROBLEM - apt on bots2002 is CRITICAL: APT CRITICAL: 3 packages available for upgrade (3 critical updates). [18:34:03] RECOVERY - apt on bots2002 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [18:35:03] $log apply security apt updates on bots2002 [18:35:12] Saved item "apply security apt updates on bots2002" [18:37:38] $log apply security apt updates on tools2002 [18:37:47] Saved item "apply security apt updates on tools2002" [18:38:09] RECOVERY - apt on tools2002 is OK: APT OK: 0 packages available for upgrade (0 critical updates). [19:03:29] .gj Sario [19:03:29] You're doing good work, Sario! [20:05:40] Ty Sario [20:08:23] I couldn't get into db2002, it kept refusing the password, so it still needs to be upgraded [20:10:45] Weird [20:13:07] Sario: can you not use normal ssh [20:13:13] What error did it give [20:13:20] It should accept your key [20:22:25] Sario: the logs don’t show any record of you trying to connect [20:25:31] Hmm, that is weird. It would have been right after I did tools [20:55:26] I got into db2002, apt was up to date