On Thu, Sep 13, 2018 at 12:07 AM <turboaaa@gmail.com> wrote:This is a stupid question, but how do I attach a file to this post? I am using the web form, as soon as I figure out this mailing list thing I will attach full logs (NOOOOB!!!!)Sorry, which web form?This is a mailing list: users@ovirt.org
Regardless, there are no logs before the reboot of Node1 in sanlock.log on that day. Node1 started coming back online at 10:04AM.
2018-09-08 09:19:38 3081 [1127]: s1 host 2 16 249 f9704a0b-9a09-42f4-819c-35055c1177af.node2.<host>
2018-09-10 10:03:54 5 [1154]: sanlock daemon started 3.6.0 host edfe4d27-bdbe-45e3-9e4c-a4e02b2101bd.node1.<host>
Messages has more information, and when I figure out how to attach files I will post it. Here are the entries around the reboot time. The node rebooted between 09:58:52 and 10:00:01
Sep 10 09:58:52 node1 libvirtd: 2018-09-10 13:58:52.405+0000: 2513: error : qemuDomainAgentAvailable:6946 : Guest agent is not responding: QEMU guest agent is not connected
Sep 10 09:58:52 node1 libvirtd: 2018-09-10 13:58:52.405+0000: 2514: error : qemuDomainAgentAvailable:6946 : Guest agent is not responding: QEMU guest agent is not connected
Sep 10 10:00:01 node1 systemd: Started Session 353 of user root.
Sep 10 10:00:01 node1 systemd: Starting Session 353 of user root.
Sep 10 10:03:51 node1 kernel: microcode: microcode updated early to revision 0x42d, date = 2018-04-25
Sep 10 10:03:51 node1 kernel: Initializing cgroup subsys cpuset
Sep 10 10:03:51 node1 kernel: Initializing cgroup subsys cpu
Sep 10 10:03:51 node1 kernel: Initializing cgroup subsys cpuacct
Sep 10 10:03:51 node1 kernel: Linux version 3.10.0-862.11.6.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) ) #1 SMP Tue Aug 14 21:49:04 UTC 2018
Sep 10 10:03:51 node1 kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-862.11.6.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet LANG=en_US.UTF-8
Sep 10 10:03:51 node1 kernel: e820: BIOS-provided physical RAM map:
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/