Jul 31 00:16:07 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8371" x-info="http://www.rsyslog.com"] start
Jul 31 00:16:07 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 31 00:16:07 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 31 00:16:07 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 31 00:16:07 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 31 00:16:07 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 31 00:16:07 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 31 00:16:07 node-2 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 31 00:16:07 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=69b270f3-b4c4-47b8-8641-5ced645b037d nomdmonddf nomdmonisw
Jul 31 00:16:07 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 31 00:16:07 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 31 00:16:07 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 31 00:16:07 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 31 00:16:07 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 31 00:16:07 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 31 00:16:07 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 31 00:16:07 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 31 00:16:07 node-2 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 31 00:16:07 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 31 00:16:07 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 31 00:16:07 node-2 kernel: [    0.000000] No AGP bridge found
Jul 31 00:16:07 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 31 00:16:07 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 31 00:16:07 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 31 00:16:07 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 31 00:16:07 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 31 00:16:07 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 31 00:16:07 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 31 00:16:07 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 31 00:16:07 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 31 00:16:07 node-2 kernel: [    0.000000]   2 disabled
Jul 31 00:16:07 node-2 kernel: [    0.000000]   3 disabled
Jul 31 00:16:07 node-2 kernel: [    0.000000]   4 disabled
Jul 31 00:16:07 node-2 kernel: [    0.000000]   5 disabled
Jul 31 00:16:07 node-2 kernel: [    0.000000]   6 disabled
Jul 31 00:16:07 node-2 kernel: [    0.000000]   7 disabled
Jul 31 00:16:07 node-2 kernel: [    0.000000]   8 disabled
Jul 31 00:16:07 node-2 kernel: [    0.000000]   9 disabled
Jul 31 00:16:07 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 31 00:16:07 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 31 00:16:07 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 31 00:16:07 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 31 00:16:07 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 31 00:16:07 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 31 00:16:07 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 31 00:16:07 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 31 00:16:07 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 31 00:16:07 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 31 00:16:07 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 31 00:16:07 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 31 00:16:07 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 31 00:16:07 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 31 00:16:07 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 31 00:16:07 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 31 00:16:07 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 31 00:16:07 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 31 00:16:07 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 31 00:16:07 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 31 00:16:07 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 31 00:16:07 node-2 kernel: [    0.000000] Zone ranges:
Jul 31 00:16:07 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 31 00:16:07 node-2 kernel: [    0.000000] Early memory node ranges
Jul 31 00:16:07 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 31 00:16:07 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 31 00:16:07 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 31 00:16:07 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 31 00:16:07 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 31 00:16:07 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 31 00:16:07 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 31 00:16:07 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 31 00:16:07 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 31 00:16:07 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 31 00:16:07 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 31 00:16:07 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 31 00:16:07 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 31 00:16:07 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 31 00:16:07 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 31 00:16:07 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 31 00:16:07 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 31 00:16:07 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 31 00:16:07 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 31 00:16:07 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 31 00:16:07 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 31 00:16:07 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 31 00:16:07 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 31 00:16:07 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 31 00:16:07 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 31 00:16:07 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 31 00:16:07 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=69b270f3-b4c4-47b8-8641-5ced645b037d nomdmonddf nomdmonisw
Jul 31 00:16:07 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 31 00:16:07 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 31 00:16:07 node-2 kernel: [    0.000000] Checking aperture...
Jul 31 00:16:07 node-2 kernel: [    0.000000] No AGP bridge found
Jul 31 00:16:07 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 31 00:16:07 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 31 00:16:07 node-2 kernel: [    0.000000] Memory: 32653320K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Jul 31 00:16:07 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 31 00:16:07 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 31 00:16:07 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 31 00:16:07 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 31 00:16:07 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 31 00:16:07 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 31 00:16:07 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 31 00:16:07 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 31 00:16:07 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 31 00:16:07 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 31 00:16:07 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 31 00:16:07 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 31 00:16:07 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 31 00:16:07 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 31 00:16:07 node-2 kernel: [    0.004000] tsc: Detected 3492.256 MHz processor
Jul 31 00:16:07 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.51 BogoMIPS (lpj=13969024)
Jul 31 00:16:07 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 31 00:16:07 node-2 kernel: [    0.000043] Security Framework initialized
Jul 31 00:16:07 node-2 kernel: [    0.000062] AppArmor: AppArmor initialized
Jul 31 00:16:07 node-2 kernel: [    0.000063] Yama: becoming mindful.
Jul 31 00:16:07 node-2 kernel: [    0.001452] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 31 00:16:07 node-2 kernel: [    0.006320] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 31 00:16:07 node-2 kernel: [    0.008244] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 31 00:16:07 node-2 kernel: [    0.008272] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 31 00:16:07 node-2 kernel: [    0.008568] Initializing cgroup subsys memory
Jul 31 00:16:07 node-2 kernel: [    0.008576] Initializing cgroup subsys devices
Jul 31 00:16:07 node-2 kernel: [    0.008578] Initializing cgroup subsys freezer
Jul 31 00:16:07 node-2 kernel: [    0.008580] Initializing cgroup subsys blkio
Jul 31 00:16:07 node-2 kernel: [    0.008582] Initializing cgroup subsys perf_event
Jul 31 00:16:07 node-2 kernel: [    0.008584] Initializing cgroup subsys hugetlb
Jul 31 00:16:07 node-2 kernel: [    0.008604] CPU: Physical Processor ID: 0
Jul 31 00:16:07 node-2 kernel: [    0.008605] CPU: Processor Core ID: 0
Jul 31 00:16:07 node-2 kernel: [    0.008609] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 31 00:16:07 node-2 kernel: [    0.008609] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 31 00:16:07 node-2 kernel: [    0.009303] mce: CPU supports 22 MCE banks
Jul 31 00:16:07 node-2 kernel: [    0.009331] CPU0: Thermal monitoring enabled (TM1)
Jul 31 00:16:07 node-2 kernel: [    0.009351] process: using mwait in idle threads
Jul 31 00:16:07 node-2 kernel: [    0.009354] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 31 00:16:07 node-2 kernel: [    0.009354] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 31 00:16:07 node-2 kernel: [    0.009354] tlb_flushall_shift: 6
Jul 31 00:16:07 node-2 kernel: [    0.009443] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 31 00:16:07 node-2 kernel: [    0.010167] ACPI: Core revision 20131115
Jul 31 00:16:07 node-2 kernel: [    0.022848] ACPI: All ACPI Tables successfully acquired
Jul 31 00:16:07 node-2 kernel: [    0.023008] ftrace: allocating 28617 entries in 112 pages
Jul 31 00:16:07 node-2 kernel: [    0.031823] dmar: Host address width 46
Jul 31 00:16:07 node-2 kernel: [    0.031825] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 31 00:16:07 node-2 kernel: [    0.031831] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 31 00:16:07 node-2 kernel: [    0.031833] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 31 00:16:07 node-2 kernel: [    0.031837] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 31 00:16:07 node-2 kernel: [    0.031838] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 31 00:16:07 node-2 kernel: [    0.031840] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 31 00:16:07 node-2 kernel: [    0.031841] dmar: ATSR flags: 0x0
Jul 31 00:16:07 node-2 kernel: [    0.031842] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 31 00:16:07 node-2 kernel: [    0.031843] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 31 00:16:07 node-2 kernel: [    0.031959] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 31 00:16:07 node-2 kernel: [    0.031960] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 31 00:16:07 node-2 kernel: [    0.031961] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 31 00:16:07 node-2 kernel: [    0.031962] HPET id 0 under DRHD base 0xc7ffc000
Jul 31 00:16:07 node-2 kernel: [    0.031963] Your BIOS is broken and requested that x2apic be disabled.
Jul 31 00:16:07 node-2 kernel: [    0.031963] This will slightly decrease performance.
Jul 31 00:16:07 node-2 kernel: [    0.031963] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 31 00:16:07 node-2 kernel: [    0.032394] Enabled IRQ remapping in xapic mode
Jul 31 00:16:07 node-2 kernel: [    0.032395] x2apic not enabled, IRQ remapping is in xapic mode
Jul 31 00:16:07 node-2 kernel: [    0.032398] Switched APIC routing to physical flat.
Jul 31 00:16:07 node-2 kernel: [    0.033025] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 31 00:16:07 node-2 kernel: [    0.072679] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 31 00:16:07 node-2 kernel: [    0.072684] TSC deadline timer enabled
Jul 31 00:16:07 node-2 kernel: [    0.072692] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 31 00:16:07 node-2 kernel: [    0.072698] ... version:                3
Jul 31 00:16:07 node-2 kernel: [    0.072699] ... bit width:              48
Jul 31 00:16:07 node-2 kernel: [    0.072700] ... generic registers:      4
Jul 31 00:16:07 node-2 kernel: [    0.072700] ... value mask:             0000ffffffffffff
Jul 31 00:16:07 node-2 kernel: [    0.072702] ... max period:             0000ffffffffffff
Jul 31 00:16:07 node-2 kernel: [    0.072702] ... fixed-purpose events:   3
Jul 31 00:16:07 node-2 kernel: [    0.072703] ... event mask:             000000070000000f
Jul 31 00:16:07 node-2 kernel: [    0.074140] x86: Booting SMP configuration:
Jul 31 00:16:07 node-2 kernel: [    0.088266] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 31 00:16:07 node-2 kernel: [    0.074142] .... node  #0, CPUs:        #1  #2  #3
Jul 31 00:16:07 node-2 kernel: [    0.116183] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 31 00:16:07 node-2 kernel: [    0.270145] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 31 00:16:07 node-2 kernel: [    0.325760] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 31 00:16:07 node-2 kernel: [    0.382218] x86: Booted up 2 nodes, 16 CPUs
Jul 31 00:16:07 node-2 kernel: [    0.382221] smpboot: Total of 16 processors activated (111764.40 BogoMIPS)
Jul 31 00:16:07 node-2 kernel: [    0.405701] devtmpfs: initialized
Jul 31 00:16:07 node-2 kernel: [    0.408773] EVM: security.selinux
Jul 31 00:16:07 node-2 kernel: [    0.408775] EVM: security.SMACK64
Jul 31 00:16:07 node-2 kernel: [    0.408776] EVM: security.ima
Jul 31 00:16:07 node-2 kernel: [    0.408777] EVM: security.capability
Jul 31 00:16:07 node-2 kernel: [    0.408827] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 31 00:16:07 node-2 kernel: [    0.409495] pinctrl core: initialized pinctrl subsystem
Jul 31 00:16:07 node-2 kernel: [    0.409558] regulator-dummy: no parameters
Jul 31 00:16:07 node-2 kernel: [    0.409590] RTC time:  0:15:27, date: 07/31/16
Jul 31 00:16:07 node-2 kernel: [    0.409625] NET: Registered protocol family 16
Jul 31 00:16:07 node-2 kernel: [    0.409708] cpuidle: using governor ladder
Jul 31 00:16:07 node-2 kernel: [    0.409709] cpuidle: using governor menu
Jul 31 00:16:07 node-2 kernel: [    0.409743] ACPI: bus type PCI registered
Jul 31 00:16:07 node-2 kernel: [    0.409745] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 31 00:16:07 node-2 kernel: [    0.409790] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 31 00:16:07 node-2 kernel: [    0.409792] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 31 00:16:07 node-2 kernel: [    0.423522] PCI: Using configuration type 1 for base access
Jul 31 00:16:07 node-2 kernel: [    0.424510] bio: create slab <bio-0> at 0
Jul 31 00:16:07 node-2 kernel: [    0.424786] ACPI: Added _OSI(Module Device)
Jul 31 00:16:07 node-2 kernel: [    0.424788] ACPI: Added _OSI(Processor Device)
Jul 31 00:16:07 node-2 kernel: [    0.424789] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 31 00:16:07 node-2 kernel: [    0.424790] ACPI: Added _OSI(Processor Aggregator Device)
Jul 31 00:16:07 node-2 kernel: [    0.437404] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 31 00:16:07 node-2 kernel: [    0.448083] ACPI: Interpreter enabled
Jul 31 00:16:07 node-2 kernel: [    0.448089] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 31 00:16:07 node-2 kernel: [    0.448093] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 31 00:16:07 node-2 kernel: [    0.448095] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 31 00:16:07 node-2 kernel: [    0.448102] ACPI: (supports S0 S4 S5)
Jul 31 00:16:07 node-2 kernel: [    0.448103] ACPI: Using IOAPIC for interrupt routing
Jul 31 00:16:07 node-2 kernel: [    0.448148] HEST: Table parsing has been initialized.
Jul 31 00:16:07 node-2 kernel: [    0.448151] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 31 00:16:07 node-2 kernel: [    0.448704] ACPI: No dock devices found.
Jul 31 00:16:07 node-2 kernel: [    0.460258] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 31 00:16:07 node-2 kernel: [    0.460262] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 00:16:07 node-2 kernel: [    0.460266] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 31 00:16:07 node-2 kernel: [    0.460294] PCI host bridge to bus 0000:ff
Jul 31 00:16:07 node-2 kernel: [    0.460296] pci_bus 0000:ff: root bus resource [bus ff]
Jul 31 00:16:07 node-2 kernel: [    0.460305] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460344] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.460373] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460408] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460437] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.460466] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.460496] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460526] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460556] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460584] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460609] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460635] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460662] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460688] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460714] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460740] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460767] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460794] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460820] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.460848] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460873] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.460898] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460924] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.460953] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.460987] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461017] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461046] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461076] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461106] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461136] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461166] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461198] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461228] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461260] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461292] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461324] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461356] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461384] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461411] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461441] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461473] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461509] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461544] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461576] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461605] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461635] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461664] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461692] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461722] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461752] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461783] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461812] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461839] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461873] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461902] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461933] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.461964] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462021] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 31 00:16:07 node-2 kernel: [    0.462024] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 00:16:07 node-2 kernel: [    0.462027] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 31 00:16:07 node-2 kernel: [    0.462045] PCI host bridge to bus 0000:7f
Jul 31 00:16:07 node-2 kernel: [    0.462046] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 31 00:16:07 node-2 kernel: [    0.462051] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462079] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.462108] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462137] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462159] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.462184] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.462213] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462240] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462265] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462289] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462314] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462339] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462364] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462387] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462411] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462437] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462458] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462481] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462505] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.462531] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462555] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.462579] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462604] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462631] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 31 00:16:07 node-2 kernel: [    0.462664] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462690] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462716] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462744] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462769] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462797] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462825] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462853] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462879] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462907] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462935] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462963] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.462992] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463018] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463044] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463072] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463097] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463124] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463152] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463180] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463206] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463231] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463256] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463283] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463309] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463336] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463364] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463388] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463410] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463436] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463461] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463492] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.463518] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.464761] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 31 00:16:07 node-2 kernel: [    0.464765] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 00:16:07 node-2 kernel: [    0.465880] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 31 00:16:07 node-2 kernel: [    0.466392] PCI host bridge to bus 0000:00
Jul 31 00:16:07 node-2 kernel: [    0.466395] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 31 00:16:07 node-2 kernel: [    0.466396] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 31 00:16:07 node-2 kernel: [    0.466398] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 31 00:16:07 node-2 kernel: [    0.466399] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 31 00:16:07 node-2 kernel: [    0.466400] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 31 00:16:07 node-2 kernel: [    0.466402] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 31 00:16:07 node-2 kernel: [    0.466403] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 31 00:16:07 node-2 kernel: [    0.466409] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 31 00:16:07 node-2 kernel: [    0.466491] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.466521] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.466563] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 31 00:16:07 node-2 kernel: [    0.466582] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.466611] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.466651] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 31 00:16:07 node-2 kernel: [    0.466669] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.466699] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.466739] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 31 00:16:07 node-2 kernel: [    0.466755] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.466825] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.466901] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.466976] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 31 00:16:07 node-2 kernel: [    0.466981] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 31 00:16:07 node-2 kernel: [    0.467064] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 31 00:16:07 node-2 kernel: [    0.467212] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 31 00:16:07 node-2 kernel: [    0.467229] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 31 00:16:07 node-2 kernel: [    0.467307] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.467361] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 31 00:16:07 node-2 kernel: [    0.467382] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.467437] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.467481] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 31 00:16:07 node-2 kernel: [    0.467507] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.467563] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.467605] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 31 00:16:07 node-2 kernel: [    0.467629] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 31 00:16:07 node-2 kernel: [    0.467646] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 31 00:16:07 node-2 kernel: [    0.467724] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.467773] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 31 00:16:07 node-2 kernel: [    0.467799] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 31 00:16:07 node-2 kernel: [    0.468047] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 31 00:16:07 node-2 kernel: [    0.468052] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 31 00:16:07 node-2 kernel: [    0.468059] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 31 00:16:07 node-2 kernel: [    0.468064] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 31 00:16:07 node-2 kernel: [    0.468071] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 31 00:16:07 node-2 kernel: [    0.468102] pci 0000:01:00.0: supports D1 D2
Jul 31 00:16:07 node-2 kernel: [    0.474202] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 31 00:16:07 node-2 kernel: [    0.474209] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 31 00:16:07 node-2 kernel: [    0.474213] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 31 00:16:07 node-2 kernel: [    0.474379] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.474413] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 31 00:16:07 node-2 kernel: [    0.482199] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 31 00:16:07 node-2 kernel: [    0.482206] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.482210] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:07 node-2 kernel: [    0.482294] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.482376] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 31 00:16:07 node-2 kernel: [    0.482452] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.482496] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 31 00:16:07 node-2 kernel: [    0.482500] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.482502] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:07 node-2 kernel: [    0.482553] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.482680] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.482733] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 31 00:16:07 node-2 kernel: [    0.482735] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.482737] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:07 node-2 kernel: [    0.482786] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.482905] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.482947] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.483066] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.483107] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.483241] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.483280] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 31 00:16:07 node-2 kernel: [    0.483399] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 31 00:16:07 node-2 kernel: [    0.483442] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 31 00:16:07 node-2 kernel: [    0.483445] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.483447] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:07 node-2 kernel: [    0.483506] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 31 00:16:07 node-2 kernel: [    0.483569] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 31 00:16:07 node-2 kernel: [    0.483624] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 31 00:16:07 node-2 kernel: [    0.483666] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 31 00:16:07 node-2 kernel: [    0.483748] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 31 00:16:07 node-2 kernel: [    0.483853] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 31 00:16:07 node-2 kernel: [    0.483855] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.483857] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 31 00:16:07 node-2 kernel: [    0.483913] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 31 00:16:07 node-2 kernel: [    0.483967] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 31 00:16:07 node-2 kernel: [    0.484015] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 31 00:16:07 node-2 kernel: [    0.484245] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 31 00:16:07 node-2 kernel: [    0.484249] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 31 00:16:07 node-2 kernel: [    0.484313] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 31 00:16:07 node-2 kernel: [    0.484370] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 31 00:16:07 node-2 kernel: [    0.484419] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 31 00:16:07 node-2 kernel: [    0.484628] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 31 00:16:07 node-2 kernel: [    0.484632] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 31 00:16:07 node-2 kernel: [    0.484692] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 31 00:16:07 node-2 kernel: [    0.484751] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 31 00:16:07 node-2 kernel: [    0.484804] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 31 00:16:07 node-2 kernel: [    0.485024] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 31 00:16:07 node-2 kernel: [    0.485028] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 31 00:16:07 node-2 kernel: [    0.485206] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 31 00:16:07 node-2 kernel: [    0.485244] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 31 00:16:07 node-2 kernel: [    0.485320] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 31 00:16:07 node-2 kernel: [    0.485339] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 31 00:16:07 node-2 kernel: [    0.485352] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 31 00:16:07 node-2 kernel: [    0.485365] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 31 00:16:07 node-2 kernel: [    0.485415] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 31 00:16:07 node-2 kernel: [    0.490207] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 31 00:16:07 node-2 kernel: [    0.490216] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 31 00:16:07 node-2 kernel: [    0.490280] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 31 00:16:07 node-2 kernel: [    0.490768] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 31 00:16:07 node-2 kernel: [    0.490771] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 00:16:07 node-2 kernel: [    0.490890] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 31 00:16:07 node-2 kernel: [    0.490997] PCI host bridge to bus 0000:80
Jul 31 00:16:07 node-2 kernel: [    0.490998] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 31 00:16:07 node-2 kernel: [    0.491000] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 31 00:16:07 node-2 kernel: [    0.491001] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 31 00:16:07 node-2 kernel: [    0.491009] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.491072] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.491138] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 31 00:16:07 node-2 kernel: [    0.491200] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 31 00:16:07 node-2 kernel: [    0.491205] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 31 00:16:07 node-2 kernel: [    0.491277] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 31 00:16:07 node-2 kernel: [    0.491573] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 31 00:16:07 node-2 kernel: [    0.491605] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 31 00:16:07 node-2 kernel: [    0.491634] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 31 00:16:07 node-2 kernel: [    0.491663] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 31 00:16:07 node-2 kernel: [    0.491692] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 00:16:07 node-2 kernel: [    0.491722] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 00:16:07 node-2 kernel: [    0.491751] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 00:16:07 node-2 kernel: [    0.491781] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 00:16:07 node-2 kernel: [    0.491866] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 31 00:16:07 node-2 kernel: [    0.491870] ACPI: \_SB_.UNC1: notify handler is installed
Jul 31 00:16:07 node-2 kernel: [    0.491872] ACPI: \_SB_.UNC0: notify handler is installed
Jul 31 00:16:07 node-2 kernel: [    0.491886] ACPI: \_SB_.PCI0: notify handler is installed
Jul 31 00:16:07 node-2 kernel: [    0.491939] ACPI: \_SB_.PCI1: notify handler is installed
Jul 31 00:16:07 node-2 kernel: [    0.492018] Found 4 acpi root devices
Jul 31 00:16:07 node-2 kernel: [    0.492127] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 31 00:16:07 node-2 kernel: [    0.492129] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 31 00:16:07 node-2 kernel: [    0.492131] vgaarb: loaded
Jul 31 00:16:07 node-2 kernel: [    0.492132] vgaarb: bridge control possible 0000:0c:00.0
Jul 31 00:16:07 node-2 kernel: [    0.492249] SCSI subsystem initialized
Jul 31 00:16:07 node-2 kernel: [    0.492312] libata version 3.00 loaded.
Jul 31 00:16:07 node-2 kernel: [    0.492326] ACPI: bus type USB registered
Jul 31 00:16:07 node-2 kernel: [    0.492336] usbcore: registered new interface driver usbfs
Jul 31 00:16:07 node-2 kernel: [    0.492341] usbcore: registered new interface driver hub
Jul 31 00:16:07 node-2 kernel: [    0.492364] usbcore: registered new device driver usb
Jul 31 00:16:07 node-2 kernel: [    0.492524] PCI: Using ACPI for IRQ routing
Jul 31 00:16:07 node-2 kernel: [    0.496129] PCI: pci_cache_line_size set to 64 bytes
Jul 31 00:16:07 node-2 kernel: [    0.496349] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 31 00:16:07 node-2 kernel: [    0.496350] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 31 00:16:07 node-2 kernel: [    0.496351] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 31 00:16:07 node-2 kernel: [    0.496415] NetLabel: Initializing
Jul 31 00:16:07 node-2 kernel: [    0.496417] NetLabel:  domain hash size = 128
Jul 31 00:16:07 node-2 kernel: [    0.496417] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 31 00:16:07 node-2 kernel: [    0.496427] NetLabel:  unlabeled traffic allowed by default
Jul 31 00:16:07 node-2 kernel: [    0.496481] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 31 00:16:07 node-2 kernel: [    0.496485] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 31 00:16:07 node-2 kernel: [    0.498541] Switched to clocksource hpet
Jul 31 00:16:07 node-2 kernel: [    0.502444] AppArmor: AppArmor Filesystem Enabled
Jul 31 00:16:07 node-2 kernel: [    0.502458] pnp: PnP ACPI init
Jul 31 00:16:07 node-2 kernel: [    0.502465] ACPI: bus type PNP registered
Jul 31 00:16:07 node-2 kernel: [    0.502589] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 31 00:16:07 node-2 kernel: [    0.502597] pnp 00:01: [dma 4]
Jul 31 00:16:07 node-2 kernel: [    0.502609] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 31 00:16:07 node-2 kernel: [    0.502634] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 31 00:16:07 node-2 kernel: [    0.502654] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 31 00:16:07 node-2 kernel: [    0.502671] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 31 00:16:07 node-2 kernel: [    0.502705] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 31 00:16:07 node-2 kernel: [    0.502758] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 31 00:16:07 node-2 kernel: [    0.502760] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 31 00:16:07 node-2 kernel: [    0.502762] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 31 00:16:07 node-2 kernel: [    0.502763] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 31 00:16:07 node-2 kernel: [    0.502765] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 31 00:16:07 node-2 kernel: [    0.502770] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 31 00:16:07 node-2 kernel: [    0.502772] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 31 00:16:07 node-2 kernel: [    0.502774] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 31 00:16:07 node-2 kernel: [    0.502775] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 31 00:16:07 node-2 kernel: [    0.502777] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 31 00:16:07 node-2 kernel: [    0.502778] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 31 00:16:07 node-2 kernel: [    0.502780] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 31 00:16:07 node-2 kernel: [    0.502781] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 31 00:16:07 node-2 kernel: [    0.502784] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 31 00:16:07 node-2 kernel: [    0.502867] pnp 00:07: [dma 0 disabled]
Jul 31 00:16:07 node-2 kernel: [    0.502896] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 31 00:16:07 node-2 kernel: [    0.502970] pnp 00:08: [dma 0 disabled]
Jul 31 00:16:07 node-2 kernel: [    0.503002] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 31 00:16:07 node-2 kernel: [    0.503053] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 31 00:16:07 node-2 kernel: [    0.503399] pnp: PnP ACPI: found 10 devices
Jul 31 00:16:07 node-2 kernel: [    0.503401] ACPI: bus type PNP unregistered
Jul 31 00:16:07 node-2 kernel: [    0.509633] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 31 00:16:07 node-2 kernel: [    0.509636] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 31 00:16:07 node-2 kernel: [    0.509638] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 31 00:16:07 node-2 kernel: [    0.509643] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 31 00:16:07 node-2 kernel: [    0.509644] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.509659] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509688] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 31 00:16:07 node-2 kernel: [    0.509706] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509735] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 31 00:16:07 node-2 kernel: [    0.509749] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 31 00:16:07 node-2 kernel: [    0.509778] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 31 00:16:07 node-2 kernel: [    0.509793] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 31 00:16:07 node-2 kernel: [    0.509821] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 31 00:16:07 node-2 kernel: [    0.509823] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.509838] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509867] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 31 00:16:07 node-2 kernel: [    0.509868] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.509883] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509912] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 31 00:16:07 node-2 kernel: [    0.509914] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.509916] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509921] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 31 00:16:07 node-2 kernel: [    0.509922] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.509925] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509928] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 31 00:16:07 node-2 kernel: [    0.509933] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 31 00:16:07 node-2 kernel: [    0.509941] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 31 00:16:07 node-2 kernel: [    0.509945] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 31 00:16:07 node-2 kernel: [    0.509951] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 31 00:16:07 node-2 kernel: [    0.509952] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 31 00:16:07 node-2 kernel: [    0.509953] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 31 00:16:07 node-2 kernel: [    0.509953] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 31 00:16:07 node-2 kernel: [    0.509954] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 31 00:16:07 node-2 kernel: [    0.509955] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 31 00:16:07 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 31 00:16:07 node-2 kernel: [    0.509956] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 31 00:16:07 node-2 kernel: [    0.509957] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 31 00:16:07 node-2 kernel: [    0.509958] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.509959] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509960] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.509961] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509961] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.509962] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509963] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.509964] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509965] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 31 00:16:07 node-2 kernel: [    0.509966] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509967] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 31 00:16:07 node-2 kernel: [    0.509968] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 31 00:16:07 node-2 kernel: [    0.509969] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 31 00:16:07 node-2 kernel: [    0.509970] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 31 00:16:07 node-2 kernel: [    0.509972] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 31 00:16:07 node-2 kernel: [    0.509973] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 31 00:16:07 node-2 kernel: [    0.510011] NET: Registered protocol family 2
Jul 31 00:16:07 node-2 kernel: [    0.510268] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 31 00:16:07 node-2 kernel: [    0.510608] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 31 00:16:07 node-2 kernel: [    0.510755] TCP: Hash tables configured (established 262144 bind 65536)
Jul 31 00:16:07 node-2 kernel: [    0.510798] TCP: reno registered
Jul 31 00:16:07 node-2 kernel: [    0.510826] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 31 00:16:07 node-2 kernel: [    0.510923] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 31 00:16:07 node-2 kernel: [    0.511065] NET: Registered protocol family 1
Jul 31 00:16:07 node-2 kernel: [    0.546641] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 31 00:16:07 node-2 kernel: [    0.546662] PCI: CLS 64 bytes, default 64
Jul 31 00:16:07 node-2 kernel: [    0.546704] Trying to unpack rootfs image as initramfs...
Jul 31 00:16:07 node-2 kernel: [    0.765875] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Jul 31 00:16:07 node-2 kernel: [    0.765921] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 31 00:16:07 node-2 kernel: [    0.765924] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 31 00:16:07 node-2 kernel: [    0.766366] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766373] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766377] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766383] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766393] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766404] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766413] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766422] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766430] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766439] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766445] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766452] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766458] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766466] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766474] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766481] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 00:16:07 node-2 kernel: [    0.766556] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 31 00:16:07 node-2 kernel: [    0.766559] Scanning for low memory corruption every 60 seconds
Jul 31 00:16:07 node-2 kernel: [    0.766929] Initialise system trusted keyring
Jul 31 00:16:07 node-2 kernel: [    0.766983] audit: initializing netlink socket (disabled)
Jul 31 00:16:07 node-2 kernel: [    0.767000] type=2000 audit(1469924127.724:1): initialized
Jul 31 00:16:07 node-2 kernel: [    0.784868] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 31 00:16:07 node-2 kernel: [    0.786395] zbud: loaded
Jul 31 00:16:07 node-2 kernel: [    0.786520] VFS: Disk quotas dquot_6.5.2
Jul 31 00:16:07 node-2 kernel: [    0.786556] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 31 00:16:07 node-2 kernel: [    0.786945] fuse init (API version 7.22)
Jul 31 00:16:07 node-2 kernel: [    0.787008] msgmni has been set to 32768
Jul 31 00:16:07 node-2 kernel: [    0.787058] Key type big_key registered
Jul 31 00:16:07 node-2 kernel: [    0.787592] Key type asymmetric registered
Jul 31 00:16:07 node-2 kernel: [    0.787594] Asymmetric key parser 'x509' registered
Jul 31 00:16:07 node-2 kernel: [    0.787616] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 31 00:16:07 node-2 kernel: [    0.787688] io scheduler noop registered
Jul 31 00:16:07 node-2 kernel: [    0.787689] io scheduler deadline registered (default)
Jul 31 00:16:07 node-2 kernel: [    0.787710] io scheduler cfq registered
Jul 31 00:16:07 node-2 kernel: [    0.788140] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    0.788266] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    0.788383] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    0.788493] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    0.788619] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    0.788754] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    0.789247] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 31 00:16:07 node-2 kernel: [    0.789273] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 31 00:16:07 node-2 kernel: [    0.789289] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 31 00:16:07 node-2 kernel: [    0.789298] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789300] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789303] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 31 00:16:07 node-2 kernel: [    0.789308] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789309] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789310] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789312] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789314] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789315] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789317] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789318] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789320] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789321] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789322] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789324] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789326] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 31 00:16:07 node-2 kernel: [    0.789331] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789334] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 31 00:16:07 node-2 kernel: [    0.789349] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789352] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 31 00:16:07 node-2 kernel: [    0.789363] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789364] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 31 00:16:07 node-2 kernel: [    0.789368] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 31 00:16:07 node-2 kernel: [    0.789404] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 31 00:16:07 node-2 kernel: [    0.789410] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 31 00:16:07 node-2 kernel: [    0.789414] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 31 00:16:07 node-2 kernel: [    0.789423] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 31 00:16:07 node-2 kernel: [    0.789464] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 31 00:16:07 node-2 kernel: [    0.789465] vesafb: scrolling: redraw
Jul 31 00:16:07 node-2 kernel: [    0.789467] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 31 00:16:07 node-2 kernel: [    0.810151] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 31 00:16:07 node-2 kernel: [    0.818672] Console: switching to colour frame buffer device 80x30
Jul 31 00:16:07 node-2 kernel: [    0.827336] fb0: VESA VGA frame buffer device
Jul 31 00:16:07 node-2 kernel: [    0.827533] intel_idle: MWAIT substates: 0x2120
Jul 31 00:16:07 node-2 kernel: [    0.827534] intel_idle: v0.4 model 0x3F
Jul 31 00:16:07 node-2 kernel: [    0.827534] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 31 00:16:07 node-2 kernel: [    0.827762] ipmi message handler version 39.2
Jul 31 00:16:07 node-2 kernel: [    0.828034] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 31 00:16:07 node-2 kernel: [    0.828467] ACPI: AC Adapter [P111] (on-line)
Jul 31 00:16:07 node-2 kernel: [    0.833702] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 31 00:16:07 node-2 kernel: [    0.844709] ACPI: Power Button [PWRB]
Jul 31 00:16:07 node-2 kernel: [    0.850462] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 31 00:16:07 node-2 kernel: [    0.862091] ACPI: Power Button [PWRF]
Jul 31 00:16:07 node-2 kernel: [    0.880052] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 31 00:16:07 node-2 kernel: [    0.891711] pstore: Registered erst as persistent store backend
Jul 31 00:16:07 node-2 kernel: [    0.897888] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 31 00:16:07 node-2 kernel: [    0.909810] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 31 00:16:07 node-2 kernel: [    0.936552] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 31 00:16:07 node-2 kernel: [    0.969824] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 31 00:16:07 node-2 kernel: [    0.984140] Linux agpgart interface v0.103
Jul 31 00:16:07 node-2 kernel: [    0.991889] brd: module loaded
Jul 31 00:16:07 node-2 kernel: [    0.998980] loop: module loaded
Jul 31 00:16:07 node-2 kernel: [    1.005755] libphy: Fixed MDIO Bus: probed
Jul 31 00:16:07 node-2 kernel: [    1.012289] tun: Universal TUN/TAP device driver, 1.6
Jul 31 00:16:07 node-2 kernel: [    1.018851] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 31 00:16:07 node-2 kernel: [    1.025442] PPP generic driver version 2.4.2
Jul 31 00:16:07 node-2 kernel: [    1.031906] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 31 00:16:07 node-2 kernel: [    1.038446] ehci-pci: EHCI PCI platform driver
Jul 31 00:16:07 node-2 kernel: [    1.045034] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 31 00:16:07 node-2 kernel: [    1.051542] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 31 00:16:07 node-2 kernel: [    1.064216] ehci-pci 0000:00:1a.0: debug port 2
Jul 31 00:16:07 node-2 kernel: [    1.074499] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 31 00:16:07 node-2 kernel: [    1.074517] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 31 00:16:07 node-2 kernel: [    1.090044] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 31 00:16:07 node-2 kernel: [    1.096204] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 31 00:16:07 node-2 kernel: [    1.102424] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 31 00:16:07 node-2 kernel: [    1.114311] usb usb1: Product: EHCI Host Controller
Jul 31 00:16:07 node-2 kernel: [    1.120334] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 31 00:16:07 node-2 kernel: [    1.126370] usb usb1: SerialNumber: 0000:00:1a.0
Jul 31 00:16:07 node-2 kernel: [    1.132303] hub 1-0:1.0: USB hub found
Jul 31 00:16:07 node-2 kernel: [    1.138071] hub 1-0:1.0: 2 ports detected
Jul 31 00:16:07 node-2 kernel: [    1.143858] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 31 00:16:07 node-2 kernel: [    1.149471] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 31 00:16:07 node-2 kernel: [    1.160454] ehci-pci 0000:00:1d.0: debug port 2
Jul 31 00:16:07 node-2 kernel: [    1.169753] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 31 00:16:07 node-2 kernel: [    1.169756] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 31 00:16:07 node-2 kernel: [    1.185963] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 31 00:16:07 node-2 kernel: [    1.191149] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 31 00:16:07 node-2 kernel: [    1.196446] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 31 00:16:07 node-2 kernel: [    1.207017] usb usb2: Product: EHCI Host Controller
Jul 31 00:16:07 node-2 kernel: [    1.212467] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 31 00:16:07 node-2 kernel: [    1.217990] usb usb2: SerialNumber: 0000:00:1d.0
Jul 31 00:16:07 node-2 kernel: [    1.223480] hub 2-0:1.0: USB hub found
Jul 31 00:16:07 node-2 kernel: [    1.228799] hub 2-0:1.0: 2 ports detected
Jul 31 00:16:07 node-2 kernel: [    1.234059] ehci-platform: EHCI generic platform driver
Jul 31 00:16:07 node-2 kernel: [    1.239264] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 31 00:16:07 node-2 kernel: [    1.244554] ohci-pci: OHCI PCI platform driver
Jul 31 00:16:07 node-2 kernel: [    1.249815] ohci-platform: OHCI generic platform driver
Jul 31 00:16:07 node-2 kernel: [    1.254977] uhci_hcd: USB Universal Host Controller Interface driver
Jul 31 00:16:07 node-2 kernel: [    1.260278] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 31 00:16:07 node-2 kernel: [    1.453744] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 31 00:16:07 node-2 kernel: [    1.761551] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 31 00:16:07 node-2 kernel: [    1.777817] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 31 00:16:07 node-2 kernel: [    1.783399] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 00:16:07 node-2 kernel: [    1.789086] hub 1-1:1.0: USB hub found
Jul 31 00:16:07 node-2 kernel: [    1.794554] hub 1-1:1.0: 6 ports detected
Jul 31 00:16:07 node-2 kernel: [    1.909379] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 31 00:16:07 node-2 kernel: [    2.298993] i8042: No controller found
Jul 31 00:16:07 node-2 kernel: [    2.304510] mousedev: PS/2 mouse device common for all mice
Jul 31 00:16:07 node-2 kernel: [    2.310243] rtc_cmos 00:02: RTC can wake from S4
Jul 31 00:16:07 node-2 kernel: [    2.313810] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 31 00:16:07 node-2 kernel: [    2.313811] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 00:16:07 node-2 kernel: [    2.314447] hub 2-1:1.0: USB hub found
Jul 31 00:16:07 node-2 kernel: [    2.314680] hub 2-1:1.0: 8 ports detected
Jul 31 00:16:07 node-2 kernel: [    2.338513] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 31 00:16:07 node-2 kernel: [    2.344265] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 31 00:16:07 node-2 kernel: [    2.355583] device-mapper: uevent: version 1.0.3
Jul 31 00:16:07 node-2 kernel: [    2.361304] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 31 00:16:07 node-2 kernel: [    2.372694] ledtrig-cpu: registered to indicate activity on CPUs
Jul 31 00:16:07 node-2 kernel: [    2.378681] TCP: cubic registered
Jul 31 00:16:07 node-2 kernel: [    2.384566] NET: Registered protocol family 10
Jul 31 00:16:07 node-2 kernel: [    2.390622] NET: Registered protocol family 17
Jul 31 00:16:07 node-2 kernel: [    2.396412] Key type dns_resolver registered
Jul 31 00:16:07 node-2 kernel: [    2.402474] Loading compiled-in X.509 certificates
Jul 31 00:16:07 node-2 kernel: [    2.408699] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 31 00:16:07 node-2 kernel: [    2.420366] registered taskstats version 1
Jul 31 00:16:07 node-2 kernel: [    2.428428] Key type trusted registered
Jul 31 00:16:07 node-2 kernel: [    2.436056] Key type encrypted registered
Jul 31 00:16:07 node-2 kernel: [    2.441588] AppArmor: AppArmor sha1 policy hashing enabled
Jul 31 00:16:07 node-2 kernel: [    2.447195] IMA: No TPM chip found, activating TPM-bypass!
Jul 31 00:16:07 node-2 kernel: [    2.453294] regulator-dummy: disabling
Jul 31 00:16:07 node-2 kernel: [    2.458790]   Magic number: 8:53:255
Jul 31 00:16:07 node-2 kernel: [    2.464346] acpi device:94: hash matches
Jul 31 00:16:07 node-2 kernel: [    2.469879] memory memory129: hash matches
Jul 31 00:16:07 node-2 kernel: [    2.475261] rtc_cmos 00:02: setting system clock to 2016-07-31 00:15:29 UTC (1469924129)
Jul 31 00:16:07 node-2 kernel: [    2.487637] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 31 00:16:07 node-2 kernel: [    2.493213] EDD information not available.
Jul 31 00:16:07 node-2 kernel: [    2.498771] PM: Hibernation image not present or could not be loaded.
Jul 31 00:16:07 node-2 kernel: [    2.499634] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 31 00:16:07 node-2 kernel: [    2.510837] Write protecting the kernel read-only data: 12288k
Jul 31 00:16:07 node-2 kernel: [    2.517126] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 31 00:16:07 node-2 kernel: [    2.529757] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 31 00:16:07 node-2 kernel: [    2.561333] device-mapper: multipath: version 1.6.0 loaded
Jul 31 00:16:07 node-2 kernel: [    2.569028] systemd-udevd[216]: starting version 204
Jul 31 00:16:07 node-2 kernel: [    2.588814] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 31 00:16:07 node-2 kernel: [    2.597297] md: linear personality registered for level -1
Jul 31 00:16:07 node-2 kernel: [    2.611485] md: multipath personality registered for level -4
Jul 31 00:16:07 node-2 kernel: [    2.619731] md: raid0 personality registered for level 0
Jul 31 00:16:07 node-2 kernel: [    2.627833] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 31 00:16:07 node-2 kernel: [    2.634256] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 31 00:16:07 node-2 kernel: [    2.640566] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 31 00:16:07 node-2 kernel: [    2.640635] md: raid1 personality registered for level 1
Jul 31 00:16:07 node-2 kernel: [    2.642883] megasas: FW now in Ready state
Jul 31 00:16:07 node-2 kernel: [    2.643140] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.643248] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.643381] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.643470] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.643642] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.643770] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.643925] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.644077] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.644239] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.644365] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.644513] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.644651] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.644731] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.645072] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.645223] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.645466] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.646132] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 31 00:16:07 node-2 kernel: [    2.680329] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 31 00:16:07 node-2 kernel: [    2.693721] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 31 00:16:07 node-2 kernel: [    2.707737] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 00:16:07 node-2 kernel: [    2.714850] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.714854] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.714858] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.714862] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.714900] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.728566] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 31 00:16:07 node-2 kernel: [    2.735614] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 31 00:16:07 node-2 kernel: [    2.740821] raid6: sse2x1     954 MB/s
Jul 31 00:16:07 node-2 kernel: [    2.745377] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 31 00:16:07 node-2 kernel: [    2.745390] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 31 00:16:07 node-2 kernel: [    2.745391] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 00:16:07 node-2 kernel: [    2.745634] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.745823] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.745946] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.746116] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.746372] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.761594] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 31 00:16:07 node-2 kernel: [    2.761627] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 31 00:16:07 node-2 kernel: [    2.761628] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 00:16:07 node-2 kernel: [    2.762285] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    2.808844] raid6: sse2x2     616 MB/s
Jul 31 00:16:07 node-2 kernel: [    2.844353] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 31 00:16:07 node-2 kernel: [    2.851309] usb 2-1.4: Manufacturer: Avocent
Jul 31 00:16:07 node-2 kernel: [    2.858166] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 31 00:16:07 node-2 kernel: [    2.876538] raid6: sse2x4    2909 MB/s
Jul 31 00:16:07 node-2 kernel: [    2.948476] raid6: avx2x1   14958 MB/s
Jul 31 00:16:07 node-2 kernel: [    3.020416] raid6: avx2x2   18870 MB/s
Jul 31 00:16:07 node-2 kernel: [    3.092356] raid6: avx2x4   21294 MB/s
Jul 31 00:16:07 node-2 kernel: [    3.098431] raid6: using algorithm avx2x4 (21294 MB/s)
Jul 31 00:16:07 node-2 kernel: [    3.104466] raid6: using avx2x2 recovery algorithm
Jul 31 00:16:07 node-2 kernel: [    3.110329] megasas:IOC Init cmd success
Jul 31 00:16:07 node-2 kernel: [    3.110331] Switched to clocksource tsc
Jul 31 00:16:07 node-2 kernel: [    3.110333] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    3.110383] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    3.110422] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    3.110512] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 00:16:07 node-2 kernel: [    3.122043] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 31 00:16:07 node-2 kernel: [    3.122044] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 31 00:16:07 node-2 kernel: [    3.122045] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 00:16:07 node-2 kernel: [    3.122106] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    3.122146] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    3.122184] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    3.122211] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 31 00:16:07 node-2 kernel: [    3.122284] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 00:16:07 node-2 kernel: [    3.132346] megasas: INIT adapter done
Jul 31 00:16:07 node-2 kernel: [    3.180886] xor: automatically using best checksumming function:
Jul 31 00:16:07 node-2 kernel: [    3.186838] hidraw: raw HID events driver (C) Jiri Kosina
Jul 31 00:16:07 node-2 kernel: [    3.195659] usbcore: registered new interface driver usbhid
Jul 31 00:16:07 node-2 kernel: [    3.201409] usbhid: USB HID core driver
Jul 31 00:16:07 node-2 kernel: [    3.207010] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 31 00:16:07 node-2 kernel: [    3.212691] scsi0 : LSI SAS based MegaRAID driver
Jul 31 00:16:07 node-2 kernel: [    3.218302] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 31 00:16:07 node-2 kernel: [    3.219701] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 31 00:16:07 node-2 kernel: [    3.224247]    avx       : 35511.000 MB/sec
Jul 31 00:16:07 node-2 kernel: [    3.230831] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 31 00:16:07 node-2 kernel: [    3.235144] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 31 00:16:07 node-2 kernel: [    3.235157] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 31 00:16:07 node-2 kernel: [    3.235475] sd 0:2:0:0: [sda] Write Protect is off
Jul 31 00:16:07 node-2 kernel: [    3.235476] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 31 00:16:07 node-2 kernel: [    3.235540] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 31 00:16:07 node-2 kernel: [    3.261678]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 31 00:16:07 node-2 kernel: [    3.263372] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 31 00:16:07 node-2 kernel: [    3.308218] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 31 00:16:07 node-2 kernel: [    3.321235] async_tx: api initialized (async)
Jul 31 00:16:07 node-2 kernel: [    3.321250] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 31 00:16:07 node-2 kernel: [    3.321309] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 31 00:16:07 node-2 kernel: [    3.321364] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 31 00:16:07 node-2 kernel: [    3.321418] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 31 00:16:07 node-2 kernel: [    3.385643] md: raid6 personality registered for level 6
Jul 31 00:16:07 node-2 kernel: [    3.392804] md: raid5 personality registered for level 5
Jul 31 00:16:07 node-2 kernel: [    3.399809] md: raid4 personality registered for level 4
Jul 31 00:16:07 node-2 kernel: [    3.409685] md: raid10 personality registered for level 10
Jul 31 00:16:07 node-2 kernel: [    3.465542] multipathd (362): /proc/362/oom_adj is deprecated, please use /proc/362/oom_score_adj instead.
Jul 31 00:16:07 node-2 kernel: [    3.479072] random: lvm urandom read with 32 bits of entropy available
Jul 31 00:16:07 node-2 kernel: [    3.591517] bio: create slab <bio-1> at 1
Jul 31 00:16:07 node-2 kernel: [    4.360720] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 00:16:07 node-2 kernel: [    4.891733] init: plymouth-upstart-bridge main process (553) terminated with status 1
Jul 31 00:16:07 node-2 kernel: [    4.904571] init: plymouth-upstart-bridge main process ended, respawning
Jul 31 00:16:07 node-2 kernel: [    4.913860] init: plymouth-upstart-bridge main process (564) terminated with status 1
Jul 31 00:16:07 node-2 kernel: [    4.926270] init: plymouth-upstart-bridge main process ended, respawning
Jul 31 00:16:07 node-2 kernel: [    5.088019] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 31 00:16:07 node-2 kernel: [    5.141663] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 31 00:16:07 node-2 kernel: [    5.171689] random: nonblocking pool is initialized
Jul 31 00:16:07 node-2 kernel: [    5.247717] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 31 00:16:07 node-2 kernel: [    5.283687] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 31 00:16:07 node-2 kernel: [    5.323866] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 00:16:07 node-2 kernel: [    5.552806] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 31 00:16:07 node-2 kernel: [    5.598830] XFS (dm-0): Mounting Filesystem
Jul 31 00:16:07 node-2 kernel: [    5.763402] XFS (dm-0): Ending clean mount
Jul 31 00:16:07 node-2 kernel: [    5.830645] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 00:16:07 node-2 kernel: [    5.859105] XFS (dm-1): Mounting Filesystem
Jul 31 00:16:07 node-2 kernel: [    5.923713] XFS (dm-1): Ending clean mount
Jul 31 00:16:07 node-2 kernel: [    7.637339] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 31 00:16:07 node-2 kernel: [    7.666060] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 31 00:16:07 node-2 kernel: [    7.803884] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 31 00:16:07 node-2 kernel: [    7.803888] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 31 00:16:07 node-2 kernel: [    7.803892] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 31 00:16:07 node-2 kernel: [    7.803896] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 31 00:16:07 node-2 kernel: [    7.822451] systemd-udevd[778]: starting version 204
Jul 31 00:16:07 node-2 kernel: [    7.977212] power_meter ACPI000D:00: Found ACPI power meter.
Jul 31 00:16:07 node-2 kernel: [    7.977221] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 31 00:16:07 node-2 kernel: [    8.003909] IPMI System Interface driver.
Jul 31 00:16:07 node-2 kernel: [    8.003963] ipmi_si: probing via ACPI
Jul 31 00:16:07 node-2 kernel: [    8.003977] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 31 00:16:07 node-2 kernel: [    8.003978] ipmi_si: Adding ACPI-specified kcs state machine
Jul 31 00:16:07 node-2 kernel: [    8.003986] ipmi_si: probing via SMBIOS
Jul 31 00:16:07 node-2 kernel: [    8.003987] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 31 00:16:07 node-2 kernel: [    8.003987] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 31 00:16:07 node-2 kernel: [    8.003989] ipmi_si: probing via SPMI
Jul 31 00:16:07 node-2 kernel: [    8.003990] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 31 00:16:07 node-2 kernel: [    8.003990] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 31 00:16:07 node-2 kernel: [    8.003991] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 31 00:16:07 node-2 kernel: [    8.036354] wmi: Mapper loaded
Jul 31 00:16:07 node-2 kernel: [    8.048560] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 31 00:16:07 node-2 kernel: [    8.052018] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 31 00:16:07 node-2 kernel: [    8.052025] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 31 00:16:07 node-2 kernel: [    8.052028] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 31 00:16:07 node-2 kernel: [    8.052031] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 31 00:16:07 node-2 kernel: [    8.052051] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 31 00:16:07 node-2 kernel: [    8.136545] systemd-udevd[803]: renamed network interface eth0 to enp6s0
Jul 31 00:16:07 node-2 kernel: [    8.148972] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 31 00:16:07 node-2 kernel: [    8.148978] ipmi_si 00:09: IPMI kcs interface initialized
Jul 31 00:16:07 node-2 kernel: [    8.168473] systemd-udevd[825]: renamed network interface eth2 to enp8s0
Jul 31 00:16:07 node-2 kernel: [    8.196764] systemd-udevd[807]: renamed network interface eth1 to enp7s0
Jul 31 00:16:07 node-2 kernel: [    8.228676] systemd-udevd[795]: renamed network interface eth3 to enp9s0
Jul 31 00:16:07 node-2 kernel: [    8.514902] type=1400 audit(1469924135.538:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1072 comm="apparmor_parser"
Jul 31 00:16:07 node-2 kernel: [    8.515062] type=1400 audit(1469924135.538:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1072 comm="apparmor_parser"
Jul 31 00:16:07 node-2 kernel: [    8.515196] type=1400 audit(1469924135.538:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1072 comm="apparmor_parser"
Jul 31 00:16:07 node-2 kernel: [    8.523236] type=1400 audit(1469924135.546:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1069 comm="apparmor_parser"
Jul 31 00:16:07 node-2 kernel: [    8.523383] type=1400 audit(1469924135.546:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1069 comm="apparmor_parser"
Jul 31 00:16:07 node-2 kernel: [    8.523507] type=1400 audit(1469924135.546:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1069 comm="apparmor_parser"
Jul 31 00:16:07 node-2 kernel: [    8.526855] type=1400 audit(1469924135.550:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1070 comm="apparmor_parser"
Jul 31 00:16:07 node-2 kernel: [    8.526994] type=1400 audit(1469924135.550:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1070 comm="apparmor_parser"
Jul 31 00:16:07 node-2 kernel: [    8.527121] type=1400 audit(1469924135.550:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1070 comm="apparmor_parser"
Jul 31 00:16:07 node-2 kernel: [    8.528095] type=1400 audit(1469924135.554:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1073 comm="apparmor_parser"
Jul 31 00:16:07 node-2 kernel: [    9.031208] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 31 00:16:07 node-2 kernel: [    9.042109] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 31 00:16:07 node-2 kernel: [    9.201317] enic 0000:06:00.0 enp6s0: Link UP
Jul 31 00:16:07 node-2 kernel: [    9.202439] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 31 00:16:07 node-2 kernel: [    9.202445] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 31 00:16:07 node-2 kernel: [   18.393340] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 31 00:16:08 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 31 00:16:08 node-2 kernel: [   41.490176] init: failsafe main process (8398) killed by TERM signal
Jul 31 00:16:08 node-2 dbus[8438]: [system] AppArmor D-Bus mediation is enabled
Jul 31 00:16:09 node-2 kernel: [   41.693692] audit_printk_skb: 30 callbacks suppressed
Jul 31 00:16:09 node-2 kernel: [   41.693693] type=1400 audit(1469924169.111:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8524 comm="apparmor_parser"
Jul 31 00:16:09 node-2 kernel: [   41.693697] type=1400 audit(1469924169.111:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8524 comm="apparmor_parser"
Jul 31 00:16:09 node-2 kernel: [   41.693700] type=1400 audit(1469924169.111:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8524 comm="apparmor_parser"
Jul 31 00:16:09 node-2 kernel: [   41.693923] type=1400 audit(1469924169.111:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8524 comm="apparmor_parser"
Jul 31 00:16:09 node-2 kernel: [   41.693925] type=1400 audit(1469924169.111:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8524 comm="apparmor_parser"
Jul 31 00:16:09 node-2 kernel: [   41.693972] type=1400 audit(1469924169.111:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8525 comm="apparmor_parser"
Jul 31 00:16:09 node-2 kernel: [   41.694043] type=1400 audit(1469924169.111:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8524 comm="apparmor_parser"
Jul 31 00:16:09 node-2 kernel: [   41.762653] type=1400 audit(1469924169.179:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8527 comm="apparmor_parser"
Jul 31 00:16:09 node-2 cron[8556]: (CRON) INFO (pidfile fd = 3)
Jul 31 00:16:09 node-2 anacron[8572]: Anacron 2.3 started on 2016-07-31
Jul 31 00:16:09 node-2 cron[8581]: (CRON) STARTUP (fork ok)
Jul 31 00:16:09 node-2 anacron[8572]: Will run job `cron.daily' in 5 min.
Jul 31 00:16:09 node-2 anacron[8572]: Will run job `cron.weekly' in 10 min.
Jul 31 00:16:09 node-2 anacron[8572]: Will run job `cron.monthly' in 15 min.
Jul 31 00:16:09 node-2 anacron[8572]: Jobs will be executed sequentially
Jul 31 00:16:09 node-2 cron[8581]: (CRON) INFO (Running @reboot jobs)
Jul 31 00:16:09 node-2 multipathd: path checkers start up
Jul 31 00:16:09 node-2 postfix/master[8735]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 31 00:16:12 node-2 puppet-agent[8920]: Reopening log files
Jul 31 00:16:13 node-2 puppet-agent[8920]: Could not request certificate: Connection refused - connect(2)
Jul 31 00:16:23 node-2 puppet-user[8999]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 31 00:16:23 node-2 puppet-user[8999]: Compiled catalog for node-2.domain.tld in environment production in 0.01 seconds
Jul 31 00:16:24 node-2 puppet-user[8999]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 31 00:16:24 node-2 puppet-user[8999]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 31 00:16:24 node-2 puppet-user[8999]: Finished catalog run in 0.66 seconds
Jul 31 00:16:25 node-2 multipathd: uevent trigger error
Jul 31 00:16:25 node-2 puppet-user[9548]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 31 00:16:25 node-2 puppet-user[9548]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Jul 31 00:16:26 node-2 puppet-user[9548]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 31 00:16:26 node-2 puppet-user[9548]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 31 00:16:26 node-2 puppet-user[9548]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 31 00:16:26 node-2 puppet-user[9548]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 31 00:16:26 node-2 puppet-user[9548]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 31 00:16:26 node-2 puppet-user[9548]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 31 00:16:26 node-2 puppet-user[9548]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 31 00:16:26 node-2 puppet-user[9548]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 31 00:16:26 node-2 puppet-user[9548]: Finished catalog run in 0.07 seconds
Jul 31 00:16:27 node-2 puppet-user[10010]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 31 00:16:27 node-2 puppet-user[10010]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Jul 31 00:16:27 node-2 puppet-user[10010]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 31 00:16:27 node-2 puppet-user[10010]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 31 00:16:27 node-2 puppet-user[10010]: Finished catalog run in 0.03 seconds
Jul 31 00:16:29 node-2 puppet-user[10473]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 31 00:16:29 node-2 puppet-user[10473]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 31 00:16:29 node-2 puppet-user[10473]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 31 00:16:29 node-2 puppet-user[10473]: Finished catalog run in 0.03 seconds
Jul 31 00:16:30 node-2 puppet-user[10925]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 31 00:16:30 node-2 puppet-user[10925]: Compiled catalog for node-2.domain.tld in environment production in 0.20 seconds
Jul 31 00:16:30 node-2 puppet-user[10925]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 31 00:16:31 node-2 puppet-user[10925]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 31 00:16:31 node-2 puppet-user[10925]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 31 00:16:32 node-2 puppet-user[10925]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Jul 31 00:16:32 node-2 puppet-user[10925]: Finished catalog run in 1.17 seconds
Jul 31 00:16:33 node-2 puppet-user[11460]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 31 00:16:33 node-2 puppet-user[11460]: Compiled catalog for node-2.domain.tld in environment production in 0.22 seconds
Jul 31 00:16:33 node-2 puppet-user[11460]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 31 00:16:33 node-2 puppet-user[11460]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Jul 31 00:16:33 node-2 puppet-user[11460]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 31 00:16:33 node-2 puppet-user[11460]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 31 00:16:33 node-2 puppet-user[11460]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 31 00:16:33 node-2 puppet-user[11460]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 31 00:16:33 node-2 puppet-user[11460]: Finished catalog run in 0.36 seconds
Jul 31 00:16:35 node-2 puppet-user[11943]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 31 00:16:35 node-2 puppet-user[11943]: Compiled catalog for node-2.domain.tld in environment production in 0.14 seconds
Jul 31 00:16:35 node-2 puppet-user[11943]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 31 00:16:35 node-2 kernel: [   68.214066] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 31 00:16:35 node-2 kernel: [   68.214116] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 31 00:16:35 node-2 puppet-user[11943]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 31 00:16:35 node-2 puppet-user[11943]: Finished catalog run in 0.05 seconds
Jul 31 00:16:37 node-2 puppet-user[12400]: (Scope(Class[main])) MODULAR: sync_time
Jul 31 00:16:37 node-2 puppet-user[12400]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 31 00:16:37 node-2 ntpdate[13001]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 31 00:16:43 node-2 ntpdate[13001]: adjust time server 10.20.0.2 offset 0.000605 sec
Jul 31 00:16:43 node-2 puppet-user[12400]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 31 00:16:43 node-2 puppet-user[12400]: Finished catalog run in 6.17 seconds
Jul 31 00:16:49 node-2 kernel: [   81.921616] init: plymouth-upstart-bridge main process ended, respawning
Jul 31 00:16:49 node-2 puppet-agent[8920]: Could not run: SIGTERM
Jul 31 00:16:49 node-2 kernel: [   82.170481] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 31 00:16:49 node-2 ec2: 
Jul 31 00:16:49 node-2 ec2: #############################################################
Jul 31 00:16:49 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 31 00:16:49 node-2 ec2: 1024 c1:ce:83:d4:24:bd:f8:43:55:35:74:a8:18:7c:66:58  root@node-2.domain.tld (DSA)
Jul 31 00:16:49 node-2 ec2: 256 1a:5f:d6:be:44:5f:d5:96:47:a1:57:f0:1d:20:75:f2  root@node-2.domain.tld (ECDSA)
Jul 31 00:16:49 node-2 ec2: 256 fd:69:2a:22:a8:bd:a8:f5:64:b4:79:29:1e:57:29:e4  root@node-2.domain.tld (ED25519)
Jul 31 00:16:49 node-2 ec2: 2048 6c:96:ef:c5:5d:7f:9e:82:e2:65:99:d2:cf:92:0d:d5  root@node-2.domain.tld (RSA)
Jul 31 00:16:49 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 31 00:16:49 node-2 ec2: #############################################################
Jul 31 00:17:01 node-2 CRON[13367]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 31 00:17:01 node-2 CRON[13366]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 31 00:17:04 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 00:17:04 node-2 nailgun-agent: I, [2016-07-31T00:17:04.568147 #13371]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 31 00:17:17 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 00:17:17 node-2 nailgun-agent: I, [2016-07-31T00:17:17.627117 #13371]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 31 00:17:33 node-2 puppet-user[13701]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 31 00:17:33 node-2 puppet-user[13701]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Jul 31 00:17:34 node-2 puppet-user[13701]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 31 00:17:34 node-2 puppet-user[13701]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 31 00:17:34 node-2 puppet-user[13701]: Finished catalog run in 0.07 seconds
Jul 31 00:17:35 node-2 puppet-user[14154]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 31 00:17:36 node-2 puppet-user[14154]: Compiled catalog for node-2.domain.tld in environment production in 1.16 seconds
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 31 00:17:37 node-2 puppet-user[14154]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 31 00:17:55 node-2 puppet-user[14154]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 31 00:17:55 node-2 puppet-user[14154]: Finished catalog run in 18.15 seconds
Jul 31 00:17:57 node-2 puppet-user[15061]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 31 00:17:57 node-2 puppet-user[15061]: Compiled catalog for node-2.domain.tld in environment production in 0.16 seconds
Jul 31 00:18:01 node-2 CRON[15947]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 31 00:18:02 node-2 puppet-user[15061]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 31 00:18:13 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 00:18:13 node-2 nailgun-agent: I, [2016-07-31T00:18:13.818814 #15950]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 31 00:18:26 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 00:18:27 node-2 nailgun-agent: I, [2016-07-31T00:18:27.057228 #15950]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 31 00:18:33 node-2 puppet-user[15061]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 31 00:18:33 node-2 puppet-user[15061]: Finished catalog run in 35.46 seconds
Jul 31 00:18:35 node-2 puppet-user[17827]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 31 00:18:35 node-2 puppet-user[17827]: Compiled catalog for node-2.domain.tld in environment production in 0.57 seconds
Jul 31 00:18:36 node-2 puppet-user[17827]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 31 00:18:36 node-2 puppet-user[17827]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 31 00:18:36 node-2 puppet-user[17827]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 31 00:18:36 node-2 puppet-user[17827]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 31 00:18:36 node-2 puppet-user[17827]: Finished catalog run in 0.13 seconds
Jul 31 00:18:37 node-2 puppet-user[18281]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 31 00:18:38 node-2 puppet-user[18281]: Compiled catalog for node-2.domain.tld in environment production in 0.94 seconds
Jul 31 00:18:39 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 31 00:18:39 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 31 00:18:39 node-2 crontab[18717]: (root) LIST (root)
Jul 31 00:18:39 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 31 00:18:39 node-2 crontab[18718]: (root) REPLACE (root)
Jul 31 00:18:41 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 31 00:18:42 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 31 00:18:43 node-2 puppet-user[18281]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 31 00:18:43 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8371" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 00:18:43 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 31 00:18:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:18:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:18:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:18:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:18:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:05 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:05 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:05 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:05 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:08 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:08 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:08 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:08 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:19:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:09 node-2 ntpdate[29171]: no servers can be used, exiting
<27>Jul 31 00:20:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:43 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:43 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:43 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:43 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:43 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:43 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:55 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:55 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:55 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:55 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:55 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:58 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:58 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:58 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:58 node-2 multipathd: uevent trigger error
<27>Jul 31 00:20:58 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:30 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:30 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:30 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:30 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:30 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:36 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:36 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:36 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:36 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:36 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:36 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:36 node-2 multipathd: uevent trigger error
<43>Jul 31 00:21:54 node-2 apache2_error [Sun Jul 31 00:21:48.938259 2016] [mpm_event:notice] [pid 11212:tid 140044322469760] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 00:21:54 node-2 apache2_error [Sun Jul 31 00:21:48.938335 2016] [core:notice] [pid 11212:tid 140044322469760] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 31 00:21:54 node-2 apache2_error [Sun Jul 31 00:21:50.989995 2016] [mpm_event:notice] [pid 11212:tid 140044322469760] AH00491: caught SIGTERM, shutting down
<43>Jul 31 00:21:54 node-2 apache2_error [Sun Jul 31 00:21:52.063420 2016] [mpm_worker:notice] [pid 11533:tid 139714757896064] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 00:21:54 node-2 apache2_error [Sun Jul 31 00:21:52.063499 2016] [core:notice] [pid 11533:tid 139714757896064] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 00:21:55 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:55 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:56 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:56 node-2 multipathd: uevent trigger error
<27>Jul 31 00:21:56 node-2 multipathd: uevent trigger error
<27>Jul 31 00:22:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:22:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:22:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:22:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:22:32 node-2 multipathd: uevent trigger error
<43>Jul 31 00:22:34 node-2 apache2_error [Sun Jul 31 00:22:29.609433 2016] [mpm_worker:notice] [pid 11533:tid 139714757896064] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 00:22:34 node-2 apache2_error [Sun Jul 31 00:22:29.618427 2016] [mpm_worker:warn] [pid 11533:tid 139714757896064] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 00:22:34 node-2 apache2_error [Sun Jul 31 00:22:29.619167 2016] [mpm_worker:notice] [pid 11533:tid 139714757896064] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 00:22:34 node-2 apache2_error [Sun Jul 31 00:22:29.619179 2016] [core:notice] [pid 11533:tid 139714757896064] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 00:23:07 node-2 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 31 00:23:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:14 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:14 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:14 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:14 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:14 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:20 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:20 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:20 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:20 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:20 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:32 node-2 multipathd: uevent trigger error
<129>Jul 31 00:23:35 node-2 haproxy[24878]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:23:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:40 node-2 multipathd: uevent trigger error
<129>Jul 31 00:23:43 node-2 haproxy[26875]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:44 node-2 haproxy[26879]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:23:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:46 node-2 multipathd: uevent trigger error
<129>Jul 31 00:23:48 node-2 haproxy[27923]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:49 node-2 haproxy[27929]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:49 node-2 haproxy[27929]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:23:51 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:51 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:51 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:51 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:51 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:51 node-2 multipathd: uevent trigger error
<129>Jul 31 00:23:53 node-2 haproxy[28991]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:53 node-2 haproxy[28991]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:54 node-2 haproxy[28995]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:54 node-2 haproxy[28995]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:55 node-2 haproxy[28995]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:23:56 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:56 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:56 node-2 multipathd: uevent trigger error
<27>Jul 31 00:23:56 node-2 multipathd: uevent trigger error
<129>Jul 31 00:23:58 node-2 haproxy[30042]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:58 node-2 haproxy[30042]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:59 node-2 haproxy[30049]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:59 node-2 haproxy[30049]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:23:59 node-2 haproxy[30049]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:00 node-2 haproxy[30049]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:24:01 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:01 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:01 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:01 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:01 node-2 multipathd: uevent trigger error
<129>Jul 31 00:24:01 node-2 haproxy[30049]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:02 node-2 haproxy[30049]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:02 node-2 haproxy[30049]: proxy aodh has no server available!
<129>Jul 31 00:24:03 node-2 haproxy[31112]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:03 node-2 haproxy[31112]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:04 node-2 haproxy[31119]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:04 node-2 haproxy[31119]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:04 node-2 haproxy[31119]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:04 node-2 haproxy[31119]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:05 node-2 haproxy[31119]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:24:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:06 node-2 multipathd: uevent trigger error
<129>Jul 31 00:24:06 node-2 haproxy[31119]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:06 node-2 haproxy[31119]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:06 node-2 haproxy[31119]: proxy aodh has no server available!
<129>Jul 31 00:24:07 node-2 haproxy[31119]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:07 node-2 haproxy[31119]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:07 node-2 haproxy[31119]: proxy ceilometer has no server available!
<129>Jul 31 00:24:08 node-2 haproxy[32198]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:08 node-2 haproxy[32198]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:09 node-2 haproxy[32202]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:09 node-2 haproxy[32202]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:09 node-2 haproxy[32202]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:09 node-2 haproxy[32202]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:10 node-2 haproxy[32202]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:24:11 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:11 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:11 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:11 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:11 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:11 node-2 multipathd: uevent trigger error
<129>Jul 31 00:24:11 node-2 haproxy[32202]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:12 node-2 haproxy[32202]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:12 node-2 haproxy[32202]: proxy aodh has no server available!
<129>Jul 31 00:24:12 node-2 haproxy[32202]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:12 node-2 haproxy[32202]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:12 node-2 haproxy[32202]: proxy ceilometer has no server available!
<129>Jul 31 00:24:13 node-2 haproxy[886]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:13 node-2 haproxy[886]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:24:13 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 31 00:24:14 node-2 haproxy[890]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:14 node-2 haproxy[890]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:14 node-2 haproxy[890]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:14 node-2 haproxy[890]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:15 node-2 haproxy[890]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:15 node-2 haproxy[890]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:15 node-2 haproxy[890]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:24:16 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:16 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:16 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:16 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:16 node-2 multipathd: uevent trigger error
<129>Jul 31 00:24:16 node-2 haproxy[890]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:16 node-2 haproxy[890]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:16 node-2 haproxy[890]: proxy aodh has no server available!
<129>Jul 31 00:24:17 node-2 haproxy[890]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:17 node-2 haproxy[890]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:17 node-2 haproxy[890]: proxy ceilometer has no server available!
<129>Jul 31 00:24:19 node-2 haproxy[2055]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:19 node-2 haproxy[2055]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:19 node-2 haproxy[2055]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:19 node-2 haproxy[2055]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:19 node-2 haproxy[2055]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:19 node-2 haproxy[2055]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:20 node-2 haproxy[2055]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:20 node-2 haproxy[2055]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:20 node-2 haproxy[2055]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:20 node-2 haproxy[2055]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:20 node-2 haproxy[2055]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:20 node-2 haproxy[2055]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:24:21 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:21 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:21 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:21 node-2 multipathd: uevent trigger error
<129>Jul 31 00:24:21 node-2 haproxy[2055]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:21 node-2 haproxy[2055]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:21 node-2 haproxy[2055]: proxy glance-registry has no server available!
<129>Jul 31 00:24:22 node-2 haproxy[2055]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:22 node-2 haproxy[2055]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:22 node-2 haproxy[2055]: proxy aodh has no server available!
<129>Jul 31 00:24:22 node-2 haproxy[2055]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:22 node-2 haproxy[2055]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:22 node-2 haproxy[2055]: proxy ceilometer has no server available!
<129>Jul 31 00:24:24 node-2 haproxy[3343]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:24 node-2 haproxy[3343]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:24 node-2 haproxy[3343]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:24 node-2 haproxy[3343]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:25 node-2 haproxy[3347]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:25 node-2 haproxy[3347]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:25 node-2 haproxy[3347]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:25 node-2 haproxy[3347]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:25 node-2 haproxy[3347]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:25 node-2 haproxy[3347]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:25 node-2 haproxy[3347]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:26 node-2 haproxy[3347]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:26 node-2 haproxy[3347]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:26 node-2 haproxy[3347]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:26 node-2 haproxy[3347]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:24:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:27 node-2 multipathd: uevent trigger error
<129>Jul 31 00:24:27 node-2 haproxy[3347]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:27 node-2 haproxy[3347]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:27 node-2 haproxy[3347]: proxy glance-registry has no server available!
<129>Jul 31 00:24:27 node-2 haproxy[3347]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:27 node-2 haproxy[3347]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:27 node-2 haproxy[3347]: proxy aodh has no server available!
<129>Jul 31 00:24:28 node-2 haproxy[3347]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:28 node-2 haproxy[3347]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:28 node-2 haproxy[3347]: proxy ceilometer has no server available!
<129>Jul 31 00:24:28 node-2 haproxy[3347]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:28 node-2 haproxy[3347]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:28 node-2 haproxy[3347]: proxy nova-novncproxy has no server available!
<129>Jul 31 00:24:29 node-2 haproxy[4438]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:29 node-2 haproxy[4438]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:29 node-2 haproxy[4438]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:29 node-2 haproxy[4438]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:30 node-2 haproxy[4443]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:30 node-2 haproxy[4443]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:30 node-2 haproxy[4443]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:30 node-2 haproxy[4443]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:30 node-2 haproxy[4443]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:30 node-2 haproxy[4443]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:30 node-2 haproxy[4443]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:31 node-2 haproxy[4443]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:31 node-2 haproxy[4443]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:31 node-2 haproxy[4443]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:31 node-2 haproxy[4443]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:31 node-2 haproxy[4443]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:24:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:32 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:32 node-2 multipathd: uevent trigger error
<129>Jul 31 00:24:32 node-2 haproxy[4443]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:32 node-2 haproxy[4443]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:32 node-2 haproxy[4443]: proxy glance-registry has no server available!
<129>Jul 31 00:24:32 node-2 haproxy[4443]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:33 node-2 haproxy[4443]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:33 node-2 haproxy[4443]: proxy aodh has no server available!
<129>Jul 31 00:24:33 node-2 haproxy[4443]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:33 node-2 haproxy[4443]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:33 node-2 haproxy[4443]: proxy ceilometer has no server available!
<129>Jul 31 00:24:33 node-2 haproxy[4443]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:33 node-2 haproxy[4443]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:33 node-2 haproxy[4443]: proxy nova-novncproxy has no server available!
<129>Jul 31 00:24:34 node-2 haproxy[5578]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:35 node-2 haproxy[5582]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:35 node-2 haproxy[5582]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:35 node-2 haproxy[5582]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:35 node-2 haproxy[5582]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:35 node-2 haproxy[5582]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:35 node-2 haproxy[5582]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:35 node-2 haproxy[5582]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:35 node-2 haproxy[5582]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:35 node-2 haproxy[5582]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:35 node-2 haproxy[5582]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:36 node-2 haproxy[5582]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:36 node-2 haproxy[5582]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:36 node-2 haproxy[5582]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:36 node-2 haproxy[5582]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:36 node-2 haproxy[5582]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:36 node-2 haproxy[5582]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:36 node-2 haproxy[5582]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:36 node-2 haproxy[5582]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:24:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:37 node-2 multipathd: uevent trigger error
<129>Jul 31 00:24:37 node-2 haproxy[5582]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:37 node-2 haproxy[5582]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:37 node-2 haproxy[5582]: proxy glance-registry has no server available!
<129>Jul 31 00:24:38 node-2 haproxy[5582]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:38 node-2 haproxy[5582]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:38 node-2 haproxy[5582]: proxy aodh has no server available!
<129>Jul 31 00:24:38 node-2 haproxy[5582]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:38 node-2 haproxy[5582]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:38 node-2 haproxy[5582]: proxy ceilometer has no server available!
<129>Jul 31 00:24:38 node-2 haproxy[5582]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:38 node-2 haproxy[5582]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:38 node-2 haproxy[5582]: proxy nova-novncproxy has no server available!
<27>Jul 31 00:24:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:40 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:43 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:43 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:43 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:43 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:43 node-2 multipathd: uevent trigger error
<129>Jul 31 00:24:44 node-2 haproxy[5582]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:44 node-2 haproxy[5582]: Server keystone-1/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:44 node-2 haproxy[5582]: proxy keystone-1 has no server available!
<129>Jul 31 00:24:44 node-2 haproxy[5582]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server keystone-2/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:45 node-2 haproxy[5582]: proxy keystone-2 has no server available!
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server nova-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:45 node-2 haproxy[5582]: proxy nova-api has no server available!
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:45 node-2 haproxy[5582]: proxy nova-metadata-api has no server available!
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:45 node-2 haproxy[5582]: proxy cinder-api has no server available!
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server glance-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:45 node-2 haproxy[5582]: proxy glance-api has no server available!
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server glance-glare/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:45 node-2 haproxy[5582]: proxy glance-glare has no server available!
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server neutron/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:45 node-2 haproxy[5582]: proxy neutron has no server available!
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:45 node-2 haproxy[5582]: proxy mysqld has no server available!
<129>Jul 31 00:24:45 node-2 haproxy[5582]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:46 node-2 haproxy[5582]: Server object-storage/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:46 node-2 haproxy[5582]: proxy object-storage has no server available!
<129>Jul 31 00:24:46 node-2 haproxy[5582]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:46 node-2 haproxy[5582]: Server heat-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:46 node-2 haproxy[5582]: proxy heat-api has no server available!
<129>Jul 31 00:24:46 node-2 haproxy[5582]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:46 node-2 haproxy[5582]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:46 node-2 haproxy[5582]: proxy heat-api-cfn has no server available!
<129>Jul 31 00:24:46 node-2 haproxy[5582]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 00:24:46 node-2 haproxy[5582]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 00:24:46 node-2 haproxy[5582]: proxy heat-api-cloudwatch has no server available!
<27>Jul 31 00:24:47 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:47 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:47 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:47 node-2 multipathd: uevent trigger error
<27>Jul 31 00:24:47 node-2 multipathd: uevent trigger error
<27>Jul 31 00:25:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:25:09 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 00:25:09 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 31 00:25:12 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 31 00:25:38 node-2 multipathd: uevent trigger error
<27>Jul 31 00:25:38 node-2 multipathd: uevent trigger error
<27>Jul 31 00:25:38 node-2 multipathd: uevent trigger error
<27>Jul 31 00:25:38 node-2 multipathd: uevent trigger error
<27>Jul 31 00:25:38 node-2 multipathd: uevent trigger error
<27>Jul 31 00:25:40 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 31 00:26:48 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 31 00:26:50 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 31 00:28:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:28:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:28:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:28:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:28:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:31:13 node-2 multipathd: uevent trigger error
<27>Jul 31 00:31:13 node-2 multipathd: uevent trigger error
<27>Jul 31 00:31:13 node-2 multipathd: uevent trigger error
<27>Jul 31 00:31:13 node-2 multipathd: uevent trigger error
<27>Jul 31 00:31:13 node-2 multipathd: uevent trigger error
<43>Jul 31 00:32:24 node-2 apache2_error [Sun Jul 31 00:32:21.400294 2016] [mpm_worker:notice] [pid 11533:tid 139714757896064] AH00295: caught SIGTERM, shutting down
<43>Jul 31 00:32:24 node-2 apache2_error [Sun Jul 31 00:32:22.139475 2016] [mpm_worker:notice] [pid 7978:tid 140023988025216] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 00:32:24 node-2 apache2_error [Sun Jul 31 00:32:22.139495 2016] [core:notice] [pid 7978:tid 140023988025216] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 31 00:32:54 node-2 apache2_error [Sun Jul 31 00:32:54.186224 2016] [mpm_worker:notice] [pid 7978:tid 140023988025216] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 00:32:54 node-2 apache2_error [Sun Jul 31 00:32:54.199110 2016] [mpm_worker:warn] [pid 7978:tid 140023988025216] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 00:32:54 node-2 apache2_error [Sun Jul 31 00:32:54.204414 2016] [mpm_worker:notice] [pid 7978:tid 140023988025216] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 00:32:54 node-2 apache2_error [Sun Jul 31 00:32:54.204439 2016] [core:notice] [pid 7978:tid 140023988025216] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 00:33:01 node-2 multipathd: uevent trigger error
<27>Jul 31 00:33:01 node-2 multipathd: uevent trigger error
<27>Jul 31 00:33:01 node-2 multipathd: uevent trigger error
<27>Jul 31 00:33:01 node-2 multipathd: uevent trigger error
<27>Jul 31 00:33:01 node-2 multipathd: uevent trigger error
<27>Jul 31 00:33:59 node-2 multipathd: uevent trigger error
<27>Jul 31 00:33:59 node-2 multipathd: uevent trigger error
<27>Jul 31 00:33:59 node-2 multipathd: uevent trigger error
<27>Jul 31 00:33:59 node-2 multipathd: uevent trigger error
<27>Jul 31 00:33:59 node-2 multipathd: uevent trigger error
<27>Jul 31 00:35:11 node-2 multipathd: uevent trigger error
<27>Jul 31 00:35:11 node-2 multipathd: uevent trigger error
<27>Jul 31 00:35:11 node-2 multipathd: uevent trigger error
<27>Jul 31 00:35:11 node-2 multipathd: uevent trigger error
<27>Jul 31 00:35:11 node-2 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-2 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-2 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-2 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-2 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-2 multipathd: uevent trigger error
<27>Jul 31 00:39:54 node-2 multipathd: uevent trigger error
<27>Jul 31 00:41:59 node-2 multipathd: uevent trigger error
<27>Jul 31 00:41:59 node-2 multipathd: uevent trigger error
<27>Jul 31 00:41:59 node-2 multipathd: uevent trigger error
<27>Jul 31 00:41:59 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:07 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:07 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:07 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:07 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:07 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:08 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:08 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:43 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:44 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:44 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:44 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:44 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:44 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:52 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:52 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:52 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:52 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:52 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:52 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:52 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:57 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:58 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:58 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:58 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:58 node-2 multipathd: uevent trigger error
<27>Jul 31 00:43:58 node-2 multipathd: uevent trigger error
<43>Jul 31 00:44:55 node-2 apache2_error [Sun Jul 31 00:44:50.016262 2016] [mpm_worker:notice] [pid 7978:tid 140023988025216] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 00:44:55 node-2 apache2_error [Sun Jul 31 00:44:50.402827 2016] [mpm_worker:warn] [pid 7978:tid 140023988025216] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 00:44:55 node-2 apache2_error [Sun Jul 31 00:44:50.406698 2016] [mpm_worker:notice] [pid 7978:tid 140023988025216] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 00:44:55 node-2 apache2_error [Sun Jul 31 00:44:50.406718 2016] [core:notice] [pid 7978:tid 140023988025216] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 00:45:31 node-2 multipathd: uevent trigger error
<27>Jul 31 00:45:31 node-2 multipathd: uevent trigger error
<27>Jul 31 00:45:31 node-2 multipathd: uevent trigger error
<27>Jul 31 00:45:31 node-2 multipathd: uevent trigger error
<27>Jul 31 00:45:31 node-2 multipathd: uevent trigger error
<27>Jul 31 00:45:31 node-2 multipathd: uevent trigger error
<43>Jul 31 00:45:35 node-2 apache2_error [Sun Jul 31 00:45:27.405589 2016] [mpm_worker:notice] [pid 7978:tid 140023988025216] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 00:45:35 node-2 apache2_error [Sun Jul 31 00:45:27.791788 2016] [mpm_worker:warn] [pid 7978:tid 140023988025216] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 00:45:35 node-2 apache2_error [Sun Jul 31 00:45:27.800499 2016] [mpm_worker:notice] [pid 7978:tid 140023988025216] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 00:45:35 node-2 apache2_error [Sun Jul 31 00:45:27.800526 2016] [core:notice] [pid 7978:tid 140023988025216] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 00:45:48 node-2 multipathd: uevent trigger error
<27>Jul 31 00:45:48 node-2 multipathd: uevent trigger error
<27>Jul 31 00:45:48 node-2 multipathd: uevent trigger error
<27>Jul 31 00:45:48 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:37 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:42 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:42 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:42 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:42 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:42 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:46:46 node-2 multipathd: uevent trigger error
<27>Jul 31 00:47:53 node-2 multipathd: uevent trigger error
<27>Jul 31 00:47:53 node-2 multipathd: uevent trigger error
<27>Jul 31 00:47:53 node-2 multipathd: uevent trigger error
<27>Jul 31 00:47:53 node-2 multipathd: uevent trigger error
<27>Jul 31 00:47:53 node-2 multipathd: uevent trigger error
<27>Jul 31 00:48:42 node-2 multipathd: uevent trigger error
<27>Jul 31 00:48:42 node-2 multipathd: uevent trigger error
<27>Jul 31 00:48:42 node-2 multipathd: uevent trigger error
<27>Jul 31 00:48:42 node-2 multipathd: uevent trigger error
<27>Jul 31 00:48:57 node-2 multipathd: uevent trigger error
<27>Jul 31 00:48:57 node-2 multipathd: uevent trigger error
<27>Jul 31 00:48:57 node-2 multipathd: uevent trigger error
<27>Jul 31 00:48:57 node-2 multipathd: uevent trigger error
<27>Jul 31 00:48:57 node-2 multipathd: uevent trigger error
<27>Jul 31 00:48:57 node-2 multipathd: uevent trigger error
<11>Jul 31 00:49:07 node-2 liberasurecode[31547]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:07 node-2 liberasurecode[31547]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:07 node-2 liberasurecode[31547]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:07 node-2 liberasurecode[31547]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:07 node-2 liberasurecode[31596]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:07 node-2 liberasurecode[31596]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:07 node-2 liberasurecode[31596]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:07 node-2 liberasurecode[31596]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:09 node-2 liberasurecode[32000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:09 node-2 liberasurecode[32000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:09 node-2 liberasurecode[32000]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:09 node-2 liberasurecode[32000]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:14 node-2 liberasurecode[32573]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:14 node-2 liberasurecode[32573]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:14 node-2 liberasurecode[32573]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:14 node-2 liberasurecode[32573]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:14 node-2 liberasurecode[32614]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:14 node-2 liberasurecode[32614]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:14 node-2 liberasurecode[32614]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:14 node-2 liberasurecode[32614]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32653]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32653]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32653]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32653]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32718]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32718]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32718]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32718]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32730]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32730]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32730]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32730]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32742]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32742]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32742]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32742]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32754]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32754]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32754]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:49:15 node-2 liberasurecode[32754]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 00:49:21 node-2 multipathd: uevent trigger error
<27>Jul 31 00:49:21 node-2 multipathd: uevent trigger error
<27>Jul 31 00:49:21 node-2 multipathd: uevent trigger error
<27>Jul 31 00:49:21 node-2 multipathd: uevent trigger error
<27>Jul 31 00:49:22 node-2 multipathd: uevent trigger error
<27>Jul 31 00:49:26 node-2 multipathd: uevent trigger error
<27>Jul 31 00:49:26 node-2 multipathd: uevent trigger error
<27>Jul 31 00:49:26 node-2 multipathd: uevent trigger error
<27>Jul 31 00:49:26 node-2 multipathd: uevent trigger error
<11>Jul 31 00:50:02 node-2 liberasurecode[9743]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:50:02 node-2 liberasurecode[9743]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:50:02 node-2 liberasurecode[9743]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:50:02 node-2 liberasurecode[9743]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 00:50:33 node-2 multipathd: uevent trigger error
<27>Jul 31 00:50:33 node-2 multipathd: uevent trigger error
<27>Jul 31 00:50:33 node-2 multipathd: uevent trigger error
<27>Jul 31 00:50:33 node-2 multipathd: uevent trigger error
<27>Jul 31 00:50:33 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:35 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:35 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:35 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:35 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:41 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:41 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:41 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:41 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:41 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:53 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:53 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:53 node-2 multipathd: uevent trigger error
<27>Jul 31 00:52:53 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:06 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:10 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:23 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:23 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:23 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:23 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:27 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:31 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:31 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:31 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:31 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:31 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:39 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:39 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:39 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:39 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:39 node-2 multipathd: uevent trigger error
<129>Jul 31 00:53:40 node-2 haproxy[5582]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 00:53:44 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:44 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:44 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:44 node-2 multipathd: uevent trigger error
<27>Jul 31 00:53:44 node-2 multipathd: uevent trigger error
<27>Jul 31 00:54:12 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 00:54:12 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Jul 31 00:55:01 node-2 liberasurecode[28352]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:55:01 node-2 liberasurecode[28352]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:55:01 node-2 liberasurecode[28352]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 00:55:01 node-2 liberasurecode[28352]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 00:55:18 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Jul 31 00:55:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:20 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:21 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:23 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:24 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:26 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:29 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:32 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Jul 31 00:55:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:35 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:38 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:41 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:45 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Jul 31 00:55:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:47 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:48 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:50 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:53 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:57 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Jul 31 00:55:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:55:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:00 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:03 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:08 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:09 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Jul 31 00:56:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:14 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:15 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:20 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:21 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Jul 31 00:56:21 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:23 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:24 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:26 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:29 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:32 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:33 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Jul 31 00:56:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:35 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:35 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:36 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:41 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:44 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:46 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Jul 31 00:56:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:47 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:48 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:50 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:53 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:56 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:58 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Jul 31 00:56:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:56:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:00 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:03 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:10 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Jul 31 00:57:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:14 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:15 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:20 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:21 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:22 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Jul 31 00:57:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:23 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:23 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:23 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:24 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:26 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
<27>Jul 31 00:57:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-32f23b01-e1" in table Interface
