On Mon, 26 Apr 2021 at 16:44, Stephen John Smoogen <smooge@gmail.com> wrote:


On Mon, 26 Apr 2021 at 16:22, Pavel Raiskup <praiskup@redhat.com> wrote:
This is (probably) my fault.  I played a bit with ipv6 && libvirt, and I
rebooted the machine, and it doesn't boot up now :-( sorry for the noise.

If there's some console (VPN?) access that we could use to fix such problems
within our (CPT) team?


There is currently no way to get to the consoles for these systems. That is part of the bring up of that environment.
 

I will drive into the datacenter tomorrow to put a console on and try to rescue the box. I will have to force a root login via USB key or similar.

 
Pavel

On Monday, April 26, 2021 10:06:41 PM CEST Nagios Monitoring User wrote:
> ***** Nagios  *****
>
> Notification Type: PROBLEM
> Host: vmhost-x86-copr01.rdu-cc.fedoraproject.org
> State: DOWN
> Address: vmhost-x86-copr01.rdu-cc.fedoraproject.org
> Info: CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds.
> Source: noc01.iad2.fedoraproject.org
>
> Date/Time: Mon Apr 26 20:06:41 GMT 2021
>



_______________________________________________
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure


--
Stephen J Smoogen.



--
Stephen J Smoogen.