Jul 22 05:58:31 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8375" x-info="http://www.rsyslog.com"] start
Jul 22 05:58:31 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 22 05:58:31 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 22 05:58:31 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 22 05:58:31 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 22 05:58:31 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 22 05:58:31 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 22 05:58:31 node-1 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 22 05:58:31 node-1 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=bc59c6d4-0742-4cb5-a32f-c652313e5942 nomdmonddf nomdmonisw
Jul 22 05:58:31 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 22 05:58:31 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 22 05:58:31 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 22 05:58:31 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 22 05:58:31 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 22 05:58:31 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 22 05:58:31 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 22 05:58:31 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 22 05:58:31 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 22 05:58:31 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 22 05:58:31 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 22 05:58:31 node-1 kernel: [    0.000000] No AGP bridge found
Jul 22 05:58:31 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 22 05:58:31 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 22 05:58:31 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 22 05:58:31 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 22 05:58:31 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 22 05:58:31 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 22 05:58:31 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 22 05:58:31 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 22 05:58:31 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 22 05:58:31 node-1 kernel: [    0.000000]   2 disabled
Jul 22 05:58:31 node-1 kernel: [    0.000000]   3 disabled
Jul 22 05:58:31 node-1 kernel: [    0.000000]   4 disabled
Jul 22 05:58:31 node-1 kernel: [    0.000000]   5 disabled
Jul 22 05:58:31 node-1 kernel: [    0.000000]   6 disabled
Jul 22 05:58:31 node-1 kernel: [    0.000000]   7 disabled
Jul 22 05:58:31 node-1 kernel: [    0.000000]   8 disabled
Jul 22 05:58:31 node-1 kernel: [    0.000000]   9 disabled
Jul 22 05:58:31 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 22 05:58:31 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 22 05:58:31 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 22 05:58:31 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 22 05:58:31 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 22 05:58:31 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 22 05:58:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 22 05:58:31 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 22 05:58:31 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 22 05:58:31 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 22 05:58:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 22 05:58:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 22 05:58:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 22 05:58:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 22 05:58:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 22 05:58:31 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 22 05:58:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 22 05:58:31 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 22 05:58:31 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 22 05:58:31 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 22 05:58:31 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 22 05:58:31 node-1 kernel: [    0.000000] Zone ranges:
Jul 22 05:58:31 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 22 05:58:31 node-1 kernel: [    0.000000] Early memory node ranges
Jul 22 05:58:31 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 22 05:58:31 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 22 05:58:31 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 22 05:58:31 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 22 05:58:31 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 22 05:58:31 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 22 05:58:31 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 22 05:58:31 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 22 05:58:31 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 22 05:58:31 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 22 05:58:31 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 22 05:58:31 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 22 05:58:31 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 22 05:58:31 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 22 05:58:31 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 22 05:58:31 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 22 05:58:31 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 22 05:58:31 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 22 05:58:31 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 22 05:58:31 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 22 05:58:31 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 22 05:58:31 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 22 05:58:31 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 22 05:58:31 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 22 05:58:31 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 22 05:58:31 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 22 05:58:31 node-1 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=bc59c6d4-0742-4cb5-a32f-c652313e5942 nomdmonddf nomdmonisw
Jul 22 05:58:31 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 22 05:58:31 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 22 05:58:31 node-1 kernel: [    0.000000] Checking aperture...
Jul 22 05:58:31 node-1 kernel: [    0.000000] No AGP bridge found
Jul 22 05:58:31 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 22 05:58:31 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 22 05:58:31 node-1 kernel: [    0.000000] Memory: 32653312K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Jul 22 05:58:31 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 22 05:58:31 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 22 05:58:31 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 22 05:58:31 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 22 05:58:31 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 22 05:58:31 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 22 05:58:31 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 22 05:58:31 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 22 05:58:31 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 22 05:58:31 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 22 05:58:31 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 22 05:58:31 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 22 05:58:31 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 22 05:58:31 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 22 05:58:31 node-1 kernel: [    0.004000] tsc: Detected 3492.116 MHz processor
Jul 22 05:58:31 node-1 kernel: [    0.000004] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.23 BogoMIPS (lpj=13968464)
Jul 22 05:58:31 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 22 05:58:31 node-1 kernel: [    0.000042] Security Framework initialized
Jul 22 05:58:31 node-1 kernel: [    0.000060] AppArmor: AppArmor initialized
Jul 22 05:58:31 node-1 kernel: [    0.000061] Yama: becoming mindful.
Jul 22 05:58:31 node-1 kernel: [    0.001449] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 22 05:58:31 node-1 kernel: [    0.006353] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 22 05:58:31 node-1 kernel: [    0.008283] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 22 05:58:31 node-1 kernel: [    0.008311] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 22 05:58:31 node-1 kernel: [    0.008607] Initializing cgroup subsys memory
Jul 22 05:58:31 node-1 kernel: [    0.008616] Initializing cgroup subsys devices
Jul 22 05:58:31 node-1 kernel: [    0.008617] Initializing cgroup subsys freezer
Jul 22 05:58:31 node-1 kernel: [    0.008619] Initializing cgroup subsys blkio
Jul 22 05:58:31 node-1 kernel: [    0.008621] Initializing cgroup subsys perf_event
Jul 22 05:58:31 node-1 kernel: [    0.008623] Initializing cgroup subsys hugetlb
Jul 22 05:58:31 node-1 kernel: [    0.008642] CPU: Physical Processor ID: 0
Jul 22 05:58:31 node-1 kernel: [    0.008644] CPU: Processor Core ID: 0
Jul 22 05:58:31 node-1 kernel: [    0.008648] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 22 05:58:31 node-1 kernel: [    0.008648] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 22 05:58:31 node-1 kernel: [    0.009342] mce: CPU supports 22 MCE banks
Jul 22 05:58:31 node-1 kernel: [    0.009369] CPU0: Thermal monitoring enabled (TM1)
Jul 22 05:58:31 node-1 kernel: [    0.009389] process: using mwait in idle threads
Jul 22 05:58:31 node-1 kernel: [    0.009392] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 22 05:58:31 node-1 kernel: [    0.009392] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 22 05:58:31 node-1 kernel: [    0.009392] tlb_flushall_shift: 6
Jul 22 05:58:31 node-1 kernel: [    0.009479] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 22 05:58:31 node-1 kernel: [    0.010203] ACPI: Core revision 20131115
Jul 22 05:58:31 node-1 kernel: [    0.022862] ACPI: All ACPI Tables successfully acquired
Jul 22 05:58:31 node-1 kernel: [    0.023024] ftrace: allocating 28617 entries in 112 pages
Jul 22 05:58:31 node-1 kernel: [    0.031838] dmar: Host address width 46
Jul 22 05:58:31 node-1 kernel: [    0.031840] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 22 05:58:31 node-1 kernel: [    0.031846] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 22 05:58:31 node-1 kernel: [    0.031848] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 22 05:58:31 node-1 kernel: [    0.031852] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 22 05:58:31 node-1 kernel: [    0.031853] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 22 05:58:31 node-1 kernel: [    0.031855] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 22 05:58:31 node-1 kernel: [    0.031856] dmar: ATSR flags: 0x0
Jul 22 05:58:31 node-1 kernel: [    0.031857] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 22 05:58:31 node-1 kernel: [    0.031858] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 22 05:58:31 node-1 kernel: [    0.031973] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 22 05:58:31 node-1 kernel: [    0.031974] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 22 05:58:31 node-1 kernel: [    0.031975] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 22 05:58:31 node-1 kernel: [    0.031976] HPET id 0 under DRHD base 0xc7ffc000
Jul 22 05:58:31 node-1 kernel: [    0.031978] Your BIOS is broken and requested that x2apic be disabled.
Jul 22 05:58:31 node-1 kernel: [    0.031978] This will slightly decrease performance.
Jul 22 05:58:31 node-1 kernel: [    0.031978] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 22 05:58:31 node-1 kernel: [    0.032410] Enabled IRQ remapping in xapic mode
Jul 22 05:58:31 node-1 kernel: [    0.032411] x2apic not enabled, IRQ remapping is in xapic mode
Jul 22 05:58:31 node-1 kernel: [    0.032415] Switched APIC routing to physical flat.
Jul 22 05:58:31 node-1 kernel: [    0.033033] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 22 05:58:31 node-1 kernel: [    0.072685] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 22 05:58:31 node-1 kernel: [    0.072691] TSC deadline timer enabled
Jul 22 05:58:31 node-1 kernel: [    0.072698] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 22 05:58:31 node-1 kernel: [    0.072704] ... version:                3
Jul 22 05:58:31 node-1 kernel: [    0.072705] ... bit width:              48
Jul 22 05:58:31 node-1 kernel: [    0.072706] ... generic registers:      4
Jul 22 05:58:31 node-1 kernel: [    0.072707] ... value mask:             0000ffffffffffff
Jul 22 05:58:31 node-1 kernel: [    0.072708] ... max period:             0000ffffffffffff
Jul 22 05:58:31 node-1 kernel: [    0.072709] ... fixed-purpose events:   3
Jul 22 05:58:31 node-1 kernel: [    0.072710] ... event mask:             000000070000000f
Jul 22 05:58:31 node-1 kernel: [    0.074144] x86: Booting SMP configuration:
Jul 22 05:58:31 node-1 kernel: [    0.088250] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 22 05:58:31 node-1 kernel: [    0.074146] .... node  #0, CPUs:        #1  #2  #3
Jul 22 05:58:31 node-1 kernel: [    0.116163] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 22 05:58:31 node-1 kernel: [    0.270114] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 22 05:58:31 node-1 kernel: [    0.325729] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 22 05:58:31 node-1 kernel: [    0.382589] x86: Booted up 2 nodes, 16 CPUs
Jul 22 05:58:31 node-1 kernel: [    0.382593] smpboot: Total of 16 processors activated (111759.64 BogoMIPS)
Jul 22 05:58:31 node-1 kernel: [    0.406633] devtmpfs: initialized
Jul 22 05:58:31 node-1 kernel: [    0.409733] EVM: security.selinux
Jul 22 05:58:31 node-1 kernel: [    0.409735] EVM: security.SMACK64
Jul 22 05:58:31 node-1 kernel: [    0.409736] EVM: security.ima
Jul 22 05:58:31 node-1 kernel: [    0.409737] EVM: security.capability
Jul 22 05:58:31 node-1 kernel: [    0.409785] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 22 05:58:31 node-1 kernel: [    0.410466] pinctrl core: initialized pinctrl subsystem
Jul 22 05:58:31 node-1 kernel: [    0.410526] regulator-dummy: no parameters
Jul 22 05:58:31 node-1 kernel: [    0.410559] RTC time:  5:57:55, date: 07/22/16
Jul 22 05:58:31 node-1 kernel: [    0.410593] NET: Registered protocol family 16
Jul 22 05:58:31 node-1 kernel: [    0.410677] cpuidle: using governor ladder
Jul 22 05:58:31 node-1 kernel: [    0.410678] cpuidle: using governor menu
Jul 22 05:58:31 node-1 kernel: [    0.410713] ACPI: bus type PCI registered
Jul 22 05:58:31 node-1 kernel: [    0.410715] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 22 05:58:31 node-1 kernel: [    0.410760] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 22 05:58:31 node-1 kernel: [    0.410762] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 22 05:58:31 node-1 kernel: [    0.424492] PCI: Using configuration type 1 for base access
Jul 22 05:58:31 node-1 kernel: [    0.425497] bio: create slab <bio-0> at 0
Jul 22 05:58:31 node-1 kernel: [    0.425775] ACPI: Added _OSI(Module Device)
Jul 22 05:58:31 node-1 kernel: [    0.425777] ACPI: Added _OSI(Processor Device)
Jul 22 05:58:31 node-1 kernel: [    0.425778] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 22 05:58:31 node-1 kernel: [    0.425779] ACPI: Added _OSI(Processor Aggregator Device)
Jul 22 05:58:31 node-1 kernel: [    0.438430] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 22 05:58:31 node-1 kernel: [    0.448920] ACPI: Interpreter enabled
Jul 22 05:58:31 node-1 kernel: [    0.448926] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 22 05:58:31 node-1 kernel: [    0.448930] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 22 05:58:31 node-1 kernel: [    0.448932] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 22 05:58:31 node-1 kernel: [    0.448939] ACPI: (supports S0 S4 S5)
Jul 22 05:58:31 node-1 kernel: [    0.448940] ACPI: Using IOAPIC for interrupt routing
Jul 22 05:58:31 node-1 kernel: [    0.448980] HEST: Table parsing has been initialized.
Jul 22 05:58:31 node-1 kernel: [    0.448983] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 22 05:58:31 node-1 kernel: [    0.449534] ACPI: No dock devices found.
Jul 22 05:58:31 node-1 kernel: [    0.461054] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 22 05:58:31 node-1 kernel: [    0.461059] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 05:58:31 node-1 kernel: [    0.461062] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 22 05:58:31 node-1 kernel: [    0.461088] PCI host bridge to bus 0000:ff
Jul 22 05:58:31 node-1 kernel: [    0.461090] pci_bus 0000:ff: root bus resource [bus ff]
Jul 22 05:58:31 node-1 kernel: [    0.461098] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 22 05:58:31 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 22 05:58:31 node-1 kernel: [    0.461136] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.461167] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461201] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461230] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.461259] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.461289] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461318] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461346] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461374] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461400] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461426] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461454] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461480] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461506] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461533] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461562] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461589] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461618] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.461646] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461671] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.461697] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461725] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461755] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.461790] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461821] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461851] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461882] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461913] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461944] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.461975] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462005] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462035] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462069] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462102] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462135] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462169] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462199] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462227] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462260] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462294] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462333] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462366] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462399] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462428] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462457] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462487] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462518] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462550] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462581] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462612] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462642] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462671] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462701] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462730] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462762] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462797] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462854] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 22 05:58:31 node-1 kernel: [    0.462857] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 05:58:31 node-1 kernel: [    0.462860] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 22 05:58:31 node-1 kernel: [    0.462878] PCI host bridge to bus 0000:7f
Jul 22 05:58:31 node-1 kernel: [    0.462879] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 22 05:58:31 node-1 kernel: [    0.462884] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462912] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.462941] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462971] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.462992] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.463017] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.463044] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463070] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463092] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463115] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463138] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463160] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463184] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463206] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463236] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463265] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463287] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463310] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463335] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.463360] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463383] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.463405] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463428] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463454] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 22 05:58:31 node-1 kernel: [    0.463488] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463514] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463541] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463569] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463594] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463622] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463649] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463679] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463706] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463734] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463762] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463791] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463820] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463844] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463869] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463897] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463922] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463948] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.463978] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464007] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464033] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464058] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464084] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464111] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464136] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464162] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464193] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464219] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464242] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464267] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464292] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464322] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.464349] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.465606] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 22 05:58:31 node-1 kernel: [    0.465609] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 05:58:31 node-1 kernel: [    0.466727] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 22 05:58:31 node-1 kernel: [    0.467237] PCI host bridge to bus 0000:00
Jul 22 05:58:31 node-1 kernel: [    0.467239] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 22 05:58:31 node-1 kernel: [    0.467241] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 22 05:58:31 node-1 kernel: [    0.467242] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 22 05:58:31 node-1 kernel: [    0.467244] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 22 05:58:31 node-1 kernel: [    0.467245] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 22 05:58:31 node-1 kernel: [    0.467246] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 22 05:58:31 node-1 kernel: [    0.467248] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 22 05:58:31 node-1 kernel: [    0.467254] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 22 05:58:31 node-1 kernel: [    0.467336] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.467367] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.467408] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 22 05:58:31 node-1 kernel: [    0.467427] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.467456] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.467496] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 22 05:58:31 node-1 kernel: [    0.467514] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.467544] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.467586] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 22 05:58:31 node-1 kernel: [    0.467603] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.467673] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.467749] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.467823] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 22 05:58:31 node-1 kernel: [    0.467828] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 22 05:58:31 node-1 kernel: [    0.467912] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 22 05:58:31 node-1 kernel: [    0.468058] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 22 05:58:31 node-1 kernel: [    0.468075] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 22 05:58:31 node-1 kernel: [    0.468153] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.468207] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 22 05:58:31 node-1 kernel: [    0.468228] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.468283] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.468326] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 22 05:58:31 node-1 kernel: [    0.468352] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.468408] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.468451] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 22 05:58:31 node-1 kernel: [    0.468475] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 22 05:58:31 node-1 kernel: [    0.468492] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 22 05:58:31 node-1 kernel: [    0.468569] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.468619] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 22 05:58:31 node-1 kernel: [    0.468644] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 22 05:58:31 node-1 kernel: [    0.468890] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 22 05:58:31 node-1 kernel: [    0.468896] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 22 05:58:31 node-1 kernel: [    0.468902] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 22 05:58:31 node-1 kernel: [    0.468907] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 22 05:58:31 node-1 kernel: [    0.468915] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 22 05:58:31 node-1 kernel: [    0.468945] pci 0000:01:00.0: supports D1 D2
Jul 22 05:58:31 node-1 kernel: [    0.479226] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 22 05:58:31 node-1 kernel: [    0.479229] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 22 05:58:31 node-1 kernel: [    0.479231] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 22 05:58:31 node-1 kernel: [    0.479337] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.479370] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 22 05:58:31 node-1 kernel: [    0.487232] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 22 05:58:31 node-1 kernel: [    0.487238] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.487242] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 05:58:31 node-1 kernel: [    0.487326] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.487398] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 22 05:58:31 node-1 kernel: [    0.487493] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.487562] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 22 05:58:31 node-1 kernel: [    0.487565] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.487567] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 05:58:31 node-1 kernel: [    0.487619] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.487741] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.487794] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 22 05:58:31 node-1 kernel: [    0.487797] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.487799] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 05:58:31 node-1 kernel: [    0.487848] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.487971] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.488028] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.488148] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.488185] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.488305] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.488342] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 22 05:58:31 node-1 kernel: [    0.488460] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 22 05:58:31 node-1 kernel: [    0.488503] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 22 05:58:31 node-1 kernel: [    0.488505] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.488507] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 05:58:31 node-1 kernel: [    0.488565] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 22 05:58:31 node-1 kernel: [    0.488627] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 22 05:58:31 node-1 kernel: [    0.488680] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 22 05:58:31 node-1 kernel: [    0.488721] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 22 05:58:31 node-1 kernel: [    0.488803] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 22 05:58:31 node-1 kernel: [    0.488908] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 22 05:58:31 node-1 kernel: [    0.488911] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.488913] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 22 05:58:31 node-1 kernel: [    0.488968] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 22 05:58:31 node-1 kernel: [    0.489046] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 22 05:58:31 node-1 kernel: [    0.489095] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 22 05:58:31 node-1 kernel: [    0.489305] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 22 05:58:31 node-1 kernel: [    0.489308] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 22 05:58:31 node-1 kernel: [    0.489371] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 22 05:58:31 node-1 kernel: [    0.489428] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 22 05:58:31 node-1 kernel: [    0.489476] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 22 05:58:31 node-1 kernel: [    0.489686] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 22 05:58:31 node-1 kernel: [    0.489689] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 22 05:58:31 node-1 kernel: [    0.489748] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 22 05:58:31 node-1 kernel: [    0.489808] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 22 05:58:31 node-1 kernel: [    0.489860] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 22 05:58:31 node-1 kernel: [    0.490105] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 22 05:58:31 node-1 kernel: [    0.490109] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 22 05:58:31 node-1 kernel: [    0.490282] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 22 05:58:31 node-1 kernel: [    0.490320] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 22 05:58:31 node-1 kernel: [    0.490394] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 22 05:58:31 node-1 kernel: [    0.490413] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 22 05:58:31 node-1 kernel: [    0.490426] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 22 05:58:31 node-1 kernel: [    0.490439] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 22 05:58:31 node-1 kernel: [    0.490489] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 22 05:58:31 node-1 kernel: [    0.495239] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 22 05:58:31 node-1 kernel: [    0.495248] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 22 05:58:31 node-1 kernel: [    0.495294] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 22 05:58:31 node-1 kernel: [    0.495782] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 22 05:58:31 node-1 kernel: [    0.495785] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 05:58:31 node-1 kernel: [    0.495908] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 22 05:58:31 node-1 kernel: [    0.496012] PCI host bridge to bus 0000:80
Jul 22 05:58:31 node-1 kernel: [    0.496014] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 22 05:58:31 node-1 kernel: [    0.496016] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 22 05:58:31 node-1 kernel: [    0.496017] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 22 05:58:31 node-1 kernel: [    0.496025] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.496087] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.496155] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 22 05:58:31 node-1 kernel: [    0.496216] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 22 05:58:31 node-1 kernel: [    0.496221] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 22 05:58:31 node-1 kernel: [    0.496293] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 22 05:58:31 node-1 kernel: [    0.496592] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 22 05:58:31 node-1 kernel: [    0.496623] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 22 05:58:31 node-1 kernel: [    0.496653] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 22 05:58:31 node-1 kernel: [    0.496682] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 22 05:58:31 node-1 kernel: [    0.496711] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 05:58:31 node-1 kernel: [    0.496741] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 05:58:31 node-1 kernel: [    0.496770] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 05:58:31 node-1 kernel: [    0.496800] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 05:58:31 node-1 kernel: [    0.496884] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 22 05:58:31 node-1 kernel: [    0.496888] ACPI: \_SB_.UNC1: notify handler is installed
Jul 22 05:58:31 node-1 kernel: [    0.496889] ACPI: \_SB_.UNC0: notify handler is installed
Jul 22 05:58:31 node-1 kernel: [    0.496904] ACPI: \_SB_.PCI0: notify handler is installed
Jul 22 05:58:31 node-1 kernel: [    0.496957] ACPI: \_SB_.PCI1: notify handler is installed
Jul 22 05:58:31 node-1 kernel: [    0.497036] Found 4 acpi root devices
Jul 22 05:58:31 node-1 kernel: [    0.497142] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 22 05:58:31 node-1 kernel: [    0.497144] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 22 05:58:31 node-1 kernel: [    0.497145] vgaarb: loaded
Jul 22 05:58:31 node-1 kernel: [    0.497147] vgaarb: bridge control possible 0000:0c:00.0
Jul 22 05:58:31 node-1 kernel: [    0.497259] SCSI subsystem initialized
Jul 22 05:58:31 node-1 kernel: [    0.497323] libata version 3.00 loaded.
Jul 22 05:58:31 node-1 kernel: [    0.497338] ACPI: bus type USB registered
Jul 22 05:58:31 node-1 kernel: [    0.497348] usbcore: registered new interface driver usbfs
Jul 22 05:58:31 node-1 kernel: [    0.497352] usbcore: registered new interface driver hub
Jul 22 05:58:31 node-1 kernel: [    0.497388] usbcore: registered new device driver usb
Jul 22 05:58:31 node-1 kernel: [    0.497544] PCI: Using ACPI for IRQ routing
Jul 22 05:58:31 node-1 kernel: [    0.501130] PCI: pci_cache_line_size set to 64 bytes
Jul 22 05:58:31 node-1 kernel: [    0.501340] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 22 05:58:31 node-1 kernel: [    0.501342] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 22 05:58:31 node-1 kernel: [    0.501342] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 22 05:58:31 node-1 kernel: [    0.501410] NetLabel: Initializing
Jul 22 05:58:31 node-1 kernel: [    0.501411] NetLabel:  domain hash size = 128
Jul 22 05:58:31 node-1 kernel: [    0.501412] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 22 05:58:31 node-1 kernel: [    0.501421] NetLabel:  unlabeled traffic allowed by default
Jul 22 05:58:31 node-1 kernel: [    0.501478] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 22 05:58:31 node-1 kernel: [    0.501482] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 22 05:58:31 node-1 kernel: [    0.503552] Switched to clocksource hpet
Jul 22 05:58:31 node-1 kernel: [    0.507943] AppArmor: AppArmor Filesystem Enabled
Jul 22 05:58:31 node-1 kernel: [    0.507981] pnp: PnP ACPI init
Jul 22 05:58:31 node-1 kernel: [    0.507993] ACPI: bus type PNP registered
Jul 22 05:58:31 node-1 kernel: [    0.508179] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 22 05:58:31 node-1 kernel: [    0.508190] pnp 00:01: [dma 4]
Jul 22 05:58:31 node-1 kernel: [    0.508209] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 22 05:58:31 node-1 kernel: [    0.508243] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 22 05:58:31 node-1 kernel: [    0.508268] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 22 05:58:31 node-1 kernel: [    0.508289] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 22 05:58:31 node-1 kernel: [    0.508337] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 22 05:58:31 node-1 kernel: [    0.508449] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 22 05:58:31 node-1 kernel: [    0.508452] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 22 05:58:31 node-1 kernel: [    0.508454] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 22 05:58:31 node-1 kernel: [    0.508455] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 22 05:58:31 node-1 kernel: [    0.508457] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 22 05:58:31 node-1 kernel: [    0.508458] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 22 05:58:31 node-1 kernel: [    0.508462] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 22 05:58:31 node-1 kernel: [    0.508463] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 22 05:58:31 node-1 kernel: [    0.508465] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 22 05:58:31 node-1 kernel: [    0.508466] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 22 05:58:31 node-1 kernel: [    0.508468] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 22 05:58:31 node-1 kernel: [    0.508469] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 22 05:58:31 node-1 kernel: [    0.508471] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 22 05:58:31 node-1 kernel: [    0.508473] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 22 05:58:31 node-1 kernel: [    0.508574] pnp 00:07: [dma 0 disabled]
Jul 22 05:58:31 node-1 kernel: [    0.508606] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 22 05:58:31 node-1 kernel: [    0.508688] pnp 00:08: [dma 0 disabled]
Jul 22 05:58:31 node-1 kernel: [    0.508724] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 22 05:58:31 node-1 kernel: [    0.508781] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 22 05:58:31 node-1 kernel: [    0.509221] pnp: PnP ACPI: found 10 devices
Jul 22 05:58:31 node-1 kernel: [    0.509223] ACPI: bus type PNP unregistered
Jul 22 05:58:31 node-1 kernel: [    0.515222] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 22 05:58:31 node-1 kernel: [    0.515226] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 22 05:58:31 node-1 kernel: [    0.515229] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 22 05:58:31 node-1 kernel: [    0.515234] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 22 05:58:31 node-1 kernel: [    0.515236] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.515250] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515280] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 22 05:58:31 node-1 kernel: [    0.515294] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515323] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 22 05:58:31 node-1 kernel: [    0.515338] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 22 05:58:31 node-1 kernel: [    0.515367] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 22 05:58:31 node-1 kernel: [    0.515381] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 22 05:58:31 node-1 kernel: [    0.515413] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 22 05:58:31 node-1 kernel: [    0.515415] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.515430] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515458] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 22 05:58:31 node-1 kernel: [    0.515460] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.515475] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515504] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 22 05:58:31 node-1 kernel: [    0.515506] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.515509] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515513] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 22 05:58:31 node-1 kernel: [    0.515515] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.515518] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515522] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 22 05:58:31 node-1 kernel: [    0.515533] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 22 05:58:31 node-1 kernel: [    0.515541] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 22 05:58:31 node-1 kernel: [    0.515545] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 22 05:58:31 node-1 kernel: [    0.515552] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 22 05:58:31 node-1 kernel: [    0.515553] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 22 05:58:31 node-1 kernel: [    0.515554] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 22 05:58:31 node-1 kernel: [    0.515555] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 22 05:58:31 node-1 kernel: [    0.515556] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 22 05:58:31 node-1 kernel: [    0.515557] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 22 05:58:31 node-1 kernel: [    0.515558] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 22 05:58:31 node-1 kernel: [    0.515559] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 22 05:58:31 node-1 kernel: [    0.515560] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.515561] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515562] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.515563] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515564] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.515565] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515566] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.515567] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515568] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 22 05:58:31 node-1 kernel: [    0.515569] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515570] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 22 05:58:31 node-1 kernel: [    0.515571] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 22 05:58:31 node-1 kernel: [    0.515572] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 22 05:58:31 node-1 kernel: [    0.515574] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 22 05:58:31 node-1 kernel: [    0.515576] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 22 05:58:31 node-1 kernel: [    0.515577] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 22 05:58:31 node-1 kernel: [    0.515618] NET: Registered protocol family 2
Jul 22 05:58:31 node-1 kernel: [    0.515932] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 22 05:58:31 node-1 kernel: [    0.516303] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 22 05:58:31 node-1 kernel: [    0.516468] TCP: Hash tables configured (established 262144 bind 65536)
Jul 22 05:58:31 node-1 kernel: [    0.516513] TCP: reno registered
Jul 22 05:58:31 node-1 kernel: [    0.516543] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 22 05:58:31 node-1 kernel: [    0.516668] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 22 05:58:31 node-1 kernel: [    0.516824] NET: Registered protocol family 1
Jul 22 05:58:31 node-1 kernel: [    0.551644] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 22 05:58:31 node-1 kernel: [    0.551659] PCI: CLS 64 bytes, default 64
Jul 22 05:58:31 node-1 kernel: [    0.551743] Trying to unpack rootfs image as initramfs...
Jul 22 05:58:31 node-1 kernel: [    0.773466] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Jul 22 05:58:31 node-1 kernel: [    0.773512] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 22 05:58:31 node-1 kernel: [    0.773515] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 22 05:58:31 node-1 kernel: [    0.773966] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.773990] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.773998] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774006] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774014] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774022] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774029] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774033] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774040] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774047] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774058] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774064] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774071] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774078] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774083] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774089] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 05:58:31 node-1 kernel: [    0.774137] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 22 05:58:31 node-1 kernel: [    0.774139] Scanning for low memory corruption every 60 seconds
Jul 22 05:58:31 node-1 kernel: [    0.774462] Initialise system trusted keyring
Jul 22 05:58:31 node-1 kernel: [    0.774510] audit: initializing netlink socket (disabled)
Jul 22 05:58:31 node-1 kernel: [    0.774521] type=2000 audit(1469167074.728:1): initialized
Jul 22 05:58:31 node-1 kernel: [    0.792431] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 22 05:58:31 node-1 kernel: [    0.793905] zbud: loaded
Jul 22 05:58:31 node-1 kernel: [    0.794026] VFS: Disk quotas dquot_6.5.2
Jul 22 05:58:31 node-1 kernel: [    0.794068] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 22 05:58:31 node-1 kernel: [    0.794424] fuse init (API version 7.22)
Jul 22 05:58:31 node-1 kernel: [    0.794479] msgmni has been set to 32768
Jul 22 05:58:31 node-1 kernel: [    0.794523] Key type big_key registered
Jul 22 05:58:31 node-1 kernel: [    0.795020] Key type asymmetric registered
Jul 22 05:58:31 node-1 kernel: [    0.795022] Asymmetric key parser 'x509' registered
Jul 22 05:58:31 node-1 kernel: [    0.795044] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 22 05:58:31 node-1 kernel: [    0.795113] io scheduler noop registered
Jul 22 05:58:31 node-1 kernel: [    0.795114] io scheduler deadline registered (default)
Jul 22 05:58:31 node-1 kernel: [    0.795133] io scheduler cfq registered
Jul 22 05:58:31 node-1 kernel: [    0.795668] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    0.795856] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    0.795971] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    0.796100] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    0.796213] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    0.796317] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    0.796692] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 22 05:58:31 node-1 kernel: [    0.796719] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 22 05:58:31 node-1 kernel: [    0.796735] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 22 05:58:31 node-1 kernel: [    0.796748] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796750] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796753] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 22 05:58:31 node-1 kernel: [    0.796758] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796760] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796761] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796763] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796765] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796767] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796768] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796770] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796771] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796773] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796774] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796776] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796778] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 22 05:58:31 node-1 kernel: [    0.796790] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796792] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 22 05:58:31 node-1 kernel: [    0.796804] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796807] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 22 05:58:31 node-1 kernel: [    0.796827] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796829] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 22 05:58:31 node-1 kernel: [    0.796832] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 22 05:58:31 node-1 kernel: [    0.796874] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 22 05:58:31 node-1 kernel: [    0.796879] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 22 05:58:31 node-1 kernel: [    0.796883] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 22 05:58:31 node-1 kernel: [    0.796892] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 22 05:58:31 node-1 kernel: [    0.796928] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 22 05:58:31 node-1 kernel: [    0.796929] vesafb: scrolling: redraw
Jul 22 05:58:31 node-1 kernel: [    0.796931] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 22 05:58:31 node-1 kernel: [    0.817503] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 22 05:58:31 node-1 kernel: [    0.825985] Console: switching to colour frame buffer device 80x30
Jul 22 05:58:31 node-1 kernel: [    0.834652] fb0: VESA VGA frame buffer device
Jul 22 05:58:31 node-1 kernel: [    0.834853] intel_idle: MWAIT substates: 0x2120
Jul 22 05:58:31 node-1 kernel: [    0.834854] intel_idle: v0.4 model 0x3F
Jul 22 05:58:31 node-1 kernel: [    0.834855] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 22 05:58:31 node-1 kernel: [    0.835087] ipmi message handler version 39.2
Jul 22 05:58:31 node-1 kernel: [    0.835383] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 22 05:58:31 node-1 kernel: [    0.835815] ACPI: AC Adapter [P111] (on-line)
Jul 22 05:58:31 node-1 kernel: [    0.841058] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 22 05:58:31 node-1 kernel: [    0.852086] ACPI: Power Button [PWRB]
Jul 22 05:58:31 node-1 kernel: [    0.857905] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 22 05:58:31 node-1 kernel: [    0.869582] ACPI: Power Button [PWRF]
Jul 22 05:58:31 node-1 kernel: [    0.889141] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 22 05:58:31 node-1 kernel: [    0.900823] pstore: Registered erst as persistent store backend
Jul 22 05:58:31 node-1 kernel: [    0.907097] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 22 05:58:31 node-1 kernel: [    0.919038] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 22 05:58:31 node-1 kernel: [    0.945780] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 22 05:58:31 node-1 kernel: [    0.979082] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 22 05:58:31 node-1 kernel: [    0.993209] Linux agpgart interface v0.103
Jul 22 05:58:31 node-1 kernel: [    1.000849] brd: module loaded
Jul 22 05:58:31 node-1 kernel: [    1.007887] loop: module loaded
Jul 22 05:58:31 node-1 kernel: [    1.014605] libphy: Fixed MDIO Bus: probed
Jul 22 05:58:31 node-1 kernel: [    1.021079] tun: Universal TUN/TAP device driver, 1.6
Jul 22 05:58:31 node-1 kernel: [    1.027629] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 22 05:58:31 node-1 kernel: [    1.034248] PPP generic driver version 2.4.2
Jul 22 05:58:31 node-1 kernel: [    1.040635] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 22 05:58:31 node-1 kernel: [    1.047066] ehci-pci: EHCI PCI platform driver
Jul 22 05:58:31 node-1 kernel: [    1.053569] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 22 05:58:31 node-1 kernel: [    1.059966] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 22 05:58:31 node-1 kernel: [    1.072470] ehci-pci 0000:00:1a.0: debug port 2
Jul 22 05:58:31 node-1 kernel: [    1.082656] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 22 05:58:31 node-1 kernel: [    1.082674] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 22 05:58:31 node-1 kernel: [    1.099039] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 22 05:58:31 node-1 kernel: [    1.105098] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 22 05:58:31 node-1 kernel: [    1.111253] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 22 05:58:31 node-1 kernel: [    1.123138] usb usb1: Product: EHCI Host Controller
Jul 22 05:58:31 node-1 kernel: [    1.129162] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 22 05:58:31 node-1 kernel: [    1.135192] usb usb1: SerialNumber: 0000:00:1a.0
Jul 22 05:58:31 node-1 kernel: [    1.141124] hub 1-0:1.0: USB hub found
Jul 22 05:58:31 node-1 kernel: [    1.146884] hub 1-0:1.0: 2 ports detected
Jul 22 05:58:31 node-1 kernel: [    1.152677] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 22 05:58:31 node-1 kernel: [    1.158236] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 22 05:58:31 node-1 kernel: [    1.169100] ehci-pci 0000:00:1d.0: debug port 2
Jul 22 05:58:31 node-1 kernel: [    1.178368] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 22 05:58:31 node-1 kernel: [    1.178371] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 22 05:58:31 node-1 kernel: [    1.194958] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 22 05:58:31 node-1 kernel: [    1.200136] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 22 05:58:31 node-1 kernel: [    1.205426] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 22 05:58:31 node-1 kernel: [    1.215967] usb usb2: Product: EHCI Host Controller
Jul 22 05:58:31 node-1 kernel: [    1.221408] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 22 05:58:31 node-1 kernel: [    1.226947] usb usb2: SerialNumber: 0000:00:1d.0
Jul 22 05:58:31 node-1 kernel: [    1.232438] hub 2-0:1.0: USB hub found
Jul 22 05:58:31 node-1 kernel: [    1.237787] hub 2-0:1.0: 2 ports detected
Jul 22 05:58:31 node-1 kernel: [    1.243075] ehci-platform: EHCI generic platform driver
Jul 22 05:58:31 node-1 kernel: [    1.248312] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 22 05:58:31 node-1 kernel: [    1.253620] ohci-pci: OHCI PCI platform driver
Jul 22 05:58:31 node-1 kernel: [    1.258917] ohci-platform: OHCI generic platform driver
Jul 22 05:58:31 node-1 kernel: [    1.264105] uhci_hcd: USB Universal Host Controller Interface driver
Jul 22 05:58:31 node-1 kernel: [    1.269453] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 22 05:58:31 node-1 kernel: [    1.462737] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 22 05:58:31 node-1 kernel: [    1.770521] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 22 05:58:31 node-1 kernel: [    1.786793] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 22 05:58:31 node-1 kernel: [    1.792399] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 22 05:58:31 node-1 kernel: [    1.798061] hub 1-1:1.0: USB hub found
Jul 22 05:58:31 node-1 kernel: [    1.803530] hub 1-1:1.0: 6 ports detected
Jul 22 05:58:31 node-1 kernel: [    1.918373] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 22 05:58:31 node-1 kernel: [    2.308692] i8042: No controller found
Jul 22 05:58:31 node-1 kernel: [    2.314247] mousedev: PS/2 mouse device common for all mice
Jul 22 05:58:31 node-1 kernel: [    2.319992] rtc_cmos 00:02: RTC can wake from S4
Jul 22 05:58:31 node-1 kernel: [    2.322782] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 22 05:58:31 node-1 kernel: [    2.322782] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 22 05:58:31 node-1 kernel: [    2.323424] hub 2-1:1.0: USB hub found
Jul 22 05:58:31 node-1 kernel: [    2.323656] hub 2-1:1.0: 8 ports detected
Jul 22 05:58:31 node-1 kernel: [    2.348306] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 22 05:58:31 node-1 kernel: [    2.354120] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 22 05:58:31 node-1 kernel: [    2.365553] device-mapper: uevent: version 1.0.3
Jul 22 05:58:31 node-1 kernel: [    2.371287] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 22 05:58:31 node-1 kernel: [    2.382679] ledtrig-cpu: registered to indicate activity on CPUs
Jul 22 05:58:31 node-1 kernel: [    2.388664] TCP: cubic registered
Jul 22 05:58:31 node-1 kernel: [    2.394549] NET: Registered protocol family 10
Jul 22 05:58:31 node-1 kernel: [    2.400625] NET: Registered protocol family 17
Jul 22 05:58:31 node-1 kernel: [    2.406400] Key type dns_resolver registered
Jul 22 05:58:31 node-1 kernel: [    2.412510] Loading compiled-in X.509 certificates
Jul 22 05:58:31 node-1 kernel: [    2.418773] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 22 05:58:31 node-1 kernel: [    2.430498] registered taskstats version 1
Jul 22 05:58:31 node-1 kernel: [    2.438631] Key type trusted registered
Jul 22 05:58:31 node-1 kernel: [    2.446336] Key type encrypted registered
Jul 22 05:58:31 node-1 kernel: [    2.451844] AppArmor: AppArmor sha1 policy hashing enabled
Jul 22 05:58:31 node-1 kernel: [    2.457354] IMA: No TPM chip found, activating TPM-bypass!
Jul 22 05:58:31 node-1 kernel: [    2.463466] regulator-dummy: disabling
Jul 22 05:58:31 node-1 kernel: [    2.468988]   Magic number: 8:629:972
Jul 22 05:58:31 node-1 kernel: [    2.474490] pci 0000:7f:14.1: hash matches
Jul 22 05:58:31 node-1 kernel: [    2.480164] rtc_cmos 00:02: setting system clock to 2016-07-22 05:57:57 UTC (1469167077)
Jul 22 05:58:31 node-1 kernel: [    2.492520] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 22 05:58:31 node-1 kernel: [    2.498145] EDD information not available.
Jul 22 05:58:31 node-1 kernel: [    2.503684] PM: Hibernation image not present or could not be loaded.
Jul 22 05:58:31 node-1 kernel: [    2.504554] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 22 05:58:31 node-1 kernel: [    2.515785] Write protecting the kernel read-only data: 12288k
Jul 22 05:58:31 node-1 kernel: [    2.522142] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 22 05:58:31 node-1 kernel: [    2.535000] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 22 05:58:31 node-1 kernel: [    2.567733] device-mapper: multipath: version 1.6.0 loaded
Jul 22 05:58:31 node-1 kernel: [    2.575563] systemd-udevd[216]: starting version 204
Jul 22 05:58:31 node-1 kernel: [    2.599716] md: linear personality registered for level -1
Jul 22 05:58:31 node-1 kernel: [    2.601978] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 22 05:58:31 node-1 kernel: [    2.620252] md: multipath personality registered for level -4
Jul 22 05:58:31 node-1 kernel: [    2.628262] md: raid0 personality registered for level 0
Jul 22 05:58:31 node-1 kernel: [    2.636547] md: raid1 personality registered for level 1
Jul 22 05:58:31 node-1 kernel: [    2.644538] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 22 05:58:31 node-1 kernel: [    2.650774] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 22 05:58:31 node-1 kernel: [    2.650974] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 22 05:58:31 node-1 kernel: [    2.663351] megasas: FW now in Ready state
Jul 22 05:58:31 node-1 kernel: [    2.663509] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 22 05:58:31 node-1 kernel: [    2.663510] 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 22 05:58:31 node-1 kernel: [    2.663511] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 05:58:31 node-1 kernel: [    2.663777] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.663988] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.664123] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.664252] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.664475] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.682598] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 22 05:58:31 node-1 kernel: [    2.682599] 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 22 05:58:31 node-1 kernel: [    2.682600] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 05:58:31 node-1 kernel: [    2.682907] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.683032] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.683143] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.683259] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.683437] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.699985] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 22 05:58:31 node-1 kernel: [    2.699986] 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 22 05:58:31 node-1 kernel: [    2.699987] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 05:58:31 node-1 kernel: [    2.700275] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.700384] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.700472] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.700568] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.700975] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.715803] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 22 05:58:31 node-1 kernel: [    2.715808] 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 22 05:58:31 node-1 kernel: [    2.715809] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 05:58:31 node-1 kernel: [    2.716166] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.716239] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.716332] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.716504] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.716852] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 05:58:31 node-1 kernel: [    2.726692] raid6: sse2x1   11322 MB/s
Jul 22 05:58:31 node-1 kernel: [    2.741757] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 22 05:58:31 node-1 kernel: [    2.741761] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 22 05:58:31 node-1 kernel: [    2.741766] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 22 05:58:31 node-1 kernel: [    2.741772] usb 2-1.4: Manufacturer: Avocent
Jul 22 05:58:31 node-1 kernel: [    2.741772] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 22 05:58:31 node-1 kernel: [    2.905402] raid6: sse2x2   29310 MB/s
Jul 22 05:58:31 node-1 kernel: [    2.977458] raid6: sse2x4   10140 MB/s
Jul 22 05:58:31 node-1 kernel: [    3.049399] raid6: avx2x1   14958 MB/s
Jul 22 05:58:31 node-1 kernel: [    3.121333] raid6: avx2x2   18867 MB/s
Jul 22 05:58:31 node-1 kernel: [    3.193276] raid6: avx2x4   21376 MB/s
Jul 22 05:58:31 node-1 kernel: [    3.198937] raid6: using algorithm sse2x2 (29310 MB/s)
Jul 22 05:58:31 node-1 kernel: [    3.204565] raid6: using avx2x2 recovery algorithm
Jul 22 05:58:31 node-1 kernel: [    3.210265] Switched to clocksource tsc
Jul 22 05:58:31 node-1 kernel: [    3.210345] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210394] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210418] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210454] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210496] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210540] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210579] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210620] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210661] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210703] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210739] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210776] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210811] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210847] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210896] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.210929] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 22 05:58:31 node-1 kernel: [    3.211093] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 22 05:58:31 node-1 kernel: [    3.227681] xor: automatically using best checksumming function:
Jul 22 05:58:31 node-1 kernel: [    3.241878] hidraw: raw HID events driver (C) Jiri Kosina
Jul 22 05:58:31 node-1 kernel: [    3.250231] usbcore: registered new interface driver usbhid
Jul 22 05:58:31 node-1 kernel: [    3.255675] usbhid: USB HID core driver
Jul 22 05:58:31 node-1 kernel: [    3.262053] 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 22 05:58:31 node-1 kernel: [    3.273193]    avx       : 35891.000 MB/sec
Jul 22 05:58:31 node-1 kernel: [    3.278697] 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 22 05:58:31 node-1 kernel: [    3.289790] async_tx: api initialized (async)
Jul 22 05:58:31 node-1 kernel: [    3.289832] 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 22 05:58:31 node-1 kernel: [    3.289879] 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 22 05:58:31 node-1 kernel: [    3.289933] 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 22 05:58:31 node-1 kernel: [    3.289978] 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 22 05:58:31 node-1 kernel: [    3.346647] md: raid6 personality registered for level 6
Jul 22 05:58:31 node-1 kernel: [    3.353031] md: raid5 personality registered for level 5
Jul 22 05:58:31 node-1 kernel: [    3.359268] md: raid4 personality registered for level 4
Jul 22 05:58:31 node-1 kernel: [    3.368459] md: raid10 personality registered for level 10
Jul 22 05:58:31 node-1 kernel: [    3.423849] multipathd (355): /proc/355/oom_adj is deprecated, please use /proc/355/oom_score_adj instead.
Jul 22 05:58:31 node-1 kernel: [    3.545007] megasas:IOC Init cmd success
Jul 22 05:58:31 node-1 kernel: [    3.596976] megasas: INIT adapter done
Jul 22 05:58:31 node-1 kernel: [    3.672928] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 22 05:58:31 node-1 kernel: [    3.679841] scsi0 : LSI SAS based MegaRAID driver
Jul 22 05:58:31 node-1 kernel: [    3.687194] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 22 05:58:31 node-1 kernel: [    3.723519] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 22 05:58:31 node-1 kernel: [    3.739816] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 22 05:58:31 node-1 kernel: [    3.739953] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 22 05:58:31 node-1 kernel: [    3.740697] sd 0:2:0:0: [sda] Write Protect is off
Jul 22 05:58:31 node-1 kernel: [    3.740704] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 22 05:58:31 node-1 kernel: [    3.741124] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 22 05:58:31 node-1 kernel: [    3.775360]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 22 05:58:31 node-1 kernel: [    3.780310] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 22 05:58:31 node-1 kernel: [    3.919667] random: lvm urandom read with 28 bits of entropy available
Jul 22 05:58:31 node-1 kernel: [    4.117680] bio: create slab <bio-1> at 1
Jul 22 05:58:31 node-1 kernel: [    4.877926] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 05:58:31 node-1 kernel: [    5.564266] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 22 05:58:31 node-1 kernel: [    5.612649] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 22 05:58:31 node-1 kernel: [    5.712029] random: nonblocking pool is initialized
Jul 22 05:58:31 node-1 kernel: [    5.849658] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 22 05:58:31 node-1 kernel: [    5.921443] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 22 05:58:31 node-1 kernel: [    5.967860] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 05:58:31 node-1 kernel: [    6.125248] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 22 05:58:31 node-1 kernel: [    6.153108] XFS (dm-0): Mounting Filesystem
Jul 22 05:58:31 node-1 kernel: [    6.431173] XFS (dm-0): Ending clean mount
Jul 22 05:58:31 node-1 kernel: [    6.468468] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 05:58:31 node-1 kernel: [    6.497159] XFS (dm-1): Mounting Filesystem
Jul 22 05:58:31 node-1 kernel: [    6.580301] XFS (dm-1): Ending clean mount
Jul 22 05:58:31 node-1 kernel: [    8.544600] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 22 05:58:31 node-1 kernel: [    8.573067] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 22 05:58:31 node-1 kernel: [    8.690405] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 22 05:58:31 node-1 kernel: [    8.690410] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 22 05:58:31 node-1 kernel: [    8.690413] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 22 05:58:31 node-1 kernel: [    8.690417] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 22 05:58:31 node-1 kernel: [    8.731157] systemd-udevd[778]: starting version 204
Jul 22 05:58:31 node-1 kernel: [    8.918349] power_meter ACPI000D:00: Found ACPI power meter.
Jul 22 05:58:31 node-1 kernel: [    8.918413] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 22 05:58:31 node-1 kernel: [    8.946600] IPMI System Interface driver.
Jul 22 05:58:31 node-1 kernel: [    8.946643] ipmi_si: probing via ACPI
Jul 22 05:58:31 node-1 kernel: [    8.946656] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 22 05:58:31 node-1 kernel: [    8.946657] ipmi_si: Adding ACPI-specified kcs state machine
Jul 22 05:58:31 node-1 kernel: [    8.946665] ipmi_si: probing via SMBIOS
Jul 22 05:58:31 node-1 kernel: [    8.946665] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 22 05:58:31 node-1 kernel: [    8.946666] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 22 05:58:31 node-1 kernel: [    8.946668] ipmi_si: probing via SPMI
Jul 22 05:58:31 node-1 kernel: [    8.946668] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 22 05:58:31 node-1 kernel: [    8.946669] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 22 05:58:31 node-1 kernel: [    8.946670] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 22 05:58:31 node-1 kernel: [    8.954909] wmi: Mapper loaded
Jul 22 05:58:31 node-1 kernel: [    8.988386] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 22 05:58:31 node-1 kernel: [    8.988391] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 22 05:58:31 node-1 kernel: [    8.988393] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 22 05:58:31 node-1 kernel: [    8.988395] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 22 05:58:31 node-1 kernel: [    8.988407] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 22 05:58:31 node-1 kernel: [    9.001504] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 22 05:58:31 node-1 kernel: [    9.068762] systemd-udevd[797]: renamed network interface eth2 to enp8s0
Jul 22 05:58:31 node-1 kernel: [    9.088661] systemd-udevd[807]: renamed network interface eth3 to enp9s0
Jul 22 05:58:31 node-1 kernel: [    9.110493] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 22 05:58:31 node-1 kernel: [    9.110500] ipmi_si 00:09: IPMI kcs interface initialized
Jul 22 05:58:31 node-1 kernel: [    9.124658] systemd-udevd[796]: renamed network interface eth1 to enp7s0
Jul 22 05:58:31 node-1 kernel: [    9.160693] systemd-udevd[806]: renamed network interface eth0 to enp6s0
Jul 22 05:58:31 node-1 kernel: [    9.351970] type=1400 audit(1469167084.370:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1054 comm="apparmor_parser"
Jul 22 05:58:31 node-1 kernel: [    9.352221] type=1400 audit(1469167084.374:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1054 comm="apparmor_parser"
Jul 22 05:58:31 node-1 kernel: [    9.352431] type=1400 audit(1469167084.374:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1054 comm="apparmor_parser"
Jul 22 05:58:31 node-1 kernel: [    9.364932] type=1400 audit(1469167084.386:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1026 comm="apparmor_parser"
Jul 22 05:58:31 node-1 kernel: [    9.365089] type=1400 audit(1469167084.386:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1026 comm="apparmor_parser"
Jul 22 05:58:31 node-1 kernel: [    9.365221] type=1400 audit(1469167084.386:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1026 comm="apparmor_parser"
Jul 22 05:58:31 node-1 kernel: [    9.371696] type=1400 audit(1469167084.390:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1025 comm="apparmor_parser"
Jul 22 05:58:31 node-1 kernel: [    9.371839] type=1400 audit(1469167084.390:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1025 comm="apparmor_parser"
Jul 22 05:58:31 node-1 kernel: [    9.371963] type=1400 audit(1469167084.390:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1025 comm="apparmor_parser"
Jul 22 05:58:31 node-1 kernel: [    9.376207] type=1400 audit(1469167084.398:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1028 comm="apparmor_parser"
Jul 22 05:58:31 node-1 kernel: [    9.947007] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 22 05:58:31 node-1 kernel: [    9.948022] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 22 05:58:31 node-1 kernel: [   10.137187] enic 0000:06:00.0 enp6s0: Link UP
Jul 22 05:58:31 node-1 kernel: [   10.137608] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 22 05:58:31 node-1 kernel: [   10.137617] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 22 05:58:31 node-1 kernel: [   19.773740] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 22 05:58:32 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 22 05:58:32 node-1 kernel: [   38.495415] init: failsafe main process (8402) killed by TERM signal
Jul 22 05:58:32 node-1 dbus[8431]: [system] AppArmor D-Bus mediation is enabled
Jul 22 05:58:33 node-1 kernel: [   38.670951] audit_printk_skb: 30 callbacks suppressed
Jul 22 05:58:33 node-1 kernel: [   38.670951] type=1400 audit(1469167113.087:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8528 comm="apparmor_parser"
Jul 22 05:58:33 node-1 kernel: [   38.674523] type=1400 audit(1469167113.091:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8527 comm="apparmor_parser"
Jul 22 05:58:33 node-1 kernel: [   38.674528] type=1400 audit(1469167113.091:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8527 comm="apparmor_parser"
Jul 22 05:58:33 node-1 kernel: [   38.674531] type=1400 audit(1469167113.091:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8527 comm="apparmor_parser"
Jul 22 05:58:33 node-1 kernel: [   38.674750] type=1400 audit(1469167113.091:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8527 comm="apparmor_parser"
Jul 22 05:58:33 node-1 kernel: [   38.674752] type=1400 audit(1469167113.091:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8527 comm="apparmor_parser"
Jul 22 05:58:33 node-1 kernel: [   38.674866] type=1400 audit(1469167113.091:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8527 comm="apparmor_parser"
Jul 22 05:58:33 node-1 kernel: [   38.735591] type=1400 audit(1469167113.155:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8530 comm="apparmor_parser"
Jul 22 05:58:33 node-1 anacron[8594]: Anacron 2.3 started on 2016-07-22
Jul 22 05:58:33 node-1 cron[8560]: (CRON) INFO (pidfile fd = 3)
Jul 22 05:58:33 node-1 cron[8601]: (CRON) STARTUP (fork ok)
Jul 22 05:58:33 node-1 anacron[8594]: Will run job `cron.daily' in 5 min.
Jul 22 05:58:33 node-1 anacron[8594]: Will run job `cron.weekly' in 10 min.
Jul 22 05:58:33 node-1 anacron[8594]: Will run job `cron.monthly' in 15 min.
Jul 22 05:58:33 node-1 anacron[8594]: Jobs will be executed sequentially
Jul 22 05:58:33 node-1 multipathd: path checkers start up
Jul 22 05:58:33 node-1 cron[8601]: (CRON) INFO (Running @reboot jobs)
Jul 22 05:58:33 node-1 postfix/master[8739]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 22 05:58:36 node-1 puppet-agent[8923]: Reopening log files
Jul 22 05:58:39 node-1 puppet-agent[8923]: Could not request certificate: Connection refused - connect(2)
Jul 22 05:58:50 node-1 puppet-user[9114]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 22 05:58:50 node-1 puppet-user[9114]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 22 05:58:51 node-1 puppet-user[9114]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 22 05:58:51 node-1 puppet-user[9114]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 22 05:58:51 node-1 puppet-user[9114]: Finished catalog run in 1.08 seconds
Jul 22 05:58:52 node-1 multipathd: uevent trigger error
Jul 22 05:58:53 node-1 puppet-user[9561]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 22 05:58:53 node-1 puppet-user[9561]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 22 05:58:53 node-1 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 22 05:58:53 node-1 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 22 05:58:53 node-1 puppet-user[9561]: (/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 22 05:58:53 node-1 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 22 05:58:53 node-1 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 22 05:58:53 node-1 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 22 05:58:53 node-1 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 22 05:58:53 node-1 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 22 05:58:53 node-1 puppet-user[9561]: Finished catalog run in 0.06 seconds
Jul 22 05:58:54 node-1 puppet-user[10013]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 22 05:58:54 node-1 puppet-user[10013]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 22 05:58:54 node-1 puppet-user[10013]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 22 05:58:54 node-1 puppet-user[10013]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 22 05:58:54 node-1 puppet-user[10013]: Finished catalog run in 0.02 seconds
Jul 22 05:58:56 node-1 puppet-user[10471]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 22 05:58:56 node-1 puppet-user[10471]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 22 05:58:56 node-1 puppet-user[10471]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 22 05:58:56 node-1 puppet-user[10471]: Finished catalog run in 0.04 seconds
Jul 22 05:58:57 node-1 puppet-user[10918]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 22 05:58:57 node-1 puppet-user[10918]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Jul 22 05:58:57 node-1 puppet-user[10918]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 22 05:58:59 node-1 puppet-user[10918]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Jul 22 05:59:00 node-1 puppet-user[10918]: Finished catalog run in 2.03 seconds
Jul 22 05:59:01 node-1 puppet-user[11447]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 22 05:59:01 node-1 puppet-user[11447]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Jul 22 05:59:01 node-1 puppet-user[11447]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 22 05:59:01 node-1 puppet-user[11447]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Jul 22 05:59:01 node-1 puppet-user[11447]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 22 05:59:01 node-1 puppet-user[11447]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 22 05:59:01 node-1 puppet-user[11447]: Finished catalog run in 0.23 seconds
Jul 22 05:59:01 node-1 CRON[11899]: (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 22 05:59:01 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 05:59:01 node-1 nailgun-agent: D, [2016-07-22T05:59:01.889406 #11902] DEBUG -- : Sleep for 0 seconds before sending request
Jul 22 05:59:01 node-1 nailgun-agent: I, [2016-07-22T05:59:01.900478 #11902]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 22 05:59:02 node-1 nailgun-agent: D, [2016-07-22T05:59:02.281648 #11902] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 22 05:59:03 node-1 puppet-user[12220]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 22 05:59:03 node-1 puppet-user[12220]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Jul 22 05:59:03 node-1 puppet-user[12220]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 22 05:59:03 node-1 kernel: [   68.669762] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 22 05:59:03 node-1 kernel: [   68.669814] 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 22 05:59:03 node-1 puppet-user[12220]: (/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 22 05:59:03 node-1 puppet-user[12220]: Finished catalog run in 0.05 seconds
Jul 22 05:59:05 node-1 puppet-user[12703]: (Scope(Class[main])) MODULAR: sync_time
Jul 22 05:59:05 node-1 puppet-user[12703]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 22 05:59:05 node-1 ntpdate[13114]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 22 05:59:11 node-1 ntpdate[13114]: adjust time server 10.20.0.2 offset -0.000029 sec
Jul 22 05:59:11 node-1 puppet-user[12703]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 22 05:59:11 node-1 puppet-user[12703]: Finished catalog run in 6.18 seconds
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.161467 #11902] DEBUG -- : Trying to find block devices
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.161605 #11902] DEBUG -- : Found block device: sda
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.161652 #11902] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.161673 #11902] DEBUG -- : Trying to get list of physical devices
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.161849 #11902] DEBUG -- : Getting udev properties for device: sda
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.163713 #11902] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc788
Jul 22 05:59:14 node-1 nailgun-agent: 0a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"37464", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.163740 #11902] DEBUG -- : Trying to find out if device sda is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.163782 #11902] DEBUG -- : Device sda removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.163798 #11902] DEBUG -- : Device sda seems to be appropriate
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.164198 #11902] DEBUG -- : Getting udev properties for device: dm-0
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.165827 #11902] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-sZ2tlWvvQRvgvkmTuW7TBGwNpxYKBV9GpoPoDVMOsv6IEYUBD1jQWC6cckPUUmDX /dev/disk/by-uuid/5a917a5a-1bb4-4595-b710-eb51a4557f84 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-sZ2tlWvvQRvgvkmTuW7TBGwNpxYKBV9GpoPoDVMOsv6IEYUBD1jQWC6cckPUUmDX", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"5a917a5a-1bb4-4595-b710-eb51a4557f84", "ID_FS_UUID_ENC"=>"5a917a5a-1bb4-4595-b710-eb51a4557f84", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77105", "nomdmonddf"=>"1", "nom
Jul 22 05:59:14 node-1 nailgun-agent: dmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.165866 #11902] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.165923 #11902] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.165937 #11902] DEBUG -- : Device dm-0 seems to be appropriate
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.165951 #11902] DEBUG -- : Getting udev properties for device: dm-1
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.167557 #11902] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-652aA83cErMEwzdwv55dz5vJiUZg41YkaIBV0vHI6L0aHHBwqDcH3edEJvWeGeX1 /dev/disk/by-uuid/8f069ffa-90c2-44b3-b27a-37fd6081f0cb /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-652aA83cErMEwzdwv55dz5vJiUZg41YkaIBV0vHI6L0aHHBwqDcH3edEJvWeGeX1", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8f069ffa-90c2-44b3-b27a-37fd6081f0cb", "ID_FS_UUID_ENC"=>"8f069ffa-90c2-44b3-b27a-37fd6081f0cb", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1
Jul 22 05:59:14 node-1 nailgun-agent: 1237", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.167584 #11902] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.167660 #11902] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.167674 #11902] DEBUG -- : Device dm-1 seems to be appropriate
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.167689 #11902] DEBUG -- : Getting udev properties for device: dm-2
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.169363 #11902] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-YrVowa2rnedWPj7vHBxFVuz6F4i0ANlbipzfTepNLNYCmLQILjWECoyGyxzLcvRt /dev/disk/by-uuid/2d0ed65f-70ca-41ad-99f2-2b947a0d3339 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-YrVowa2rnedWPj7vHBxFVuz6F4i0ANlbipzfTepNLNYCmLQILjWECoyGyxzLcvRt", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2d0ed65f-70ca-41ad-99f2-2b947a0d3339", "ID_FS_UUID_ENC"=>"2d0ed65f-70ca-41ad-99f2-2b947a0d3339", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"12256", "nomdmon
Jul 22 05:59:14 node-1 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.169400 #11902] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.169430 #11902] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.169444 #11902] DEBUG -- : Device dm-2 seems to be appropriate
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.169458 #11902] DEBUG -- : Getting udev properties for device: dm-3
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.171056 #11902] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-PXooFgSeEe4r04ubxozqi33v3mM71mp2tAzFIPKm7FLnvUDcE0WIs5VIXIVlK5xX /dev/disk/by-uuid/d17c89fb-f2eb-438e-a021-dd9a01cd0675 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-PXooFgSeEe4r04ubxozqi33v3mM71mp2tAzFIPKm7FLnvUDcE0WIs5VIXIVlK5xX", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d17c89fb-f2eb-438e-a021-dd9a01cd0675", "ID_FS_UUID_ENC"=>"d17c89fb-f2eb-438e-a021-dd9a01cd0675", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14519", "nomdmonddf"=>"1",
Jul 22 05:59:14 node-1 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.171083 #11902] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.171128 #11902] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.171163 #11902] DEBUG -- : Device dm-3 seems to be appropriate
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.171178 #11902] DEBUG -- : Getting udev properties for device: dm-4
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.172949 #11902] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-tAE7xlr0WJIhuW4pyCxfexfjZkncxUKUBueJ7rf5QMBSLa2oNPCtt22puz66eoAm /dev/disk/by-uuid/bc59c6d4-0742-4cb5-a32f-c652313e5942 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-tAE7xlr0WJIhuW4pyCxfexfjZkncxUKUBueJ7rf5QMBSLa2oNPCtt22puz66eoAm", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"bc59c6d4-0742-4cb5-a32f-c652313e5942", "ID_FS_UUID_ENC"=>"bc59c6d4-0742-4cb5-a32f-c652313e5942", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17943", "nomdmonddf"=>"1", "nom
Jul 22 05:59:14 node-1 nailgun-agent: dmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.172977 #11902] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.173038 #11902] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.173053 #11902] DEBUG -- : Device dm-4 seems to be appropriate
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.173067 #11902] DEBUG -- : Getting udev properties for device: dm-5
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.174648 #11902] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-tAE7xlr0WJIhuW4pyCxfexfjZkncxUKUY3302x4meN8r1VNxKBjkOVEjff6PLo3f /dev/disk/by-uuid/18e865e7-3c4a-46b4-956c-1115dc938956 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-tAE7xlr0WJIhuW4pyCxfexfjZkncxUKUY3302x4meN8r1VNxKBjkOVEjff6PLo3f", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"18e865e7-3c4a-46b4-956c-1115dc938956", "ID_FS_UUID_ENC"=>"18e865e7-3c4a-46b4-956c-1115dc938956", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18348", "nomdmonddf"=>"1", "nomdmonisw
Jul 22 05:59:14 node-1 nailgun-agent: "=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.174707 #11902] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.174754 #11902] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.174767 #11902] DEBUG -- : Device dm-5 seems to be appropriate
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.174783 #11902] DEBUG -- : Getting udev properties for device: ram0
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.176487 #11902] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93721", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.176513 #11902] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.176551 #11902] DEBUG -- : Device ram0 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.176572 #11902] DEBUG -- : Getting udev properties for device: ram1
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.178007 #11902] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93733", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.178033 #11902] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.178071 #11902] DEBUG -- : Device ram1 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.178104 #11902] DEBUG -- : Getting udev properties for device: ram2
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.180054 #11902] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93817", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.180079 #11902] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.180172 #11902] DEBUG -- : Device ram2 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.180192 #11902] DEBUG -- : Getting udev properties for device: ram3
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.181690 #11902] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93834", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.181717 #11902] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.181750 #11902] DEBUG -- : Device ram3 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.181770 #11902] DEBUG -- : Getting udev properties for device: ram4
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.183233 #11902] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93847", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.183257 #11902] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.183289 #11902] DEBUG -- : Device ram4 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.183309 #11902] DEBUG -- : Getting udev properties for device: ram5
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.184780 #11902] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93862", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.184805 #11902] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.184872 #11902] DEBUG -- : Device ram5 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.184893 #11902] DEBUG -- : Getting udev properties for device: ram6
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.186414 #11902] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93876", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.186440 #11902] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.186492 #11902] DEBUG -- : Device ram6 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.186512 #11902] DEBUG -- : Getting udev properties for device: ram7
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.188054 #11902] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93894", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.188089 #11902] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.188122 #11902] DEBUG -- : Device ram7 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.188146 #11902] DEBUG -- : Getting udev properties for device: ram8
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.190053 #11902] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93908", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.190078 #11902] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.190110 #11902] DEBUG -- : Device ram8 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.190131 #11902] DEBUG -- : Getting udev properties for device: ram9
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.191608 #11902] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93922", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.191633 #11902] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.191675 #11902] DEBUG -- : Device ram9 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.191695 #11902] DEBUG -- : Getting udev properties for device: loop0
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.193148 #11902] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93647", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.193172 #11902] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.193205 #11902] DEBUG -- : Device loop0 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.193237 #11902] DEBUG -- : Getting udev properties for device: loop1
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.194682 #11902] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93656", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.194709 #11902] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.194742 #11902] DEBUG -- : Device loop1 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.194780 #11902] DEBUG -- : Getting udev properties for device: loop2
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.196252 #11902] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93663", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.196309 #11902] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.196343 #11902] DEBUG -- : Device loop2 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.196362 #11902] DEBUG -- : Getting udev properties for device: loop3
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.197881 #11902] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93673", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.197907 #11902] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.197946 #11902] DEBUG -- : Device loop3 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.197984 #11902] DEBUG -- : Getting udev properties for device: loop4
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.199507 #11902] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93680", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.199533 #11902] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.199571 #11902] DEBUG -- : Device loop4 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.199590 #11902] DEBUG -- : Getting udev properties for device: loop5
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.201065 #11902] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93688", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.201104 #11902] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.201137 #11902] DEBUG -- : Device loop5 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.201171 #11902] DEBUG -- : Getting udev properties for device: loop6
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.203071 #11902] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93699", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.203097 #11902] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.203143 #11902] DEBUG -- : Device loop6 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.203162 #11902] DEBUG -- : Getting udev properties for device: loop7
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.205096 #11902] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93710", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.205134 #11902] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.205168 #11902] DEBUG -- : Device loop7 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.205214 #11902] DEBUG -- : Getting udev properties for device: ram10
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.207270 #11902] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93744", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.207305 #11902] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.207346 #11902] DEBUG -- : Device ram10 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.207375 #11902] DEBUG -- : Getting udev properties for device: ram11
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.209412 #11902] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93755", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.209477 #11902] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.209534 #11902] DEBUG -- : Device ram11 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.209561 #11902] DEBUG -- : Getting udev properties for device: ram12
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.215542 #11902] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93766", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.215569 #11902] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.215624 #11902] DEBUG -- : Device ram12 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.215644 #11902] DEBUG -- : Getting udev properties for device: ram13
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.217931 #11902] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93779", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.217967 #11902] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.218012 #11902] DEBUG -- : Device ram13 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.218041 #11902] DEBUG -- : Getting udev properties for device: ram14
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.222922 #11902] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93791", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.222945 #11902] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.222978 #11902] DEBUG -- : Device ram14 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.223025 #11902] DEBUG -- : Getting udev properties for device: ram15
Jul 22 05:59:14 node-1 kernel: [   79.488466] init: plymouth-upstart-bridge main process ended, respawning
Jul 22 05:59:14 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.224879 #11902] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93804", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.224907 #11902] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.224968 #11902] DEBUG -- : Device ram15 removable parameter: "0"
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225004 #11902] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225029 #11902] DEBUG -- : Block device seems to be physical data storage: sda
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225062 #11902] DEBUG -- : Found block device: dm-0
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225103 #11902] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225116 #11902] DEBUG -- : Found block device: dm-1
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225128 #11902] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225138 #11902] DEBUG -- : Found block device: dm-2
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225164 #11902] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225174 #11902] DEBUG -- : Found block device: dm-3
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225185 #11902] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225208 #11902] DEBUG -- : Found block device: dm-4
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225218 #11902] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225241 #11902] DEBUG -- : Found block device: dm-5
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225252 #11902] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225276 #11902] DEBUG -- : Found block device: ram0
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225286 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225296 #11902] DEBUG -- : Found block device: ram1
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225325 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225340 #11902] DEBUG -- : Found block device: ram2
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225372 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225383 #11902] DEBUG -- : Found block device: ram3
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225393 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225401 #11902] DEBUG -- : Found block device: ram4
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225420 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225440 #11902] DEBUG -- : Found block device: ram5
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225450 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225477 #11902] DEBUG -- : Found block device: ram6
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225486 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225495 #11902] DEBUG -- : Found block device: ram7
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225515 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.225530 #11902] DEBUG -- : Found block device: ram8
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233262 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233278 #11902] DEBUG -- : Found block device: ram9
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233289 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233298 #11902] DEBUG -- : Found block device: loop0
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233309 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233318 #11902] DEBUG -- : Found block device: loop1
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233327 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233340 #11902] DEBUG -- : Found block device: loop2
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233351 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233389 #11902] DEBUG -- : Found block device: loop3
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233400 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233408 #11902] DEBUG -- : Found block device: loop4
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233418 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233426 #11902] DEBUG -- : Found block device: loop5
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233436 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233445 #11902] DEBUG -- : Found block device: loop6
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233455 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233464 #11902] DEBUG -- : Found block device: loop7
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233509 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233519 #11902] DEBUG -- : Found block device: ram10
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233529 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233537 #11902] DEBUG -- : Found block device: ram11
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233547 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233556 #11902] DEBUG -- : Found block device: ram12
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233565 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233573 #11902] DEBUG -- : Found block device: ram13
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233583 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233591 #11902] DEBUG -- : Found block device: ram14
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233636 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233644 #11902] DEBUG -- : Found block device: ram15
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233654 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.233684 #11902] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.302590 #11902] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 22 05:59:14 node-1 nailgun-agent: D, [2016-07-22T05:59:14.302649 #11902] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 22 05:59:14 node-1 puppet-agent[8923]: Could not run: SIGTERM
Jul 22 05:59:14 node-1 kernel: [   79.767964] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 22 05:59:14 node-1 ec2: 
Jul 22 05:59:14 node-1 ec2: #############################################################
Jul 22 05:59:14 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 22 05:59:14 node-1 ec2: 1024 0e:81:9e:6b:72:e4:fd:d4:ec:20:6f:a6:f5:ee:48:fc  root@node-1.domain.tld (DSA)
Jul 22 05:59:14 node-1 ec2: 256 c4:bf:db:ef:21:05:69:73:49:d1:73:68:e9:0e:ae:80  root@node-1.domain.tld (ECDSA)
Jul 22 05:59:14 node-1 ec2: 256 7f:0c:99:e7:2a:75:70:2f:4a:4c:94:77:34:26:28:3c  root@node-1.domain.tld (ED25519)
Jul 22 05:59:14 node-1 ec2: 2048 cc:b2:0a:c1:6f:61:d2:8a:26:10:e2:1d:58:b8:12:0f  root@node-1.domain.tld (RSA)
Jul 22 05:59:14 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 22 05:59:14 node-1 ec2: #############################################################
Jul 22 05:59:17 node-1 puppet-user[13662]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 22 05:59:17 node-1 puppet-user[13662]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 22 05:59:17 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 22 05:59:17 node-1 puppet-user[13662]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Jul 22 05:59:17 node-1 puppet-user[13662]: Finished catalog run in 0.07 seconds
Jul 22 05:59:18 node-1 puppet-user[14109]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 22 05:59:19 node-1 puppet-user[14109]: Compiled catalog for node-1.domain.tld in environment production in 1.39 seconds
Jul 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:20 node-1 puppet-user[14109]: (/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 22 05:59:26 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.368830 #11902] DEBUG -- : Trying to find block devices
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.368908 #11902] DEBUG -- : Found block device: sda
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.368936 #11902] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.368954 #11902] DEBUG -- : Block device seems to be physical data storage: sda
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.368977 #11902] DEBUG -- : Found block device: dm-0
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.368991 #11902] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369002 #11902] DEBUG -- : Found block device: dm-1
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369014 #11902] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369025 #11902] DEBUG -- : Found block device: dm-2
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369035 #11902] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369068 #11902] DEBUG -- : Found block device: dm-3
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369080 #11902] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369090 #11902] DEBUG -- : Found block device: dm-4
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369101 #11902] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369111 #11902] DEBUG -- : Found block device: dm-5
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369133 #11902] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369143 #11902] DEBUG -- : Found block device: ram0
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369154 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369162 #11902] DEBUG -- : Found block device: ram1
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369172 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369204 #11902] DEBUG -- : Found block device: ram2
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369215 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369225 #11902] DEBUG -- : Found block device: ram3
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369235 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369244 #11902] DEBUG -- : Found block device: ram4
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369254 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369264 #11902] DEBUG -- : Found block device: ram5
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369274 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369282 #11902] DEBUG -- : Found block device: ram6
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369292 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369301 #11902] DEBUG -- : Found block device: ram7
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369342 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369355 #11902] DEBUG -- : Found block device: ram8
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369365 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369375 #11902] DEBUG -- : Found block device: ram9
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369385 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369394 #11902] DEBUG -- : Found block device: loop0
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369404 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369414 #11902] DEBUG -- : Found block device: loop1
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369423 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369432 #11902] DEBUG -- : Found block device: loop2
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369441 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369478 #11902] DEBUG -- : Found block device: loop3
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369489 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369498 #11902] DEBUG -- : Found block device: loop4
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369507 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369517 #11902] DEBUG -- : Found block device: loop5
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369527 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369537 #11902] DEBUG -- : Found block device: loop6
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369546 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369555 #11902] DEBUG -- : Found block device: loop7
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369565 #11902] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369601 #11902] DEBUG -- : Found block device: ram10
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369611 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369620 #11902] DEBUG -- : Found block device: ram11
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369630 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369640 #11902] DEBUG -- : Found block device: ram12
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369649 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369659 #11902] DEBUG -- : Found block device: ram13
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369668 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369677 #11902] DEBUG -- : Found block device: ram14
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369710 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369719 #11902] DEBUG -- : Found block device: ram15
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369729 #11902] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.369757 #11902] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 22 05:59:26 node-1 nailgun-agent: D, [2016-07-22T05:59:26.499320 #11902] DEBUG -- : Response: status: 200 body: {"id": 1}
Jul 22 05:59:26 node-1 nailgun-agent: I, [2016-07-22T05:59:26.499541 #11902]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 22 05:59:38 node-1 puppet-user[14109]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 22 05:59:38 node-1 puppet-user[14109]: Finished catalog run in 18.24 seconds
Jul 22 05:59:40 node-1 puppet-user[15256]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 22 05:59:40 node-1 puppet-user[15256]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Jul 22 05:59:44 node-1 puppet-user[15256]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 22 06:00:01 node-1 CRON[16831]: (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 22 06:00:14 node-1 puppet-user[15256]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 22 06:00:14 node-1 puppet-user[15256]: Finished catalog run in 33.77 seconds
Jul 22 06:00:16 node-1 puppet-user[17668]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 22 06:00:16 node-1 puppet-user[17668]: Compiled catalog for node-1.domain.tld in environment production in 0.58 seconds
Jul 22 06:00:16 node-1 puppet-user[17668]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 22 06:00:16 node-1 puppet-user[17668]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 22 06:00:16 node-1 puppet-user[17668]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 22 06:00:16 node-1 puppet-user[17668]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 22 06:00:17 node-1 puppet-user[17668]: Finished catalog run in 0.10 seconds
Jul 22 06:00:18 node-1 puppet-user[18127]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 22 06:00:19 node-1 puppet-user[18127]: Compiled catalog for node-1.domain.tld in environment production in 0.88 seconds
Jul 22 06:00:20 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 22 06:00:20 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 22 06:00:20 node-1 crontab[18567]: (root) LIST (root)
Jul 22 06:00:20 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 22 06:00:20 node-1 crontab[18568]: (root) REPLACE (root)
Jul 22 06:00:22 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 22 06:00:23 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 06:00:23 node-1 nailgun-agent: I, [2016-07-22T06:00:23.680396 #16836]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 22 06:00:23 node-1 puppet-user[18127]: (/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 22 06:00:23 node-1 puppet-user[18127]: (/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 22 06:00:23 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 22 06:00:23 node-1 puppet-user[18127]: (/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 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/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 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/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 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/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 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/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 22 06:00:24 node-1 puppet-user[18127]: (/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 22 06:00:24 node-1 puppet-user[18127]: (/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 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/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 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/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 22 06:00:24 node-1 puppet-user[18127]: (/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 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 22 06:00:24 node-1 puppet-user[18127]: (/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 22 06:00:24 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8375" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 06:00:24 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 22 06:00:26 node-1 multipathd: uevent trigger error
<27>Jul 22 06:00:26 node-1 multipathd: uevent trigger error
<27>Jul 22 06:00:26 node-1 multipathd: uevent trigger error
<27>Jul 22 06:00:26 node-1 multipathd: uevent trigger error
<27>Jul 22 06:00:26 node-1 multipathd: uevent trigger error
<27>Jul 22 06:00:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:00:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:00:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:00:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:00:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:01:33 node-1 multipathd: uevent trigger error
<27>Jul 22 06:01:33 node-1 multipathd: uevent trigger error
<27>Jul 22 06:01:33 node-1 multipathd: uevent trigger error
<27>Jul 22 06:01:33 node-1 multipathd: uevent trigger error
<27>Jul 22 06:01:33 node-1 multipathd: uevent trigger error
<27>Jul 22 06:01:36 node-1 multipathd: uevent trigger error
<27>Jul 22 06:01:36 node-1 multipathd: uevent trigger error
<27>Jul 22 06:01:36 node-1 multipathd: uevent trigger error
<27>Jul 22 06:01:36 node-1 multipathd: uevent trigger error
<27>Jul 22 06:02:18 node-1 ntpdate[2308]: no servers can be used, exiting
<27>Jul 22 06:02:18 node-1 ntpdate[2527]: no servers can be used, exiting
<27>Jul 22 06:02:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:02:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:02:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:02:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:02:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:02:54 node-1 multipathd: uevent trigger error
<27>Jul 22 06:02:54 node-1 multipathd: uevent trigger error
<27>Jul 22 06:02:54 node-1 multipathd: uevent trigger error
<27>Jul 22 06:02:54 node-1 multipathd: uevent trigger error
<27>Jul 22 06:02:54 node-1 multipathd: uevent trigger error
<27>Jul 22 06:03:06 node-1 multipathd: uevent trigger error
<27>Jul 22 06:03:06 node-1 multipathd: uevent trigger error
<27>Jul 22 06:03:06 node-1 multipathd: uevent trigger error
<27>Jul 22 06:03:06 node-1 multipathd: uevent trigger error
<27>Jul 22 06:03:06 node-1 multipathd: uevent trigger error
<27>Jul 22 06:03:09 node-1 multipathd: uevent trigger error
<27>Jul 22 06:03:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:03:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:03:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:03:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:18 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:18 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:18 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:18 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:21 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 06:04:21 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 06:04:27 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 06:04:27 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 06:04:32 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 06:04:38 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 06:04:38 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 22 06:04:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:58 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:58 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:58 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:58 node-1 multipathd: uevent trigger error
<27>Jul 22 06:04:58 node-1 multipathd: uevent trigger error
<129>Jul 22 06:05:00 node-1 haproxy[23418]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:01 node-1 haproxy[23424]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:02 node-1 haproxy[23424]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:02 node-1 haproxy[23424]: proxy mysqld has no server available!
<27>Jul 22 06:05:04 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:04 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:04 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:04 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:04 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:04 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:07 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:07 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:07 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:07 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:07 node-1 multipathd: uevent trigger error
<129>Jul 22 06:05:09 node-1 haproxy[26199]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:10 node-1 haproxy[26203]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:10 node-1 haproxy[26203]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:10 node-1 haproxy[26203]: proxy mysqld has no server available!
<129>Jul 22 06:05:10 node-1 haproxy[26203]: Server object-storage/node-1 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 22 06:05:11 node-1 haproxy[26203]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:11 node-1 haproxy[26203]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:11 node-1 haproxy[26203]: proxy object-storage has no server available!
<27>Jul 22 06:05:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:12 node-1 multipathd: uevent trigger error
<129>Jul 22 06:05:15 node-1 haproxy[27766]: Server neutron/node-1 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 22 06:05:15 node-1 haproxy[27766]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:15 node-1 haproxy[27766]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:15 node-1 haproxy[27766]: proxy neutron has no server available!
<129>Jul 22 06:05:15 node-1 haproxy[27766]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:15 node-1 haproxy[27766]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:16 node-1 haproxy[27766]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:16 node-1 haproxy[27766]: proxy mysqld has no server available!
<129>Jul 22 06:05:16 node-1 haproxy[27766]: Server object-storage/node-1 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 22 06:05:16 node-1 haproxy[27766]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:16 node-1 haproxy[27766]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:16 node-1 haproxy[27766]: proxy object-storage has no server available!
<27>Jul 22 06:05:18 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:18 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:18 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:18 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:18 node-1 multipathd: uevent trigger error
<129>Jul 22 06:05:20 node-1 haproxy[29195]: Server keystone-1/node-1 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 22 06:05:20 node-1 haproxy[29195]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:20 node-1 haproxy[29195]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:20 node-1 haproxy[29195]: proxy keystone-1 has no server available!
<129>Jul 22 06:05:21 node-1 haproxy[29204]: Server keystone-2/node-1 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 22 06:05:21 node-1 haproxy[29204]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:21 node-1 haproxy[29204]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:21 node-1 haproxy[29204]: proxy keystone-2 has no server available!
<129>Jul 22 06:05:21 node-1 haproxy[29204]: Server neutron/node-1 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 22 06:05:21 node-1 haproxy[29204]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:21 node-1 haproxy[29204]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:21 node-1 haproxy[29204]: proxy neutron has no server available!
<129>Jul 22 06:05:21 node-1 haproxy[29204]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:21 node-1 haproxy[29204]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:22 node-1 haproxy[29204]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:22 node-1 haproxy[29204]: proxy mysqld has no server available!
<129>Jul 22 06:05:22 node-1 haproxy[29204]: Server object-storage/node-1 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 22 06:05:22 node-1 haproxy[29204]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:22 node-1 haproxy[29204]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:22 node-1 haproxy[29204]: proxy object-storage has no server available!
<27>Jul 22 06:05:23 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:23 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:23 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:23 node-1 multipathd: uevent trigger error
<129>Jul 22 06:05:25 node-1 haproxy[30565]: Server keystone-1/node-1 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 22 06:05:26 node-1 haproxy[30569]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:26 node-1 haproxy[30569]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:26 node-1 haproxy[30569]: proxy keystone-1 has no server available!
<129>Jul 22 06:05:26 node-1 haproxy[30569]: Server keystone-2/node-1 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 22 06:05:26 node-1 haproxy[30569]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:26 node-1 haproxy[30569]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:26 node-1 haproxy[30569]: proxy keystone-2 has no server available!
<129>Jul 22 06:05:26 node-1 haproxy[30569]: Server neutron/node-1 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 22 06:05:26 node-1 haproxy[30569]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:26 node-1 haproxy[30569]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:26 node-1 haproxy[30569]: proxy neutron has no server available!
<129>Jul 22 06:05:26 node-1 haproxy[30569]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:27 node-1 haproxy[30569]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:27 node-1 haproxy[30569]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:27 node-1 haproxy[30569]: proxy mysqld has no server available!
<129>Jul 22 06:05:27 node-1 haproxy[30569]: Server object-storage/node-1 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 22 06:05:27 node-1 haproxy[30569]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:27 node-1 haproxy[30569]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:27 node-1 haproxy[30569]: proxy object-storage has no server available!
<129>Jul 22 06:05:27 node-1 haproxy[30569]: Server aodh/node-1 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 22 06:05:27 node-1 haproxy[30569]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:27 node-1 haproxy[30569]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:27 node-1 haproxy[30569]: proxy aodh has no server available!
<27>Jul 22 06:05:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:29 node-1 multipathd: uevent trigger error
<129>Jul 22 06:05:31 node-1 haproxy[31908]: Server keystone-1/node-1 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 22 06:05:31 node-1 haproxy[31908]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:31 node-1 haproxy[31908]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:31 node-1 haproxy[31908]: proxy keystone-1 has no server available!
<129>Jul 22 06:05:31 node-1 haproxy[31908]: Server keystone-2/node-1 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 22 06:05:31 node-1 haproxy[31908]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:31 node-1 haproxy[31908]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:31 node-1 haproxy[31908]: proxy keystone-2 has no server available!
<129>Jul 22 06:05:32 node-1 haproxy[31912]: Server neutron/node-1 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 22 06:05:32 node-1 haproxy[31912]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:32 node-1 haproxy[31912]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:32 node-1 haproxy[31912]: proxy neutron has no server available!
<129>Jul 22 06:05:32 node-1 haproxy[31912]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:32 node-1 haproxy[31912]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:32 node-1 haproxy[31912]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:32 node-1 haproxy[31912]: proxy mysqld has no server available!
<129>Jul 22 06:05:32 node-1 haproxy[31912]: Server object-storage/node-1 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 22 06:05:32 node-1 haproxy[31912]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:32 node-1 haproxy[31912]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:32 node-1 haproxy[31912]: proxy object-storage has no server available!
<129>Jul 22 06:05:32 node-1 haproxy[31912]: Server aodh/node-1 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 22 06:05:33 node-1 haproxy[31912]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:33 node-1 haproxy[31912]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:33 node-1 haproxy[31912]: proxy aodh has no server available!
<129>Jul 22 06:05:33 node-1 haproxy[31912]: Server ceilometer/node-1 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 22 06:05:33 node-1 haproxy[31912]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:33 node-1 haproxy[31912]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:33 node-1 haproxy[31912]: proxy ceilometer has no server available!
<27>Jul 22 06:05:34 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:34 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:34 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:34 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:34 node-1 multipathd: uevent trigger error
<129>Jul 22 06:05:37 node-1 haproxy[831]: Server keystone-1/node-1 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 22 06:05:37 node-1 haproxy[831]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:37 node-1 haproxy[831]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:37 node-1 haproxy[831]: proxy keystone-1 has no server available!
<129>Jul 22 06:05:37 node-1 haproxy[831]: Server keystone-2/node-1 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 22 06:05:37 node-1 haproxy[831]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:37 node-1 haproxy[831]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:37 node-1 haproxy[831]: proxy keystone-2 has no server available!
<129>Jul 22 06:05:37 node-1 haproxy[831]: Server neutron/node-1 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 22 06:05:37 node-1 haproxy[831]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:37 node-1 haproxy[831]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:37 node-1 haproxy[831]: proxy neutron has no server available!
<129>Jul 22 06:05:37 node-1 haproxy[831]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:38 node-1 haproxy[835]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:38 node-1 haproxy[835]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:38 node-1 haproxy[835]: proxy mysqld has no server available!
<129>Jul 22 06:05:38 node-1 haproxy[835]: Server object-storage/node-1 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 22 06:05:38 node-1 haproxy[835]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:38 node-1 haproxy[835]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:38 node-1 haproxy[835]: proxy object-storage has no server available!
<129>Jul 22 06:05:38 node-1 haproxy[835]: Server aodh/node-1 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 22 06:05:38 node-1 haproxy[835]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:38 node-1 haproxy[835]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:38 node-1 haproxy[835]: proxy aodh has no server available!
<129>Jul 22 06:05:38 node-1 haproxy[835]: Server ceilometer/node-1 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 22 06:05:38 node-1 haproxy[835]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:38 node-1 haproxy[835]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:38 node-1 haproxy[835]: proxy ceilometer has no server available!
<27>Jul 22 06:05:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:40 node-1 multipathd: uevent trigger error
<129>Jul 22 06:05:42 node-1 haproxy[2169]: Server horizon/node-1 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 22 06:05:42 node-1 haproxy[2169]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:42 node-1 haproxy[2169]: Server keystone-1/node-1 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 22 06:05:42 node-1 haproxy[2169]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:42 node-1 haproxy[2169]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:42 node-1 haproxy[2169]: proxy keystone-1 has no server available!
<129>Jul 22 06:05:42 node-1 haproxy[2169]: Server keystone-2/node-1 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 22 06:05:42 node-1 haproxy[2169]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:42 node-1 haproxy[2169]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:42 node-1 haproxy[2169]: proxy keystone-2 has no server available!
<129>Jul 22 06:05:42 node-1 haproxy[2169]: Server neutron/node-1 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 22 06:05:43 node-1 haproxy[2173]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:43 node-1 haproxy[2173]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:43 node-1 haproxy[2173]: proxy neutron has no server available!
<129>Jul 22 06:05:43 node-1 haproxy[2173]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:43 node-1 haproxy[2173]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:43 node-1 haproxy[2173]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:43 node-1 haproxy[2173]: proxy mysqld has no server available!
<129>Jul 22 06:05:43 node-1 haproxy[2173]: Server object-storage/node-1 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 22 06:05:43 node-1 haproxy[2173]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:43 node-1 haproxy[2173]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:43 node-1 haproxy[2173]: proxy object-storage has no server available!
<129>Jul 22 06:05:43 node-1 haproxy[2173]: Server aodh/node-1 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 22 06:05:43 node-1 haproxy[2173]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:43 node-1 haproxy[2173]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:43 node-1 haproxy[2173]: proxy aodh has no server available!
<129>Jul 22 06:05:43 node-1 haproxy[2173]: Server ceilometer/node-1 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 22 06:05:44 node-1 haproxy[2173]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:44 node-1 haproxy[2173]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:44 node-1 haproxy[2173]: proxy ceilometer has no server available!
<27>Jul 22 06:05:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:45 node-1 multipathd: uevent trigger error
<129>Jul 22 06:05:48 node-1 haproxy[3563]: Server horizon/node-1 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 22 06:05:48 node-1 haproxy[3563]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:48 node-1 haproxy[3563]: Server keystone-1/node-1 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 22 06:05:48 node-1 haproxy[3563]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:48 node-1 haproxy[3563]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:48 node-1 haproxy[3563]: proxy keystone-1 has no server available!
<129>Jul 22 06:05:48 node-1 haproxy[3563]: Server keystone-2/node-1 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 22 06:05:48 node-1 haproxy[3563]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:48 node-1 haproxy[3563]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:48 node-1 haproxy[3563]: proxy keystone-2 has no server available!
<129>Jul 22 06:05:48 node-1 haproxy[3563]: Server glance-api/node-1 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 22 06:05:48 node-1 haproxy[3563]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:48 node-1 haproxy[3563]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:48 node-1 haproxy[3563]: proxy glance-api has no server available!
<129>Jul 22 06:05:48 node-1 haproxy[3563]: Server glance-glare/node-1 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 22 06:05:48 node-1 haproxy[3563]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:48 node-1 haproxy[3563]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:48 node-1 haproxy[3563]: proxy glance-glare has no server available!
<129>Jul 22 06:05:48 node-1 haproxy[3563]: Server neutron/node-1 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 22 06:05:49 node-1 haproxy[3567]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:49 node-1 haproxy[3567]: proxy neutron has no server available!
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Server glance-registry/node-1 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 22 06:05:49 node-1 haproxy[3567]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:49 node-1 haproxy[3567]: proxy glance-registry has no server available!
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:49 node-1 haproxy[3567]: proxy mysqld has no server available!
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Server object-storage/node-1 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 22 06:05:49 node-1 haproxy[3567]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:49 node-1 haproxy[3567]: proxy object-storage has no server available!
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Server aodh/node-1 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 22 06:05:49 node-1 haproxy[3567]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:49 node-1 haproxy[3567]: proxy aodh has no server available!
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Server ceilometer/node-1 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 22 06:05:49 node-1 haproxy[3567]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:49 node-1 haproxy[3567]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:49 node-1 haproxy[3567]: proxy ceilometer has no server available!
<27>Jul 22 06:05:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:51 node-1 multipathd: uevent trigger error
<129>Jul 22 06:05:53 node-1 haproxy[4952]: Server horizon/node-1 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 22 06:05:53 node-1 haproxy[4952]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:53 node-1 haproxy[4952]: Server keystone-1/node-1 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 22 06:05:53 node-1 haproxy[4952]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:53 node-1 haproxy[4952]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:53 node-1 haproxy[4952]: proxy keystone-1 has no server available!
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server keystone-2/node-1 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 22 06:05:54 node-1 haproxy[4956]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:54 node-1 haproxy[4956]: proxy keystone-2 has no server available!
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server nova-api/node-1 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 22 06:05:54 node-1 haproxy[4956]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:54 node-1 haproxy[4956]: proxy nova-api has no server available!
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server nova-metadata-api/node-1 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 22 06:05:54 node-1 haproxy[4956]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:54 node-1 haproxy[4956]: proxy nova-metadata-api has no server available!
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server glance-api/node-1 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 22 06:05:54 node-1 haproxy[4956]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:54 node-1 haproxy[4956]: proxy glance-api has no server available!
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server glance-glare/node-1 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 22 06:05:54 node-1 haproxy[4956]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:54 node-1 haproxy[4956]: proxy glance-glare has no server available!
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server neutron/node-1 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 22 06:05:54 node-1 haproxy[4956]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:54 node-1 haproxy[4956]: proxy neutron has no server available!
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server glance-registry/node-1 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 22 06:05:54 node-1 haproxy[4956]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:54 node-1 haproxy[4956]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:54 node-1 haproxy[4956]: proxy glance-registry has no server available!
<129>Jul 22 06:05:55 node-1 haproxy[4956]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:55 node-1 haproxy[4956]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:55 node-1 haproxy[4956]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:55 node-1 haproxy[4956]: proxy mysqld has no server available!
<129>Jul 22 06:05:55 node-1 haproxy[4956]: Server object-storage/node-1 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 22 06:05:55 node-1 haproxy[4956]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:55 node-1 haproxy[4956]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:55 node-1 haproxy[4956]: proxy object-storage has no server available!
<129>Jul 22 06:05:55 node-1 haproxy[4956]: Server aodh/node-1 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 22 06:05:55 node-1 haproxy[4956]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:55 node-1 haproxy[4956]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:55 node-1 haproxy[4956]: proxy aodh has no server available!
<129>Jul 22 06:05:55 node-1 haproxy[4956]: Server ceilometer/node-1 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 22 06:05:55 node-1 haproxy[4956]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:55 node-1 haproxy[4956]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:55 node-1 haproxy[4956]: proxy ceilometer has no server available!
<129>Jul 22 06:05:55 node-1 haproxy[4956]: Server nova-novncproxy/node-1 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 22 06:05:55 node-1 haproxy[4956]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:55 node-1 haproxy[4956]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:55 node-1 haproxy[4956]: proxy nova-novncproxy has no server available!
<27>Jul 22 06:05:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:05:57 node-1 multipathd: uevent trigger error
<129>Jul 22 06:05:59 node-1 haproxy[6292]: Server horizon/node-1 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 22 06:05:59 node-1 haproxy[6292]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:59 node-1 haproxy[6292]: Server keystone-1/node-1 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 22 06:05:59 node-1 haproxy[6292]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:59 node-1 haproxy[6292]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:59 node-1 haproxy[6292]: proxy keystone-1 has no server available!
<129>Jul 22 06:05:59 node-1 haproxy[6292]: Server keystone-2/node-1 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 22 06:05:59 node-1 haproxy[6292]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:59 node-1 haproxy[6292]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:59 node-1 haproxy[6292]: proxy keystone-2 has no server available!
<129>Jul 22 06:05:59 node-1 haproxy[6292]: Server nova-api/node-1 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 22 06:05:59 node-1 haproxy[6292]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:05:59 node-1 haproxy[6292]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:05:59 node-1 haproxy[6292]: proxy nova-api has no server available!
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server nova-metadata-api/node-1 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 22 06:06:00 node-1 haproxy[6303]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:00 node-1 haproxy[6303]: proxy nova-metadata-api has no server available!
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:00 node-1 haproxy[6303]: proxy cinder-api has no server available!
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server glance-api/node-1 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 22 06:06:00 node-1 haproxy[6303]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:00 node-1 haproxy[6303]: proxy glance-api has no server available!
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server glance-glare/node-1 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 22 06:06:00 node-1 haproxy[6303]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:00 node-1 haproxy[6303]: proxy glance-glare has no server available!
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server neutron/node-1 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 22 06:06:00 node-1 haproxy[6303]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:00 node-1 haproxy[6303]: proxy neutron has no server available!
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server glance-registry/node-1 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 22 06:06:00 node-1 haproxy[6303]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:00 node-1 haproxy[6303]: proxy glance-registry has no server available!
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:00 node-1 haproxy[6303]: proxy mysqld has no server available!
<129>Jul 22 06:06:00 node-1 haproxy[6303]: Server object-storage/node-1 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 22 06:06:01 node-1 haproxy[6303]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:01 node-1 haproxy[6303]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:01 node-1 haproxy[6303]: proxy object-storage has no server available!
<129>Jul 22 06:06:01 node-1 haproxy[6303]: Server aodh/node-1 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 22 06:06:01 node-1 haproxy[6303]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:01 node-1 haproxy[6303]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:01 node-1 haproxy[6303]: proxy aodh has no server available!
<129>Jul 22 06:06:01 node-1 haproxy[6303]: Server ceilometer/node-1 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 22 06:06:01 node-1 haproxy[6303]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:01 node-1 haproxy[6303]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:01 node-1 haproxy[6303]: proxy ceilometer has no server available!
<129>Jul 22 06:06:01 node-1 haproxy[6303]: Server nova-novncproxy/node-1 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 22 06:06:01 node-1 haproxy[6303]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:01 node-1 haproxy[6303]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:01 node-1 haproxy[6303]: proxy nova-novncproxy has no server available!
<27>Jul 22 06:06:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:03 node-1 multipathd: uevent trigger error
<129>Jul 22 06:06:05 node-1 haproxy[7678]: Server horizon/node-1 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 22 06:06:05 node-1 haproxy[7678]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server keystone-1/node-1 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 22 06:06:06 node-1 haproxy[7682]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:06 node-1 haproxy[7682]: proxy keystone-1 has no server available!
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server keystone-2/node-1 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 22 06:06:06 node-1 haproxy[7682]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:06 node-1 haproxy[7682]: proxy keystone-2 has no server available!
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server nova-api/node-1 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 22 06:06:06 node-1 haproxy[7682]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:06 node-1 haproxy[7682]: proxy nova-api has no server available!
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server nova-metadata-api/node-1 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 22 06:06:06 node-1 haproxy[7682]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:06 node-1 haproxy[7682]: proxy nova-metadata-api has no server available!
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:06 node-1 haproxy[7682]: proxy cinder-api has no server available!
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server glance-api/node-1 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 22 06:06:06 node-1 haproxy[7682]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:06 node-1 haproxy[7682]: proxy glance-api has no server available!
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server glance-glare/node-1 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 22 06:06:06 node-1 haproxy[7682]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:06 node-1 haproxy[7682]: proxy glance-glare has no server available!
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server neutron/node-1 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 22 06:06:06 node-1 haproxy[7682]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:06 node-1 haproxy[7682]: proxy neutron has no server available!
<129>Jul 22 06:06:06 node-1 haproxy[7682]: Server glance-registry/node-1 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 22 06:06:06 node-1 haproxy[7682]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:07 node-1 haproxy[7682]: proxy glance-registry has no server available!
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:07 node-1 haproxy[7682]: proxy mysqld has no server available!
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server object-storage/node-1 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 22 06:06:07 node-1 haproxy[7682]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:07 node-1 haproxy[7682]: proxy object-storage has no server available!
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server aodh/node-1 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 22 06:06:07 node-1 haproxy[7682]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:07 node-1 haproxy[7682]: proxy aodh has no server available!
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server ceilometer/node-1 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 22 06:06:07 node-1 haproxy[7682]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:07 node-1 haproxy[7682]: proxy ceilometer has no server available!
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server heat-api/node-1 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 22 06:06:07 node-1 haproxy[7682]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:07 node-1 haproxy[7682]: proxy heat-api has no server available!
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server heat-api-cfn/node-1 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 22 06:06:07 node-1 haproxy[7682]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:07 node-1 haproxy[7682]: proxy heat-api-cfn has no server available!
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server heat-api-cloudwatch/node-1 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 22 06:06:07 node-1 haproxy[7682]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:07 node-1 haproxy[7682]: proxy heat-api-cloudwatch has no server available!
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server nova-novncproxy/node-1 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 22 06:06:07 node-1 haproxy[7682]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 06:06:07 node-1 haproxy[7682]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 06:06:07 node-1 haproxy[7682]: proxy nova-novncproxy has no server available!
<27>Jul 22 06:06:09 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:09 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:09 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:09 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:09 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:06:22 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 22 06:06:46 node-1 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 22 06:06:48 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 22 06:07:15 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 06:07:22 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 22 06:07:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:07:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:07:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:07:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:07:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:09:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:09:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:09:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:09:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:09:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:16 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 06:10:24 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:24 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:24 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:24 node-1 multipathd: uevent trigger error
<43>Jul 22 06:10:25 node-1 apache2_error [Fri Jul 22 06:10:16.528008 2016] [mpm_event:notice] [pid 16489:tid 139827491284864] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 22 06:10:25 node-1 apache2_error [Fri Jul 22 06:10:16.528082 2016] [core:notice] [pid 16489:tid 139827491284864] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 22 06:10:25 node-1 apache2_error [Fri Jul 22 06:10:18.694125 2016] [mpm_event:notice] [pid 16489:tid 139827491284864] AH00491: caught SIGTERM, shutting down
<43>Jul 22 06:10:25 node-1 apache2_error [Fri Jul 22 06:10:19.808590 2016] [mpm_worker:notice] [pid 16859:tid 140099262384000] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 22 06:10:25 node-1 apache2_error [Fri Jul 22 06:10:19.808655 2016] [core:notice] [pid 16859:tid 140099262384000] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 06:10:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:32 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:32 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:32 node-1 multipathd: uevent trigger error
<27>Jul 22 06:10:32 node-1 multipathd: uevent trigger error
<43>Jul 22 06:11:45 node-1 apache2_error [Fri Jul 22 06:11:42.052044 2016] [mpm_worker:notice] [pid 16859:tid 140099262384000] AH00295: caught SIGTERM, shutting down
<43>Jul 22 06:11:45 node-1 apache2_error [Fri Jul 22 06:11:42.808484 2016] [mpm_worker:notice] [pid 31039:tid 140430977521536] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 06:11:45 node-1 apache2_error [Fri Jul 22 06:11:42.808514 2016] [core:notice] [pid 31039:tid 140430977521536] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 22 06:12:35 node-1 apache2_error [Fri Jul 22 06:12:26.731556 2016] [mpm_worker:notice] [pid 31039:tid 140430977521536] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 06:12:35 node-1 apache2_error [Fri Jul 22 06:12:26.924974 2016] [mpm_worker:warn] [pid 31039:tid 140430977521536] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 06:12:35 node-1 apache2_error [Fri Jul 22 06:12:26.927704 2016] [mpm_worker:notice] [pid 31039:tid 140430977521536] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 06:12:35 node-1 apache2_error [Fri Jul 22 06:12:26.927717 2016] [core:notice] [pid 31039:tid 140430977521536] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 06:13:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:12 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:17 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:17 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:17 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:17 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:17 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 06:13:32 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:32 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:32 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:32 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:32 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:32 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:13:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:14:02 node-1 multipathd: uevent trigger error
<27>Jul 22 06:14:02 node-1 multipathd: uevent trigger error
<27>Jul 22 06:14:02 node-1 multipathd: uevent trigger error
<27>Jul 22 06:14:02 node-1 multipathd: uevent trigger error
<27>Jul 22 06:14:20 node-1 multipathd: uevent trigger error
<27>Jul 22 06:14:20 node-1 multipathd: uevent trigger error
<27>Jul 22 06:14:20 node-1 multipathd: uevent trigger error
<27>Jul 22 06:14:20 node-1 multipathd: uevent trigger error
<27>Jul 22 06:14:20 node-1 multipathd: uevent trigger error
<27>Jul 22 06:14:20 node-1 multipathd: uevent trigger error
<27>Jul 22 06:15:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:15:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:15:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:15:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:15:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:15:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:16:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 06:16:30 node-1 multipathd: uevent trigger error
<27>Jul 22 06:16:30 node-1 multipathd: uevent trigger error
<27>Jul 22 06:16:30 node-1 multipathd: uevent trigger error
<27>Jul 22 06:16:30 node-1 multipathd: uevent trigger error
<27>Jul 22 06:16:30 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:29 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:34 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:34 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:34 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:34 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:17:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:19:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 06:20:25 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:25 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:25 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:25 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:25 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:25 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:55 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:55 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:55 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:55 node-1 multipathd: uevent trigger error
<27>Jul 22 06:20:55 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:37 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:37 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:37 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:37 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:37 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:37 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:42 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:42 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:42 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:42 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:42 node-1 multipathd: uevent trigger error
<27>Jul 22 06:21:42 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:03 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:23 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 06:22:50 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:50 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:50 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:50 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:50 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:57 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Jul 22 06:22:57 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Jul 22 06:22:57 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Jul 22 06:22:58 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Jul 22 06:22:59 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Jul 22 06:22:59 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:59 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:59 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:59 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:59 node-1 multipathd: uevent trigger error
<27>Jul 22 06:22:59 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:13 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:13 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:13 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:13 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:13 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:28 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:28 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:28 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:28 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:46 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:46 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:46 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:46 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:46 node-1 multipathd: uevent trigger error
<27>Jul 22 06:23:46 node-1 multipathd: uevent trigger error
<27>Jul 22 06:25:24 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 06:26:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:46 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:46 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:46 node-1 multipathd: uevent trigger error
<27>Jul 22 06:26:46 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:14 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:14 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:14 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:15 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:15 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:19 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:37 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:37 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:38 node-1 multipathd: uevent trigger error
<27>Jul 22 06:27:38 node-1 multipathd: uevent trigger error
<27>Jul 22 06:28:17 node-1 multipathd: uevent trigger error
<27>Jul 22 06:28:17 node-1 multipathd: uevent trigger error
<27>Jul 22 06:28:17 node-1 multipathd: uevent trigger error
<27>Jul 22 06:28:17 node-1 multipathd: uevent trigger error
<27>Jul 22 06:28:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 06:29:30 node-1 multipathd: uevent trigger error
<27>Jul 22 06:29:30 node-1 multipathd: uevent trigger error
<27>Jul 22 06:29:30 node-1 multipathd: uevent trigger error
<27>Jul 22 06:29:30 node-1 multipathd: uevent trigger error
<27>Jul 22 06:29:30 node-1 multipathd: uevent trigger error
<27>Jul 22 06:29:48 node-1 multipathd: uevent trigger error
<27>Jul 22 06:29:48 node-1 multipathd: uevent trigger error
<27>Jul 22 06:29:48 node-1 multipathd: uevent trigger error
<27>Jul 22 06:29:48 node-1 multipathd: uevent trigger error
<11>Jul 22 06:30:02 node-1 liberasurecode[21184]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:02 node-1 liberasurecode[21184]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:02 node-1 liberasurecode[21184]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:02 node-1 liberasurecode[21184]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:02 node-1 liberasurecode[21213]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:02 node-1 liberasurecode[21213]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:02 node-1 liberasurecode[21213]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:02 node-1 liberasurecode[21213]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:05 node-1 liberasurecode[22035]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:05 node-1 liberasurecode[22035]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:05 node-1 liberasurecode[22035]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:05 node-1 liberasurecode[22035]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:10 node-1 liberasurecode[22667]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:10 node-1 liberasurecode[22667]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:10 node-1 liberasurecode[22667]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:10 node-1 liberasurecode[22667]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:10 node-1 liberasurecode[22708]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:10 node-1 liberasurecode[22708]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:10 node-1 liberasurecode[22708]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:10 node-1 liberasurecode[22708]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22746]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22746]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22746]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22746]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22804]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22804]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22804]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22804]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22819]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22819]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22819]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22819]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22836]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22836]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22836]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22836]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22855]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22855]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22855]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:11 node-1 liberasurecode[22855]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:20 node-1 liberasurecode[23510]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:20 node-1 liberasurecode[23510]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:20 node-1 liberasurecode[23510]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:30:20 node-1 liberasurecode[23510]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 22 06:30:28 node-1 multipathd: uevent trigger error
<27>Jul 22 06:30:28 node-1 multipathd: uevent trigger error
<27>Jul 22 06:30:28 node-1 multipathd: uevent trigger error
<27>Jul 22 06:30:28 node-1 multipathd: uevent trigger error
<27>Jul 22 06:30:28 node-1 multipathd: uevent trigger error
<43>Jul 22 06:31:17 node-1 apache2_error [Fri Jul 22 06:31:16.378981 2016] [mpm_worker:notice] [pid 31039:tid 140430977521536] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 06:31:17 node-1 apache2_error [Fri Jul 22 06:31:16.762435 2016] [mpm_worker:warn] [pid 31039:tid 140430977521536] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 06:31:17 node-1 apache2_error [Fri Jul 22 06:31:16.767710 2016] [mpm_worker:notice] [pid 31039:tid 140430977521536] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 06:31:17 node-1 apache2_error [Fri Jul 22 06:31:16.767742 2016] [core:notice] [pid 31039:tid 140430977521536] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 06:31:27 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 22 06:31:57 node-1 apache2_error [Fri Jul 22 06:31:53.941679 2016] [mpm_worker:notice] [pid 31039:tid 140430977521536] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 06:31:57 node-1 apache2_error [Fri Jul 22 06:31:54.134795 2016] [mpm_worker:warn] [pid 31039:tid 140430977521536] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 06:31:57 node-1 apache2_error [Fri Jul 22 06:31:54.143967 2016] [mpm_worker:notice] [pid 31039:tid 140430977521536] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 06:31:57 node-1 apache2_error [Fri Jul 22 06:31:54.143996 2016] [core:notice] [pid 31039:tid 140430977521536] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 06:31:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:31:58 node-1 multipathd: uevent trigger error
<27>Jul 22 06:31:58 node-1 multipathd: uevent trigger error
<27>Jul 22 06:31:58 node-1 multipathd: uevent trigger error
<27>Jul 22 06:31:58 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:05 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:05 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:05 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:05 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:05 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:44 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:44 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:44 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:44 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:44 node-1 multipathd: uevent trigger error
<43>Jul 22 06:32:47 node-1 apache2_error [Fri Jul 22 06:32:40.348578 2016] [mpm_worker:notice] [pid 31039:tid 140430977521536] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 06:32:47 node-1 apache2_error [Fri Jul 22 06:32:40.543140 2016] [mpm_worker:warn] [pid 31039:tid 140430977521536] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 06:32:47 node-1 apache2_error [Fri Jul 22 06:32:40.550944 2016] [mpm_worker:notice] [pid 31039:tid 140430977521536] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 06:32:47 node-1 apache2_error [Fri Jul 22 06:32:40.550964 2016] [core:notice] [pid 31039:tid 140430977521536] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 06:32:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:51 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:32:57 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:06 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:06 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:06 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:06 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:06 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:22 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:22 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:22 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:22 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:22 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:43 node-1 multipathd: uevent trigger error
<27>Jul 22 06:33:50 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 22 06:34:00 node-1 multipathd: uevent trigger error
<27>Jul 22 06:34:00 node-1 multipathd: uevent trigger error
<27>Jul 22 06:34:00 node-1 multipathd: uevent trigger error
<27>Jul 22 06:34:00 node-1 multipathd: uevent trigger error
<27>Jul 22 06:34:00 node-1 multipathd: uevent trigger error
<27>Jul 22 06:34:05 node-1 multipathd: uevent trigger error
<27>Jul 22 06:34:05 node-1 multipathd: uevent trigger error
<27>Jul 22 06:34:05 node-1 multipathd: uevent trigger error
<27>Jul 22 06:34:05 node-1 multipathd: uevent trigger error
<27>Jul 22 06:34:05 node-1 multipathd: uevent trigger error
<27>Jul 22 06:34:51 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<11>Jul 22 06:35:01 node-1 liberasurecode[15771]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:35:01 node-1 liberasurecode[15771]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:35:01 node-1 liberasurecode[15771]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:35:01 node-1 liberasurecode[15771]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 22 06:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:36:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:02 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:02 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:02 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:02 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:02 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:10 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:10 node-1 multipathd: uevent trigger error
<129>Jul 22 06:37:21 node-1 haproxy[5759]: 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 22 06:37:21 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:21 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:21 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:21 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:21 node-1 multipathd: uevent trigger error
<129>Jul 22 06:37:21 node-1 haproxy[5759]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 22 06:37:38 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:38 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:38 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:38 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:38 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:43 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:43 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:43 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:43 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:43 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:37:56 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:04 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:04 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:04 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:04 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:04 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:09 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:09 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:09 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:09 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:09 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:20 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:20 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:20 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:20 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:20 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:38:31 node-1 multipathd: uevent trigger error
<129>Jul 22 06:38:41 node-1 haproxy[5759]: Server neutron/node-1 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 22 06:39:27 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:27 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:27 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:27 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:27 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:31 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:36 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:36 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:36 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:36 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:36 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:40 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:45 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:49 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:49 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:49 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:49 node-1 multipathd: uevent trigger error
<27>Jul 22 06:39:49 node-1 multipathd: uevent trigger error
<11>Jul 22 06:40:02 node-1 liberasurecode[22850]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:40:02 node-1 liberasurecode[22850]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:40:02 node-1 liberasurecode[22850]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 06:40:02 node-1 liberasurecode[22850]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
