8 years ago
6 years ago


(Reporter: aki, Assigned: mlarrain)





8 years ago
It wasn't running buildbot, so I |sudo reboot|ed.
Then it hung around for another hour without killing my ssh session, but wouldn't allow me to sudo anything (sudo: uid 502 does not exist in the passwd file!).

At the least it needs a hard boot.
There may be something wrong with the box as well.
The error you saw during reboot occurs other places as well.  I think that whatever authentication source sudo uses gets shut down early in the shutdown process, and presumably it then got hung up on some other (hardware-related?) error.  I saw this on one of the talos leopard slaves last night when I accidentally ran 'sudo reboot' twice in quick succession.
Assignee: server-ops-releng → zandr
colo-trip: --- → sjc1
Assignee: zandr → mlarrain

Comment 2

8 years ago
After checking with Aki I hard rebooted the server.
Last Resolved: 8 years ago
Resolution: --- → FIXED
This box seems to be working fine now, and is up to date with puppet, so I've re-enabled it in slavealloc for production.
Component: Server Operations: RelEng → RelOps
Product: → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.