Sep 13 18:09:46 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8427" x-info="http://www.rsyslog.com"] start
Sep 13 18:09:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 13 18:09:46 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep 13 18:09:46 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep 13 18:09:46 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 13 18:09:46 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 13 18:09:46 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 13 18:09:46 node-1 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 13 18:09:46 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=10c5969a-0bee-4214-8b38-01b49ebc4211 nomdmonddf nomdmonisw
Sep 13 18:09:46 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep 13 18:09:46 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep 13 18:09:46 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep 13 18:09:46 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep 13 18:09:46 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 13 18:09:46 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 13 18:09:46 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 13 18:09:46 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 13 18:09:46 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
Sep 13 18:09:46 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 13 18:09:46 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 13 18:09:46 node-1 kernel: [    0.000000] No AGP bridge found
Sep 13 18:09:46 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 13 18:09:46 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep 13 18:09:46 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 13 18:09:46 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep 13 18:09:46 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 13 18:09:46 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 13 18:09:46 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 13 18:09:46 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 13 18:09:46 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 13 18:09:46 node-1 kernel: [    0.000000]   2 disabled
Sep 13 18:09:46 node-1 kernel: [    0.000000]   3 disabled
Sep 13 18:09:46 node-1 kernel: [    0.000000]   4 disabled
Sep 13 18:09:46 node-1 kernel: [    0.000000]   5 disabled
Sep 13 18:09:46 node-1 kernel: [    0.000000]   6 disabled
Sep 13 18:09:46 node-1 kernel: [    0.000000]   7 disabled
Sep 13 18:09:46 node-1 kernel: [    0.000000]   8 disabled
Sep 13 18:09:46 node-1 kernel: [    0.000000]   9 disabled
Sep 13 18:09:46 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 13 18:09:46 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 13 18:09:46 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 13 18:09:46 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 13 18:09:46 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 13 18:09:46 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep 13 18:09:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 13 18:09:46 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 13 18:09:46 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 13 18:09:46 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 13 18:09:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 13 18:09:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 13 18:09:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 13 18:09:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 13 18:09:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 13 18:09:46 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 13 18:09:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 13 18:09:46 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 13 18:09:46 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 13 18:09:46 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 13 18:09:46 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 13 18:09:46 node-1 kernel: [    0.000000] Zone ranges:
Sep 13 18:09:46 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] Movable zone start for each node
Sep 13 18:09:46 node-1 kernel: [    0.000000] Early memory node ranges
Sep 13 18:09:46 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 13 18:09:46 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 13 18:09:46 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 13 18:09:46 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 13 18:09:46 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 13 18:09:46 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 13 18:09:46 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 13 18:09:46 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 13 18:09:46 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 13 18:09:46 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 13 18:09:46 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 13 18:09:46 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 13 18:09:46 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 13 18:09:46 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 13 18:09:46 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 13 18:09:46 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 13 18:09:46 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 13 18:09:46 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 13 18:09:46 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 13 18:09:46 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 13 18:09:46 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 13 18:09:46 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 13 18:09:46 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 13 18:09:46 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 
Sep 13 18:09:46 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 13 18:09:46 node-1 kernel: [    0.000000] Policy zone: Normal
Sep 13 18:09:46 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=10c5969a-0bee-4214-8b38-01b49ebc4211 nomdmonddf nomdmonisw
Sep 13 18:09:46 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 13 18:09:46 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 13 18:09:46 node-1 kernel: [    0.000000] Checking aperture...
Sep 13 18:09:46 node-1 kernel: [    0.000000] No AGP bridge found
Sep 13 18:09:46 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 13 18:09:46 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 13 18:09:46 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 13 18:09:46 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Sep 13 18:09:46 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 13 18:09:46 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 13 18:09:46 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 13 18:09:46 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 13 18:09:46 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 13 18:09:46 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 13 18:09:46 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 13 18:09:46 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 13 18:09:46 node-1 kernel: [    0.000000] console [tty0] enabled
Sep 13 18:09:46 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 13 18:09:46 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 13 18:09:46 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 13 18:09:46 node-1 kernel: [    0.000000] hpet clockevent registered
Sep 13 18:09:46 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 13 18:09:46 node-1 kernel: [    0.004000] tsc: Detected 3491.872 MHz processor
Sep 13 18:09:46 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.74 BogoMIPS (lpj=13967488)
Sep 13 18:09:46 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 13 18:09:46 node-1 kernel: [    0.000048] Security Framework initialized
Sep 13 18:09:46 node-1 kernel: [    0.000066] AppArmor: AppArmor initialized
Sep 13 18:09:46 node-1 kernel: [    0.000068] Yama: becoming mindful.
Sep 13 18:09:46 node-1 kernel: [    0.001458] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 13 18:09:46 node-1 kernel: [    0.006309] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 13 18:09:46 node-1 kernel: [    0.008238] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 13 18:09:46 node-1 kernel: [    0.008266] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 13 18:09:46 node-1 kernel: [    0.008555] Initializing cgroup subsys memory
Sep 13 18:09:46 node-1 kernel: [    0.008564] Initializing cgroup subsys devices
Sep 13 18:09:46 node-1 kernel: [    0.008566] Initializing cgroup subsys freezer
Sep 13 18:09:46 node-1 kernel: [    0.008567] Initializing cgroup subsys blkio
Sep 13 18:09:46 node-1 kernel: [    0.008569] Initializing cgroup subsys perf_event
Sep 13 18:09:46 node-1 kernel: [    0.008571] Initializing cgroup subsys hugetlb
Sep 13 18:09:46 node-1 kernel: [    0.008590] CPU: Physical Processor ID: 0
Sep 13 18:09:46 node-1 kernel: [    0.008592] CPU: Processor Core ID: 0
Sep 13 18:09:46 node-1 kernel: [    0.008596] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 13 18:09:46 node-1 kernel: [    0.008596] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 13 18:09:46 node-1 kernel: [    0.009289] mce: CPU supports 22 MCE banks
Sep 13 18:09:46 node-1 kernel: [    0.009316] CPU0: Thermal monitoring enabled (TM1)
Sep 13 18:09:46 node-1 kernel: [    0.009337] process: using mwait in idle threads
Sep 13 18:09:46 node-1 kernel: [    0.009340] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 13 18:09:46 node-1 kernel: [    0.009340] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 13 18:09:46 node-1 kernel: [    0.009340] tlb_flushall_shift: 6
Sep 13 18:09:46 node-1 kernel: [    0.009429] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 13 18:09:46 node-1 kernel: [    0.010154] ACPI: Core revision 20131115
Sep 13 18:09:46 node-1 kernel: [    0.022827] ACPI: All ACPI Tables successfully acquired
Sep 13 18:09:46 node-1 kernel: [    0.022989] ftrace: allocating 28617 entries in 112 pages
Sep 13 18:09:46 node-1 kernel: [    0.031972] dmar: Host address width 46
Sep 13 18:09:46 node-1 kernel: [    0.031974] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 13 18:09:46 node-1 kernel: [    0.031980] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 13 18:09:46 node-1 kernel: [    0.031982] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 13 18:09:46 node-1 kernel: [    0.031985] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 13 18:09:46 node-1 kernel: [    0.031987] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 13 18:09:46 node-1 kernel: [    0.031988] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 13 18:09:46 node-1 kernel: [    0.031989] dmar: ATSR flags: 0x0
Sep 13 18:09:46 node-1 kernel: [    0.031990] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 13 18:09:46 node-1 kernel: [    0.031991] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 13 18:09:46 node-1 kernel: [    0.032107] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 13 18:09:46 node-1 kernel: [    0.032108] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 13 18:09:46 node-1 kernel: [    0.032109] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 13 18:09:46 node-1 kernel: [    0.032110] HPET id 0 under DRHD base 0xc7ffc000
Sep 13 18:09:46 node-1 kernel: [    0.032111] Your BIOS is broken and requested that x2apic be disabled.
Sep 13 18:09:46 node-1 kernel: [    0.032111] This will slightly decrease performance.
Sep 13 18:09:46 node-1 kernel: [    0.032111] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 13 18:09:46 node-1 kernel: [    0.032541] Enabled IRQ remapping in xapic mode
Sep 13 18:09:46 node-1 kernel: [    0.032542] x2apic not enabled, IRQ remapping is in xapic mode
Sep 13 18:09:46 node-1 kernel: [    0.032546] Switched APIC routing to physical flat.
Sep 13 18:09:46 node-1 kernel: [    0.033180] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 13 18:09:46 node-1 kernel: [    0.072830] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 13 18:09:46 node-1 kernel: [    0.072835] TSC deadline timer enabled
Sep 13 18:09:46 node-1 kernel: [    0.072842] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 13 18:09:46 node-1 kernel: [    0.072849] ... version:                3
Sep 13 18:09:46 node-1 kernel: [    0.072850] ... bit width:              48
Sep 13 18:09:46 node-1 kernel: [    0.072851] ... generic registers:      4
Sep 13 18:09:46 node-1 kernel: [    0.072852] ... value mask:             0000ffffffffffff
Sep 13 18:09:46 node-1 kernel: [    0.072853] ... max period:             0000ffffffffffff
Sep 13 18:09:46 node-1 kernel: [    0.072854] ... fixed-purpose events:   3
Sep 13 18:09:46 node-1 kernel: [    0.072855] ... event mask:             000000070000000f
Sep 13 18:09:46 node-1 kernel: [    0.074244] x86: Booting SMP configuration:
Sep 13 18:09:46 node-1 kernel: [    0.088355] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 13 18:09:46 node-1 kernel: [    0.074246] .... node  #0, CPUs:        #1  #2  #3
Sep 13 18:09:46 node-1 kernel: [    0.116262] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 13 18:09:46 node-1 kernel: [    0.270210] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 13 18:09:46 node-1 kernel: [    0.325821] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 13 18:09:46 node-1 kernel: [    0.382672] x86: Booted up 2 nodes, 16 CPUs
Sep 13 18:09:46 node-1 kernel: [    0.382675] smpboot: Total of 16 processors activated (111751.98 BogoMIPS)
Sep 13 18:09:46 node-1 kernel: [    0.406288] devtmpfs: initialized
Sep 13 18:09:46 node-1 kernel: [    0.409614] EVM: security.selinux
Sep 13 18:09:46 node-1 kernel: [    0.409616] EVM: security.SMACK64
Sep 13 18:09:46 node-1 kernel: [    0.409617] EVM: security.ima
Sep 13 18:09:46 node-1 kernel: [    0.409618] EVM: security.capability
Sep 13 18:09:46 node-1 kernel: [    0.409668] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 13 18:09:46 node-1 kernel: [    0.410347] pinctrl core: initialized pinctrl subsystem
Sep 13 18:09:46 node-1 kernel: [    0.410415] regulator-dummy: no parameters
Sep 13 18:09:46 node-1 kernel: [    0.410447] RTC time: 18:09:08, date: 09/13/16
Sep 13 18:09:46 node-1 kernel: [    0.410480] NET: Registered protocol family 16
Sep 13 18:09:46 node-1 kernel: [    0.410565] cpuidle: using governor ladder
Sep 13 18:09:46 node-1 kernel: [    0.410566] cpuidle: using governor menu
Sep 13 18:09:46 node-1 kernel: [    0.410600] ACPI: bus type PCI registered
Sep 13 18:09:46 node-1 kernel: [    0.410602] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 13 18:09:46 node-1 kernel: [    0.410646] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 13 18:09:46 node-1 kernel: [    0.410648] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 13 18:09:46 node-1 kernel: [    0.424378] PCI: Using configuration type 1 for base access
Sep 13 18:09:46 node-1 kernel: [    0.425394] bio: create slab <bio-0> at 0
Sep 13 18:09:46 node-1 kernel: [    0.425675] ACPI: Added _OSI(Module Device)
Sep 13 18:09:46 node-1 kernel: [    0.425677] ACPI: Added _OSI(Processor Device)
Sep 13 18:09:46 node-1 kernel: [    0.425678] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 13 18:09:46 node-1 kernel: [    0.425679] ACPI: Added _OSI(Processor Aggregator Device)
Sep 13 18:09:46 node-1 kernel: [    0.438328] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 13 18:09:46 node-1 kernel: [    0.449936] ACPI: Interpreter enabled
Sep 13 18:09:46 node-1 kernel: [    0.449942] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 13 18:09:46 node-1 kernel: [    0.449946] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 13 18:09:46 node-1 kernel: [    0.449948] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 13 18:09:46 node-1 kernel: [    0.449955] ACPI: (supports S0 S4 S5)
Sep 13 18:09:46 node-1 kernel: [    0.449957] ACPI: Using IOAPIC for interrupt routing
Sep 13 18:09:46 node-1 kernel: [    0.450002] HEST: Table parsing has been initialized.
Sep 13 18:09:46 node-1 kernel: [    0.450005] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 13 18:09:46 node-1 kernel: [    0.450559] ACPI: No dock devices found.
Sep 13 18:09:46 node-1 kernel: [    0.462294] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 13 18:09:46 node-1 kernel: [    0.462299] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 18:09:46 node-1 kernel: [    0.462302] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 13 18:09:46 node-1 kernel: [    0.462329] PCI host bridge to bus 0000:ff
Sep 13 18:09:46 node-1 kernel: [    0.462331] pci_bus 0000:ff: root bus resource [bus ff]
Sep 13 18:09:46 node-1 kernel: [    0.462339] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462377] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.462408] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462442] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462471] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.462500] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.462531] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462559] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462589] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462620] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462646] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462672] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462700] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462726] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462753] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462780] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462808] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462835] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462862] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.462889] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462915] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.462942] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462968] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.462998] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.463034] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463065] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463095] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463127] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463159] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463192] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463223] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463253] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463284] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463318] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463351] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463384] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463419] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463448] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463475] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463507] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463542] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463580] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463616] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463650] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463679] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463708] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463739] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463770] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463804] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463835] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463868] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463898] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463928] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463959] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.463988] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464019] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464051] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464108] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 13 18:09:46 node-1 kernel: [    0.464111] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 18:09:46 node-1 kernel: [    0.464114] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 13 18:09:46 node-1 kernel: [    0.464131] PCI host bridge to bus 0000:7f
Sep 13 18:09:46 node-1 kernel: [    0.464133] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 13 18:09:46 node-1 kernel: [    0.464141] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464169] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.464197] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464227] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464249] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.464273] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.464298] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464324] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464346] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464369] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464391] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464413] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464437] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464459] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464482] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464508] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464530] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464552] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464575] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.464599] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464621] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.464643] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464666] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464692] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 13 18:09:46 node-1 kernel: [    0.464724] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464750] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464776] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464803] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464828] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464856] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464883] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464913] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464938] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464965] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.464993] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465020] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465049] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465074] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465099] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465127] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465152] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465180] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465210] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465238] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465263] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465289] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465315] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465343] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465370] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465396] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465427] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465452] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465475] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465503] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465529] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465558] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.465584] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.466827] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 13 18:09:46 node-1 kernel: [    0.466831] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 18:09:46 node-1 kernel: [    0.467958] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 13 18:09:46 node-1 kernel: [    0.468467] PCI host bridge to bus 0000:00
Sep 13 18:09:46 node-1 kernel: [    0.468469] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 13 18:09:46 node-1 kernel: [    0.468471] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 13 18:09:46 node-1 kernel: [    0.468472] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 13 18:09:46 node-1 kernel: [    0.468473] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 13 18:09:46 node-1 kernel: [    0.468475] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 13 18:09:46 node-1 kernel: [    0.468476] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 13 18:09:46 node-1 kernel: [    0.468478] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 13 18:09:46 node-1 kernel: [    0.468484] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 13 18:09:46 node-1 kernel: [    0.468566] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.468597] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.468638] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 13 18:09:46 node-1 kernel: [    0.468657] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.468687] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.468727] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 13 18:09:46 node-1 kernel: [    0.468745] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.468775] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.468817] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 13 18:09:46 node-1 kernel: [    0.468834] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.468904] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.468980] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.469055] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 13 18:09:46 node-1 kernel: [    0.469060] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 13 18:09:46 node-1 kernel: [    0.469144] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 13 18:09:46 node-1 kernel: [    0.469293] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 13 18:09:46 node-1 kernel: [    0.469310] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 13 18:09:46 node-1 kernel: [    0.469387] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.469442] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 13 18:09:46 node-1 kernel: [    0.469463] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.469518] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.469562] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 13 18:09:46 node-1 kernel: [    0.469588] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.469644] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.469687] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 13 18:09:46 node-1 kernel: [    0.469711] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 13 18:09:46 node-1 kernel: [    0.469728] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 13 18:09:46 node-1 kernel: [    0.469806] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.469856] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 13 18:09:46 node-1 kernel: [    0.469881] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 13 18:09:46 node-1 kernel: [    0.470128] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 13 18:09:46 node-1 kernel: [    0.470134] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 13 18:09:46 node-1 kernel: [    0.470140] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 13 18:09:46 node-1 kernel: [    0.470146] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 13 18:09:46 node-1 kernel: [    0.470153] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 13 18:09:46 node-1 kernel: [    0.470183] pci 0000:01:00.0: supports D1 D2
Sep 13 18:09:46 node-1 kernel: [    0.480151] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 13 18:09:46 node-1 kernel: [    0.480157] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 13 18:09:46 node-1 kernel: [    0.480161] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 13 18:09:46 node-1 kernel: [    0.480428] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.480488] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 13 18:09:46 node-1 kernel: [    0.488148] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 13 18:09:46 node-1 kernel: [    0.488151] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.488153] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:46 node-1 kernel: [    0.488208] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.488276] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 13 18:09:46 node-1 kernel: [    0.488367] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.488412] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 13 18:09:46 node-1 kernel: [    0.488415] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.488417] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:46 node-1 kernel: [    0.488470] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.488594] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.488648] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 13 18:09:46 node-1 kernel: [    0.488650] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.488652] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:46 node-1 kernel: [    0.488702] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.488821] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.488863] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.488982] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.489020] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.489141] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.489177] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 13 18:09:46 node-1 kernel: [    0.489296] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:46 node-1 kernel: [    0.489337] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 13 18:09:46 node-1 kernel: [    0.489339] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.489341] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:46 node-1 kernel: [    0.489413] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 13 18:09:46 node-1 kernel: [    0.489476] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 13 18:09:46 node-1 kernel: [    0.489528] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 13 18:09:46 node-1 kernel: [    0.489573] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 13 18:09:46 node-1 kernel: [    0.489655] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 13 18:09:46 node-1 kernel: [    0.489763] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 13 18:09:46 node-1 kernel: [    0.489766] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.489768] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 13 18:09:46 node-1 kernel: [    0.489823] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 13 18:09:46 node-1 kernel: [    0.489877] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 13 18:09:46 node-1 kernel: [    0.489925] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 13 18:09:46 node-1 kernel: [    0.490138] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 13 18:09:46 node-1 kernel: [    0.490142] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 13 18:09:46 node-1 kernel: [    0.490205] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 13 18:09:46 node-1 kernel: [    0.490258] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 13 18:09:46 node-1 kernel: [    0.490306] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 13 18:09:46 node-1 kernel: [    0.490541] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 13 18:09:46 node-1 kernel: [    0.490545] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 13 18:09:46 node-1 kernel: [    0.490604] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 13 18:09:46 node-1 kernel: [    0.490668] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 13 18:09:46 node-1 kernel: [    0.490720] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 13 18:09:46 node-1 kernel: [    0.490942] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 13 18:09:46 node-1 kernel: [    0.490946] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 13 18:09:46 node-1 kernel: [    0.491120] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 13 18:09:46 node-1 kernel: [    0.491158] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 13 18:09:46 node-1 kernel: [    0.491233] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 13 18:09:46 node-1 kernel: [    0.491252] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 13 18:09:46 node-1 kernel: [    0.491265] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 13 18:09:46 node-1 kernel: [    0.491279] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 13 18:09:46 node-1 kernel: [    0.491329] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 13 18:09:46 node-1 kernel: [    0.496162] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 13 18:09:46 node-1 kernel: [    0.496171] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 13 18:09:46 node-1 kernel: [    0.496223] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 13 18:09:46 node-1 kernel: [    0.496813] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 13 18:09:46 node-1 kernel: [    0.496816] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 18:09:46 node-1 kernel: [    0.496941] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 13 18:09:46 node-1 kernel: [    0.497049] PCI host bridge to bus 0000:80
Sep 13 18:09:46 node-1 kernel: [    0.497051] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 13 18:09:46 node-1 kernel: [    0.497052] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 13 18:09:46 node-1 kernel: [    0.497054] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 13 18:09:46 node-1 kernel: [    0.497062] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.497126] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.497195] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 13 18:09:46 node-1 kernel: [    0.497255] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 13 18:09:46 node-1 kernel: [    0.497261] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 13 18:09:46 node-1 kernel: [    0.497333] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 13 18:09:46 node-1 kernel: [    0.497633] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 13 18:09:46 node-1 kernel: [    0.497665] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 13 18:09:46 node-1 kernel: [    0.497695] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 13 18:09:46 node-1 kernel: [    0.497724] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 13 18:09:46 node-1 kernel: [    0.497753] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 18:09:46 node-1 kernel: [    0.497784] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 18:09:46 node-1 kernel: [    0.497813] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 18:09:46 node-1 kernel: [    0.497843] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 18:09:46 node-1 kernel: [    0.497927] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 13 18:09:46 node-1 kernel: [    0.497932] ACPI: \_SB_.UNC1: notify handler is installed
Sep 13 18:09:46 node-1 kernel: [    0.497933] ACPI: \_SB_.UNC0: notify handler is installed
Sep 13 18:09:46 node-1 kernel: [    0.497948] ACPI: \_SB_.PCI0: notify handler is installed
Sep 13 18:09:46 node-1 kernel: [    0.498000] ACPI: \_SB_.PCI1: notify handler is installed
Sep 13 18:09:46 node-1 kernel: [    0.498079] Found 4 acpi root devices
Sep 13 18:09:46 node-1 kernel: [    0.498186] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 13 18:09:46 node-1 kernel: [    0.498188] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 13 18:09:46 node-1 kernel: [    0.498189] vgaarb: loaded
Sep 13 18:09:46 node-1 kernel: [    0.498190] vgaarb: bridge control possible 0000:0c:00.0
Sep 13 18:09:46 node-1 kernel: [    0.498306] SCSI subsystem initialized
Sep 13 18:09:46 node-1 kernel: [    0.498370] libata version 3.00 loaded.
Sep 13 18:09:46 node-1 kernel: [    0.498386] ACPI: bus type USB registered
Sep 13 18:09:46 node-1 kernel: [    0.498396] usbcore: registered new interface driver usbfs
Sep 13 18:09:46 node-1 kernel: [    0.498401] usbcore: registered new interface driver hub
Sep 13 18:09:46 node-1 kernel: [    0.498424] usbcore: registered new device driver usb
Sep 13 18:09:46 node-1 kernel: [    0.498590] PCI: Using ACPI for IRQ routing
Sep 13 18:09:46 node-1 kernel: [    0.502184] PCI: pci_cache_line_size set to 64 bytes
Sep 13 18:09:46 node-1 kernel: [    0.502403] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 13 18:09:46 node-1 kernel: [    0.502405] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 13 18:09:46 node-1 kernel: [    0.502405] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 13 18:09:46 node-1 kernel: [    0.502471] NetLabel: Initializing
Sep 13 18:09:46 node-1 kernel: [    0.502472] NetLabel:  domain hash size = 128
Sep 13 18:09:46 node-1 kernel: [    0.502473] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 13 18:09:46 node-1 kernel: [    0.502483] NetLabel:  unlabeled traffic allowed by default
Sep 13 18:09:46 node-1 kernel: [    0.502539] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 13 18:09:46 node-1 kernel: [    0.502543] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 13 18:09:46 node-1 kernel: [    0.504610] Switched to clocksource hpet
Sep 13 18:09:46 node-1 kernel: [    0.508555] AppArmor: AppArmor Filesystem Enabled
Sep 13 18:09:46 node-1 kernel: [    0.508569] pnp: PnP ACPI init
Sep 13 18:09:46 node-1 kernel: [    0.508576] ACPI: bus type PNP registered
Sep 13 18:09:46 node-1 kernel: [    0.508693] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 13 18:09:46 node-1 kernel: [    0.508701] pnp 00:01: [dma 4]
Sep 13 18:09:46 node-1 kernel: [    0.508713] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 13 18:09:46 node-1 kernel: [    0.508740] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 13 18:09:46 node-1 kernel: [    0.508759] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 13 18:09:46 node-1 kernel: [    0.508777] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 13 18:09:46 node-1 kernel: [    0.508810] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 13 18:09:46 node-1 kernel: [    0.508863] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 13 18:09:46 node-1 kernel: [    0.508865] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 13 18:09:46 node-1 kernel: [    0.508867] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 13 18:09:46 node-1 kernel: [    0.508868] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 13 18:09:46 node-1 kernel: [    0.508869] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 13 18:09:46 node-1 kernel: [    0.508874] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 13 18:09:46 node-1 kernel: [    0.508877] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 13 18:09:46 node-1 kernel: [    0.508878] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 13 18:09:46 node-1 kernel: [    0.508880] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 13 18:09:46 node-1 kernel: [    0.508881] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 13 18:09:46 node-1 kernel: [    0.508883] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 13 18:09:46 node-1 kernel: [    0.508884] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 13 18:09:46 node-1 kernel: [    0.508886] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 13 18:09:46 node-1 kernel: [    0.508888] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 13 18:09:46 node-1 kernel: [    0.508971] pnp 00:07: [dma 0 disabled]
Sep 13 18:09:46 node-1 kernel: [    0.509000] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 13 18:09:46 node-1 kernel: [    0.509074] pnp 00:08: [dma 0 disabled]
Sep 13 18:09:46 node-1 kernel: [    0.509107] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 13 18:09:46 node-1 kernel: [    0.509158] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 13 18:09:46 node-1 kernel: [    0.509508] pnp: PnP ACPI: found 10 devices
Sep 13 18:09:46 node-1 kernel: [    0.509509] ACPI: bus type PNP unregistered
Sep 13 18:09:46 node-1 kernel: [    0.515799] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 13 18:09:46 node-1 kernel: [    0.515802] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 13 18:09:46 node-1 kernel: [    0.515804] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 13 18:09:46 node-1 kernel: [    0.515809] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 13 18:09:46 node-1 kernel: [    0.515811] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.515825] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 13 18:09:46 node-1 kernel: [    0.515854] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 13 18:09:46 node-1 kernel: [    0.515868] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 13 18:09:46 node-1 kernel: [    0.515900] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 13 18:09:46 node-1 kernel: [    0.515915] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 13 18:09:46 node-1 kernel: [    0.515943] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 13 18:09:46 node-1 kernel: [    0.515958] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 13 18:09:46 node-1 kernel: [    0.515987] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 13 18:09:46 node-1 kernel: [    0.515988] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.516003] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:46 node-1 kernel: [    0.516032] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 13 18:09:46 node-1 kernel: [    0.516034] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.516048] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:46 node-1 kernel: [    0.516077] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 13 18:09:46 node-1 kernel: [    0.516079] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.516082] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:46 node-1 kernel: [    0.516086] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 13 18:09:46 node-1 kernel: [    0.516087] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.516090] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:46 node-1 kernel: [    0.516093] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 13 18:09:46 node-1 kernel: [    0.516098] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 13 18:09:46 node-1 kernel: [    0.516106] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 13 18:09:46 node-1 kernel: [    0.516110] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 13 18:09:46 node-1 kernel: [    0.516116] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 13 18:09:46 node-1 kernel: [    0.516117] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 13 18:09:46 node-1 kernel: [    0.516118] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 13 18:09:46 node-1 kernel: [    0.516118] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 13 18:09:46 node-1 kernel: [    0.516119] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 13 18:09:46 node-1 kernel: [    0.516120] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 13 18:09:46 node-1 kernel: [    0.516121] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 13 18:09:46 node-1 kernel: [    0.516122] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 13 18:09:46 node-1 kernel: [    0.516123] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.516124] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:46 node-1 kernel: [    0.516125] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.516126] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:46 node-1 kernel: [    0.516126] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.516127] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:46 node-1 kernel: [    0.516128] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.516129] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:46 node-1 kernel: [    0.516130] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 13 18:09:46 node-1 kernel: [    0.516131] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 13 18:09:46 node-1 kernel: [    0.516132] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 13 18:09:46 node-1 kernel: [    0.516133] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 13 18:09:46 node-1 kernel: [    0.516134] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 13 18:09:46 node-1 kernel: [    0.516135] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 13 18:09:46 node-1 kernel: [    0.516137] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 13 18:09:46 node-1 kernel: [    0.516138] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 13 18:09:46 node-1 kernel: [    0.516176] NET: Registered protocol family 2
Sep 13 18:09:46 node-1 kernel: [    0.516429] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 13 18:09:46 node-1 kernel: [    0.516764] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 13 18:09:46 node-1 kernel: [    0.516905] TCP: Hash tables configured (established 262144 bind 65536)
Sep 13 18:09:46 node-1 kernel: [    0.516948] TCP: reno registered
Sep 13 18:09:46 node-1 kernel: [    0.516977] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 13 18:09:46 node-1 kernel: [    0.517070] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 13 18:09:46 node-1 kernel: [    0.517220] NET: Registered protocol family 1
Sep 13 18:09:46 node-1 kernel: [    0.552715] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 13 18:09:46 node-1 kernel: [    0.552731] PCI: CLS 64 bytes, default 64
Sep 13 18:09:46 node-1 kernel: [    0.552805] Trying to unpack rootfs image as initramfs...
Sep 13 18:09:46 node-1 kernel: [    0.773025] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Sep 13 18:09:46 node-1 kernel: [    0.773058] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 13 18:09:46 node-1 kernel: [    0.773061] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 13 18:09:46 node-1 kernel: [    0.773456] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773463] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773467] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773473] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773482] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773493] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773502] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773511] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773519] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773527] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773533] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773539] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773546] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773553] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773561] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773568] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:46 node-1 kernel: [    0.773609] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 13 18:09:46 node-1 kernel: [    0.773612] Scanning for low memory corruption every 60 seconds
Sep 13 18:09:46 node-1 kernel: [    0.773917] Initialise system trusted keyring
Sep 13 18:09:46 node-1 kernel: [    0.773965] audit: initializing netlink socket (disabled)
Sep 13 18:09:46 node-1 kernel: [    0.773975] type=2000 audit(1473790148.724:1): initialized
Sep 13 18:09:46 node-1 kernel: [    0.791768] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 13 18:09:46 node-1 kernel: [    0.793229] zbud: loaded
Sep 13 18:09:46 node-1 kernel: [    0.793340] VFS: Disk quotas dquot_6.5.2
Sep 13 18:09:46 node-1 kernel: [    0.793380] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 13 18:09:46 node-1 kernel: [    0.793743] fuse init (API version 7.22)
Sep 13 18:09:46 node-1 kernel: [    0.793798] msgmni has been set to 32768
Sep 13 18:09:46 node-1 kernel: [    0.793841] Key type big_key registered
Sep 13 18:09:46 node-1 kernel: [    0.794358] Key type asymmetric registered
Sep 13 18:09:46 node-1 kernel: [    0.794360] Asymmetric key parser 'x509' registered
Sep 13 18:09:46 node-1 kernel: [    0.794381] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 13 18:09:46 node-1 kernel: [    0.794433] io scheduler noop registered
Sep 13 18:09:46 node-1 kernel: [    0.794435] io scheduler deadline registered (default)
Sep 13 18:09:46 node-1 kernel: [    0.794452] io scheduler cfq registered
Sep 13 18:09:46 node-1 kernel: [    0.794740] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    0.794830] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    0.794917] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    0.795006] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    0.795100] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    0.795165] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    0.795442] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 13 18:09:46 node-1 kernel: [    0.795460] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 13 18:09:46 node-1 kernel: [    0.795473] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 13 18:09:46 node-1 kernel: [    0.795482] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795484] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795486] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 13 18:09:46 node-1 kernel: [    0.795490] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795492] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795493] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795494] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795495] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795497] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795498] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795500] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795501] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795502] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795504] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795505] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795507] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 13 18:09:46 node-1 kernel: [    0.795511] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795513] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 13 18:09:46 node-1 kernel: [    0.795522] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795525] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 13 18:09:46 node-1 kernel: [    0.795534] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795536] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:46 node-1 kernel: [    0.795538] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 13 18:09:46 node-1 kernel: [    0.795551] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 13 18:09:46 node-1 kernel: [    0.795638] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 13 18:09:46 node-1 kernel: [    0.795642] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 13 18:09:46 node-1 kernel: [    0.795650] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 13 18:09:46 node-1 kernel: [    0.795685] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 13 18:09:46 node-1 kernel: [    0.795687] vesafb: scrolling: redraw
Sep 13 18:09:46 node-1 kernel: [    0.795688] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 13 18:09:46 node-1 kernel: [    0.816454] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 13 18:09:46 node-1 kernel: [    0.825025] Console: switching to colour frame buffer device 80x30
Sep 13 18:09:46 node-1 kernel: [    0.833739] fb0: VESA VGA frame buffer device
Sep 13 18:09:46 node-1 kernel: [    0.833937] intel_idle: MWAIT substates: 0x2120
Sep 13 18:09:46 node-1 kernel: [    0.833938] intel_idle: v0.4 model 0x3F
Sep 13 18:09:46 node-1 kernel: [    0.833939] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 13 18:09:46 node-1 kernel: [    0.834178] ipmi message handler version 39.2
Sep 13 18:09:46 node-1 kernel: [    0.834451] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 13 18:09:46 node-1 kernel: [    0.834890] ACPI: AC Adapter [P111] (on-line)
Sep 13 18:09:46 node-1 kernel: [    0.840139] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 13 18:09:46 node-1 kernel: [    0.851225] ACPI: Power Button [PWRB]
Sep 13 18:09:46 node-1 kernel: [    0.857036] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 13 18:09:46 node-1 kernel: [    0.868761] ACPI: Power Button [PWRF]
Sep 13 18:09:46 node-1 kernel: [    0.886261] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 13 18:09:46 node-1 kernel: [    0.898051] pstore: Registered erst as persistent store backend
Sep 13 18:09:46 node-1 kernel: [    0.904373] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 13 18:09:46 node-1 kernel: [    0.916516] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 13 18:09:46 node-1 kernel: [    0.943338] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 13 18:09:46 node-1 kernel: [    0.976713] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 13 18:09:46 node-1 kernel: [    0.990825] Linux agpgart interface v0.103
Sep 13 18:09:46 node-1 kernel: [    0.998447] brd: module loaded
Sep 13 18:09:46 node-1 kernel: [    1.005466] loop: module loaded
Sep 13 18:09:46 node-1 kernel: [    1.012180] libphy: Fixed MDIO Bus: probed
Sep 13 18:09:46 node-1 kernel: [    1.018640] tun: Universal TUN/TAP device driver, 1.6
Sep 13 18:09:46 node-1 kernel: [    1.025116] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 13 18:09:46 node-1 kernel: [    1.031630] PPP generic driver version 2.4.2
Sep 13 18:09:46 node-1 kernel: [    1.038013] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 13 18:09:46 node-1 kernel: [    1.044457] ehci-pci: EHCI PCI platform driver
Sep 13 18:09:46 node-1 kernel: [    1.051072] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 13 18:09:46 node-1 kernel: [    1.057539] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 13 18:09:46 node-1 kernel: [    1.070069] ehci-pci 0000:00:1a.0: debug port 2
Sep 13 18:09:46 node-1 kernel: [    1.080262] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 13 18:09:46 node-1 kernel: [    1.080280] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 13 18:09:46 node-1 kernel: [    1.096113] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 13 18:09:46 node-1 kernel: [    1.102185] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 13 18:09:46 node-1 kernel: [    1.108378] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 13 18:09:46 node-1 kernel: [    1.120279] usb usb1: Product: EHCI Host Controller
Sep 13 18:09:46 node-1 kernel: [    1.126309] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 13 18:09:46 node-1 kernel: [    1.132350] usb usb1: SerialNumber: 0000:00:1a.0
Sep 13 18:09:46 node-1 kernel: [    1.138297] hub 1-0:1.0: USB hub found
Sep 13 18:09:46 node-1 kernel: [    1.144071] hub 1-0:1.0: 2 ports detected
Sep 13 18:09:46 node-1 kernel: [    1.149852] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 13 18:09:46 node-1 kernel: [    1.155426] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 13 18:09:46 node-1 kernel: [    1.166307] ehci-pci 0000:00:1d.0: debug port 2
Sep 13 18:09:46 node-1 kernel: [    1.175604] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 13 18:09:46 node-1 kernel: [    1.175607] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 13 18:09:46 node-1 kernel: [    1.192032] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 13 18:09:46 node-1 kernel: [    1.197228] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 13 18:09:46 node-1 kernel: [    1.202519] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 13 18:09:46 node-1 kernel: [    1.213089] usb usb2: Product: EHCI Host Controller
Sep 13 18:09:46 node-1 kernel: [    1.218543] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 13 18:09:46 node-1 kernel: [    1.224097] usb usb2: SerialNumber: 0000:00:1d.0
Sep 13 18:09:46 node-1 kernel: [    1.229608] hub 2-0:1.0: USB hub found
Sep 13 18:09:46 node-1 kernel: [    1.234954] hub 2-0:1.0: 2 ports detected
Sep 13 18:09:46 node-1 kernel: [    1.240250] ehci-platform: EHCI generic platform driver
Sep 13 18:09:46 node-1 kernel: [    1.245482] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 13 18:09:46 node-1 kernel: [    1.250793] ohci-pci: OHCI PCI platform driver
Sep 13 18:09:46 node-1 kernel: [    1.256094] ohci-platform: OHCI generic platform driver
Sep 13 18:09:46 node-1 kernel: [    1.261277] uhci_hcd: USB Universal Host Controller Interface driver
Sep 13 18:09:46 node-1 kernel: [    1.266622] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 13 18:09:46 node-1 kernel: [    1.459811] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 13 18:09:46 node-1 kernel: [    1.632042] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 13 18:09:46 node-1 kernel: [    1.637564] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 13 18:09:46 node-1 kernel: [    1.643306] hub 1-1:1.0: USB hub found
Sep 13 18:09:46 node-1 kernel: [    1.648780] hub 1-1:1.0: 6 ports detected
Sep 13 18:09:46 node-1 kernel: [    1.763546] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 13 18:09:46 node-1 kernel: [    1.771559] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 13 18:09:46 node-1 kernel: [    2.031705] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 13 18:09:46 node-1 kernel: [    2.037258] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 13 18:09:46 node-1 kernel: [    2.043096] hub 2-1:1.0: USB hub found
Sep 13 18:09:46 node-1 kernel: [    2.048816] hub 2-1:1.0: 8 ports detected
Sep 13 18:09:46 node-1 kernel: [    2.307995] i8042: No controller found
Sep 13 18:09:46 node-1 kernel: [    2.313387] mousedev: PS/2 mouse device common for all mice
Sep 13 18:09:46 node-1 kernel: [    2.318886] rtc_cmos 00:02: RTC can wake from S4
Sep 13 18:09:46 node-1 kernel: [    2.324465] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 13 18:09:46 node-1 kernel: [    2.327139] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 13 18:09:46 node-1 kernel: [    2.335610] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 13 18:09:46 node-1 kernel: [    2.346721] device-mapper: uevent: version 1.0.3
Sep 13 18:09:46 node-1 kernel: [    2.352347] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 13 18:09:46 node-1 kernel: [    2.363591] ledtrig-cpu: registered to indicate activity on CPUs
Sep 13 18:09:46 node-1 kernel: [    2.369526] TCP: cubic registered
Sep 13 18:09:46 node-1 kernel: [    2.375421] NET: Registered protocol family 10
Sep 13 18:09:46 node-1 kernel: [    2.381397] NET: Registered protocol family 17
Sep 13 18:09:46 node-1 kernel: [    2.387091] Key type dns_resolver registered
Sep 13 18:09:46 node-1 kernel: [    2.393061] Loading compiled-in X.509 certificates
Sep 13 18:09:46 node-1 kernel: [    2.399244] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 13 18:09:46 node-1 kernel: [    2.410613] registered taskstats version 1
Sep 13 18:09:46 node-1 kernel: [    2.418511] Key type trusted registered
Sep 13 18:09:46 node-1 kernel: [    2.426051] Key type encrypted registered
Sep 13 18:09:46 node-1 kernel: [    2.431495] AppArmor: AppArmor sha1 policy hashing enabled
Sep 13 18:09:46 node-1 kernel: [    2.436976] IMA: No TPM chip found, activating TPM-bypass!
Sep 13 18:09:46 node-1 kernel: [    2.443141] regulator-dummy: disabling
Sep 13 18:09:46 node-1 kernel: [    2.448695]   Magic number: 0:521:190
Sep 13 18:09:46 node-1 kernel: [    2.454182] acpi device:49: hash matches
Sep 13 18:09:46 node-1 kernel: [    2.459462] acpi device:1c: hash matches
Sep 13 18:09:46 node-1 kernel: [    2.463776] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 13 18:09:46 node-1 kernel: [    2.463777] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 13 18:09:46 node-1 kernel: [    2.463777] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 13 18:09:46 node-1 kernel: [    2.463778] usb 2-1.4: Manufacturer: Avocent
Sep 13 18:09:46 node-1 kernel: [    2.463779] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 13 18:09:46 node-1 kernel: [    2.496858] rtc_cmos 00:02: setting system clock to 2016-09-13 18:09:10 UTC (1473790150)
Sep 13 18:09:46 node-1 kernel: [    2.509025] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 13 18:09:46 node-1 kernel: [    2.514455] EDD information not available.
Sep 13 18:09:46 node-1 kernel: [    2.519861] PM: Hibernation image not present or could not be loaded.
Sep 13 18:09:46 node-1 kernel: [    2.520724] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 13 18:09:46 node-1 kernel: [    2.531525] Write protecting the kernel read-only data: 12288k
Sep 13 18:09:46 node-1 kernel: [    2.537461] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 13 18:09:46 node-1 kernel: [    2.549508] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 13 18:09:46 node-1 kernel: [    2.582326] device-mapper: multipath: version 1.6.0 loaded
Sep 13 18:09:46 node-1 kernel: [    2.590126] systemd-udevd[217]: starting version 204
Sep 13 18:09:46 node-1 kernel: [    2.614008] md: linear personality registered for level -1
Sep 13 18:09:46 node-1 kernel: [    2.628088] md: multipath personality registered for level -4
Sep 13 18:09:46 node-1 kernel: [    2.636034] md: raid0 personality registered for level 0
Sep 13 18:09:46 node-1 kernel: [    2.644121] md: raid1 personality registered for level 1
Sep 13 18:09:46 node-1 kernel: [    2.653756] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 13 18:09:46 node-1 kernel: [    2.659999] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 13 18:09:46 node-1 kernel: [    2.660001] hidraw: raw HID events driver (C) Jiri Kosina
Sep 13 18:09:46 node-1 kernel: [    2.668815] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Sep 13 18:09:46 node-1 kernel: [    2.668816] 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
Sep 13 18:09:46 node-1 kernel: [    2.668817] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 18:09:46 node-1 kernel: [    2.668894] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.668934] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.668969] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.669008] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.669080] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.680764] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Sep 13 18:09:46 node-1 kernel: [    2.680765] 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
Sep 13 18:09:46 node-1 kernel: [    2.680766] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 18:09:46 node-1 kernel: [    2.680821] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.680859] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.680893] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.680932] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.681004] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.692824] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Sep 13 18:09:46 node-1 kernel: [    2.692825] 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
Sep 13 18:09:46 node-1 kernel: [    2.692826] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 18:09:46 node-1 kernel: [    2.692884] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.692923] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.692961] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.692994] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.693055] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.704046] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Sep 13 18:09:46 node-1 kernel: [    2.704047] 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
Sep 13 18:09:46 node-1 kernel: [    2.704048] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 18:09:46 node-1 kernel: [    2.704107] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.704147] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.704181] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.704218] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.704294] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 18:09:46 node-1 kernel: [    2.718928] raid6: sse2x1     610 MB/s
Sep 13 18:09:46 node-1 kernel: [    2.786946] raid6: sse2x2     459 MB/s
Sep 13 18:09:46 node-1 kernel: [    2.854837] raid6: sse2x4     570 MB/s
Sep 13 18:09:46 node-1 kernel: [    2.922581] raid6: avx2x1    9876 MB/s
Sep 13 18:09:46 node-1 kernel: [    2.994518] raid6: avx2x2   18853 MB/s
Sep 13 18:09:46 node-1 kernel: [    3.066461] raid6: avx2x4   21334 MB/s
Sep 13 18:09:46 node-1 kernel: [    3.072342] raid6: using algorithm avx2x4 (21334 MB/s)
Sep 13 18:09:46 node-1 kernel: [    3.078309] raid6: using avx2x2 recovery algorithm
Sep 13 18:09:46 node-1 kernel: [    3.084135] Switched to clocksource tsc
Sep 13 18:09:46 node-1 kernel: [    3.086870] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 13 18:09:46 node-1 kernel: [    3.088413] megasas: FW now in Ready state
Sep 13 18:09:46 node-1 kernel: [    3.088863] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.088953] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.089019] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.089113] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.089263] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.089408] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.089533] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.089718] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.089812] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.089816] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.090030] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.090135] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.090285] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.090631] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.090802] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.090847] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Sep 13 18:09:46 node-1 kernel: [    3.091577] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 13 18:09:46 node-1 kernel: [    3.112457] xor: automatically using best checksumming function:
Sep 13 18:09:46 node-1 kernel: [    3.115245] usbcore: registered new interface driver usbhid
Sep 13 18:09:46 node-1 kernel: [    3.115246] usbhid: USB HID core driver
Sep 13 18:09:46 node-1 kernel: [    3.130462] 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
Sep 13 18:09:46 node-1 kernel: [    3.141809] 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
Sep 13 18:09:46 node-1 kernel: [    3.153342] 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
Sep 13 18:09:46 node-1 kernel: [    3.165296] 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
Sep 13 18:09:46 node-1 kernel: [    3.177350] 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
Sep 13 18:09:46 node-1 kernel: [    3.182421]    avx       : 101515.000 MB/sec
Sep 13 18:09:46 node-1 kernel: [    3.195115] 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
Sep 13 18:09:46 node-1 kernel: [    3.207448] async_tx: api initialized (async)
Sep 13 18:09:46 node-1 kernel: [    3.217364] md: raid6 personality registered for level 6
Sep 13 18:09:46 node-1 kernel: [    3.223707] md: raid5 personality registered for level 5
Sep 13 18:09:46 node-1 kernel: [    3.230026] md: raid4 personality registered for level 4
Sep 13 18:09:46 node-1 kernel: [    3.239387] md: raid10 personality registered for level 10
Sep 13 18:09:46 node-1 kernel: [    3.294590] multipathd (355): /proc/355/oom_adj is deprecated, please use /proc/355/oom_score_adj instead.
Sep 13 18:09:46 node-1 kernel: [    3.446161] megasas:IOC Init cmd success
Sep 13 18:09:46 node-1 kernel: [    3.474148] megasas: INIT adapter done
Sep 13 18:09:46 node-1 kernel: [    3.574057] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 13 18:09:46 node-1 kernel: [    3.580911] scsi0 : LSI SAS based MegaRAID driver
Sep 13 18:09:46 node-1 kernel: [    3.588170] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 13 18:09:46 node-1 kernel: [    3.610284] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 13 18:09:46 node-1 kernel: [    3.625434] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 13 18:09:46 node-1 kernel: [    3.625438] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 13 18:09:46 node-1 kernel: [    3.643669] sd 0:2:0:0: [sda] Write Protect is off
Sep 13 18:09:46 node-1 kernel: [    3.649554] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 13 18:09:46 node-1 kernel: [    3.649574] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 13 18:09:46 node-1 kernel: [    3.685610]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 13 18:09:46 node-1 kernel: [    3.691977] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 13 18:09:46 node-1 kernel: [    3.811710] random: lvm urandom read with 27 bits of entropy available
Sep 13 18:09:46 node-1 kernel: [    3.969988] bio: create slab <bio-1> at 1
Sep 13 18:09:46 node-1 kernel: [    4.945486] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 18:09:46 node-1 kernel: [    5.604706] random: nonblocking pool is initialized
Sep 13 18:09:46 node-1 kernel: [    5.617456] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Sep 13 18:09:46 node-1 kernel: [    5.648175] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 13 18:09:46 node-1 kernel: [    5.775326] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 13 18:09:46 node-1 kernel: [    5.823197] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 13 18:09:46 node-1 kernel: [    5.874883] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 18:09:46 node-1 kernel: [    6.081961] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 13 18:09:46 node-1 kernel: [    6.136264] XFS (dm-1): Mounting Filesystem
Sep 13 18:09:46 node-1 kernel: [    6.397258] XFS (dm-1): Ending clean mount
Sep 13 18:09:46 node-1 kernel: [    6.473686] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 18:09:46 node-1 kernel: [    6.499654] XFS (dm-2): Mounting Filesystem
Sep 13 18:09:46 node-1 kernel: [    6.577483] XFS (dm-2): Ending clean mount
Sep 13 18:09:46 node-1 kernel: [    6.722439] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 18:09:46 node-1 kernel: [    8.524145] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 13 18:09:46 node-1 kernel: [    8.538976] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 13 18:09:46 node-1 kernel: [    8.672419] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 13 18:09:46 node-1 kernel: [    8.672430] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 13 18:09:46 node-1 kernel: [    8.672434] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 13 18:09:46 node-1 kernel: [    8.672438] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 13 18:09:46 node-1 kernel: [    8.709729] systemd-udevd[805]: starting version 204
Sep 13 18:09:46 node-1 kernel: [    8.923148] power_meter ACPI000D:00: Found ACPI power meter.
Sep 13 18:09:46 node-1 kernel: [    8.923156] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 13 18:09:46 node-1 kernel: [    8.936118] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 13 18:09:46 node-1 kernel: [    8.936124] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 13 18:09:46 node-1 kernel: [    8.936127] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 13 18:09:46 node-1 kernel: [    8.936130] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 13 18:09:46 node-1 kernel: [    8.936193] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 13 18:09:46 node-1 kernel: [    8.946875] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 13 18:09:46 node-1 kernel: [    8.955084] wmi: Mapper loaded
Sep 13 18:09:46 node-1 kernel: [    8.973660] IPMI System Interface driver.
Sep 13 18:09:46 node-1 kernel: [    8.973725] ipmi_si: probing via ACPI
Sep 13 18:09:46 node-1 kernel: [    8.973736] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 13 18:09:46 node-1 kernel: [    8.973737] ipmi_si: Adding ACPI-specified kcs state machine
Sep 13 18:09:46 node-1 kernel: [    8.973758] ipmi_si: probing via SMBIOS
Sep 13 18:09:46 node-1 kernel: [    8.973759] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 13 18:09:46 node-1 kernel: [    8.973759] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 13 18:09:46 node-1 kernel: [    8.973761] ipmi_si: probing via SPMI
Sep 13 18:09:46 node-1 kernel: [    8.973762] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 13 18:09:46 node-1 kernel: [    8.973762] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 13 18:09:46 node-1 kernel: [    8.973764] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 13 18:09:46 node-1 kernel: [    9.017909] systemd-udevd[843]: renamed network interface eth1 to enp7s0
Sep 13 18:09:46 node-1 kernel: [    9.045781] systemd-udevd[840]: renamed network interface eth3 to enp9s0
Sep 13 18:09:46 node-1 kernel: [    9.073752] systemd-udevd[841]: renamed network interface eth0 to enp6s0
Sep 13 18:09:46 node-1 kernel: [    9.101731] systemd-udevd[844]: renamed network interface eth2 to enp8s0
Sep 13 18:09:46 node-1 kernel: [    9.111741] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 13 18:09:46 node-1 kernel: [    9.111749] ipmi_si 00:09: IPMI kcs interface initialized
Sep 13 18:09:46 node-1 kernel: [    9.394337] type=1400 audit(1473790157.401:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1095 comm="apparmor_parser"
Sep 13 18:09:46 node-1 kernel: [    9.394492] type=1400 audit(1473790157.401:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1095 comm="apparmor_parser"
Sep 13 18:09:46 node-1 kernel: [    9.394628] type=1400 audit(1473790157.401:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1095 comm="apparmor_parser"
Sep 13 18:09:46 node-1 kernel: [    9.397453] type=1400 audit(1473790157.405:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1097 comm="apparmor_parser"
Sep 13 18:09:46 node-1 kernel: [    9.397601] type=1400 audit(1473790157.405:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1097 comm="apparmor_parser"
Sep 13 18:09:46 node-1 kernel: [    9.397723] type=1400 audit(1473790157.405:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1097 comm="apparmor_parser"
Sep 13 18:09:46 node-1 kernel: [    9.412646] type=1400 audit(1473790157.417:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1094 comm="apparmor_parser"
Sep 13 18:09:46 node-1 kernel: [    9.412798] type=1400 audit(1473790157.417:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1094 comm="apparmor_parser"
Sep 13 18:09:46 node-1 kernel: [    9.412914] type=1400 audit(1473790157.417:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1094 comm="apparmor_parser"
Sep 13 18:09:46 node-1 kernel: [    9.419277] type=1400 audit(1473790157.425:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1096 comm="apparmor_parser"
Sep 13 18:09:46 node-1 kernel: [    9.966079] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 13 18:09:46 node-1 kernel: [    9.967033] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 13 18:09:46 node-1 kernel: [   10.168683] enic 0000:06:00.0 enp6s0: Link UP
Sep 13 18:09:46 node-1 kernel: [   10.171296] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 13 18:09:46 node-1 kernel: [   10.171305] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 13 18:09:46 node-1 kernel: [   20.567213] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 13 18:09:47 node-1 failsafe: Failsafe of 120 seconds reached.
Sep 13 18:09:47 node-1 kernel: [   39.661357] init: failsafe main process (8454) killed by TERM signal
Sep 13 18:09:47 node-1 dbus[8476]: [system] AppArmor D-Bus mediation is enabled
Sep 13 18:09:48 node-1 kernel: [   39.872453] audit_printk_skb: 30 callbacks suppressed
Sep 13 18:09:48 node-1 kernel: [   39.872454] type=1400 audit(1473790188.160:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8579 comm="apparmor_parser"
Sep 13 18:09:48 node-1 kernel: [   39.872458] type=1400 audit(1473790188.160:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8579 comm="apparmor_parser"
Sep 13 18:09:48 node-1 kernel: [   39.872461] type=1400 audit(1473790188.160:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8579 comm="apparmor_parser"
Sep 13 18:09:48 node-1 kernel: [   39.872681] type=1400 audit(1473790188.160:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8579 comm="apparmor_parser"
Sep 13 18:09:48 node-1 kernel: [   39.872682] type=1400 audit(1473790188.160:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8579 comm="apparmor_parser"
Sep 13 18:09:48 node-1 kernel: [   39.872794] type=1400 audit(1473790188.160:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8579 comm="apparmor_parser"
Sep 13 18:09:48 node-1 kernel: [   39.875763] type=1400 audit(1473790188.164:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8580 comm="apparmor_parser"
Sep 13 18:09:48 node-1 kernel: [   39.957018] type=1400 audit(1473790188.244:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8582 comm="apparmor_parser"
Sep 13 18:09:48 node-1 cron[8612]: (CRON) INFO (pidfile fd = 3)
Sep 13 18:09:48 node-1 anacron[8629]: Anacron 2.3 started on 2016-09-13
Sep 13 18:09:48 node-1 cron[8636]: (CRON) STARTUP (fork ok)
Sep 13 18:09:48 node-1 anacron[8629]: Will run job `cron.daily' in 5 min.
Sep 13 18:09:48 node-1 anacron[8629]: Will run job `cron.weekly' in 10 min.
Sep 13 18:09:48 node-1 anacron[8629]: Will run job `cron.monthly' in 15 min.
Sep 13 18:09:48 node-1 anacron[8629]: Jobs will be executed sequentially
Sep 13 18:09:48 node-1 cron[8636]: (CRON) INFO (Running @reboot jobs)
Sep 13 18:09:48 node-1 multipathd: path checkers start up
Sep 13 18:09:48 node-1 postfix/master[8792]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 13 18:09:52 node-1 puppet-agent[8976]: Reopening log files
Sep 13 18:09:52 node-1 puppet-agent[8976]: Could not request certificate: Connection refused - connect(2)
Sep 13 18:10:01 node-1 CRON[9019]: (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")
Sep 13 18:10:02 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 13 18:10:02 node-1 nailgun-agent: D, [2016-09-13T18:10:01.688052 #9022] DEBUG -- : Sleep for 1 seconds before sending request
Sep 13 18:10:02 node-1 nailgun-agent: I, [2016-09-13T18:10:02.724518 #9022]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 13 18:10:02 node-1 puppet-user[9066]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 13 18:10:02 node-1 puppet-user[9066]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 13 18:10:03 node-1 nailgun-agent: D, [2016-09-13T18:10:03.473238 #9022] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Sep 13 18:10:03 node-1 puppet-user[9066]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 13 18:10:03 node-1 puppet-user[9066]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 13 18:10:03 node-1 puppet-user[9066]: Finished catalog run in 0.87 seconds
Sep 13 18:10:05 node-1 multipathd: uevent trigger error
Sep 13 18:10:05 node-1 puppet-user[9635]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 13 18:10:05 node-1 puppet-user[9635]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Sep 13 18:10:05 node-1 puppet-user[9635]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 13 18:10:05 node-1 puppet-user[9635]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 13 18:10:05 node-1 puppet-user[9635]: (/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"]'
Sep 13 18:10:05 node-1 puppet-user[9635]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 13 18:10:05 node-1 puppet-user[9635]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 13 18:10:05 node-1 puppet-user[9635]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 13 18:10:05 node-1 puppet-user[9635]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 13 18:10:05 node-1 puppet-user[9635]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 13 18:10:05 node-1 puppet-user[9635]: Finished catalog run in 0.06 seconds
Sep 13 18:10:06 node-1 puppet-user[10108]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 13 18:10:07 node-1 puppet-user[10108]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 13 18:10:07 node-1 puppet-user[10108]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 13 18:10:07 node-1 puppet-user[10108]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 13 18:10:07 node-1 puppet-user[10108]: Finished catalog run in 0.03 seconds
Sep 13 18:10:08 node-1 puppet-user[10578]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 13 18:10:08 node-1 puppet-user[10578]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 13 18:10:08 node-1 puppet-user[10578]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 13 18:10:08 node-1 puppet-user[10578]: Finished catalog run in 0.03 seconds
Sep 13 18:10:10 node-1 puppet-user[11041]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 13 18:10:10 node-1 puppet-user[11041]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Sep 13 18:10:10 node-1 puppet-user[11041]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 13 18:10:10 node-1 puppet-user[11041]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Sep 13 18:10:11 node-1 puppet-user[11041]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Sep 13 18:10:11 node-1 puppet-user[11041]: Finished catalog run in 0.84 seconds
Sep 13 18:10:12 node-1 puppet-user[11555]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 13 18:10:12 node-1 puppet-user[11555]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Sep 13 18:10:12 node-1 puppet-user[11555]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Sep 13 18:10:12 node-1 puppet-user[11555]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 13 18:10:12 node-1 puppet-user[11555]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 13 18:10:12 node-1 puppet-user[11555]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Sep 13 18:10:13 node-1 puppet-user[11555]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 13 18:10:13 node-1 puppet-user[11555]: Finished catalog run in 0.34 seconds
Sep 13 18:10:14 node-1 puppet-user[12049]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 13 18:10:14 node-1 puppet-user[12049]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Sep 13 18:10:14 node-1 puppet-user[12049]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 13 18:10:14 node-1 kernel: [   66.505559] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 13 18:10:14 node-1 kernel: [   66.505610] 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.
Sep 13 18:10:14 node-1 puppet-user[12049]: (/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'
Sep 13 18:10:14 node-1 puppet-user[12049]: Finished catalog run in 0.06 seconds
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.639337 #9022] DEBUG -- : Trying to find block devices
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.639444 #9022] DEBUG -- : Found block device: sda
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.639481 #9022] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.639522 #9022] DEBUG -- : Trying to get list of physical devices
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.639674 #9022] DEBUG -- : Getting udev properties for device: sda
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.641481 #9022] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /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"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc7884
Sep 13 18:10:15 node-1 nailgun-agent: d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45919", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.641508 #9022] DEBUG -- : Trying to find out if device sda is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.641552 #9022] DEBUG -- : Device sda removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.641568 #9022] DEBUG -- : Device sda seems to be appropriate
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.642004 #9022] DEBUG -- : Getting udev properties for device: dm-0
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.643576 #9022] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-LUiaoRFqw19zQikIzxCbylllGcCRn9BNXdmpgW3df9ROjFzDG00uxcPfEXNBo1uT /dev/disk/by-uuid/863bb60c-2303-413e-b720-e4e4ba704847 /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "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-LUiaoRFqw19zQikIzxCbylllGcCRn9BNXdmpgW3df9ROjFzDG00uxcPfEXNBo1uT", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"863bb60c-2303-413e-b720-e4e4ba704847", "ID_FS_UUID_ENC"=>"863bb60c-2303-413e-b720-e4e4ba704847", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"24
Sep 13 18:10:15 node-1 nailgun-agent: 233", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.643606 #9022] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.643661 #9022] DEBUG -- : Device dm-0 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.643676 #9022] DEBUG -- : Device dm-0 seems to be appropriate
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.643703 #9022] DEBUG -- : Getting udev properties for device: dm-1
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.645310 #9022] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-VAzKEQBMxcYtoVlbc44leGheiQA2Jv2qKm4ltXb0VzgoQo0hFWaF1xXPtgMOM9yr /dev/disk/by-uuid/b0eff16c-d385-4c1e-8f44-abb131098e9f /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "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-VAzKEQBMxcYtoVlbc44leGheiQA2Jv2qKm4ltXb0VzgoQo0hFWaF1xXPtgMOM9yr", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b0eff16c-d385-4c1e-8f44-abb131098e9f", "ID_FS_UUID_ENC"=>"b0eff16c-d385-4c1e-8f44-abb131098e9f", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53389", "nomdmonddf"=>"1", "nomd
Sep 13 18:10:15 node-1 nailgun-agent: monisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.645337 #9022] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.645378 #9022] DEBUG -- : Device dm-1 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.645409 #9022] DEBUG -- : Device dm-1 seems to be appropriate
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.645432 #9022] DEBUG -- : Getting udev properties for device: dm-2
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.647006 #9022] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-75JAY0NaiYX3zqzMhOyeivxcxm0cuSItOO5d0frc8OUXI8C0R1djXMfFYDbhK2D5 /dev/disk/by-uuid/9b98205f-53d0-499e-b605-932b3c50a999 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "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-75JAY0NaiYX3zqzMhOyeivxcxm0cuSItOO5d0frc8OUXI8C0R1djXMfFYDbhK2D5", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9b98205f-53d0-499e-b605-932b3c50a999", "ID_FS_UUID_ENC"=>"9b98205f-53d0-499e-b605-932b3c50a999", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79
Sep 13 18:10:15 node-1 nailgun-agent: 875", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.647044 #9022] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.647075 #9022] DEBUG -- : Device dm-2 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.647088 #9022] DEBUG -- : Device dm-2 seems to be appropriate
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.647116 #9022] DEBUG -- : Getting udev properties for device: dm-3
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.648708 #9022] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-0oRMnT0zOjlZgkqjyb40G6N1u1keG5HZ2Ww4YFZ91uzqoleo6FNNcEYAp0w4o41e /dev/disk/by-uuid/c05d0884-700a-49d8-bf9e-4396a95791dc /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "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-0oRMnT0zOjlZgkqjyb40G6N1u1keG5HZ2Ww4YFZ91uzqoleo6FNNcEYAp0w4o41e", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c05d0884-700a-49d8-bf9e-4396a95791dc", "ID_FS_UUID_ENC"=>"c05d0884-700a-49d8-bf9e-4396a95791dc", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89198", "nomdmond
Sep 13 18:10:15 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.648746 #9022] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.648796 #9022] DEBUG -- : Device dm-3 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.648809 #9022] DEBUG -- : Device dm-3 seems to be appropriate
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.648824 #9022] DEBUG -- : Getting udev properties for device: dm-4
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.650397 #9022] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-TBpHG3b6yTj9UJLAf2GF4pS62INHAyifhGn3i6DzmVJ1kPvOi024VceIqH5Sc6aZ /dev/disk/by-uuid/a0cfe6b8-de81-45b6-8797-6a43efd9690e /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "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-TBpHG3b6yTj9UJLAf2GF4pS62INHAyifhGn3i6DzmVJ1kPvOi024VceIqH5Sc6aZ", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a0cfe6b8-de81-45b6-8797-6a43efd9690e", "ID_FS_UUID_ENC"=>"a0cfe6b8-de81-45b6-8797-6a43efd9690e", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"94094", "nomdmonddf"=>"1", 
Sep 13 18:10:15 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.650425 #9022] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.650454 #9022] DEBUG -- : Device dm-4 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.650468 #9022] DEBUG -- : Device dm-4 seems to be appropriate
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.650483 #9022] DEBUG -- : Getting udev properties for device: dm-5
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.652094 #9022] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-ddolqHMwssuSoUrBQSWk5wxgX2BOE6iUelAu8pb28VMU6sVsnjvEymvGYGpQyx1y /dev/disk/by-uuid/10c5969a-0bee-4214-8b38-01b49ebc4211 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "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-ddolqHMwssuSoUrBQSWk5wxgX2BOE6iUelAu8pb28VMU6sVsnjvEymvGYGpQyx1y", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"10c5969a-0bee-4214-8b38-01b49ebc4211", "ID_FS_UUID_ENC"=>"10c5969a-0bee-4214-8b38-01b49ebc4211", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95311", "nomdmonddf"=>"1", "nomd
Sep 13 18:10:15 node-1 nailgun-agent: monisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.652121 #9022] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.652151 #9022] DEBUG -- : Device dm-5 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.652165 #9022] DEBUG -- : Device dm-5 seems to be appropriate
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.652192 #9022] DEBUG -- : Getting udev properties for device: dm-6
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.653740 #9022] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-ddolqHMwssuSoUrBQSWk5wxgX2BOE6iUckE7Z4nVv7eZRh6xtYrzDQvqMLimsaGx /dev/disk/by-uuid/f4da9308-6150-4072-a8f2-fb11d7efc87b /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "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-ddolqHMwssuSoUrBQSWk5wxgX2BOE6iUckE7Z4nVv7eZRh6xtYrzDQvqMLimsaGx", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"f4da9308-6150-4072-a8f2-fb11d7efc87b", "ID_FS_UUID_ENC"=>"f4da9308-6150-4072-a8f2-fb11d7efc87b", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95920", "nomdmonddf"=>"1", "nomdmonisw"
Sep 13 18:10:15 node-1 nailgun-agent: =>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.653785 #9022] DEBUG -- : Trying to find out if device dm-6 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.653818 #9022] DEBUG -- : Device dm-6 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.653839 #9022] DEBUG -- : Device dm-6 seems to be appropriate
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.653855 #9022] DEBUG -- : Getting udev properties for device: ram0
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.655284 #9022] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52633", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.655325 #9022] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.655384 #9022] DEBUG -- : Device ram0 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.655404 #9022] DEBUG -- : Getting udev properties for device: ram1
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.656832 #9022] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52796", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.656856 #9022] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.656891 #9022] DEBUG -- : Device ram1 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.656919 #9022] DEBUG -- : Getting udev properties for device: ram2
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.658303 #9022] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54920", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.658329 #9022] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.658374 #9022] DEBUG -- : Device ram2 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.658394 #9022] DEBUG -- : Getting udev properties for device: ram3
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.659807 #9022] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55307", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.659832 #9022] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.659871 #9022] DEBUG -- : Device ram3 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.659905 #9022] DEBUG -- : Getting udev properties for device: ram4
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.661292 #9022] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55627", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.661324 #9022] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.661373 #9022] DEBUG -- : Device ram4 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.661393 #9022] DEBUG -- : Getting udev properties for device: ram5
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.662780 #9022] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55864", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.662805 #9022] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.662850 #9022] DEBUG -- : Device ram5 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.662871 #9022] DEBUG -- : Getting udev properties for device: ram6
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.664265 #9022] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56477", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.664291 #9022] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.664327 #9022] DEBUG -- : Device ram6 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.664363 #9022] DEBUG -- : Getting udev properties for device: ram7
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.665730 #9022] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56743", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.665754 #9022] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.665786 #9022] DEBUG -- : Device ram7 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.665812 #9022] DEBUG -- : Getting udev properties for device: ram8
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.672405 #9022] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57069", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.672431 #9022] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.672472 #9022] DEBUG -- : Device ram8 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.672491 #9022] DEBUG -- : Getting udev properties for device: ram9
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.673978 #9022] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57382", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.674002 #9022] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.674040 #9022] DEBUG -- : Device ram9 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.674059 #9022] DEBUG -- : Getting udev properties for device: loop0
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.675459 #9022] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50856", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.675486 #9022] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.675523 #9022] DEBUG -- : Device loop0 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.675542 #9022] DEBUG -- : Getting udev properties for device: loop1
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.676904 #9022] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51064", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.676928 #9022] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.677014 #9022] DEBUG -- : Device loop1 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.677032 #9022] DEBUG -- : Getting udev properties for device: loop2
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.678372 #9022] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51199", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.678397 #9022] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.678429 #9022] DEBUG -- : Device loop2 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.678477 #9022] DEBUG -- : Getting udev properties for device: loop3
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.679812 #9022] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51349", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.679836 #9022] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.679867 #9022] DEBUG -- : Device loop3 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.679891 #9022] DEBUG -- : Getting udev properties for device: loop4
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.681237 #9022] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51487", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.681264 #9022] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.681294 #9022] DEBUG -- : Device loop4 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.681312 #9022] DEBUG -- : Getting udev properties for device: loop5
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.682691 #9022] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51680", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.682715 #9022] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.682754 #9022] DEBUG -- : Device loop5 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.682773 #9022] DEBUG -- : Getting udev properties for device: loop6
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.684161 #9022] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51913", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.684186 #9022] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.684224 #9022] DEBUG -- : Device loop6 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.684244 #9022] DEBUG -- : Getting udev properties for device: loop7
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.685608 #9022] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52309", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.685632 #9022] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.685670 #9022] DEBUG -- : Device loop7 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.685689 #9022] DEBUG -- : Getting udev properties for device: ram10
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.687024 #9022] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53019", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.687081 #9022] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.687123 #9022] DEBUG -- : Device ram10 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.687141 #9022] DEBUG -- : Getting udev properties for device: ram11
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.688518 #9022] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53118", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.688543 #9022] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.688627 #9022] DEBUG -- : Device ram11 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.688646 #9022] DEBUG -- : Getting udev properties for device: ram12
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.690004 #9022] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53394", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.690029 #9022] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.690058 #9022] DEBUG -- : Device ram12 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.690077 #9022] DEBUG -- : Getting udev properties for device: ram13
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.691435 #9022] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53659", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.691461 #9022] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.691491 #9022] DEBUG -- : Device ram13 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.691511 #9022] DEBUG -- : Getting udev properties for device: ram14
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.692849 #9022] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54187", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.692873 #9022] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.692907 #9022] DEBUG -- : Device ram14 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.692925 #9022] DEBUG -- : Getting udev properties for device: ram15
Sep 13 18:10:15 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694288 #9022] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54462", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694313 #9022] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694345 #9022] DEBUG -- : Device ram15 removable parameter: "0"
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694378 #9022] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694392 #9022] DEBUG -- : Block device seems to be physical data storage: sda
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694426 #9022] DEBUG -- : Found block device: dm-0
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694451 #9022] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694491 #9022] DEBUG -- : Found block device: dm-1
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694501 #9022] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694510 #9022] DEBUG -- : Found block device: dm-2
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694523 #9022] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694531 #9022] DEBUG -- : Found block device: dm-3
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694541 #9022] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694548 #9022] DEBUG -- : Found block device: dm-4
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694558 #9022] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694566 #9022] DEBUG -- : Found block device: dm-5
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694575 #9022] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694607 #9022] DEBUG -- : Found block device: dm-6
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694617 #9022] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694625 #9022] DEBUG -- : Found block device: ram0
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694634 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694642 #9022] DEBUG -- : Found block device: ram1
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694651 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694659 #9022] DEBUG -- : Found block device: ram2
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694668 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694676 #9022] DEBUG -- : Found block device: ram3
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694685 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694715 #9022] DEBUG -- : Found block device: ram4
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694725 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694732 #9022] DEBUG -- : Found block device: ram5
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694741 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694749 #9022] DEBUG -- : Found block device: ram6
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694759 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694766 #9022] DEBUG -- : Found block device: ram7
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694774 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694783 #9022] DEBUG -- : Found block device: ram8
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694793 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694834 #9022] DEBUG -- : Found block device: ram9
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694844 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694852 #9022] DEBUG -- : Found block device: loop0
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694861 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694869 #9022] DEBUG -- : Found block device: loop1
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694879 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694887 #9022] DEBUG -- : Found block device: loop2
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694896 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694904 #9022] DEBUG -- : Found block device: loop3
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694950 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694959 #9022] DEBUG -- : Found block device: loop4
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694968 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694976 #9022] DEBUG -- : Found block device: loop5
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694985 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.694993 #9022] DEBUG -- : Found block device: loop6
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695003 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695011 #9022] DEBUG -- : Found block device: loop7
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695020 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695064 #9022] DEBUG -- : Found block device: ram10
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695074 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695082 #9022] DEBUG -- : Found block device: ram11
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695091 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695099 #9022] DEBUG -- : Found block device: ram12
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695108 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695115 #9022] DEBUG -- : Found block device: ram13
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695124 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695132 #9022] DEBUG -- : Found block device: ram14
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695180 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695189 #9022] DEBUG -- : Found block device: ram15
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695199 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.695227 #9022] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.795594 #9022] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Sep 13 18:10:15 node-1 nailgun-agent: D, [2016-09-13T18:10:15.795663 #9022] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep 13 18:10:16 node-1 puppet-user[12520]: (Scope(Class[main])) MODULAR: sync_time
Sep 13 18:10:16 node-1 puppet-user[12520]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 13 18:10:16 node-1 ntpdate[13112]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 13 18:10:22 node-1 ntpdate[13112]: adjust time server 10.20.0.2 offset 0.001987 sec
Sep 13 18:10:22 node-1 puppet-user[12520]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 13 18:10:22 node-1 puppet-user[12520]: Finished catalog run in 6.18 seconds
Sep 13 18:10:27 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707031 #9022] DEBUG -- : Trying to find block devices
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707145 #9022] DEBUG -- : Found block device: sda
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707217 #9022] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707244 #9022] DEBUG -- : Block device seems to be physical data storage: sda
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707268 #9022] DEBUG -- : Found block device: dm-0
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707293 #9022] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707305 #9022] DEBUG -- : Found block device: dm-1
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707318 #9022] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707327 #9022] DEBUG -- : Found block device: dm-2
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707339 #9022] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707350 #9022] DEBUG -- : Found block device: dm-3
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707362 #9022] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707371 #9022] DEBUG -- : Found block device: dm-4
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707418 #9022] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707428 #9022] DEBUG -- : Found block device: dm-5
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707440 #9022] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707449 #9022] DEBUG -- : Found block device: dm-6
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707460 #9022] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707469 #9022] DEBUG -- : Found block device: ram0
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707480 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707489 #9022] DEBUG -- : Found block device: ram1
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707499 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707539 #9022] DEBUG -- : Found block device: ram2
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707551 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707560 #9022] DEBUG -- : Found block device: ram3
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707571 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707582 #9022] DEBUG -- : Found block device: ram4
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707592 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707600 #9022] DEBUG -- : Found block device: ram5
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707610 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707644 #9022] DEBUG -- : Found block device: ram6
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707655 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707665 #9022] DEBUG -- : Found block device: ram7
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707676 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707685 #9022] DEBUG -- : Found block device: ram8
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707695 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707704 #9022] DEBUG -- : Found block device: ram9
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707743 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707752 #9022] DEBUG -- : Found block device: loop0
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707763 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707771 #9022] DEBUG -- : Found block device: loop1
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707782 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707791 #9022] DEBUG -- : Found block device: loop2
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707801 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707809 #9022] DEBUG -- : Found block device: loop3
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707820 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707829 #9022] DEBUG -- : Found block device: loop4
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707904 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707916 #9022] DEBUG -- : Found block device: loop5
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707927 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707937 #9022] DEBUG -- : Found block device: loop6
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707949 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707957 #9022] DEBUG -- : Found block device: loop7
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707967 #9022] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707976 #9022] DEBUG -- : Found block device: ram10
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707987 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.707995 #9022] DEBUG -- : Found block device: ram11
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.708045 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.708056 #9022] DEBUG -- : Found block device: ram12
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.708067 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.708075 #9022] DEBUG -- : Found block device: ram13
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.708086 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.708095 #9022] DEBUG -- : Found block device: ram14
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.708106 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.708115 #9022] DEBUG -- : Found block device: ram15
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.708125 #9022] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.708208 #9022] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Sep 13 18:10:27 node-1 nailgun-agent: D, [2016-09-13T18:10:27.875468 #9022] DEBUG -- : Response: status: 200 body: {"id": 1}
Sep 13 18:10:27 node-1 nailgun-agent: I, [2016-09-13T18:10:27.875741 #9022]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 13 18:10:28 node-1 puppet-user[13453]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 13 18:10:28 node-1 puppet-user[13453]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Sep 13 18:10:28 node-1 puppet-user[13453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 13 18:10:28 node-1 puppet-user[13453]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Sep 13 18:10:28 node-1 puppet-user[13453]: Finished catalog run in 0.08 seconds
Sep 13 18:10:29 node-1 puppet-user[14029]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 13 18:10:31 node-1 puppet-user[14029]: Compiled catalog for node-1.domain.tld in environment production in 1.29 seconds
Sep 13 18:10:31 node-1 puppet-user[14029]: (/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
Sep 13 18:10:31 node-1 puppet-user[14029]: (/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
Sep 13 18:10:31 node-1 puppet-user[14029]: (/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
Sep 13 18:10:31 node-1 puppet-user[14029]: (/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
Sep 13 18:10:31 node-1 puppet-user[14029]: (/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
Sep 13 18:10:31 node-1 puppet-user[14029]: (/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
Sep 13 18:10:31 node-1 puppet-user[14029]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 13 18:10:31 node-1 puppet-user[14029]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 13 18:10:31 node-1 puppet-user[14029]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 13 18:10:31 node-1 puppet-user[14029]: (/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
Sep 13 18:10:31 node-1 puppet-user[14029]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 13 18:10:31 node-1 puppet-user[14029]: (/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
Sep 13 18:10:31 node-1 puppet-user[14029]: (/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
Sep 13 18:10:31 node-1 puppet-user[14029]: (/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
Sep 13 18:10:31 node-1 puppet-user[14029]: (/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
Sep 13 18:10:31 node-1 puppet-user[14029]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 13 18:10:42 node-1 kernel: [   94.555510] init: plymouth-upstart-bridge main process ended, respawning
Sep 13 18:10:43 node-1 puppet-agent[8976]: Could not run: SIGTERM
Sep 13 18:10:43 node-1 kernel: [   94.842327] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 13 18:10:43 node-1 ec2: 
Sep 13 18:10:43 node-1 ec2: #############################################################
Sep 13 18:10:43 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 13 18:10:43 node-1 ec2: 1024 20:85:24:04:9f:47:6e:31:e1:a9:f4:57:70:bc:99:1b  root@node-1.domain.tld (DSA)
Sep 13 18:10:43 node-1 ec2: 256 3a:9d:4c:31:48:85:3f:41:f0:04:e8:96:9c:2d:0c:98  root@node-1.domain.tld (ECDSA)
Sep 13 18:10:43 node-1 ec2: 256 01:4f:54:5a:16:c5:d9:b6:8c:e4:c0:73:d6:84:4a:99  root@node-1.domain.tld (ED25519)
Sep 13 18:10:43 node-1 ec2: 2048 b1:ca:c2:df:b5:58:94:de:04:c3:61:1b:70:33:2d:31  root@node-1.domain.tld (RSA)
Sep 13 18:10:43 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 13 18:10:43 node-1 ec2: #############################################################
Sep 13 18:10:48 node-1 puppet-user[14029]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Sep 13 18:10:48 node-1 puppet-user[14029]: Finished catalog run in 16.75 seconds
Sep 13 18:10:50 node-1 puppet-user[15426]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 13 18:10:50 node-1 puppet-user[15426]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Sep 13 18:10:55 node-1 puppet-user[15426]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 13 18:11:01 node-1 CRON[16679]: (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")
Sep 13 18:11:26 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 13 18:11:26 node-1 nailgun-agent: I, [2016-09-13T18:11:26.068894 #16682]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 13 18:11:28 node-1 puppet-user[15426]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 13 18:11:28 node-1 puppet-user[15426]: Finished catalog run in 38.41 seconds
Sep 13 18:11:30 node-1 puppet-user[18122]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 13 18:11:31 node-1 puppet-user[18122]: Compiled catalog for node-1.domain.tld in environment production in 0.55 seconds
Sep 13 18:11:31 node-1 puppet-user[18122]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 13 18:11:31 node-1 puppet-user[18122]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 13 18:11:31 node-1 puppet-user[18122]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 13 18:11:31 node-1 puppet-user[18122]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 13 18:11:31 node-1 puppet-user[18122]: Finished catalog run in 0.12 seconds
Sep 13 18:11:33 node-1 puppet-user[18582]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 13 18:11:34 node-1 puppet-user[18582]: Compiled catalog for node-1.domain.tld in environment production in 0.93 seconds
Sep 13 18:11:34 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 13 18:11:34 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 13 18:11:34 node-1 crontab[19032]: (root) LIST (root)
Sep 13 18:11:34 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 13 18:11:34 node-1 crontab[19036]: (root) REPLACE (root)
Sep 13 18:11:36 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/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
Sep 13 18:11:38 node-1 puppet-user[18582]: (/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
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/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
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/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
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/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
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 13 18:11:38 node-1 puppet-user[18582]: (/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
Sep 13 18:11:38 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 13 18:11:38 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 13 18:11:39 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 13 18:11:39 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 13 18:11:39 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:39 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 13 18:11:39 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 13 18:11:39 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 13 18:11:39 node-1 puppet-user[18582]: (/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
Sep 13 18:11:39 node-1 nailgun-agent: I, [2016-09-13T18:11:39.138323 #16682]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 13 18:11:39 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 13 18:11:39 node-1 puppet-user[18582]: (/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
Sep 13 18:11:39 node-1 puppet-user[18582]: (/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
Sep 13 18:11:39 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 13 18:11:39 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 13 18:11:39 node-1 puppet-user[18582]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 13 18:11:39 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8427" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:39 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 13 18:11:41 node-1 multipathd: uevent trigger error
<27>Sep 13 18:11:41 node-1 multipathd: uevent trigger error
<27>Sep 13 18:11:41 node-1 multipathd: uevent trigger error
<27>Sep 13 18:11:41 node-1 multipathd: uevent trigger error
<27>Sep 13 18:11:41 node-1 multipathd: uevent trigger error
<27>Sep 13 18:11:41 node-1 multipathd: uevent trigger error
<27>Sep 13 18:11:41 node-1 multipathd: uevent trigger error
<27>Sep 13 18:12:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:12:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:12:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:12:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:12:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:12:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:12:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:12:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:12:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:12:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:05 node-1 ntpdate[30605]: no servers can be used, exiting
<27>Sep 13 18:13:05 node-1 ntpdate[30855]: no servers can be used, exiting
<27>Sep 13 18:13:37 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:37 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:37 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:37 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:40 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:40 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:40 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:40 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:13:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:14:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:14:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:14:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:14:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:14:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:08 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 13 18:15:08 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 13 18:15:14 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 13 18:15:14 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 13 18:15:20 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 13 18:15:25 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 13 18:15:25 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 13 18:15:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:46 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:46 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:46 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:46 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:46 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:46 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:52 node-1 multipathd: uevent trigger error
<129>Sep 13 18:15:54 node-1 haproxy[20588]: 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>Sep 13 18:15:54 node-1 haproxy[20588]: Backup Server mysqld/node-4 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>Sep 13 18:15:55 node-1 haproxy[20594]: 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>Sep 13 18:15:55 node-1 haproxy[20594]: proxy mysqld has no server available!
<27>Sep 13 18:15:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:15:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:01 node-1 multipathd: uevent trigger error
<129>Sep 13 18:16:03 node-1 haproxy[23259]: 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>Sep 13 18:16:04 node-1 haproxy[23263]: Backup Server mysqld/node-4 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>Sep 13 18:16:04 node-1 haproxy[23263]: 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>Sep 13 18:16:04 node-1 haproxy[23263]: proxy mysqld has no server available!
<129>Sep 13 18:16:04 node-1 haproxy[23263]: 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>Sep 13 18:16:04 node-1 haproxy[23263]: Server object-storage/node-4 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>Sep 13 18:16:05 node-1 haproxy[23263]: 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>Sep 13 18:16:05 node-1 haproxy[23263]: proxy object-storage has no server available!
<27>Sep 13 18:16:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:07 node-1 multipathd: uevent trigger error
<129>Sep 13 18:16:09 node-1 haproxy[24876]: 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>Sep 13 18:16:09 node-1 haproxy[24876]: Server neutron/node-4 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>Sep 13 18:16:09 node-1 haproxy[24876]: 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>Sep 13 18:16:09 node-1 haproxy[24876]: proxy neutron has no server available!
<129>Sep 13 18:16:09 node-1 haproxy[24876]: 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>Sep 13 18:16:09 node-1 haproxy[24876]: Backup Server mysqld/node-4 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>Sep 13 18:16:10 node-1 haproxy[24880]: 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>Sep 13 18:16:10 node-1 haproxy[24880]: proxy mysqld has no server available!
<129>Sep 13 18:16:10 node-1 haproxy[24880]: 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>Sep 13 18:16:10 node-1 haproxy[24880]: Server object-storage/node-4 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>Sep 13 18:16:10 node-1 haproxy[24880]: 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>Sep 13 18:16:10 node-1 haproxy[24880]: proxy object-storage has no server available!
<27>Sep 13 18:16:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:12 node-1 multipathd: uevent trigger error
<129>Sep 13 18:16:14 node-1 haproxy[26278]: 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>Sep 13 18:16:14 node-1 haproxy[26278]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:14 node-1 haproxy[26278]: 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>Sep 13 18:16:14 node-1 haproxy[26278]: proxy keystone-1 has no server available!
<129>Sep 13 18:16:14 node-1 haproxy[26278]: 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>Sep 13 18:16:15 node-1 haproxy[26282]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:15 node-1 haproxy[26282]: 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>Sep 13 18:16:15 node-1 haproxy[26282]: proxy keystone-2 has no server available!
<129>Sep 13 18:16:15 node-1 haproxy[26282]: 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>Sep 13 18:16:15 node-1 haproxy[26282]: Server neutron/node-4 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>Sep 13 18:16:15 node-1 haproxy[26282]: 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>Sep 13 18:16:15 node-1 haproxy[26282]: proxy neutron has no server available!
<129>Sep 13 18:16:15 node-1 haproxy[26282]: 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>Sep 13 18:16:15 node-1 haproxy[26282]: Backup Server mysqld/node-4 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>Sep 13 18:16:15 node-1 haproxy[26282]: 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>Sep 13 18:16:15 node-1 haproxy[26282]: proxy mysqld has no server available!
<129>Sep 13 18:16:15 node-1 haproxy[26282]: 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>Sep 13 18:16:16 node-1 haproxy[26282]: Server object-storage/node-4 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>Sep 13 18:16:16 node-1 haproxy[26282]: 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>Sep 13 18:16:16 node-1 haproxy[26282]: proxy object-storage has no server available!
<27>Sep 13 18:16:17 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:17 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:17 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:17 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:17 node-1 multipathd: uevent trigger error
<129>Sep 13 18:16:20 node-1 haproxy[27828]: 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>Sep 13 18:16:20 node-1 haproxy[27828]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:20 node-1 haproxy[27828]: 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>Sep 13 18:16:20 node-1 haproxy[27828]: proxy keystone-1 has no server available!
<129>Sep 13 18:16:20 node-1 haproxy[27828]: 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>Sep 13 18:16:20 node-1 haproxy[27828]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:20 node-1 haproxy[27828]: 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>Sep 13 18:16:20 node-1 haproxy[27828]: proxy keystone-2 has no server available!
<129>Sep 13 18:16:20 node-1 haproxy[27828]: 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>Sep 13 18:16:20 node-1 haproxy[27828]: Server neutron/node-4 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>Sep 13 18:16:20 node-1 haproxy[27828]: 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>Sep 13 18:16:20 node-1 haproxy[27828]: proxy neutron has no server available!
<129>Sep 13 18:16:20 node-1 haproxy[27828]: 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>Sep 13 18:16:21 node-1 haproxy[27832]: Backup Server mysqld/node-4 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>Sep 13 18:16:21 node-1 haproxy[27832]: 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>Sep 13 18:16:21 node-1 haproxy[27832]: proxy mysqld has no server available!
<129>Sep 13 18:16:21 node-1 haproxy[27832]: 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>Sep 13 18:16:21 node-1 haproxy[27832]: Server object-storage/node-4 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>Sep 13 18:16:21 node-1 haproxy[27832]: 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>Sep 13 18:16:21 node-1 haproxy[27832]: proxy object-storage has no server available!
<129>Sep 13 18:16:21 node-1 haproxy[27832]: 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>Sep 13 18:16:21 node-1 haproxy[27832]: Server aodh/node-4 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>Sep 13 18:16:21 node-1 haproxy[27832]: 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>Sep 13 18:16:21 node-1 haproxy[27832]: proxy aodh has no server available!
<27>Sep 13 18:16:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:23 node-1 multipathd: uevent trigger error
<129>Sep 13 18:16:25 node-1 haproxy[29197]: 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>Sep 13 18:16:25 node-1 haproxy[29197]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:25 node-1 haproxy[29197]: 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>Sep 13 18:16:25 node-1 haproxy[29197]: proxy keystone-1 has no server available!
<129>Sep 13 18:16:25 node-1 haproxy[29197]: 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>Sep 13 18:16:25 node-1 haproxy[29197]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:25 node-1 haproxy[29197]: 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>Sep 13 18:16:25 node-1 haproxy[29197]: proxy keystone-2 has no server available!
<129>Sep 13 18:16:25 node-1 haproxy[29197]: 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>Sep 13 18:16:26 node-1 haproxy[29201]: Server neutron/node-4 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>Sep 13 18:16:26 node-1 haproxy[29201]: 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>Sep 13 18:16:26 node-1 haproxy[29201]: proxy neutron has no server available!
<129>Sep 13 18:16:26 node-1 haproxy[29201]: 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>Sep 13 18:16:26 node-1 haproxy[29201]: Backup Server mysqld/node-4 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>Sep 13 18:16:26 node-1 haproxy[29201]: 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>Sep 13 18:16:26 node-1 haproxy[29201]: proxy mysqld has no server available!
<129>Sep 13 18:16:26 node-1 haproxy[29201]: 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>Sep 13 18:16:26 node-1 haproxy[29201]: Server object-storage/node-4 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>Sep 13 18:16:26 node-1 haproxy[29201]: 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>Sep 13 18:16:26 node-1 haproxy[29201]: proxy object-storage has no server available!
<129>Sep 13 18:16:26 node-1 haproxy[29201]: 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>Sep 13 18:16:26 node-1 haproxy[29201]: Server aodh/node-4 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>Sep 13 18:16:26 node-1 haproxy[29201]: 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>Sep 13 18:16:26 node-1 haproxy[29201]: proxy aodh has no server available!
<129>Sep 13 18:16:27 node-1 haproxy[29201]: 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>Sep 13 18:16:27 node-1 haproxy[29201]: Server ceilometer/node-4 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>Sep 13 18:16:27 node-1 haproxy[29201]: 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>Sep 13 18:16:27 node-1 haproxy[29201]: proxy ceilometer has no server available!
<27>Sep 13 18:16:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:28 node-1 multipathd: uevent trigger error
<129>Sep 13 18:16:30 node-1 haproxy[30589]: 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>Sep 13 18:16:30 node-1 haproxy[30589]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:31 node-1 haproxy[30593]: 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>Sep 13 18:16:31 node-1 haproxy[30593]: proxy keystone-1 has no server available!
<129>Sep 13 18:16:31 node-1 haproxy[30593]: 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>Sep 13 18:16:31 node-1 haproxy[30593]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:31 node-1 haproxy[30593]: 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>Sep 13 18:16:31 node-1 haproxy[30593]: proxy keystone-2 has no server available!
<129>Sep 13 18:16:31 node-1 haproxy[30593]: 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>Sep 13 18:16:31 node-1 haproxy[30593]: Server neutron/node-4 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>Sep 13 18:16:31 node-1 haproxy[30593]: 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>Sep 13 18:16:31 node-1 haproxy[30593]: proxy neutron has no server available!
<129>Sep 13 18:16:31 node-1 haproxy[30593]: 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>Sep 13 18:16:31 node-1 haproxy[30593]: Backup Server mysqld/node-4 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>Sep 13 18:16:31 node-1 haproxy[30593]: 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>Sep 13 18:16:31 node-1 haproxy[30593]: proxy mysqld has no server available!
<129>Sep 13 18:16:31 node-1 haproxy[30593]: 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>Sep 13 18:16:32 node-1 haproxy[30593]: Server object-storage/node-4 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>Sep 13 18:16:32 node-1 haproxy[30593]: 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>Sep 13 18:16:32 node-1 haproxy[30593]: proxy object-storage has no server available!
<129>Sep 13 18:16:32 node-1 haproxy[30593]: 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>Sep 13 18:16:32 node-1 haproxy[30593]: Server aodh/node-4 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>Sep 13 18:16:32 node-1 haproxy[30593]: 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>Sep 13 18:16:32 node-1 haproxy[30593]: proxy aodh has no server available!
<129>Sep 13 18:16:32 node-1 haproxy[30593]: 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>Sep 13 18:16:32 node-1 haproxy[30593]: Server ceilometer/node-4 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>Sep 13 18:16:32 node-1 haproxy[30593]: 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>Sep 13 18:16:32 node-1 haproxy[30593]: proxy ceilometer has no server available!
<27>Sep 13 18:16:34 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:34 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:34 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:34 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:34 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:34 node-1 multipathd: uevent trigger error
<129>Sep 13 18:16:36 node-1 haproxy[31942]: 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>Sep 13 18:16:36 node-1 haproxy[31942]: 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>Sep 13 18:16:36 node-1 haproxy[31942]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:36 node-1 haproxy[31942]: 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>Sep 13 18:16:36 node-1 haproxy[31942]: proxy keystone-1 has no server available!
<129>Sep 13 18:16:36 node-1 haproxy[31942]: 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>Sep 13 18:16:36 node-1 haproxy[31942]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:36 node-1 haproxy[31942]: 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>Sep 13 18:16:36 node-1 haproxy[31942]: proxy keystone-2 has no server available!
<129>Sep 13 18:16:36 node-1 haproxy[31942]: 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>Sep 13 18:16:37 node-1 haproxy[31946]: Server neutron/node-4 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>Sep 13 18:16:37 node-1 haproxy[31946]: 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>Sep 13 18:16:37 node-1 haproxy[31946]: proxy neutron has no server available!
<129>Sep 13 18:16:37 node-1 haproxy[31946]: 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>Sep 13 18:16:37 node-1 haproxy[31946]: Backup Server mysqld/node-4 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>Sep 13 18:16:37 node-1 haproxy[31946]: 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>Sep 13 18:16:37 node-1 haproxy[31946]: proxy mysqld has no server available!
<129>Sep 13 18:16:37 node-1 haproxy[31946]: 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>Sep 13 18:16:37 node-1 haproxy[31946]: Server object-storage/node-4 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>Sep 13 18:16:37 node-1 haproxy[31946]: 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>Sep 13 18:16:37 node-1 haproxy[31946]: proxy object-storage has no server available!
<129>Sep 13 18:16:37 node-1 haproxy[31946]: 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>Sep 13 18:16:37 node-1 haproxy[31946]: Server aodh/node-4 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>Sep 13 18:16:37 node-1 haproxy[31946]: 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>Sep 13 18:16:37 node-1 haproxy[31946]: proxy aodh has no server available!
<129>Sep 13 18:16:37 node-1 haproxy[31946]: 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>Sep 13 18:16:37 node-1 haproxy[31946]: Server ceilometer/node-4 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>Sep 13 18:16:38 node-1 haproxy[31946]: 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>Sep 13 18:16:38 node-1 haproxy[31946]: proxy ceilometer has no server available!
<27>Sep 13 18:16:39 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:39 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:39 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:39 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:39 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:39 node-1 multipathd: uevent trigger error
<129>Sep 13 18:16:42 node-1 haproxy[966]: 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>Sep 13 18:16:42 node-1 haproxy[966]: 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>Sep 13 18:16:42 node-1 haproxy[966]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:42 node-1 haproxy[966]: 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>Sep 13 18:16:42 node-1 haproxy[966]: proxy keystone-1 has no server available!
<129>Sep 13 18:16:42 node-1 haproxy[966]: 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>Sep 13 18:16:42 node-1 haproxy[966]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:42 node-1 haproxy[966]: 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>Sep 13 18:16:42 node-1 haproxy[966]: proxy keystone-2 has no server available!
<129>Sep 13 18:16:42 node-1 haproxy[966]: 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>Sep 13 18:16:42 node-1 haproxy[966]: Server glance-api/node-4 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>Sep 13 18:16:42 node-1 haproxy[966]: 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>Sep 13 18:16:42 node-1 haproxy[966]: proxy glance-api has no server available!
<129>Sep 13 18:16:42 node-1 haproxy[966]: 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>Sep 13 18:16:42 node-1 haproxy[966]: Server glance-glare/node-4 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>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: proxy glance-glare has no server available!
<129>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: Server neutron/node-4 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>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: proxy neutron has no server available!
<129>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: Server glance-registry/node-4 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>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: proxy glance-registry has no server available!
<129>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: Backup Server mysqld/node-4 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>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: proxy mysqld has no server available!
<129>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: Server object-storage/node-4 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>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: proxy object-storage has no server available!
<129>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: Server aodh/node-4 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>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: proxy aodh has no server available!
<129>Sep 13 18:16:43 node-1 haproxy[970]: 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>Sep 13 18:16:43 node-1 haproxy[970]: Server ceilometer/node-4 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>Sep 13 18:16:44 node-1 haproxy[970]: 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>Sep 13 18:16:44 node-1 haproxy[970]: proxy ceilometer has no server available!
<27>Sep 13 18:16:45 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:45 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:45 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:45 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:45 node-1 multipathd: uevent trigger error
<129>Sep 13 18:16:48 node-1 haproxy[2378]: 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>Sep 13 18:16:48 node-1 haproxy[2378]: 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>Sep 13 18:16:48 node-1 haproxy[2378]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:48 node-1 haproxy[2378]: 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>Sep 13 18:16:48 node-1 haproxy[2378]: proxy keystone-1 has no server available!
<129>Sep 13 18:16:48 node-1 haproxy[2378]: 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>Sep 13 18:16:48 node-1 haproxy[2378]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:48 node-1 haproxy[2378]: 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>Sep 13 18:16:48 node-1 haproxy[2378]: proxy keystone-2 has no server available!
<129>Sep 13 18:16:48 node-1 haproxy[2378]: 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>Sep 13 18:16:48 node-1 haproxy[2378]: Server nova-api/node-4 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>Sep 13 18:16:48 node-1 haproxy[2378]: 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>Sep 13 18:16:48 node-1 haproxy[2378]: proxy nova-api has no server available!
<129>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: Server nova-metadata-api/node-4 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>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: proxy nova-metadata-api has no server available!
<129>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: Server glance-api/node-4 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>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: proxy glance-api has no server available!
<129>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: Server glance-glare/node-4 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>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: proxy glance-glare has no server available!
<129>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: Server neutron/node-4 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>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: proxy neutron has no server available!
<129>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: Server glance-registry/node-4 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>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: proxy glance-registry has no server available!
<129>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: Backup Server mysqld/node-4 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>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: proxy mysqld has no server available!
<129>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: Server object-storage/node-4 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>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:49 node-1 haproxy[2382]: proxy object-storage has no server available!
<129>Sep 13 18:16:49 node-1 haproxy[2382]: 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>Sep 13 18:16:50 node-1 haproxy[2382]: Server aodh/node-4 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>Sep 13 18:16:50 node-1 haproxy[2382]: 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>Sep 13 18:16:50 node-1 haproxy[2382]: proxy aodh has no server available!
<129>Sep 13 18:16:50 node-1 haproxy[2382]: 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>Sep 13 18:16:50 node-1 haproxy[2382]: Server ceilometer/node-4 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>Sep 13 18:16:50 node-1 haproxy[2382]: 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>Sep 13 18:16:50 node-1 haproxy[2382]: proxy ceilometer has no server available!
<129>Sep 13 18:16:50 node-1 haproxy[2382]: 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>Sep 13 18:16:50 node-1 haproxy[2382]: Server nova-novncproxy/node-4 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>Sep 13 18:16:50 node-1 haproxy[2382]: 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>Sep 13 18:16:50 node-1 haproxy[2382]: proxy nova-novncproxy has no server available!
<27>Sep 13 18:16:51 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:51 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:51 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:51 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:51 node-1 multipathd: uevent trigger error
<129>Sep 13 18:16:53 node-1 haproxy[3688]: 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>Sep 13 18:16:53 node-1 haproxy[3688]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: proxy keystone-1 has no server available!
<129>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: proxy keystone-2 has no server available!
<129>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: Server nova-api/node-4 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>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: proxy nova-api has no server available!
<129>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: Server nova-metadata-api/node-4 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>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: proxy nova-metadata-api has no server available!
<129>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: Backup Server cinder-api/node-4 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>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: proxy cinder-api has no server available!
<129>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: Server glance-api/node-4 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>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: proxy glance-api has no server available!
<129>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: Server glance-glare/node-4 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>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: proxy glance-glare has no server available!
<129>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: Server neutron/node-4 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>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:54 node-1 haproxy[3692]: proxy neutron has no server available!
<129>Sep 13 18:16:54 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: Server glance-registry/node-4 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>Sep 13 18:16:55 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: proxy glance-registry has no server available!
<129>Sep 13 18:16:55 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: Backup Server mysqld/node-4 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>Sep 13 18:16:55 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: proxy mysqld has no server available!
<129>Sep 13 18:16:55 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: Server object-storage/node-4 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>Sep 13 18:16:55 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: proxy object-storage has no server available!
<129>Sep 13 18:16:55 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: Server aodh/node-4 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>Sep 13 18:16:55 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: proxy aodh has no server available!
<129>Sep 13 18:16:55 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: Server ceilometer/node-4 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>Sep 13 18:16:55 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: proxy ceilometer has no server available!
<129>Sep 13 18:16:55 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: Server nova-novncproxy/node-4 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>Sep 13 18:16:55 node-1 haproxy[3692]: 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>Sep 13 18:16:55 node-1 haproxy[3692]: proxy nova-novncproxy has no server available!
<27>Sep 13 18:16:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:16:57 node-1 multipathd: uevent trigger error
<129>Sep 13 18:16:59 node-1 haproxy[5112]: 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>Sep 13 18:16:59 node-1 haproxy[5112]: 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>Sep 13 18:16:59 node-1 haproxy[5112]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:59 node-1 haproxy[5112]: 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>Sep 13 18:16:59 node-1 haproxy[5112]: proxy keystone-1 has no server available!
<129>Sep 13 18:16:59 node-1 haproxy[5112]: 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>Sep 13 18:16:59 node-1 haproxy[5112]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:59 node-1 haproxy[5112]: 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>Sep 13 18:16:59 node-1 haproxy[5112]: proxy keystone-2 has no server available!
<129>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: Server nova-api/node-4 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>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: proxy nova-api has no server available!
<129>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: Server nova-metadata-api/node-4 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>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: proxy nova-metadata-api has no server available!
<129>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: Backup Server cinder-api/node-4 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>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: proxy cinder-api has no server available!
<129>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: Server glance-api/node-4 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>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: proxy glance-api has no server available!
<129>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: Server glance-glare/node-4 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>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: proxy glance-glare has no server available!
<129>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: Server neutron/node-4 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>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: proxy neutron has no server available!
<129>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: Server glance-registry/node-4 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>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: proxy glance-registry has no server available!
<129>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: Backup Server mysqld/node-4 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>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: proxy mysqld has no server available!
<129>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: Server object-storage/node-4 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>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:00 node-1 haproxy[5117]: proxy object-storage has no server available!
<129>Sep 13 18:17:00 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: Server aodh/node-4 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>Sep 13 18:17:01 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: proxy aodh has no server available!
<129>Sep 13 18:17:01 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: Server ceilometer/node-4 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>Sep 13 18:17:01 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: proxy ceilometer has no server available!
<129>Sep 13 18:17:01 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: Server heat-api/node-4 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>Sep 13 18:17:01 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: proxy heat-api has no server available!
<129>Sep 13 18:17:01 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: Server heat-api-cfn/node-4 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>Sep 13 18:17:01 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: proxy heat-api-cfn has no server available!
<129>Sep 13 18:17:01 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: Server heat-api-cloudwatch/node-4 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>Sep 13 18:17:01 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: proxy heat-api-cloudwatch has no server available!
<129>Sep 13 18:17:01 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: Server nova-novncproxy/node-4 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>Sep 13 18:17:01 node-1 haproxy[5117]: 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>Sep 13 18:17:01 node-1 haproxy[5117]: proxy nova-novncproxy has no server available!
<27>Sep 13 18:17:03 node-1 multipathd: uevent trigger error
<27>Sep 13 18:17:03 node-1 multipathd: uevent trigger error
<27>Sep 13 18:17:03 node-1 multipathd: uevent trigger error
<27>Sep 13 18:17:03 node-1 multipathd: uevent trigger error
<27>Sep 13 18:17:03 node-1 multipathd: uevent trigger error
<27>Sep 13 18:17:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:17:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:17:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:17:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:17:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:17:16 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 13 18:17:42 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>Sep 13 18:17:44 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 13 18:18:13 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 18:18:16 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 13 18:18:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:18:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:18:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:18:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:18:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:18:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:18:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:20:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:20:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:20:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:20:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:20:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:20:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:15 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 13 18:21:20 node-1 apache2_error [Tue Sep 13 18:21:15.747498 2016] [mpm_event:notice] [pid 16256:tid 140238295152512] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 13 18:21:20 node-1 apache2_error [Tue Sep 13 18:21:15.747634 2016] [core:notice] [pid 16256:tid 140238295152512] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 13 18:21:20 node-1 apache2_error [Tue Sep 13 18:21:19.051608 2016] [mpm_event:notice] [pid 16256:tid 140238295152512] AH00491: caught SIGTERM, shutting down
<43>Sep 13 18:21:20 node-1 apache2_error [Tue Sep 13 18:21:20.142324 2016] [mpm_worker:notice] [pid 16638:tid 139810032732032] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 13 18:21:20 node-1 apache2_error [Tue Sep 13 18:21:20.142398 2016] [core:notice] [pid 16638:tid 139810032732032] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 18:21:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:29 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:29 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:29 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:29 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:29 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:29 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:21:33 node-1 multipathd: uevent trigger error
<43>Sep 13 18:22:50 node-1 apache2_error [Tue Sep 13 18:22:47.482010 2016] [mpm_worker:notice] [pid 16638:tid 139810032732032] AH00295: caught SIGTERM, shutting down
<43>Sep 13 18:22:50 node-1 apache2_error [Tue Sep 13 18:22:48.241848 2016] [mpm_worker:notice] [pid 1033:tid 139634390030208] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 18:22:50 node-1 apache2_error [Tue Sep 13 18:22:48.241898 2016] [core:notice] [pid 1033:tid 139634390030208] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 13 18:23:40 node-1 apache2_error [Tue Sep 13 18:23:33.886170 2016] [mpm_worker:notice] [pid 1033:tid 139634390030208] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 18:23:40 node-1 apache2_error [Tue Sep 13 18:23:34.078905 2016] [mpm_worker:warn] [pid 1033:tid 139634390030208] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 18:23:40 node-1 apache2_error [Tue Sep 13 18:23:34.081735 2016] [mpm_worker:notice] [pid 1033:tid 139634390030208] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 18:23:40 node-1 apache2_error [Tue Sep 13 18:23:34.081749 2016] [core:notice] [pid 1033:tid 139634390030208] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 18:24:16 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 18:24:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:38 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:38 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:38 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:38 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:38 node-1 multipathd: uevent trigger error
<27>Sep 13 18:24:38 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:09 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:09 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:09 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:09 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:09 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:56 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:56 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:56 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:56 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:56 node-1 multipathd: uevent trigger error
<27>Sep 13 18:25:56 node-1 multipathd: uevent trigger error
<27>Sep 13 18:26:11 node-1 multipathd: uevent trigger error
<27>Sep 13 18:26:11 node-1 multipathd: uevent trigger error
<27>Sep 13 18:26:11 node-1 multipathd: uevent trigger error
<27>Sep 13 18:26:11 node-1 multipathd: uevent trigger error
<27>Sep 13 18:26:11 node-1 multipathd: uevent trigger error
<27>Sep 13 18:27:05 node-1 multipathd: uevent trigger error
<27>Sep 13 18:27:05 node-1 multipathd: uevent trigger error
<27>Sep 13 18:27:05 node-1 multipathd: uevent trigger error
<27>Sep 13 18:27:05 node-1 multipathd: uevent trigger error
<27>Sep 13 18:27:05 node-1 multipathd: uevent trigger error
<27>Sep 13 18:27:17 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 18:28:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:28:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:28:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:28:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:28:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:28:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:21 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:21 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:21 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:21 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:21 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:21 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:43 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:43 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:43 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:43 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:43 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:50 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:50 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:50 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:50 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:50 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:50 node-1 multipathd: uevent trigger error
<27>Sep 13 18:29:50 node-1 multipathd: uevent trigger error
<27>Sep 13 18:30:18 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 18:32:27 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:27 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:27 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:27 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:27 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:43 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:43 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:43 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:43 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:43 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:43 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:54 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:54 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:54 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:54 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:54 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:54 node-1 multipathd: uevent trigger error
<27>Sep 13 18:32:54 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:18 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:22 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 18:33:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:33:23 node-1 multipathd: uevent trigger error
<27>Sep 13 18:34:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:34:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:34:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:34:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:34:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:34:58 node-1 multipathd: uevent trigger error
<27>Sep 13 18:34:58 node-1 multipathd: uevent trigger error
<27>Sep 13 18:34:58 node-1 multipathd: uevent trigger error
<27>Sep 13 18:34:58 node-1 multipathd: uevent trigger error
<27>Sep 13 18:34:58 node-1 multipathd: uevent trigger error
<27>Sep 13 18:34:58 node-1 multipathd: uevent trigger error
<27>Sep 13 18:35:13 node-1 multipathd: uevent trigger error
<27>Sep 13 18:35:13 node-1 multipathd: uevent trigger error
<27>Sep 13 18:35:13 node-1 multipathd: uevent trigger error
<27>Sep 13 18:35:13 node-1 multipathd: uevent trigger error
<27>Sep 13 18:35:13 node-1 multipathd: uevent trigger error
<27>Sep 13 18:35:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:35:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:35:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:35:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:35:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:35:33 node-1 multipathd: uevent trigger error
<27>Sep 13 18:36:23 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 18:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:37 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:37 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:37 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:37 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:37 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:38:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:25 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 18:39:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:36 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:36 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:36 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:36 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:36 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:39:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:40:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:40:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:40:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:40:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:40:25 node-1 multipathd: uevent trigger error
<27>Sep 13 18:41:29 node-1 multipathd: uevent trigger error
<27>Sep 13 18:41:30 node-1 multipathd: uevent trigger error
<27>Sep 13 18:41:30 node-1 multipathd: uevent trigger error
<27>Sep 13 18:41:30 node-1 multipathd: uevent trigger error
<27>Sep 13 18:41:30 node-1 multipathd: uevent trigger error
<27>Sep 13 18:41:48 node-1 multipathd: uevent trigger error
<27>Sep 13 18:41:48 node-1 multipathd: uevent trigger error
<27>Sep 13 18:41:48 node-1 multipathd: uevent trigger error
<27>Sep 13 18:41:48 node-1 multipathd: uevent trigger error
<27>Sep 13 18:41:48 node-1 multipathd: uevent trigger error
<11>Sep 13 18:42:02 node-1 liberasurecode[27762]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:02 node-1 liberasurecode[27762]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:02 node-1 liberasurecode[27762]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:02 node-1 liberasurecode[27762]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:02 node-1 liberasurecode[27800]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:02 node-1 liberasurecode[27800]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:02 node-1 liberasurecode[27800]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:02 node-1 liberasurecode[27800]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:04 node-1 liberasurecode[28245]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:04 node-1 liberasurecode[28245]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:04 node-1 liberasurecode[28245]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:04 node-1 liberasurecode[28245]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[28963]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[28963]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[28963]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[28963]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[29119]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[29119]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[29119]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[29119]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[29222]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[29222]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[29222]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:10 node-1 liberasurecode[29222]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29488]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29488]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29488]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29488]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29502]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29502]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29502]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29502]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29521]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29521]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29521]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29521]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29558]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29558]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29558]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:11 node-1 liberasurecode[29558]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:19 node-1 liberasurecode[31420]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:19 node-1 liberasurecode[31420]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:19 node-1 liberasurecode[31420]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:19 node-1 liberasurecode[31420]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 13 18:42:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 18:42:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:42:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:42:28 node-1 multipathd: uevent trigger error
<27>Sep 13 18:42:28 node-1 multipathd: uevent trigger error
<43>Sep 13 18:43:22 node-1 apache2_error [Tue Sep 13 18:43:15.178931 2016] [mpm_worker:notice] [pid 1033:tid 139634390030208] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 18:43:22 node-1 apache2_error [Tue Sep 13 18:43:15.562048 2016] [mpm_worker:warn] [pid 1033:tid 139634390030208] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 18:43:22 node-1 apache2_error [Tue Sep 13 18:43:15.566538 2016] [mpm_worker:notice] [pid 1033:tid 139634390030208] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 18:43:22 node-1 apache2_error [Tue Sep 13 18:43:15.566566 2016] [core:notice] [pid 1033:tid 139634390030208] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 18:43:56 node-1 multipathd: uevent trigger error
<27>Sep 13 18:43:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:43:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:43:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:43:57 node-1 multipathd: uevent trigger error
<43>Sep 13 18:44:02 node-1 apache2_error [Tue Sep 13 18:43:52.839045 2016] [mpm_worker:notice] [pid 1033:tid 139634390030208] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 18:44:02 node-1 apache2_error [Tue Sep 13 18:43:53.223650 2016] [mpm_worker:warn] [pid 1033:tid 139634390030208] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 18:44:02 node-1 apache2_error [Tue Sep 13 18:43:53.233201 2016] [mpm_worker:notice] [pid 1033:tid 139634390030208] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 18:44:02 node-1 apache2_error [Tue Sep 13 18:43:53.233234 2016] [core:notice] [pid 1033:tid 139634390030208] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 18:44:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:04 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:04 node-1 multipathd: uevent trigger error
<43>Sep 13 18:44:42 node-1 apache2_error [Tue Sep 13 18:44:38.328367 2016] [mpm_worker:notice] [pid 1033:tid 139634390030208] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 18:44:42 node-1 apache2_error [Tue Sep 13 18:44:38.523548 2016] [mpm_worker:warn] [pid 1033:tid 139634390030208] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 18:44:42 node-1 apache2_error [Tue Sep 13 18:44:38.531628 2016] [mpm_worker:notice] [pid 1033:tid 139634390030208] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 18:44:42 node-1 apache2_error [Tue Sep 13 18:44:38.531659 2016] [core:notice] [pid 1033:tid 139634390030208] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 18:44:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:42 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:49 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:44:55 node-1 multipathd: uevent trigger error
<11>Sep 13 18:45:02 node-1 liberasurecode[28304]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:45:02 node-1 liberasurecode[28304]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:45:02 node-1 liberasurecode[28304]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:45:02 node-1 liberasurecode[28304]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 13 18:45:11 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:11 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:11 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:11 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:11 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:28 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 13 18:45:34 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:40 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:40 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:41 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:41 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:41 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:48 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 13 18:45:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:45:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:02 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:07 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:13 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:13 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:13 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:20 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 13 18:46:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:24 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:51 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:51 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:51 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:51 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:51 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:46:55 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:08 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:08 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:08 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:08 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:08 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:15 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:15 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:15 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:15 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:15 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:20 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:20 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:20 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:20 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:20 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:32 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:47 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:47 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:47 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:47 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:47 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:52 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:47:57 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:01 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:06 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:12 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:16 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:16 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:16 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:16 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:16 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:21 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:21 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:21 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:21 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:21 node-1 multipathd: uevent trigger error
<27>Sep 13 18:48:21 node-1 multipathd: uevent trigger error
<11>Sep 13 18:50:01 node-1 liberasurecode[32434]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:50:01 node-1 liberasurecode[32434]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:50:01 node-1 liberasurecode[32434]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:50:01 node-1 liberasurecode[32434]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
