Oct 24 02:57:45 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8386" x-info="http://www.rsyslog.com"] start
Oct 24 02:57:45 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 24 02:57:45 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 24 02:57:45 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 24 02:57:45 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 24 02:57:45 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 24 02:57:45 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 24 02:57:45 node-1 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Oct 24 02:57:45 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=5c8da145-f2cb-47df-87a8-1f6d3d105cfa nomdmonddf nomdmonisw
Oct 24 02:57:45 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 24 02:57:45 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 24 02:57:45 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 24 02:57:45 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 24 02:57:45 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 24 02:57:45 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 24 02:57:45 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 24 02:57:45 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 24 02:57:45 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
Oct 24 02:57:45 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 24 02:57:45 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 24 02:57:45 node-1 kernel: [    0.000000] No AGP bridge found
Oct 24 02:57:45 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 24 02:57:45 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 24 02:57:45 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 24 02:57:45 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 24 02:57:45 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 24 02:57:45 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 24 02:57:45 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 24 02:57:45 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 24 02:57:45 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 24 02:57:45 node-1 kernel: [    0.000000]   2 disabled
Oct 24 02:57:45 node-1 kernel: [    0.000000]   3 disabled
Oct 24 02:57:45 node-1 kernel: [    0.000000]   4 disabled
Oct 24 02:57:45 node-1 kernel: [    0.000000]   5 disabled
Oct 24 02:57:45 node-1 kernel: [    0.000000]   6 disabled
Oct 24 02:57:45 node-1 kernel: [    0.000000]   7 disabled
Oct 24 02:57:45 node-1 kernel: [    0.000000]   8 disabled
Oct 24 02:57:45 node-1 kernel: [    0.000000]   9 disabled
Oct 24 02:57:45 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 24 02:57:45 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 24 02:57:45 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 24 02:57:45 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 24 02:57:45 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 24 02:57:45 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 24 02:57:45 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 24 02:57:45 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 24 02:57:45 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 24 02:57:45 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 24 02:57:45 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 24 02:57:45 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 24 02:57:45 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 24 02:57:45 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Oct 24 02:57:45 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 24 02:57:45 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 24 02:57:45 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 24 02:57:45 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 24 02:57:45 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 24 02:57:45 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 24 02:57:45 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 24 02:57:45 node-1 kernel: [    0.000000] Zone ranges:
Oct 24 02:57:45 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 24 02:57:45 node-1 kernel: [    0.000000] Early memory node ranges
Oct 24 02:57:45 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Oct 24 02:57:45 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 24 02:57:45 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 24 02:57:45 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 24 02:57:45 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Oct 24 02:57:45 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Oct 24 02:57:45 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 24 02:57:45 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 24 02:57:45 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 24 02:57:45 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 24 02:57:45 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 24 02:57:45 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 24 02:57:45 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 24 02:57:45 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 24 02:57:45 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 24 02:57:45 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 24 02:57:45 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 24 02:57:45 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 24 02:57:45 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 24 02:57:45 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 24 02:57:45 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 24 02:57:45 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 24 02:57:45 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 24 02:57:45 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 
Oct 24 02:57:45 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Oct 24 02:57:45 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 24 02:57:45 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=5c8da145-f2cb-47df-87a8-1f6d3d105cfa nomdmonddf nomdmonisw
Oct 24 02:57:45 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 24 02:57:45 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 24 02:57:45 node-1 kernel: [    0.000000] Checking aperture...
Oct 24 02:57:45 node-1 kernel: [    0.000000] No AGP bridge found
Oct 24 02:57:45 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 24 02:57:45 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 24 02:57:45 node-1 kernel: [    0.000000] Memory: 32653456K/33280636K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627180K reserved)
Oct 24 02:57:45 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 24 02:57:45 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 24 02:57:45 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 24 02:57:45 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 24 02:57:45 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 24 02:57:45 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 24 02:57:45 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 24 02:57:45 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 24 02:57:45 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 24 02:57:45 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 24 02:57:45 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 24 02:57:45 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 24 02:57:45 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 24 02:57:45 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 24 02:57:45 node-1 kernel: [    0.004000] tsc: Detected 3492.083 MHz processor
Oct 24 02:57:45 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 24 02:57:45 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.16 BogoMIPS (lpj=13968332)
Oct 24 02:57:45 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct 24 02:57:45 node-1 kernel: [    0.000043] Security Framework initialized
Oct 24 02:57:45 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Oct 24 02:57:45 node-1 kernel: [    0.000062] Yama: becoming mindful.
Oct 24 02:57:45 node-1 kernel: [    0.001459] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 24 02:57:45 node-1 kernel: [    0.006380] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 24 02:57:45 node-1 kernel: [    0.008306] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 24 02:57:45 node-1 kernel: [    0.008334] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 24 02:57:45 node-1 kernel: [    0.008622] Initializing cgroup subsys memory
Oct 24 02:57:45 node-1 kernel: [    0.008630] Initializing cgroup subsys devices
Oct 24 02:57:45 node-1 kernel: [    0.008632] Initializing cgroup subsys freezer
Oct 24 02:57:45 node-1 kernel: [    0.008634] Initializing cgroup subsys blkio
Oct 24 02:57:45 node-1 kernel: [    0.008635] Initializing cgroup subsys perf_event
Oct 24 02:57:45 node-1 kernel: [    0.008637] Initializing cgroup subsys hugetlb
Oct 24 02:57:45 node-1 kernel: [    0.008657] CPU: Physical Processor ID: 0
Oct 24 02:57:45 node-1 kernel: [    0.008658] CPU: Processor Core ID: 0
Oct 24 02:57:45 node-1 kernel: [    0.008662] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 24 02:57:45 node-1 kernel: [    0.008662] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 24 02:57:45 node-1 kernel: [    0.009356] mce: CPU supports 22 MCE banks
Oct 24 02:57:45 node-1 kernel: [    0.009384] CPU0: Thermal monitoring enabled (TM1)
Oct 24 02:57:45 node-1 kernel: [    0.009404] process: using mwait in idle threads
Oct 24 02:57:45 node-1 kernel: [    0.009407] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 24 02:57:45 node-1 kernel: [    0.009407] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 24 02:57:45 node-1 kernel: [    0.009407] tlb_flushall_shift: 6
Oct 24 02:57:45 node-1 kernel: [    0.009495] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 24 02:57:45 node-1 kernel: [    0.010220] ACPI: Core revision 20131115
Oct 24 02:57:45 node-1 kernel: [    0.023015] ACPI: All ACPI Tables successfully acquired
Oct 24 02:57:45 node-1 kernel: [    0.023192] ftrace: allocating 28622 entries in 112 pages
Oct 24 02:57:45 node-1 kernel: [    0.031952] dmar: Host address width 46
Oct 24 02:57:45 node-1 kernel: [    0.031954] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 24 02:57:45 node-1 kernel: [    0.031960] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 24 02:57:45 node-1 kernel: [    0.031962] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 24 02:57:45 node-1 kernel: [    0.031966] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 24 02:57:45 node-1 kernel: [    0.031968] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 24 02:57:45 node-1 kernel: [    0.031969] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 24 02:57:45 node-1 kernel: [    0.031970] dmar: ATSR flags: 0x0
Oct 24 02:57:45 node-1 kernel: [    0.031971] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 24 02:57:45 node-1 kernel: [    0.031973] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 24 02:57:45 node-1 kernel: [    0.032088] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 24 02:57:45 node-1 kernel: [    0.032090] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 24 02:57:45 node-1 kernel: [    0.032091] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 24 02:57:45 node-1 kernel: [    0.032092] HPET id 0 under DRHD base 0xc7ffc000
Oct 24 02:57:45 node-1 kernel: [    0.032093] Your BIOS is broken and requested that x2apic be disabled.
Oct 24 02:57:45 node-1 kernel: [    0.032093] This will slightly decrease performance.
Oct 24 02:57:45 node-1 kernel: [    0.032093] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 24 02:57:45 node-1 kernel: [    0.032525] Enabled IRQ remapping in xapic mode
Oct 24 02:57:45 node-1 kernel: [    0.032526] x2apic not enabled, IRQ remapping is in xapic mode
Oct 24 02:57:45 node-1 kernel: [    0.032529] Switched APIC routing to physical flat.
Oct 24 02:57:45 node-1 kernel: [    0.033156] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 24 02:57:45 node-1 kernel: [    0.072808] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 24 02:57:45 node-1 kernel: [    0.072813] TSC deadline timer enabled
Oct 24 02:57:45 node-1 kernel: [    0.072821] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 24 02:57:45 node-1 kernel: [    0.072827] ... version:                3
Oct 24 02:57:45 node-1 kernel: [    0.072828] ... bit width:              48
Oct 24 02:57:45 node-1 kernel: [    0.072829] ... generic registers:      4
Oct 24 02:57:45 node-1 kernel: [    0.072830] ... value mask:             0000ffffffffffff
Oct 24 02:57:45 node-1 kernel: [    0.072831] ... max period:             0000ffffffffffff
Oct 24 02:57:45 node-1 kernel: [    0.072832] ... fixed-purpose events:   3
Oct 24 02:57:45 node-1 kernel: [    0.072833] ... event mask:             000000070000000f
Oct 24 02:57:45 node-1 kernel: [    0.074263] x86: Booting SMP configuration:
Oct 24 02:57:45 node-1 kernel: [    0.088367] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 24 02:57:45 node-1 kernel: [    0.074265] .... node  #0, CPUs:        #1  #2  #3
Oct 24 02:57:45 node-1 kernel: [    0.116295] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 24 02:57:45 node-1 kernel: [    0.270456] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 24 02:57:45 node-1 kernel: [    0.326081] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 24 02:57:45 node-1 kernel: [    0.382738] x86: Booted up 2 nodes, 16 CPUs
Oct 24 02:57:45 node-1 kernel: [    0.382742] smpboot: Total of 16 processors activated (111759.05 BogoMIPS)
Oct 24 02:57:45 node-1 kernel: [    0.406363] devtmpfs: initialized
Oct 24 02:57:45 node-1 kernel: [    0.408868] EVM: security.selinux
Oct 24 02:57:45 node-1 kernel: [    0.408870] EVM: security.SMACK64
Oct 24 02:57:45 node-1 kernel: [    0.408871] EVM: security.ima
Oct 24 02:57:45 node-1 kernel: [    0.408872] EVM: security.capability
Oct 24 02:57:45 node-1 kernel: [    0.408920] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Oct 24 02:57:45 node-1 kernel: [    0.409577] pinctrl core: initialized pinctrl subsystem
Oct 24 02:57:45 node-1 kernel: [    0.409639] regulator-dummy: no parameters
Oct 24 02:57:45 node-1 kernel: [    0.409671] RTC time:  2:57:09, date: 10/24/16
Oct 24 02:57:45 node-1 kernel: [    0.409705] NET: Registered protocol family 16
Oct 24 02:57:45 node-1 kernel: [    0.409789] cpuidle: using governor ladder
Oct 24 02:57:45 node-1 kernel: [    0.409790] cpuidle: using governor menu
Oct 24 02:57:45 node-1 kernel: [    0.409824] ACPI: bus type PCI registered
Oct 24 02:57:45 node-1 kernel: [    0.409826] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 24 02:57:45 node-1 kernel: [    0.409885] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 24 02:57:45 node-1 kernel: [    0.409887] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 24 02:57:45 node-1 kernel: [    0.423615] PCI: Using configuration type 1 for base access
Oct 24 02:57:45 node-1 kernel: [    0.424616] bio: create slab <bio-0> at 0
Oct 24 02:57:45 node-1 kernel: [    0.424918] ACPI: Added _OSI(Module Device)
Oct 24 02:57:45 node-1 kernel: [    0.424920] ACPI: Added _OSI(Processor Device)
Oct 24 02:57:45 node-1 kernel: [    0.424921] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 24 02:57:45 node-1 kernel: [    0.424922] ACPI: Added _OSI(Processor Aggregator Device)
Oct 24 02:57:45 node-1 kernel: [    0.437562] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 24 02:57:45 node-1 kernel: [    0.448210] ACPI: Interpreter enabled
Oct 24 02:57:45 node-1 kernel: [    0.448216] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 24 02:57:45 node-1 kernel: [    0.448220] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 24 02:57:45 node-1 kernel: [    0.448222] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 24 02:57:45 node-1 kernel: [    0.448229] ACPI: (supports S0 S4 S5)
Oct 24 02:57:45 node-1 kernel: [    0.448231] ACPI: Using IOAPIC for interrupt routing
Oct 24 02:57:45 node-1 kernel: [    0.448274] HEST: Table parsing has been initialized.
Oct 24 02:57:45 node-1 kernel: [    0.448277] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 24 02:57:45 node-1 kernel: [    0.448831] ACPI: No dock devices found.
Oct 24 02:57:45 node-1 kernel: [    0.460370] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 24 02:57:45 node-1 kernel: [    0.460375] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 24 02:57:45 node-1 kernel: [    0.460378] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 24 02:57:45 node-1 kernel: [    0.460404] PCI host bridge to bus 0000:ff
Oct 24 02:57:45 node-1 kernel: [    0.460406] pci_bus 0000:ff: root bus resource [bus ff]
Oct 24 02:57:45 node-1 kernel: [    0.460414] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460450] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.460480] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460514] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460542] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.460570] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.460599] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460627] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460655] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460683] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460708] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460734] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460762] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460789] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460815] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460843] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460873] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460900] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460926] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.460953] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.460978] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.461003] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461029] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461058] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.461091] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461122] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461151] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461181] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461211] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461243] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461275] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461307] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461337] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461368] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461398] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461430] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461463] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461495] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461521] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461552] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461584] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461621] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461656] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461688] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461719] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461747] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461776] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461805] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461834] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461865] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461896] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461925] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461953] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.461982] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462011] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462042] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462074] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462130] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 24 02:57:45 node-1 kernel: [    0.462133] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 24 02:57:45 node-1 kernel: [    0.462136] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 24 02:57:45 node-1 kernel: [    0.462153] PCI host bridge to bus 0000:7f
Oct 24 02:57:45 node-1 kernel: [    0.462155] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 24 02:57:45 node-1 kernel: [    0.462160] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462187] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.462213] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462242] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462264] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.462288] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.462313] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462339] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462367] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462391] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462414] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462438] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462463] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462487] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462512] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462537] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462558] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462581] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462603] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.462627] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462648] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.462670] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462692] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462718] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 24 02:57:45 node-1 kernel: [    0.462750] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462776] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462801] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462828] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462853] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462881] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462908] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462936] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462961] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.462987] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463013] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463040] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463068] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463094] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463119] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463148] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463173] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463202] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463232] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463261] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463288] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463313] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463338] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463367] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463394] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463421] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463451] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463476] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463498] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463524] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463549] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463577] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.463603] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.464843] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 24 02:57:45 node-1 kernel: [    0.464846] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 24 02:57:45 node-1 kernel: [    0.465962] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 24 02:57:45 node-1 kernel: [    0.466479] PCI host bridge to bus 0000:00
Oct 24 02:57:45 node-1 kernel: [    0.466481] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 24 02:57:45 node-1 kernel: [    0.466482] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 24 02:57:45 node-1 kernel: [    0.466484] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 24 02:57:45 node-1 kernel: [    0.466485] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 24 02:57:45 node-1 kernel: [    0.466487] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 24 02:57:45 node-1 kernel: [    0.466488] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 24 02:57:45 node-1 kernel: [    0.466489] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 24 02:57:45 node-1 kernel: [    0.466495] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 24 02:57:45 node-1 kernel: [    0.466578] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.466608] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.466650] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 24 02:57:45 node-1 kernel: [    0.466670] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.466699] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.466739] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 24 02:57:45 node-1 kernel: [    0.466758] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.466787] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.466828] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 24 02:57:45 node-1 kernel: [    0.466844] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.466915] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.466993] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.467070] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 24 02:57:45 node-1 kernel: [    0.467075] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 24 02:57:45 node-1 kernel: [    0.467161] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 24 02:57:45 node-1 kernel: [    0.467310] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 24 02:57:45 node-1 kernel: [    0.467327] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 24 02:57:45 node-1 kernel: [    0.467405] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.467458] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 24 02:57:45 node-1 kernel: [    0.467480] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.467536] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.467580] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 24 02:57:45 node-1 kernel: [    0.467608] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.467664] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.467707] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 24 02:57:45 node-1 kernel: [    0.467732] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 24 02:57:45 node-1 kernel: [    0.467749] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 24 02:57:45 node-1 kernel: [    0.467827] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.467876] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 24 02:57:45 node-1 kernel: [    0.467904] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 24 02:57:45 node-1 kernel: [    0.468152] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 24 02:57:45 node-1 kernel: [    0.468158] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 24 02:57:45 node-1 kernel: [    0.468164] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 24 02:57:45 node-1 kernel: [    0.468170] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 24 02:57:45 node-1 kernel: [    0.468177] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 24 02:57:45 node-1 kernel: [    0.468207] pci 0000:01:00.0: supports D1 D2
Oct 24 02:57:45 node-1 kernel: [    0.474358] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 24 02:57:45 node-1 kernel: [    0.474364] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 24 02:57:45 node-1 kernel: [    0.474368] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 24 02:57:45 node-1 kernel: [    0.474492] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.474525] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 24 02:57:45 node-1 kernel: [    0.482355] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 24 02:57:45 node-1 kernel: [    0.482361] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.482365] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 24 02:57:45 node-1 kernel: [    0.482450] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.482522] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 24 02:57:45 node-1 kernel: [    0.482616] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.482674] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 24 02:57:45 node-1 kernel: [    0.482677] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.482679] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 24 02:57:45 node-1 kernel: [    0.482734] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.482857] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.482910] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 24 02:57:45 node-1 kernel: [    0.482913] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.482915] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 24 02:57:45 node-1 kernel: [    0.482964] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.483104] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.483143] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.483263] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.483300] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.483423] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.483460] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 24 02:57:45 node-1 kernel: [    0.483579] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 24 02:57:45 node-1 kernel: [    0.483621] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 24 02:57:45 node-1 kernel: [    0.483624] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.483626] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 24 02:57:45 node-1 kernel: [    0.483683] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 24 02:57:45 node-1 kernel: [    0.483746] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 24 02:57:45 node-1 kernel: [    0.483798] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 24 02:57:45 node-1 kernel: [    0.483842] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 24 02:57:45 node-1 kernel: [    0.483923] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 24 02:57:45 node-1 kernel: [    0.484029] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 24 02:57:45 node-1 kernel: [    0.484031] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.484033] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 24 02:57:45 node-1 kernel: [    0.484114] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 24 02:57:45 node-1 kernel: [    0.484173] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 24 02:57:45 node-1 kernel: [    0.484220] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 24 02:57:45 node-1 kernel: [    0.484438] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 24 02:57:45 node-1 kernel: [    0.484442] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 24 02:57:45 node-1 kernel: [    0.484509] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 24 02:57:45 node-1 kernel: [    0.484567] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 24 02:57:45 node-1 kernel: [    0.484614] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 24 02:57:45 node-1 kernel: [    0.484827] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 24 02:57:45 node-1 kernel: [    0.484830] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 24 02:57:45 node-1 kernel: [    0.484893] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 24 02:57:45 node-1 kernel: [    0.484959] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 24 02:57:45 node-1 kernel: [    0.485010] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 24 02:57:45 node-1 kernel: [    0.485269] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 24 02:57:45 node-1 kernel: [    0.485273] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 24 02:57:45 node-1 kernel: [    0.485447] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 24 02:57:45 node-1 kernel: [    0.485486] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 24 02:57:45 node-1 kernel: [    0.485562] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 24 02:57:45 node-1 kernel: [    0.485581] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 24 02:57:45 node-1 kernel: [    0.485594] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 24 02:57:45 node-1 kernel: [    0.485607] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 24 02:57:45 node-1 kernel: [    0.485657] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 24 02:57:45 node-1 kernel: [    0.490363] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 24 02:57:45 node-1 kernel: [    0.490372] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 24 02:57:45 node-1 kernel: [    0.490424] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 24 02:57:45 node-1 kernel: [    0.491157] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 24 02:57:45 node-1 kernel: [    0.491160] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 24 02:57:45 node-1 kernel: [    0.491281] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 24 02:57:45 node-1 kernel: [    0.491387] PCI host bridge to bus 0000:80
Oct 24 02:57:45 node-1 kernel: [    0.491389] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 24 02:57:45 node-1 kernel: [    0.491390] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 24 02:57:45 node-1 kernel: [    0.491392] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 24 02:57:45 node-1 kernel: [    0.491400] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.491462] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.491529] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 24 02:57:45 node-1 kernel: [    0.491589] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 24 02:57:45 node-1 kernel: [    0.491594] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 24 02:57:45 node-1 kernel: [    0.491664] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 24 02:57:45 node-1 kernel: [    0.491960] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 24 02:57:45 node-1 kernel: [    0.491991] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 24 02:57:45 node-1 kernel: [    0.492021] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 24 02:57:45 node-1 kernel: [    0.492050] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 24 02:57:45 node-1 kernel: [    0.492079] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 24 02:57:45 node-1 kernel: [    0.492109] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 24 02:57:45 node-1 kernel: [    0.492138] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 24 02:57:45 node-1 kernel: [    0.492168] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 24 02:57:45 node-1 kernel: [    0.492253] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 24 02:57:45 node-1 kernel: [    0.492257] ACPI: \_SB_.UNC1: notify handler is installed
Oct 24 02:57:45 node-1 kernel: [    0.492258] ACPI: \_SB_.UNC0: notify handler is installed
Oct 24 02:57:45 node-1 kernel: [    0.492273] ACPI: \_SB_.PCI0: notify handler is installed
Oct 24 02:57:45 node-1 kernel: [    0.492325] ACPI: \_SB_.PCI1: notify handler is installed
Oct 24 02:57:45 node-1 kernel: [    0.492405] Found 4 acpi root devices
Oct 24 02:57:45 node-1 kernel: [    0.492510] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 24 02:57:45 node-1 kernel: [    0.492512] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 24 02:57:45 node-1 kernel: [    0.492513] vgaarb: loaded
Oct 24 02:57:45 node-1 kernel: [    0.492514] vgaarb: bridge control possible 0000:0c:00.0
Oct 24 02:57:45 node-1 kernel: [    0.492635] SCSI subsystem initialized
Oct 24 02:57:45 node-1 kernel: [    0.492699] libata version 3.00 loaded.
Oct 24 02:57:45 node-1 kernel: [    0.492715] ACPI: bus type USB registered
Oct 24 02:57:45 node-1 kernel: [    0.492725] usbcore: registered new interface driver usbfs
Oct 24 02:57:45 node-1 kernel: [    0.492730] usbcore: registered new interface driver hub
Oct 24 02:57:45 node-1 kernel: [    0.492752] usbcore: registered new device driver usb
Oct 24 02:57:45 node-1 kernel: [    0.492937] PCI: Using ACPI for IRQ routing
Oct 24 02:57:45 node-1 kernel: [    0.496547] PCI: pci_cache_line_size set to 64 bytes
Oct 24 02:57:45 node-1 kernel: [    0.496758] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 24 02:57:45 node-1 kernel: [    0.496759] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Oct 24 02:57:45 node-1 kernel: [    0.496760] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 24 02:57:45 node-1 kernel: [    0.496824] NetLabel: Initializing
Oct 24 02:57:45 node-1 kernel: [    0.496826] NetLabel:  domain hash size = 128
Oct 24 02:57:45 node-1 kernel: [    0.496826] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 24 02:57:45 node-1 kernel: [    0.496836] NetLabel:  unlabeled traffic allowed by default
Oct 24 02:57:45 node-1 kernel: [    0.496893] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 24 02:57:45 node-1 kernel: [    0.496897] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 24 02:57:45 node-1 kernel: [    0.498967] Switched to clocksource hpet
Oct 24 02:57:45 node-1 kernel: [    0.502893] AppArmor: AppArmor Filesystem Enabled
Oct 24 02:57:45 node-1 kernel: [    0.502916] pnp: PnP ACPI init
Oct 24 02:57:45 node-1 kernel: [    0.502923] ACPI: bus type PNP registered
Oct 24 02:57:45 node-1 kernel: [    0.503036] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 24 02:57:45 node-1 kernel: [    0.503044] pnp 00:01: [dma 4]
Oct 24 02:57:45 node-1 kernel: [    0.503056] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 24 02:57:45 node-1 kernel: [    0.503082] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 24 02:57:45 node-1 kernel: [    0.503102] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 24 02:57:45 node-1 kernel: [    0.503120] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 24 02:57:45 node-1 kernel: [    0.503153] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 24 02:57:45 node-1 kernel: [    0.503205] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 24 02:57:45 node-1 kernel: [    0.503207] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 24 02:57:45 node-1 kernel: [    0.503209] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 24 02:57:45 node-1 kernel: [    0.503211] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 24 02:57:45 node-1 kernel: [    0.503212] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 24 02:57:45 node-1 kernel: [    0.503217] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 24 02:57:45 node-1 kernel: [    0.503219] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 24 02:57:45 node-1 kernel: [    0.503221] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 24 02:57:45 node-1 kernel: [    0.503222] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 24 02:57:45 node-1 kernel: [    0.503224] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 24 02:57:45 node-1 kernel: [    0.503225] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 24 02:57:45 node-1 kernel: [    0.503226] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 24 02:57:45 node-1 kernel: [    0.503228] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 24 02:57:45 node-1 kernel: [    0.503230] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 24 02:57:45 node-1 kernel: [    0.503313] pnp 00:07: [dma 0 disabled]
Oct 24 02:57:45 node-1 kernel: [    0.503341] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 24 02:57:45 node-1 kernel: [    0.503415] pnp 00:08: [dma 0 disabled]
Oct 24 02:57:45 node-1 kernel: [    0.503448] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 24 02:57:45 node-1 kernel: [    0.503498] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 24 02:57:45 node-1 kernel: [    0.503842] pnp: PnP ACPI: found 10 devices
Oct 24 02:57:45 node-1 kernel: [    0.503844] ACPI: bus type PNP unregistered
Oct 24 02:57:45 node-1 kernel: [    0.510264] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 24 02:57:45 node-1 kernel: [    0.510267] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 24 02:57:45 node-1 kernel: [    0.510270] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 24 02:57:45 node-1 kernel: [    0.510274] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 24 02:57:45 node-1 kernel: [    0.510276] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.510291] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510319] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 24 02:57:45 node-1 kernel: [    0.510334] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510366] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 24 02:57:45 node-1 kernel: [    0.510381] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 24 02:57:45 node-1 kernel: [    0.510409] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 24 02:57:45 node-1 kernel: [    0.510424] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 24 02:57:45 node-1 kernel: [    0.510453] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 24 02:57:45 node-1 kernel: [    0.510454] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.510469] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510498] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 24 02:57:45 node-1 kernel: [    0.510500] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.510514] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510543] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 24 02:57:45 node-1 kernel: [    0.510545] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.510547] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510551] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 24 02:57:45 node-1 kernel: [    0.510553] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.510556] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510559] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 24 02:57:45 node-1 kernel: [    0.510564] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 24 02:57:45 node-1 kernel: [    0.510572] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 24 02:57:45 node-1 kernel: [    0.510575] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 24 02:57:45 node-1 kernel: [    0.510582] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 24 02:57:45 node-1 kernel: [    0.510583] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 24 02:57:45 node-1 kernel: [    0.510584] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 24 02:57:45 node-1 kernel: [    0.510584] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 24 02:57:45 node-1 kernel: [    0.510585] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 24 02:57:45 node-1 kernel: [    0.510586] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 24 02:57:45 node-1 kernel: [    0.510587] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 24 02:57:45 node-1 kernel: [    0.510588] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 24 02:57:45 node-1 kernel: [    0.510589] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.510590] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510591] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.510592] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510592] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.510593] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510594] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.510595] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510596] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 24 02:57:45 node-1 kernel: [    0.510597] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510598] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 24 02:57:45 node-1 kernel: [    0.510599] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 24 02:57:45 node-1 kernel: [    0.510600] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 24 02:57:45 node-1 kernel: [    0.510601] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 24 02:57:45 node-1 kernel: [    0.510603] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 24 02:57:45 node-1 kernel: [    0.510604] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 24 02:57:45 node-1 kernel: [    0.510642] NET: Registered protocol family 2
Oct 24 02:57:45 node-1 kernel: [    0.510907] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 24 02:57:45 node-1 kernel: [    0.511247] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 24 02:57:45 node-1 kernel: [    0.511394] TCP: Hash tables configured (established 262144 bind 65536)
Oct 24 02:57:45 node-1 kernel: [    0.511436] TCP: reno registered
Oct 24 02:57:45 node-1 kernel: [    0.511466] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 24 02:57:45 node-1 kernel: [    0.511560] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 24 02:57:45 node-1 kernel: [    0.511707] NET: Registered protocol family 1
Oct 24 02:57:45 node-1 kernel: [    0.547062] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 24 02:57:45 node-1 kernel: [    0.547075] PCI: CLS 64 bytes, default 64
Oct 24 02:57:45 node-1 kernel: [    0.547152] Trying to unpack rootfs image as initramfs...
Oct 24 02:57:45 node-1 kernel: [    0.766647] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Oct 24 02:57:45 node-1 kernel: [    0.766684] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 24 02:57:45 node-1 kernel: [    0.766686] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Oct 24 02:57:45 node-1 kernel: [    0.767096] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767102] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767107] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767113] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767125] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767142] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767157] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767172] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767184] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767194] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767200] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767206] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767216] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767229] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767242] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767254] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 24 02:57:45 node-1 kernel: [    0.767350] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 24 02:57:45 node-1 kernel: [    0.767353] Scanning for low memory corruption every 60 seconds
Oct 24 02:57:45 node-1 kernel: [    0.767745] Initialise system trusted keyring
Oct 24 02:57:45 node-1 kernel: [    0.767800] audit: initializing netlink socket (disabled)
Oct 24 02:57:45 node-1 kernel: [    0.767815] type=2000 audit(1477277828.720:1): initialized
Oct 24 02:57:45 node-1 kernel: [    0.785545] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 24 02:57:45 node-1 kernel: [    0.787059] zbud: loaded
Oct 24 02:57:45 node-1 kernel: [    0.787184] VFS: Disk quotas dquot_6.5.2
Oct 24 02:57:45 node-1 kernel: [    0.787221] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 24 02:57:45 node-1 kernel: [    0.787592] fuse init (API version 7.22)
Oct 24 02:57:45 node-1 kernel: [    0.787648] msgmni has been set to 32768
Oct 24 02:57:45 node-1 kernel: [    0.787700] Key type big_key registered
Oct 24 02:57:45 node-1 kernel: [    0.788238] Key type asymmetric registered
Oct 24 02:57:45 node-1 kernel: [    0.788240] Asymmetric key parser 'x509' registered
Oct 24 02:57:45 node-1 kernel: [    0.788262] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 24 02:57:45 node-1 kernel: [    0.788328] io scheduler noop registered
Oct 24 02:57:45 node-1 kernel: [    0.788330] io scheduler deadline registered (default)
Oct 24 02:57:45 node-1 kernel: [    0.788347] io scheduler cfq registered
Oct 24 02:57:45 node-1 kernel: [    0.788737] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    0.788862] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    0.788975] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    0.789087] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    0.789202] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    0.789295] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    0.789710] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 24 02:57:45 node-1 kernel: [    0.789735] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 24 02:57:45 node-1 kernel: [    0.789752] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 24 02:57:45 node-1 kernel: [    0.789765] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789767] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789770] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 24 02:57:45 node-1 kernel: [    0.789776] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789777] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789778] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789780] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789782] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789783] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789785] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789786] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789788] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789789] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789791] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789792] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789795] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 24 02:57:45 node-1 kernel: [    0.789800] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789802] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 24 02:57:45 node-1 kernel: [    0.789813] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789816] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 24 02:57:45 node-1 kernel: [    0.789827] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789829] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 24 02:57:45 node-1 kernel: [    0.789832] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 24 02:57:45 node-1 kernel: [    0.789859] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 24 02:57:45 node-1 kernel: [    0.789866] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 24 02:57:45 node-1 kernel: [    0.789870] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 24 02:57:45 node-1 kernel: [    0.789886] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 24 02:57:45 node-1 kernel: [    0.789926] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 24 02:57:45 node-1 kernel: [    0.789927] vesafb: scrolling: redraw
Oct 24 02:57:45 node-1 kernel: [    0.789929] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 24 02:57:45 node-1 kernel: [    0.810568] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 24 02:57:45 node-1 kernel: [    0.819069] Console: switching to colour frame buffer device 80x30
Oct 24 02:57:45 node-1 kernel: [    0.827737] fb0: VESA VGA frame buffer device
Oct 24 02:57:45 node-1 kernel: [    0.827937] intel_idle: MWAIT substates: 0x2120
Oct 24 02:57:45 node-1 kernel: [    0.827938] intel_idle: v0.4 model 0x3F
Oct 24 02:57:45 node-1 kernel: [    0.827939] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 24 02:57:45 node-1 kernel: [    0.828165] ipmi message handler version 39.2
Oct 24 02:57:45 node-1 kernel: [    0.828435] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 24 02:57:45 node-1 kernel: [    0.828868] ACPI: AC Adapter [P111] (on-line)
Oct 24 02:57:45 node-1 kernel: [    0.834110] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 24 02:57:45 node-1 kernel: [    0.845119] ACPI: Power Button [PWRB]
Oct 24 02:57:45 node-1 kernel: [    0.850871] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 24 02:57:45 node-1 kernel: [    0.862496] ACPI: Power Button [PWRF]
Oct 24 02:57:45 node-1 kernel: [    0.888526] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 24 02:57:45 node-1 kernel: [    0.900180] pstore: Registered erst as persistent store backend
Oct 24 02:57:45 node-1 kernel: [    0.906378] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 24 02:57:45 node-1 kernel: [    0.918300] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 24 02:57:45 node-1 kernel: [    0.945037] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 24 02:57:45 node-1 kernel: [    0.978310] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 24 02:57:45 node-1 kernel: [    0.992395] Linux agpgart interface v0.103
Oct 24 02:57:45 node-1 kernel: [    1.000035] brd: module loaded
Oct 24 02:57:45 node-1 kernel: [    1.007057] loop: module loaded
Oct 24 02:57:45 node-1 kernel: [    1.013754] libphy: Fixed MDIO Bus: probed
Oct 24 02:57:45 node-1 kernel: [    1.020210] tun: Universal TUN/TAP device driver, 1.6
Oct 24 02:57:45 node-1 kernel: [    1.026682] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 24 02:57:45 node-1 kernel: [    1.033194] PPP generic driver version 2.4.2
Oct 24 02:57:45 node-1 kernel: [    1.039577] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 24 02:57:45 node-1 kernel: [    1.046015] ehci-pci: EHCI PCI platform driver
Oct 24 02:57:45 node-1 kernel: [    1.052531] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 24 02:57:45 node-1 kernel: [    1.058927] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 24 02:57:45 node-1 kernel: [    1.071434] ehci-pci 0000:00:1a.0: debug port 2
Oct 24 02:57:45 node-1 kernel: [    1.081649] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 24 02:57:45 node-1 kernel: [    1.081669] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 24 02:57:45 node-1 kernel: [    1.098459] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 24 02:57:45 node-1 kernel: [    1.104532] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 24 02:57:45 node-1 kernel: [    1.110781] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 24 02:57:45 node-1 kernel: [    1.122772] usb usb1: Product: EHCI Host Controller
Oct 24 02:57:45 node-1 kernel: [    1.128847] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 24 02:57:45 node-1 kernel: [    1.134950] usb usb1: SerialNumber: 0000:00:1a.0
Oct 24 02:57:45 node-1 kernel: [    1.140958] hub 1-0:1.0: USB hub found
Oct 24 02:57:45 node-1 kernel: [    1.146781] hub 1-0:1.0: 2 ports detected
Oct 24 02:57:45 node-1 kernel: [    1.152640] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 24 02:57:45 node-1 kernel: [    1.158262] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 24 02:57:45 node-1 kernel: [    1.169274] ehci-pci 0000:00:1d.0: debug port 2
Oct 24 02:57:45 node-1 kernel: [    1.178611] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 24 02:57:45 node-1 kernel: [    1.178617] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 24 02:57:45 node-1 kernel: [    1.194378] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 24 02:57:45 node-1 kernel: [    1.199634] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 24 02:57:45 node-1 kernel: [    1.204978] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 24 02:57:45 node-1 kernel: [    1.215692] usb usb2: Product: EHCI Host Controller
Oct 24 02:57:45 node-1 kernel: [    1.221218] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 24 02:57:45 node-1 kernel: [    1.226839] usb usb2: SerialNumber: 0000:00:1d.0
Oct 24 02:57:45 node-1 kernel: [    1.232438] hub 2-0:1.0: USB hub found
Oct 24 02:57:45 node-1 kernel: [    1.237846] hub 2-0:1.0: 2 ports detected
Oct 24 02:57:45 node-1 kernel: [    1.243217] ehci-platform: EHCI generic platform driver
Oct 24 02:57:45 node-1 kernel: [    1.248520] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 24 02:57:45 node-1 kernel: [    1.253899] ohci-pci: OHCI PCI platform driver
Oct 24 02:57:45 node-1 kernel: [    1.259267] ohci-platform: OHCI generic platform driver
Oct 24 02:57:45 node-1 kernel: [    1.264536] uhci_hcd: USB Universal Host Controller Interface driver
Oct 24 02:57:45 node-1 kernel: [    1.269945] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 24 02:57:45 node-1 kernel: [    1.462156] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 24 02:57:45 node-1 kernel: [    1.622322] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 24 02:57:45 node-1 kernel: [    1.627847] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 24 02:57:45 node-1 kernel: [    1.633590] hub 1-1:1.0: USB hub found
Oct 24 02:57:45 node-1 kernel: [    1.639058] hub 1-1:1.0: 6 ports detected
Oct 24 02:57:45 node-1 kernel: [    1.753902] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 24 02:57:45 node-1 kernel: [    1.765935] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 24 02:57:45 node-1 kernel: [    2.021983] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 24 02:57:45 node-1 kernel: [    2.027550] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 24 02:57:45 node-1 kernel: [    2.033372] hub 2-1:1.0: USB hub found
Oct 24 02:57:45 node-1 kernel: [    2.039094] hub 2-1:1.0: 8 ports detected
Oct 24 02:57:45 node-1 kernel: [    2.311675] i8042: No controller found
Oct 24 02:57:45 node-1 kernel: [    2.317097] mousedev: PS/2 mouse device common for all mice
Oct 24 02:57:45 node-1 kernel: [    2.317534] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 24 02:57:45 node-1 kernel: [    2.328272] rtc_cmos 00:02: RTC can wake from S4
Oct 24 02:57:45 node-1 kernel: [    2.334098] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 24 02:57:45 node-1 kernel: [    2.339815] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 24 02:57:45 node-1 kernel: [    2.350918] device-mapper: uevent: version 1.0.3
Oct 24 02:57:45 node-1 kernel: [    2.356558] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 24 02:57:45 node-1 kernel: [    2.367761] ledtrig-cpu: registered to indicate activity on CPUs
Oct 24 02:57:45 node-1 kernel: [    2.373678] TCP: cubic registered
Oct 24 02:57:45 node-1 kernel: [    2.379560] NET: Registered protocol family 10
Oct 24 02:57:45 node-1 kernel: [    2.385523] NET: Registered protocol family 17
Oct 24 02:57:45 node-1 kernel: [    2.391189] Key type dns_resolver registered
Oct 24 02:57:45 node-1 kernel: [    2.397144] Loading compiled-in X.509 certificates
Oct 24 02:57:45 node-1 kernel: [    2.403308] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 24 02:57:45 node-1 kernel: [    2.414677] registered taskstats version 1
Oct 24 02:57:45 node-1 kernel: [    2.422919] Key type trusted registered
Oct 24 02:57:45 node-1 kernel: [    2.430493] Key type encrypted registered
Oct 24 02:57:45 node-1 kernel: [    2.435956] AppArmor: AppArmor sha1 policy hashing enabled
Oct 24 02:57:45 node-1 kernel: [    2.441442] IMA: No TPM chip found, activating TPM-bypass!
Oct 24 02:57:45 node-1 kernel: [    2.447582] regulator-dummy: disabling
Oct 24 02:57:45 node-1 kernel: [    2.449685] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 24 02:57:45 node-1 kernel: [    2.449686] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 24 02:57:45 node-1 kernel: [    2.449687] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 24 02:57:45 node-1 kernel: [    2.449687] usb 2-1.4: Manufacturer: Avocent
Oct 24 02:57:45 node-1 kernel: [    2.449688] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 24 02:57:45 node-1 kernel: [    2.487018]   Magic number: 4:480:966
Oct 24 02:57:45 node-1 kernel: [    2.492898] rtc_cmos 00:02: setting system clock to 2016-10-24 02:57:11 UTC (1477277831)
Oct 24 02:57:45 node-1 kernel: [    2.505630] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 24 02:57:45 node-1 kernel: [    2.511502] EDD information not available.
Oct 24 02:57:45 node-1 kernel: [    2.517286] PM: Hibernation image not present or could not be loaded.
Oct 24 02:57:45 node-1 kernel: [    2.518145] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 24 02:57:45 node-1 kernel: [    2.529710] Write protecting the kernel read-only data: 12288k
Oct 24 02:57:45 node-1 kernel: [    2.536154] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 24 02:57:45 node-1 kernel: [    2.548934] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 24 02:57:45 node-1 kernel: [    2.579891] device-mapper: multipath: version 1.6.0 loaded
Oct 24 02:57:45 node-1 kernel: [    2.587948] systemd-udevd[216]: starting version 204
Oct 24 02:57:45 node-1 kernel: [    2.608315] md: linear personality registered for level -1
Oct 24 02:57:45 node-1 kernel: [    2.623293] md: multipath personality registered for level -4
Oct 24 02:57:45 node-1 kernel: [    2.631398] md: raid0 personality registered for level 0
Oct 24 02:57:45 node-1 kernel: [    2.639740] md: raid1 personality registered for level 1
Oct 24 02:57:45 node-1 kernel: [    2.648933] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 24 02:57:45 node-1 kernel: [    2.655344] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 24 02:57:45 node-1 kernel: [    2.655594] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 24 02:57:45 node-1 kernel: [    2.668216] hidraw: raw HID events driver (C) Jiri Kosina
Oct 24 02:57:45 node-1 kernel: [    2.668235] megasas: FW now in Ready state
Oct 24 02:57:45 node-1 kernel: [    2.668296] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668334] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668371] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668429] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668466] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668503] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668540] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668577] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668611] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668650] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668683] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668721] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668732] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Oct 24 02:57:45 node-1 kernel: [    2.668733] 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
Oct 24 02:57:45 node-1 kernel: [    2.668734] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 24 02:57:45 node-1 kernel: [    2.668757] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668814] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668824] enic 0000:06:00.0: irq 110 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668851] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668862] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668888] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668895] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.668933] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.669040] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.669045] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 24 02:57:45 node-1 kernel: [    2.680002] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Oct 24 02:57:45 node-1 kernel: [    2.680004] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Oct 24 02:57:45 node-1 kernel: [    2.680006] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 24 02:57:45 node-1 kernel: [    2.680088] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.680136] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.680180] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.680224] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.680261] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.680311] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.680424] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.689382] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Oct 24 02:57:45 node-1 kernel: [    2.689384] 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
Oct 24 02:57:45 node-1 kernel: [    2.689385] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 24 02:57:45 node-1 kernel: [    2.689510] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.689552] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.689590] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.689644] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.689757] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.697329] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Oct 24 02:57:45 node-1 kernel: [    2.697331] 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
Oct 24 02:57:45 node-1 kernel: [    2.697338] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 24 02:57:45 node-1 kernel: [    2.697455] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.697500] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.697518] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.697564] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.697695] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 24 02:57:45 node-1 kernel: [    2.713316] raid6: sse2x1    3588 MB/s
Oct 24 02:57:45 node-1 kernel: [    2.889559] raid6: sse2x2    1981 MB/s
Oct 24 02:57:45 node-1 kernel: [    2.960893] raid6: sse2x4   10137 MB/s
Oct 24 02:57:45 node-1 kernel: [    3.032828] raid6: avx2x1   14958 MB/s
Oct 24 02:57:45 node-1 kernel: [    3.104762] raid6: avx2x2   18856 MB/s
Oct 24 02:57:45 node-1 kernel: [    3.176713] raid6: avx2x4   21258 MB/s
Oct 24 02:57:45 node-1 kernel: [    3.182766] raid6: using algorithm avx2x4 (21258 MB/s)
Oct 24 02:57:45 node-1 kernel: [    3.188776] raid6: using avx2x2 recovery algorithm
Oct 24 02:57:45 node-1 kernel: [    3.194591] Switched to clocksource tsc
Oct 24 02:57:45 node-1 kernel: [    3.196292] megasas:IOC Init cmd success
Oct 24 02:57:45 node-1 kernel: [    3.206466] xor: automatically using best checksumming function:
Oct 24 02:57:45 node-1 kernel: [    3.213767] usbcore: registered new interface driver usbhid
Oct 24 02:57:45 node-1 kernel: [    3.216682] megasas: INIT adapter done
Oct 24 02:57:45 node-1 kernel: [    3.224510] usbhid: USB HID core driver
Oct 24 02:57:45 node-1 kernel: [    3.230833] 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
Oct 24 02:57:45 node-1 kernel: [    3.241788] 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
Oct 24 02:57:45 node-1 kernel: [    3.248623]    avx       : 35725.000 MB/sec
Oct 24 02:57:45 node-1 kernel: [    3.258275] 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
Oct 24 02:57:45 node-1 kernel: [    3.269480] async_tx: api initialized (async)
Oct 24 02:57:45 node-1 kernel: [    3.269650] 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
Oct 24 02:57:45 node-1 kernel: [    3.269704] 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
Oct 24 02:57:45 node-1 kernel: [    3.270037] 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
Oct 24 02:57:45 node-1 kernel: [    3.288757] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 24 02:57:45 node-1 kernel: [    3.290721] scsi0 : LSI SAS based MegaRAID driver
Oct 24 02:57:45 node-1 kernel: [    3.297703] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 24 02:57:45 node-1 kernel: [    3.337244] md: raid6 personality registered for level 6
Oct 24 02:57:45 node-1 kernel: [    3.337414] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 24 02:57:45 node-1 kernel: [    3.356867] md: raid5 personality registered for level 5
Oct 24 02:57:45 node-1 kernel: [    3.363667] md: raid4 personality registered for level 4
Oct 24 02:57:45 node-1 kernel: [    3.370749] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 24 02:57:45 node-1 kernel: [    3.371081] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 24 02:57:45 node-1 kernel: [    3.371731] sd 0:2:0:0: [sda] Write Protect is off
Oct 24 02:57:45 node-1 kernel: [    3.371740] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 24 02:57:45 node-1 kernel: [    3.372089] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 24 02:57:45 node-1 kernel: [    3.408116]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct 24 02:57:45 node-1 kernel: [    3.412941] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 24 02:57:45 node-1 kernel: [    3.425851] md: raid10 personality registered for level 10
Oct 24 02:57:45 node-1 kernel: [    3.480480] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Oct 24 02:57:45 node-1 kernel: [    3.546627] random: lvm urandom read with 30 bits of entropy available
Oct 24 02:57:45 node-1 kernel: [    3.790523] bio: create slab <bio-1> at 1
Oct 24 02:57:45 node-1 kernel: [    4.532721] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 24 02:57:45 node-1 kernel: [    5.257199] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 24 02:57:45 node-1 kernel: [    5.289416] random: nonblocking pool is initialized
Oct 24 02:57:45 node-1 kernel: [    5.316116] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 24 02:57:45 node-1 kernel: [    5.452005] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 24 02:57:45 node-1 kernel: [    5.487922] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 24 02:57:45 node-1 kernel: [    5.581114] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 24 02:57:45 node-1 kernel: [    5.744805] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 24 02:57:45 node-1 kernel: [    5.789822] XFS (dm-0): Mounting Filesystem
Oct 24 02:57:45 node-1 kernel: [    6.094485] XFS (dm-0): Ending clean mount
Oct 24 02:57:45 node-1 kernel: [    6.138121] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 24 02:57:45 node-1 kernel: [    6.166786] XFS (dm-1): Mounting Filesystem
Oct 24 02:57:45 node-1 kernel: [    6.239909] XFS (dm-1): Ending clean mount
Oct 24 02:57:45 node-1 kernel: [    8.014126] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 24 02:57:45 node-1 kernel: [    8.027638] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 24 02:57:45 node-1 kernel: [    8.221346] systemd-udevd[772]: starting version 204
Oct 24 02:57:45 node-1 kernel: [    8.385365] wmi: Mapper loaded
Oct 24 02:57:45 node-1 kernel: [    8.390316] power_meter ACPI000D:00: Found ACPI power meter.
Oct 24 02:57:45 node-1 kernel: [    8.390324] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 24 02:57:45 node-1 kernel: [    8.408675] IPMI System Interface driver.
Oct 24 02:57:45 node-1 kernel: [    8.408711] ipmi_si: probing via ACPI
Oct 24 02:57:45 node-1 kernel: [    8.408722] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 24 02:57:45 node-1 kernel: [    8.408723] ipmi_si: Adding ACPI-specified kcs state machine
Oct 24 02:57:45 node-1 kernel: [    8.408731] ipmi_si: probing via SMBIOS
Oct 24 02:57:45 node-1 kernel: [    8.408732] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 24 02:57:45 node-1 kernel: [    8.408733] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 24 02:57:45 node-1 kernel: [    8.408735] ipmi_si: probing via SPMI
Oct 24 02:57:45 node-1 kernel: [    8.408735] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 24 02:57:45 node-1 kernel: [    8.408736] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 24 02:57:45 node-1 kernel: [    8.408737] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 24 02:57:45 node-1 kernel: [    8.424930] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 24 02:57:45 node-1 kernel: [    8.424937] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 24 02:57:45 node-1 kernel: [    8.424940] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 24 02:57:45 node-1 kernel: [    8.424942] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 24 02:57:45 node-1 kernel: [    8.424989] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 24 02:57:45 node-1 kernel: [    8.432731] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 24 02:57:45 node-1 kernel: [    8.488681] systemd-udevd[816]: renamed network interface eth2 to enp8s0
Oct 24 02:57:45 node-1 kernel: [    8.520572] systemd-udevd[793]: renamed network interface eth1 to enp7s0
Oct 24 02:57:45 node-1 kernel: [    8.551596] systemd-udevd[823]: renamed network interface eth0 to enp6s0
Oct 24 02:57:45 node-1 kernel: [    8.551854] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 24 02:57:45 node-1 kernel: [    8.551858] ipmi_si 00:09: IPMI kcs interface initialized
Oct 24 02:57:45 node-1 kernel: [    8.576530] systemd-udevd[817]: renamed network interface eth3 to enp9s0
Oct 24 02:57:45 node-1 kernel: [    8.899884] type=1400 audit(1477277837.912:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1048 comm="apparmor_parser"
Oct 24 02:57:45 node-1 kernel: [    8.900053] type=1400 audit(1477277837.912:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1048 comm="apparmor_parser"
Oct 24 02:57:45 node-1 kernel: [    8.900189] type=1400 audit(1477277837.912:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1048 comm="apparmor_parser"
Oct 24 02:57:45 node-1 kernel: [    8.902756] type=1400 audit(1477277837.912:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Oct 24 02:57:45 node-1 kernel: [    8.902899] type=1400 audit(1477277837.912:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1050 comm="apparmor_parser"
Oct 24 02:57:45 node-1 kernel: [    8.903020] type=1400 audit(1477277837.912:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1050 comm="apparmor_parser"
Oct 24 02:57:45 node-1 kernel: [    8.913388] type=1400 audit(1477277837.924:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1052 comm="apparmor_parser"
Oct 24 02:57:45 node-1 kernel: [    8.913541] type=1400 audit(1477277837.924:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1052 comm="apparmor_parser"
Oct 24 02:57:45 node-1 kernel: [    8.913664] type=1400 audit(1477277837.924:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1052 comm="apparmor_parser"
Oct 24 02:57:45 node-1 kernel: [    8.917012] type=1400 audit(1477277837.928:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Oct 24 02:57:45 node-1 kernel: [    9.527697] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 24 02:57:45 node-1 kernel: [    9.528818] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 24 02:57:45 node-1 kernel: [    9.721940] enic 0000:06:00.0 enp6s0: Link UP
Oct 24 02:57:45 node-1 kernel: [    9.723064] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 24 02:57:45 node-1 kernel: [    9.723070] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 24 02:57:45 node-1 kernel: [   19.251515] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 24 02:57:47 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 24 02:57:47 node-1 kernel: [   38.130013] init: failsafe main process (8413) killed by TERM signal
Oct 24 02:57:47 node-1 dbus[8479]: [system] AppArmor D-Bus mediation is enabled
Oct 24 02:57:47 node-1 kernel: [   38.345987] audit_printk_skb: 30 callbacks suppressed
Oct 24 02:57:47 node-1 kernel: [   38.345987] type=1400 audit(1477277867.320:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8532 comm="apparmor_parser"
Oct 24 02:57:47 node-1 kernel: [   38.349992] type=1400 audit(1477277867.324:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8531 comm="apparmor_parser"
Oct 24 02:57:47 node-1 kernel: [   38.349997] type=1400 audit(1477277867.324:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8531 comm="apparmor_parser"
Oct 24 02:57:47 node-1 kernel: [   38.350000] type=1400 audit(1477277867.324:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8531 comm="apparmor_parser"
Oct 24 02:57:47 node-1 kernel: [   38.350226] type=1400 audit(1477277867.324:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8531 comm="apparmor_parser"
Oct 24 02:57:47 node-1 kernel: [   38.350228] type=1400 audit(1477277867.324:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8531 comm="apparmor_parser"
Oct 24 02:57:47 node-1 kernel: [   38.350354] type=1400 audit(1477277867.324:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8531 comm="apparmor_parser"
Oct 24 02:57:47 node-1 kernel: [   38.457102] type=1400 audit(1477277867.432:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8534 comm="apparmor_parser"
Oct 24 02:57:47 node-1 anacron[8606]: Anacron 2.3 started on 2016-10-24
Oct 24 02:57:47 node-1 cron[8572]: (CRON) INFO (pidfile fd = 3)
Oct 24 02:57:47 node-1 cron[8613]: (CRON) STARTUP (fork ok)
Oct 24 02:57:47 node-1 anacron[8606]: Will run job `cron.daily' in 5 min.
Oct 24 02:57:47 node-1 anacron[8606]: Will run job `cron.weekly' in 10 min.
Oct 24 02:57:47 node-1 anacron[8606]: Will run job `cron.monthly' in 15 min.
Oct 24 02:57:47 node-1 anacron[8606]: Jobs will be executed sequentially
Oct 24 02:57:47 node-1 multipathd: path checkers start up
Oct 24 02:57:47 node-1 cron[8613]: (CRON) INFO (Running @reboot jobs)
Oct 24 02:57:48 node-1 postfix/master[8751]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 24 02:57:50 node-1 puppet-agent[8936]: Reopening log files
Oct 24 02:57:51 node-1 puppet-agent[8936]: Could not request certificate: Connection refused - connect(2)
Oct 24 02:58:01 node-1 CRON[8967]: (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")
Oct 24 02:58:06 node-1 puppet-user[9026]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 24 02:58:06 node-1 puppet-user[9026]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 24 02:58:08 node-1 puppet-user[9026]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 24 02:58:08 node-1 puppet-user[9026]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 24 02:58:08 node-1 puppet-user[9026]: Finished catalog run in 1.01 seconds
Oct 24 02:58:09 node-1 multipathd: uevent trigger error
Oct 24 02:58:09 node-1 puppet-user[9451]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 24 02:58:09 node-1 puppet-user[9451]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Oct 24 02:58:09 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 24 02:58:09 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 24 02:58:09 node-1 puppet-user[9451]: (/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"]'
Oct 24 02:58:09 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 24 02:58:09 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 24 02:58:09 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 24 02:58:09 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 24 02:58:09 node-1 puppet-user[9451]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 24 02:58:09 node-1 puppet-user[9451]: Finished catalog run in 0.06 seconds
Oct 24 02:58:11 node-1 puppet-user[9916]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 24 02:58:11 node-1 puppet-user[9916]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Oct 24 02:58:11 node-1 puppet-user[9916]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 24 02:58:11 node-1 puppet-user[9916]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 24 02:58:11 node-1 puppet-user[9916]: Finished catalog run in 0.05 seconds
Oct 24 02:58:12 node-1 puppet-user[10378]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 24 02:58:12 node-1 puppet-user[10378]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 24 02:58:13 node-1 puppet-user[10378]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 24 02:58:13 node-1 puppet-user[10378]: Finished catalog run in 0.05 seconds
Oct 24 02:58:14 node-1 puppet-user[10834]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 24 02:58:14 node-1 puppet-user[10834]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Oct 24 02:58:14 node-1 puppet-user[10834]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 24 02:58:15 node-1 puppet-user[10834]: (/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
Oct 24 02:58:15 node-1 puppet-user[10834]: (/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
Oct 24 02:58:15 node-1 puppet-user[10834]: Finished catalog run in 0.80 seconds
Oct 24 02:58:16 node-1 puppet-user[11460]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 24 02:58:16 node-1 puppet-user[11460]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Oct 24 02:58:17 node-1 puppet-user[11460]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Oct 24 02:58:17 node-1 puppet-user[11460]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 24 02:58:17 node-1 puppet-user[11460]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 24 02:58:17 node-1 puppet-user[11460]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Oct 24 02:58:17 node-1 puppet-user[11460]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 24 02:58:17 node-1 puppet-user[11460]: Finished catalog run in 0.29 seconds
Oct 24 02:58:18 node-1 puppet-user[11946]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 24 02:58:18 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 24 02:58:18 node-1 nailgun-agent: D, [2016-10-24T02:58:01.828360 #8970] DEBUG -- : Sleep for 17 seconds before sending request
Oct 24 02:58:18 node-1 nailgun-agent: I, [2016-10-24T02:58:18.841933 #8970]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 24 02:58:18 node-1 puppet-user[11946]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Oct 24 02:58:19 node-1 puppet-user[11946]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 24 02:58:19 node-1 kernel: [   70.082379] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 24 02:58:19 node-1 kernel: [   70.082436] 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.
Oct 24 02:58:19 node-1 puppet-user[11946]: (/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'
Oct 24 02:58:19 node-1 puppet-user[11946]: Finished catalog run in 0.06 seconds
Oct 24 02:58:19 node-1 nailgun-agent: D, [2016-10-24T02:58:19.241151 #8970] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 24 02:58:20 node-1 puppet-user[12531]: (Scope(Class[main])) MODULAR: sync_time
Oct 24 02:58:20 node-1 puppet-user[12531]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 24 02:58:20 node-1 ntpdate[12951]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 24 02:58:26 node-1 ntpdate[12951]: adjust time server 10.20.0.2 offset 0.001169 sec
Oct 24 02:58:26 node-1 puppet-user[12531]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 24 02:58:27 node-1 puppet-user[12531]: Finished catalog run in 6.19 seconds
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.116663 #8970] DEBUG -- : Trying to find block devices
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.116754 #8970] DEBUG -- : Found block device: sda
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.116821 #8970] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.116846 #8970] DEBUG -- : Trying to get list of physical devices
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.117026 #8970] DEBUG -- : Getting udev properties for device: sda
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.118933 #8970] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /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"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc7886
Oct 24 02:58:31 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"66478", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.118961 #8970] DEBUG -- : Trying to find out if device sda is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.119005 #8970] DEBUG -- : Device sda removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.119041 #8970] DEBUG -- : Device sda seems to be appropriate
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.119481 #8970] DEBUG -- : Getting udev properties for device: dm-0
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.121071 #8970] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-CtfzckGeYV7r19zQewO4N4dS0pdouCDbIeTQ1Bjyl17t7JE3dr8iHH5rUDMSNny5 /dev/disk/by-uuid/181f3e3b-23dd-43ea-9d2b-99ff917ab0cb /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-CtfzckGeYV7r19zQewO4N4dS0pdouCDbIeTQ1Bjyl17t7JE3dr8iHH5rUDMSNny5", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"181f3e3b-23dd-43ea-9d2b-99ff917ab0cb", "ID_FS_UUID_ENC"=>"181f3e3b-23dd-43ea-9d2b-99ff917ab0cb", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"46268", "nomdmonddf"=>"1", "nomd
Oct 24 02:58:31 node-1 nailgun-agent: monisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.121098 #8970] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.121141 #8970] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.121156 #8970] DEBUG -- : Device dm-0 seems to be appropriate
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.121194 #8970] DEBUG -- : Getting udev properties for device: dm-1
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.122704 #8970] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-6FCuU6jIDFGbuS0Ddr2qNcHCQyZtv49QRp3A3rmT0WnmqCvWQNpdUtxWe5PjxgV3 /dev/disk/by-uuid/f3638546-92bd-4600-bc87-922c7aa75a81 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-6FCuU6jIDFGbuS0Ddr2qNcHCQyZtv49QRp3A3rmT0WnmqCvWQNpdUtxWe5PjxgV3", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f3638546-92bd-4600-bc87-922c7aa75a81", "ID_FS_UUID_ENC"=>"f3638546-92bd-4600-bc87-922c7aa75a81", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56
Oct 24 02:58:31 node-1 nailgun-agent: 176", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.122788 #8970] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.122820 #8970] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.122835 #8970] DEBUG -- : Device dm-1 seems to be appropriate
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.122851 #8970] DEBUG -- : Getting udev properties for device: dm-2
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.124425 #8970] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-dYRmRLxdvypvrNSSl0yY0S38hW64o8o72OfTJu8fzgEKsfQMtNkHNA3S3wTGczz5 /dev/disk/by-uuid/17c214d0-e550-4953-82eb-90f2273acf64 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-dYRmRLxdvypvrNSSl0yY0S38hW64o8o72OfTJu8fzgEKsfQMtNkHNA3S3wTGczz5", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"17c214d0-e550-4953-82eb-90f2273acf64", "ID_FS_UUID_ENC"=>"17c214d0-e550-4953-82eb-90f2273acf64", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60990", "nomdmond
Oct 24 02:58:31 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.124464 #8970] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.124495 #8970] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.124509 #8970] DEBUG -- : Device dm-2 seems to be appropriate
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.124542 #8970] DEBUG -- : Getting udev properties for device: dm-3
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.126084 #8970] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-qxYzbXCJDyUPFqLVlS1yQLvairaTLEC6LhjUxjoyh0fRc3tH4s1tWEPkAatNyK5H /dev/disk/by-uuid/d39d1718-5d47-464e-bfc3-d1b480adfbce /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-qxYzbXCJDyUPFqLVlS1yQLvairaTLEC6LhjUxjoyh0fRc3tH4s1tWEPkAatNyK5H", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d39d1718-5d47-464e-bfc3-d1b480adfbce", "ID_FS_UUID_ENC"=>"d39d1718-5d47-464e-bfc3-d1b480adfbce", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59001", "nomdmonddf"=>"1", 
Oct 24 02:58:31 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.126111 #8970] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.126154 #8970] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.126187 #8970] DEBUG -- : Device dm-3 seems to be appropriate
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.126202 #8970] DEBUG -- : Getting udev properties for device: dm-4
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.127798 #8970] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-Xqywvvw98NUylZDTwAI3bqg1SAqch7Bi3UHYBnVEdNiTtSPkkde1W38iFVdAjJOr /dev/disk/by-uuid/5c8da145-f2cb-47df-87a8-1f6d3d105cfa /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-Xqywvvw98NUylZDTwAI3bqg1SAqch7Bi3UHYBnVEdNiTtSPkkde1W38iFVdAjJOr", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"5c8da145-f2cb-47df-87a8-1f6d3d105cfa", "ID_FS_UUID_ENC"=>"5c8da145-f2cb-47df-87a8-1f6d3d105cfa", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55083", "nomdmonddf"=>"1", "nomd
Oct 24 02:58:31 node-1 nailgun-agent: monisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.127840 #8970] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.127871 #8970] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.127885 #8970] DEBUG -- : Device dm-4 seems to be appropriate
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.127900 #8970] DEBUG -- : Getting udev properties for device: dm-5
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.129405 #8970] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-Xqywvvw98NUylZDTwAI3bqg1SAqch7BiHqAnDgxzGTFjQs4uXzm6i04inZh9nQZO /dev/disk/by-uuid/5a5ebd56-5d77-4c6f-b4e2-7e61692b7fe9 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-Xqywvvw98NUylZDTwAI3bqg1SAqch7BiHqAnDgxzGTFjQs4uXzm6i04inZh9nQZO", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"5a5ebd56-5d77-4c6f-b4e2-7e61692b7fe9", "ID_FS_UUID_ENC"=>"5a5ebd56-5d77-4c6f-b4e2-7e61692b7fe9", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55726", "nomdmonddf"=>"1", "nomdmonisw"
Oct 24 02:58:31 node-1 nailgun-agent: =>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.129432 #8970] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.129465 #8970] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.129531 #8970] DEBUG -- : Device dm-5 seems to be appropriate
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.129546 #8970] DEBUG -- : Getting udev properties for device: ram0
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.130924 #8970] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80877", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.130952 #8970] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.130987 #8970] DEBUG -- : Device ram0 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.131025 #8970] DEBUG -- : Getting udev properties for device: ram1
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.132415 #8970] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80949", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.132440 #8970] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.132475 #8970] DEBUG -- : Device ram1 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.132495 #8970] DEBUG -- : Getting udev properties for device: ram2
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.133876 #8970] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81746", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.133926 #8970] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.133964 #8970] DEBUG -- : Device ram2 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.134003 #8970] DEBUG -- : Getting udev properties for device: ram3
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.135451 #8970] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81818", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.135476 #8970] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.135512 #8970] DEBUG -- : Device ram3 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.135533 #8970] DEBUG -- : Getting udev properties for device: ram4
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.136910 #8970] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81929", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.136947 #8970] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.136980 #8970] DEBUG -- : Device ram4 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.137015 #8970] DEBUG -- : Getting udev properties for device: ram5
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.138384 #8970] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82021", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.138409 #8970] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.138443 #8970] DEBUG -- : Device ram5 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.138488 #8970] DEBUG -- : Getting udev properties for device: ram6
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.139860 #8970] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82120", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.139886 #8970] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.139920 #8970] DEBUG -- : Device ram6 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.139940 #8970] DEBUG -- : Getting udev properties for device: ram7
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.141306 #8970] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82224", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.141331 #8970] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.141380 #8970] DEBUG -- : Device ram7 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.141402 #8970] DEBUG -- : Getting udev properties for device: ram8
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.142779 #8970] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82338", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.142805 #8970] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.142839 #8970] DEBUG -- : Device ram8 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.142888 #8970] DEBUG -- : Getting udev properties for device: ram9
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.144274 #8970] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"82488", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.144300 #8970] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.144338 #8970] DEBUG -- : Device ram9 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.144367 #8970] DEBUG -- : Getting udev properties for device: loop0
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.145756 #8970] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79549", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.145781 #8970] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.145819 #8970] DEBUG -- : Device loop0 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.145855 #8970] DEBUG -- : Getting udev properties for device: loop1
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.147218 #8970] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79643", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.147251 #8970] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.147294 #8970] DEBUG -- : Device loop1 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.147315 #8970] DEBUG -- : Getting udev properties for device: loop2
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.148702 #8970] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79725", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.148727 #8970] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.148765 #8970] DEBUG -- : Device loop2 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.148786 #8970] DEBUG -- : Getting udev properties for device: loop3
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.150161 #8970] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79823", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.150194 #8970] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.150243 #8970] DEBUG -- : Device loop3 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.150262 #8970] DEBUG -- : Getting udev properties for device: loop4
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.151632 #8970] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79875", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.151673 #8970] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.151710 #8970] DEBUG -- : Device loop4 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.151739 #8970] DEBUG -- : Getting udev properties for device: loop5
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.153109 #8970] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79960", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.153134 #8970] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.153184 #8970] DEBUG -- : Device loop5 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.153205 #8970] DEBUG -- : Getting udev properties for device: loop6
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.154590 #8970] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80359", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.154622 #8970] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.154666 #8970] DEBUG -- : Device loop6 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.154697 #8970] DEBUG -- : Getting udev properties for device: loop7
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.156069 #8970] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"80761", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.156094 #8970] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.156170 #8970] DEBUG -- : Device loop7 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.156190 #8970] DEBUG -- : Getting udev properties for device: ram10
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.157620 #8970] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81043", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.157647 #8970] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.157678 #8970] DEBUG -- : Device ram10 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.157708 #8970] DEBUG -- : Getting udev properties for device: ram11
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.159057 #8970] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81165", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.159107 #8970] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.159161 #8970] DEBUG -- : Device ram11 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.159191 #8970] DEBUG -- : Getting udev properties for device: ram12
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.160572 #8970] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81277", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.160596 #8970] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.160645 #8970] DEBUG -- : Device ram12 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.160665 #8970] DEBUG -- : Getting udev properties for device: ram13
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.162038 #8970] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81458", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.162072 #8970] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.162112 #8970] DEBUG -- : Device ram13 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.162134 #8970] DEBUG -- : Getting udev properties for device: ram14
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.168580 #8970] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81549", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.168608 #8970] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.168652 #8970] DEBUG -- : Device ram14 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.168672 #8970] DEBUG -- : Getting udev properties for device: ram15
Oct 24 02:58:31 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170166 #8970] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81677", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170191 #8970] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170275 #8970] DEBUG -- : Device ram15 removable parameter: "0"
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170309 #8970] 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-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170324 #8970] DEBUG -- : Block device seems to be physical data storage: sda
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170370 #8970] DEBUG -- : Found block device: dm-0
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170384 #8970] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170397 #8970] DEBUG -- : Found block device: dm-1
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170407 #8970] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170415 #8970] DEBUG -- : Found block device: dm-2
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170423 #8970] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170469 #8970] DEBUG -- : Found block device: dm-3
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170479 #8970] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170487 #8970] DEBUG -- : Found block device: dm-4
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170496 #8970] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170504 #8970] DEBUG -- : Found block device: dm-5
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170513 #8970] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170521 #8970] DEBUG -- : Found block device: ram0
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170530 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170538 #8970] DEBUG -- : Found block device: ram1
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170575 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170584 #8970] DEBUG -- : Found block device: ram2
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170593 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170601 #8970] DEBUG -- : Found block device: ram3
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170610 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170618 #8970] DEBUG -- : Found block device: ram4
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170628 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170636 #8970] DEBUG -- : Found block device: ram5
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170646 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170654 #8970] DEBUG -- : Found block device: ram6
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170695 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170704 #8970] DEBUG -- : Found block device: ram7
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170712 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170720 #8970] DEBUG -- : Found block device: ram8
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170728 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170736 #8970] DEBUG -- : Found block device: ram9
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170745 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170753 #8970] DEBUG -- : Found block device: loop0
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170761 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170805 #8970] DEBUG -- : Found block device: loop1
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170814 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170822 #8970] DEBUG -- : Found block device: loop2
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170833 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170841 #8970] DEBUG -- : Found block device: loop3
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170849 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170858 #8970] DEBUG -- : Found block device: loop4
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170867 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170875 #8970] DEBUG -- : Found block device: loop5
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170910 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170918 #8970] DEBUG -- : Found block device: loop6
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170928 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170935 #8970] DEBUG -- : Found block device: loop7
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170944 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170952 #8970] DEBUG -- : Found block device: ram10
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170961 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170968 #8970] DEBUG -- : Found block device: ram11
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.170977 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.171013 #8970] DEBUG -- : Found block device: ram12
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.171024 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.171032 #8970] DEBUG -- : Found block device: ram13
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.171041 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.171049 #8970] DEBUG -- : Found block device: ram14
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.171058 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.171066 #8970] DEBUG -- : Found block device: ram15
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.171075 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.171102 #8970] 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-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.251733 #8970] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 24 02:58:31 node-1 nailgun-agent: D, [2016-10-24T02:58:31.251784 #8970] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 24 02:58:33 node-1 puppet-user[13503]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 24 02:58:33 node-1 puppet-user[13503]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Oct 24 02:58:33 node-1 puppet-user[13503]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 24 02:58:33 node-1 puppet-user[13503]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Oct 24 02:58:34 node-1 puppet-user[13503]: Finished catalog run in 0.08 seconds
Oct 24 02:58:35 node-1 puppet-user[13965]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 24 02:58:35 node-1 puppet-user[13965]: Compiled catalog for node-1.domain.tld in environment production in 0.54 seconds
Oct 24 02:58:36 node-1 puppet-user[13965]: (/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
Oct 24 02:58:36 node-1 puppet-user[13965]: (/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
Oct 24 02:58:36 node-1 puppet-user[13965]: (/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
Oct 24 02:58:36 node-1 puppet-user[13965]: (/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
Oct 24 02:58:36 node-1 puppet-user[13965]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 24 02:58:36 node-1 puppet-user[13965]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct 24 02:58:36 node-1 puppet-user[13965]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 24 02:58:36 node-1 puppet-user[13965]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct 24 02:58:36 node-1 puppet-user[13965]: (/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
Oct 24 02:58:36 node-1 puppet-user[13965]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct 24 02:58:36 node-1 puppet-user[13965]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 24 02:58:36 node-1 puppet-user[13965]: Finished catalog run in 0.87 seconds
Oct 24 02:58:38 node-1 puppet-user[14483]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 24 02:58:38 node-1 puppet-user[14483]: Compiled catalog for node-1.domain.tld in environment production in 0.12 seconds
Oct 24 02:58:40 node-1 kernel: [   91.308017] init: plymouth-upstart-bridge main process ended, respawning
Oct 24 02:58:40 node-1 puppet-agent[8936]: Could not run: SIGTERM
Oct 24 02:58:40 node-1 kernel: [   91.611142] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 24 02:58:40 node-1 ec2: 
Oct 24 02:58:40 node-1 ec2: #############################################################
Oct 24 02:58:40 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 24 02:58:40 node-1 ec2: 1024 34:fa:08:02:05:2b:1f:ee:f7:50:0d:02:af:ba:ec:ab  root@node-1.domain.tld (DSA)
Oct 24 02:58:40 node-1 ec2: 256 6f:6d:f8:fb:c2:69:b7:7c:40:fb:85:db:f9:34:8f:cd  root@node-1.domain.tld (ECDSA)
Oct 24 02:58:40 node-1 ec2: 256 d2:8f:28:6f:84:fb:68:f2:d2:48:5a:18:1c:73:f8:53  root@node-1.domain.tld (ED25519)
Oct 24 02:58:40 node-1 ec2: 2048 ef:17:0c:e0:5e:a0:e7:45:00:50:12:2c:8e:1f:71:17  root@node-1.domain.tld (RSA)
Oct 24 02:58:40 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 24 02:58:40 node-1 ec2: #############################################################
Oct 24 02:58:41 node-1 puppet-user[14483]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 24 02:58:43 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285309 #8970] DEBUG -- : Trying to find block devices
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285450 #8970] DEBUG -- : Found block device: sda
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285480 #8970] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285511 #8970] DEBUG -- : Block device seems to be physical data storage: sda
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285533 #8970] DEBUG -- : Found block device: dm-0
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285547 #8970] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285579 #8970] DEBUG -- : Found block device: dm-1
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285590 #8970] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285599 #8970] DEBUG -- : Found block device: dm-2
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285610 #8970] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285619 #8970] DEBUG -- : Found block device: dm-3
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285629 #8970] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285638 #8970] DEBUG -- : Found block device: dm-4
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285648 #8970] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285656 #8970] DEBUG -- : Found block device: dm-5
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285689 #8970] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285699 #8970] DEBUG -- : Found block device: ram0
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285709 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285718 #8970] DEBUG -- : Found block device: ram1
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285728 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285736 #8970] DEBUG -- : Found block device: ram2
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285745 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285753 #8970] DEBUG -- : Found block device: ram3
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285785 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285794 #8970] DEBUG -- : Found block device: ram4
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285803 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285812 #8970] DEBUG -- : Found block device: ram5
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285821 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285830 #8970] DEBUG -- : Found block device: ram6
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285839 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285847 #8970] DEBUG -- : Found block device: ram7
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285885 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285895 #8970] DEBUG -- : Found block device: ram8
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285905 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285913 #8970] DEBUG -- : Found block device: ram9
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285922 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285930 #8970] DEBUG -- : Found block device: loop0
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285939 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285948 #8970] DEBUG -- : Found block device: loop1
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285956 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285965 #8970] DEBUG -- : Found block device: loop2
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.285999 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286008 #8970] DEBUG -- : Found block device: loop3
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286017 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286026 #8970] DEBUG -- : Found block device: loop4
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286035 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286043 #8970] DEBUG -- : Found block device: loop5
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286052 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286060 #8970] DEBUG -- : Found block device: loop6
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286070 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286096 #8970] DEBUG -- : Found block device: loop7
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286107 #8970] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286115 #8970] DEBUG -- : Found block device: ram10
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286125 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286132 #8970] DEBUG -- : Found block device: ram11
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286141 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286175 #8970] DEBUG -- : Found block device: ram12
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286185 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286193 #8970] DEBUG -- : Found block device: ram13
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286203 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286211 #8970] DEBUG -- : Found block device: ram14
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286221 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286228 #8970] DEBUG -- : Found block device: ram15
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286237 #8970] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.286265 #8970] 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-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Oct 24 02:58:43 node-1 nailgun-agent: D, [2016-10-24T02:58:43.436985 #8970] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct 24 02:58:43 node-1 nailgun-agent: I, [2016-10-24T02:58:43.437137 #8970]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 24 02:59:01 node-1 CRON[16620]: (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")
Oct 24 02:59:08 node-1 puppet-user[14483]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 24 02:59:08 node-1 puppet-user[14483]: Finished catalog run in 29.70 seconds
Oct 24 02:59:10 node-1 puppet-user[17164]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 24 02:59:10 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 24 02:59:10 node-1 nailgun-agent: I, [2016-10-24T02:59:10.621157 #16627]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 24 02:59:10 node-1 puppet-user[17164]: Compiled catalog for node-1.domain.tld in environment production in 0.62 seconds
Oct 24 02:59:11 node-1 puppet-user[17164]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 24 02:59:11 node-1 puppet-user[17164]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 24 02:59:11 node-1 puppet-user[17164]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 24 02:59:11 node-1 puppet-user[17164]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 24 02:59:11 node-1 puppet-user[17164]: Finished catalog run in 0.08 seconds
Oct 24 02:59:12 node-1 puppet-user[17759]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 24 02:59:13 node-1 puppet-user[17759]: Compiled catalog for node-1.domain.tld in environment production in 0.84 seconds
Oct 24 02:59:13 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 24 02:59:14 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 24 02:59:14 node-1 crontab[18204]: (root) LIST (root)
Oct 24 02:59:14 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 24 02:59:14 node-1 crontab[18205]: (root) REPLACE (root)
Oct 24 02:59:15 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 24 02:59:15 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 24 02:59:15 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 24 02:59:15 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 24 02:59:15 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 24 02:59:15 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 24 02:59:15 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 24 02:59:15 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 24 02:59:15 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/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
Oct 24 02:59:16 node-1 puppet-user[17759]: (/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
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/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
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/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
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/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
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/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
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/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
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/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
Oct 24 02:59:16 node-1 puppet-user[17759]: (/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
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 24 02:59:16 node-1 puppet-user[17759]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct 24 02:59:16 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8386" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 24 02:59:16 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 24 02:59:18 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:18 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:18 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:18 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:18 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:31 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:31 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:31 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:31 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:31 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:33 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:33 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:33 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:33 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:33 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:33 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:36 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:36 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:36 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:36 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:36 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:36 node-1 multipathd: uevent trigger error
<27>Oct 24 02:59:36 node-1 multipathd: uevent trigger error
<27>Oct 24 03:00:31 node-1 ntpdate[29102]: no servers can be used, exiting
<27>Oct 24 03:00:31 node-1 ntpdate[29347]: no servers can be used, exiting
<27>Oct 24 03:01:02 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:17 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:17 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:17 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:17 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:17 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:01:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:25 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 24 03:02:25 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 24 03:02:31 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 24 03:02:31 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 24 03:02:37 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 24 03:02:42 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 24 03:02:42 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 24 03:02:50 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:50 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:50 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:50 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:50 node-1 multipathd: uevent trigger error
<27>Oct 24 03:02:51 node-1 ntpdate[15012]: the NTP socket is in use, exiting
<27>Oct 24 03:02:51 node-1 ntpdate[15070]: the NTP socket is in use, exiting
<27>Oct 24 03:03:02 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:08 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:08 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:08 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:08 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:08 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:08 node-1 multipathd: uevent trigger error
<129>Oct 24 03:03:10 node-1 haproxy[19102]: 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>Oct 24 03:03:11 node-1 haproxy[19108]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:11 node-1 haproxy[19108]: Backup Server mysqld/node-3 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>Oct 24 03:03:11 node-1 haproxy[19108]: proxy mysqld has no server available!
<27>Oct 24 03:03:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:17 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:17 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:17 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:17 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:17 node-1 multipathd: uevent trigger error
<129>Oct 24 03:03:20 node-1 haproxy[21907]: 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>Oct 24 03:03:20 node-1 haproxy[21907]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:20 node-1 haproxy[21907]: Backup Server mysqld/node-3 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>Oct 24 03:03:20 node-1 haproxy[21907]: proxy mysqld has no server available!
<129>Oct 24 03:03:20 node-1 haproxy[21907]: 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>Oct 24 03:03:21 node-1 haproxy[21911]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:21 node-1 haproxy[21911]: Server object-storage/node-3 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>Oct 24 03:03:21 node-1 haproxy[21911]: proxy object-storage has no server available!
<27>Oct 24 03:03:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:23 node-1 multipathd: uevent trigger error
<129>Oct 24 03:03:25 node-1 haproxy[23281]: 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>Oct 24 03:03:25 node-1 haproxy[23281]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:25 node-1 haproxy[23281]: Server neutron/node-3 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>Oct 24 03:03:25 node-1 haproxy[23281]: proxy neutron has no server available!
<129>Oct 24 03:03:25 node-1 haproxy[23281]: 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>Oct 24 03:03:26 node-1 haproxy[23285]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:26 node-1 haproxy[23285]: Backup Server mysqld/node-3 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>Oct 24 03:03:26 node-1 haproxy[23285]: proxy mysqld has no server available!
<129>Oct 24 03:03:26 node-1 haproxy[23285]: 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>Oct 24 03:03:26 node-1 haproxy[23285]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:26 node-1 haproxy[23285]: Server object-storage/node-3 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>Oct 24 03:03:26 node-1 haproxy[23285]: proxy object-storage has no server available!
<27>Oct 24 03:03:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:28 node-1 multipathd: uevent trigger error
<129>Oct 24 03:03:31 node-1 haproxy[24665]: 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>Oct 24 03:03:31 node-1 haproxy[24665]: Server keystone-1/node-2 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>Oct 24 03:03:31 node-1 haproxy[24665]: Server keystone-1/node-3 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>Oct 24 03:03:31 node-1 haproxy[24665]: proxy keystone-1 has no server available!
<129>Oct 24 03:03:31 node-1 haproxy[24665]: 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>Oct 24 03:03:31 node-1 haproxy[24665]: Server keystone-2/node-2 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>Oct 24 03:03:31 node-1 haproxy[24665]: Server keystone-2/node-3 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>Oct 24 03:03:31 node-1 haproxy[24665]: proxy keystone-2 has no server available!
<129>Oct 24 03:03:31 node-1 haproxy[24665]: 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>Oct 24 03:03:31 node-1 haproxy[24665]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:31 node-1 haproxy[24665]: Server neutron/node-3 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>Oct 24 03:03:31 node-1 haproxy[24665]: proxy neutron has no server available!
<129>Oct 24 03:03:32 node-1 haproxy[24669]: 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>Oct 24 03:03:32 node-1 haproxy[24669]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:32 node-1 haproxy[24669]: Backup Server mysqld/node-3 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>Oct 24 03:03:32 node-1 haproxy[24669]: proxy mysqld has no server available!
<129>Oct 24 03:03:32 node-1 haproxy[24669]: 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>Oct 24 03:03:32 node-1 haproxy[24669]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:32 node-1 haproxy[24669]: Server object-storage/node-3 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>Oct 24 03:03:32 node-1 haproxy[24669]: proxy object-storage has no server available!
<27>Oct 24 03:03:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:34 node-1 multipathd: uevent trigger error
<129>Oct 24 03:03:36 node-1 haproxy[26012]: 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>Oct 24 03:03:36 node-1 haproxy[26012]: Server keystone-1/node-2 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>Oct 24 03:03:36 node-1 haproxy[26012]: Server keystone-1/node-3 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>Oct 24 03:03:36 node-1 haproxy[26012]: proxy keystone-1 has no server available!
<129>Oct 24 03:03:36 node-1 haproxy[26012]: 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>Oct 24 03:03:36 node-1 haproxy[26012]: Server keystone-2/node-2 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>Oct 24 03:03:36 node-1 haproxy[26012]: Server keystone-2/node-3 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>Oct 24 03:03:36 node-1 haproxy[26012]: proxy keystone-2 has no server available!
<129>Oct 24 03:03:37 node-1 haproxy[26016]: 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>Oct 24 03:03:37 node-1 haproxy[26016]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:37 node-1 haproxy[26016]: Server neutron/node-3 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>Oct 24 03:03:37 node-1 haproxy[26016]: proxy neutron has no server available!
<129>Oct 24 03:03:37 node-1 haproxy[26016]: 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>Oct 24 03:03:37 node-1 haproxy[26016]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:37 node-1 haproxy[26016]: Backup Server mysqld/node-3 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>Oct 24 03:03:37 node-1 haproxy[26016]: proxy mysqld has no server available!
<129>Oct 24 03:03:37 node-1 haproxy[26016]: 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>Oct 24 03:03:37 node-1 haproxy[26016]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:37 node-1 haproxy[26016]: Server object-storage/node-3 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>Oct 24 03:03:37 node-1 haproxy[26016]: proxy object-storage has no server available!
<129>Oct 24 03:03:37 node-1 haproxy[26016]: 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>Oct 24 03:03:38 node-1 haproxy[26016]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:38 node-1 haproxy[26016]: Server aodh/node-3 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>Oct 24 03:03:38 node-1 haproxy[26016]: proxy aodh has no server available!
<27>Oct 24 03:03:39 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:39 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:39 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:39 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:39 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:39 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:39 node-1 multipathd: uevent trigger error
<129>Oct 24 03:03:41 node-1 haproxy[27371]: 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>Oct 24 03:03:42 node-1 haproxy[27375]: Server keystone-1/node-2 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>Oct 24 03:03:42 node-1 haproxy[27375]: Server keystone-1/node-3 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>Oct 24 03:03:42 node-1 haproxy[27375]: proxy keystone-1 has no server available!
<129>Oct 24 03:03:42 node-1 haproxy[27375]: 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>Oct 24 03:03:42 node-1 haproxy[27375]: Server keystone-2/node-2 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>Oct 24 03:03:42 node-1 haproxy[27375]: Server keystone-2/node-3 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>Oct 24 03:03:42 node-1 haproxy[27375]: proxy keystone-2 has no server available!
<129>Oct 24 03:03:42 node-1 haproxy[27375]: 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>Oct 24 03:03:42 node-1 haproxy[27375]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:42 node-1 haproxy[27375]: Server neutron/node-3 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>Oct 24 03:03:42 node-1 haproxy[27375]: proxy neutron has no server available!
<129>Oct 24 03:03:42 node-1 haproxy[27375]: 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>Oct 24 03:03:42 node-1 haproxy[27375]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:42 node-1 haproxy[27375]: Backup Server mysqld/node-3 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>Oct 24 03:03:42 node-1 haproxy[27375]: proxy mysqld has no server available!
<129>Oct 24 03:03:43 node-1 haproxy[27375]: 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>Oct 24 03:03:43 node-1 haproxy[27375]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:43 node-1 haproxy[27375]: Server object-storage/node-3 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>Oct 24 03:03:43 node-1 haproxy[27375]: proxy object-storage has no server available!
<129>Oct 24 03:03:43 node-1 haproxy[27375]: 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>Oct 24 03:03:43 node-1 haproxy[27375]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:43 node-1 haproxy[27375]: Server aodh/node-3 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>Oct 24 03:03:43 node-1 haproxy[27375]: proxy aodh has no server available!
<129>Oct 24 03:03:43 node-1 haproxy[27375]: 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>Oct 24 03:03:43 node-1 haproxy[27375]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:43 node-1 haproxy[27375]: Server ceilometer/node-3 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>Oct 24 03:03:43 node-1 haproxy[27375]: proxy ceilometer has no server available!
<27>Oct 24 03:03:45 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:45 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:45 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:45 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:45 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:45 node-1 multipathd: uevent trigger error
<129>Oct 24 03:03:47 node-1 haproxy[28744]: 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>Oct 24 03:03:47 node-1 haproxy[28744]: Server keystone-1/node-2 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>Oct 24 03:03:47 node-1 haproxy[28744]: Server keystone-1/node-3 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>Oct 24 03:03:47 node-1 haproxy[28744]: proxy keystone-1 has no server available!
<129>Oct 24 03:03:47 node-1 haproxy[28744]: 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>Oct 24 03:03:48 node-1 haproxy[28749]: Server keystone-2/node-2 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>Oct 24 03:03:48 node-1 haproxy[28749]: Server keystone-2/node-3 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>Oct 24 03:03:48 node-1 haproxy[28749]: proxy keystone-2 has no server available!
<129>Oct 24 03:03:48 node-1 haproxy[28749]: 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>Oct 24 03:03:48 node-1 haproxy[28749]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:48 node-1 haproxy[28749]: Server neutron/node-3 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>Oct 24 03:03:48 node-1 haproxy[28749]: proxy neutron has no server available!
<129>Oct 24 03:03:48 node-1 haproxy[28749]: 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>Oct 24 03:03:48 node-1 haproxy[28749]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:48 node-1 haproxy[28749]: Backup Server mysqld/node-3 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>Oct 24 03:03:48 node-1 haproxy[28749]: proxy mysqld has no server available!
<129>Oct 24 03:03:48 node-1 haproxy[28749]: 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>Oct 24 03:03:48 node-1 haproxy[28749]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:48 node-1 haproxy[28749]: Server object-storage/node-3 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>Oct 24 03:03:48 node-1 haproxy[28749]: proxy object-storage has no server available!
<129>Oct 24 03:03:49 node-1 haproxy[28749]: 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>Oct 24 03:03:49 node-1 haproxy[28749]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:49 node-1 haproxy[28749]: Server aodh/node-3 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>Oct 24 03:03:49 node-1 haproxy[28749]: proxy aodh has no server available!
<129>Oct 24 03:03:49 node-1 haproxy[28749]: 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>Oct 24 03:03:49 node-1 haproxy[28749]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:49 node-1 haproxy[28749]: Server ceilometer/node-3 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>Oct 24 03:03:49 node-1 haproxy[28749]: proxy ceilometer has no server available!
<27>Oct 24 03:03:51 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:51 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:51 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:51 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:51 node-1 multipathd: uevent trigger error
<129>Oct 24 03:03:53 node-1 haproxy[30119]: 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>Oct 24 03:03:53 node-1 haproxy[30119]: 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>Oct 24 03:03:53 node-1 haproxy[30119]: Server keystone-1/node-2 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>Oct 24 03:03:53 node-1 haproxy[30119]: Server keystone-1/node-3 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>Oct 24 03:03:53 node-1 haproxy[30119]: proxy keystone-1 has no server available!
<129>Oct 24 03:03:53 node-1 haproxy[30119]: 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>Oct 24 03:03:53 node-1 haproxy[30119]: Server keystone-2/node-2 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>Oct 24 03:03:54 node-1 haproxy[30127]: Server keystone-2/node-3 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>Oct 24 03:03:54 node-1 haproxy[30127]: proxy keystone-2 has no server available!
<129>Oct 24 03:03:54 node-1 haproxy[30127]: 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>Oct 24 03:03:54 node-1 haproxy[30127]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:54 node-1 haproxy[30127]: Server neutron/node-3 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>Oct 24 03:03:54 node-1 haproxy[30127]: proxy neutron has no server available!
<129>Oct 24 03:03:54 node-1 haproxy[30127]: 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>Oct 24 03:03:54 node-1 haproxy[30127]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:54 node-1 haproxy[30127]: Backup Server mysqld/node-3 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>Oct 24 03:03:54 node-1 haproxy[30127]: proxy mysqld has no server available!
<129>Oct 24 03:03:54 node-1 haproxy[30127]: 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>Oct 24 03:03:54 node-1 haproxy[30127]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:54 node-1 haproxy[30127]: Server object-storage/node-3 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>Oct 24 03:03:54 node-1 haproxy[30127]: proxy object-storage has no server available!
<129>Oct 24 03:03:54 node-1 haproxy[30127]: 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>Oct 24 03:03:54 node-1 haproxy[30127]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:54 node-1 haproxy[30127]: Server aodh/node-3 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>Oct 24 03:03:54 node-1 haproxy[30127]: proxy aodh has no server available!
<129>Oct 24 03:03:55 node-1 haproxy[30127]: 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>Oct 24 03:03:55 node-1 haproxy[30127]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:03:55 node-1 haproxy[30127]: Server ceilometer/node-3 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>Oct 24 03:03:55 node-1 haproxy[30127]: proxy ceilometer has no server available!
<27>Oct 24 03:03:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:03:57 node-1 multipathd: uevent trigger error
<129>Oct 24 03:04:00 node-1 haproxy[31534]: 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>Oct 24 03:04:00 node-1 haproxy[31534]: 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>Oct 24 03:04:00 node-1 haproxy[31534]: Server keystone-1/node-2 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>Oct 24 03:04:00 node-1 haproxy[31534]: Server keystone-1/node-3 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>Oct 24 03:04:00 node-1 haproxy[31534]: proxy keystone-1 has no server available!
<129>Oct 24 03:04:00 node-1 haproxy[31534]: 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>Oct 24 03:04:00 node-1 haproxy[31534]: Server keystone-2/node-2 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>Oct 24 03:04:00 node-1 haproxy[31534]: Server keystone-2/node-3 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>Oct 24 03:04:00 node-1 haproxy[31534]: proxy keystone-2 has no server available!
<129>Oct 24 03:04:00 node-1 haproxy[31534]: 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>Oct 24 03:04:00 node-1 haproxy[31534]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:00 node-1 haproxy[31534]: Server glance-api/node-3 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>Oct 24 03:04:00 node-1 haproxy[31534]: proxy glance-api has no server available!
<129>Oct 24 03:04:00 node-1 haproxy[31534]: 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>Oct 24 03:04:01 node-1 haproxy[31539]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:01 node-1 haproxy[31539]: Server glance-glare/node-3 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>Oct 24 03:04:01 node-1 haproxy[31539]: proxy glance-glare has no server available!
<129>Oct 24 03:04:01 node-1 haproxy[31539]: 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>Oct 24 03:04:01 node-1 haproxy[31539]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:01 node-1 haproxy[31539]: Server neutron/node-3 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>Oct 24 03:04:01 node-1 haproxy[31539]: proxy neutron has no server available!
<129>Oct 24 03:04:01 node-1 haproxy[31539]: 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>Oct 24 03:04:01 node-1 haproxy[31539]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:01 node-1 haproxy[31539]: Server glance-registry/node-3 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>Oct 24 03:04:01 node-1 haproxy[31539]: proxy glance-registry has no server available!
<129>Oct 24 03:04:01 node-1 haproxy[31539]: 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>Oct 24 03:04:01 node-1 haproxy[31539]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:01 node-1 haproxy[31539]: Backup Server mysqld/node-3 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>Oct 24 03:04:01 node-1 haproxy[31539]: proxy mysqld has no server available!
<129>Oct 24 03:04:01 node-1 haproxy[31539]: 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>Oct 24 03:04:01 node-1 haproxy[31539]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:01 node-1 haproxy[31539]: Server object-storage/node-3 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>Oct 24 03:04:01 node-1 haproxy[31539]: proxy object-storage has no server available!
<129>Oct 24 03:04:01 node-1 haproxy[31539]: 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>Oct 24 03:04:01 node-1 haproxy[31539]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:01 node-1 haproxy[31539]: Server aodh/node-3 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>Oct 24 03:04:01 node-1 haproxy[31539]: proxy aodh has no server available!
<129>Oct 24 03:04:02 node-1 haproxy[31539]: 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>Oct 24 03:04:02 node-1 haproxy[31539]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:02 node-1 haproxy[31539]: Server ceilometer/node-3 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>Oct 24 03:04:02 node-1 haproxy[31539]: proxy ceilometer has no server available!
<27>Oct 24 03:04:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:03 node-1 multipathd: uevent trigger error
<129>Oct 24 03:04:06 node-1 haproxy[629]: 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>Oct 24 03:04:06 node-1 haproxy[629]: 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>Oct 24 03:04:06 node-1 haproxy[629]: Server keystone-1/node-2 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>Oct 24 03:04:06 node-1 haproxy[629]: Server keystone-1/node-3 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>Oct 24 03:04:06 node-1 haproxy[629]: proxy keystone-1 has no server available!
<129>Oct 24 03:04:06 node-1 haproxy[629]: 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>Oct 24 03:04:06 node-1 haproxy[629]: Server keystone-2/node-2 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>Oct 24 03:04:06 node-1 haproxy[629]: Server keystone-2/node-3 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>Oct 24 03:04:06 node-1 haproxy[629]: proxy keystone-2 has no server available!
<129>Oct 24 03:04:06 node-1 haproxy[629]: 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>Oct 24 03:04:06 node-1 haproxy[629]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:06 node-1 haproxy[629]: Server nova-api/node-3 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>Oct 24 03:04:06 node-1 haproxy[629]: proxy nova-api has no server available!
<129>Oct 24 03:04:06 node-1 haproxy[629]: 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>Oct 24 03:04:06 node-1 haproxy[629]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:06 node-1 haproxy[629]: Server nova-metadata-api/node-3 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>Oct 24 03:04:06 node-1 haproxy[629]: proxy nova-metadata-api has no server available!
<129>Oct 24 03:04:06 node-1 haproxy[629]: 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>Oct 24 03:04:06 node-1 haproxy[629]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:06 node-1 haproxy[629]: Server glance-api/node-3 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>Oct 24 03:04:06 node-1 haproxy[629]: proxy glance-api has no server available!
<129>Oct 24 03:04:06 node-1 haproxy[629]: 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>Oct 24 03:04:06 node-1 haproxy[629]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:06 node-1 haproxy[629]: Server glance-glare/node-3 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>Oct 24 03:04:06 node-1 haproxy[629]: proxy glance-glare has no server available!
<129>Oct 24 03:04:07 node-1 haproxy[633]: 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>Oct 24 03:04:07 node-1 haproxy[633]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:07 node-1 haproxy[633]: Server neutron/node-3 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>Oct 24 03:04:07 node-1 haproxy[633]: proxy neutron has no server available!
<129>Oct 24 03:04:07 node-1 haproxy[633]: 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>Oct 24 03:04:07 node-1 haproxy[633]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:07 node-1 haproxy[633]: Server glance-registry/node-3 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>Oct 24 03:04:07 node-1 haproxy[633]: proxy glance-registry has no server available!
<129>Oct 24 03:04:07 node-1 haproxy[633]: 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>Oct 24 03:04:07 node-1 haproxy[633]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:07 node-1 haproxy[633]: Backup Server mysqld/node-3 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>Oct 24 03:04:07 node-1 haproxy[633]: proxy mysqld has no server available!
<129>Oct 24 03:04:07 node-1 haproxy[633]: 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>Oct 24 03:04:07 node-1 haproxy[633]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:07 node-1 haproxy[633]: Server object-storage/node-3 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>Oct 24 03:04:07 node-1 haproxy[633]: proxy object-storage has no server available!
<129>Oct 24 03:04:07 node-1 haproxy[633]: 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>Oct 24 03:04:07 node-1 haproxy[633]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:07 node-1 haproxy[633]: Server aodh/node-3 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>Oct 24 03:04:07 node-1 haproxy[633]: proxy aodh has no server available!
<129>Oct 24 03:04:07 node-1 haproxy[633]: 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>Oct 24 03:04:07 node-1 haproxy[633]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:07 node-1 haproxy[633]: Server ceilometer/node-3 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>Oct 24 03:04:07 node-1 haproxy[633]: proxy ceilometer has no server available!
<129>Oct 24 03:04:07 node-1 haproxy[633]: 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>Oct 24 03:04:07 node-1 haproxy[633]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:07 node-1 haproxy[633]: Server nova-novncproxy/node-3 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>Oct 24 03:04:07 node-1 haproxy[633]: proxy nova-novncproxy has no server available!
<27>Oct 24 03:04:09 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:09 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:09 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:09 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:09 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:09 node-1 multipathd: uevent trigger error
<129>Oct 24 03:04:11 node-1 haproxy[2022]: 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>Oct 24 03:04:11 node-1 haproxy[2022]: 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>Oct 24 03:04:11 node-1 haproxy[2022]: Server keystone-1/node-2 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>Oct 24 03:04:11 node-1 haproxy[2022]: Server keystone-1/node-3 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>Oct 24 03:04:11 node-1 haproxy[2022]: proxy keystone-1 has no server available!
<129>Oct 24 03:04:11 node-1 haproxy[2022]: 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>Oct 24 03:04:11 node-1 haproxy[2022]: Server keystone-2/node-2 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>Oct 24 03:04:11 node-1 haproxy[2022]: Server keystone-2/node-3 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>Oct 24 03:04:11 node-1 haproxy[2022]: proxy keystone-2 has no server available!
<129>Oct 24 03:04:11 node-1 haproxy[2022]: 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>Oct 24 03:04:11 node-1 haproxy[2022]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:11 node-1 haproxy[2022]: Server nova-api/node-3 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>Oct 24 03:04:11 node-1 haproxy[2022]: proxy nova-api has no server available!
<129>Oct 24 03:04:11 node-1 haproxy[2022]: 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>Oct 24 03:04:11 node-1 haproxy[2022]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:11 node-1 haproxy[2022]: Server nova-metadata-api/node-3 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>Oct 24 03:04:11 node-1 haproxy[2022]: proxy nova-metadata-api has no server available!
<129>Oct 24 03:04:11 node-1 haproxy[2022]: 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>Oct 24 03:04:11 node-1 haproxy[2022]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:11 node-1 haproxy[2022]: Backup Server cinder-api/node-3 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>Oct 24 03:04:11 node-1 haproxy[2022]: proxy cinder-api has no server available!
<129>Oct 24 03:04:12 node-1 haproxy[2026]: 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>Oct 24 03:04:12 node-1 haproxy[2026]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:12 node-1 haproxy[2026]: Server glance-api/node-3 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>Oct 24 03:04:12 node-1 haproxy[2026]: proxy glance-api has no server available!
<129>Oct 24 03:04:12 node-1 haproxy[2026]: 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>Oct 24 03:04:12 node-1 haproxy[2026]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:12 node-1 haproxy[2026]: Server glance-glare/node-3 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>Oct 24 03:04:12 node-1 haproxy[2026]: proxy glance-glare has no server available!
<129>Oct 24 03:04:12 node-1 haproxy[2026]: 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>Oct 24 03:04:12 node-1 haproxy[2026]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:12 node-1 haproxy[2026]: Server neutron/node-3 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>Oct 24 03:04:12 node-1 haproxy[2026]: proxy neutron has no server available!
<129>Oct 24 03:04:12 node-1 haproxy[2026]: 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>Oct 24 03:04:12 node-1 haproxy[2026]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:12 node-1 haproxy[2026]: Server glance-registry/node-3 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>Oct 24 03:04:12 node-1 haproxy[2026]: proxy glance-registry has no server available!
<129>Oct 24 03:04:12 node-1 haproxy[2026]: 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>Oct 24 03:04:12 node-1 haproxy[2026]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:12 node-1 haproxy[2026]: Backup Server mysqld/node-3 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>Oct 24 03:04:12 node-1 haproxy[2026]: proxy mysqld has no server available!
<129>Oct 24 03:04:12 node-1 haproxy[2026]: 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>Oct 24 03:04:12 node-1 haproxy[2026]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:12 node-1 haproxy[2026]: Server object-storage/node-3 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>Oct 24 03:04:12 node-1 haproxy[2026]: proxy object-storage has no server available!
<129>Oct 24 03:04:12 node-1 haproxy[2026]: 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>Oct 24 03:04:12 node-1 haproxy[2026]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:12 node-1 haproxy[2026]: Server aodh/node-3 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>Oct 24 03:04:12 node-1 haproxy[2026]: proxy aodh has no server available!
<129>Oct 24 03:04:12 node-1 haproxy[2026]: 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>Oct 24 03:04:12 node-1 haproxy[2026]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:13 node-1 haproxy[2026]: Server ceilometer/node-3 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>Oct 24 03:04:13 node-1 haproxy[2026]: proxy ceilometer has no server available!
<129>Oct 24 03:04:13 node-1 haproxy[2026]: 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>Oct 24 03:04:13 node-1 haproxy[2026]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:13 node-1 haproxy[2026]: Server nova-novncproxy/node-3 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>Oct 24 03:04:13 node-1 haproxy[2026]: proxy nova-novncproxy has no server available!
<27>Oct 24 03:04:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:14 node-1 multipathd: uevent trigger error
<129>Oct 24 03:04:17 node-1 haproxy[3625]: 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>Oct 24 03:04:17 node-1 haproxy[3625]: 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>Oct 24 03:04:17 node-1 haproxy[3625]: Server keystone-1/node-2 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>Oct 24 03:04:17 node-1 haproxy[3625]: Server keystone-1/node-3 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>Oct 24 03:04:17 node-1 haproxy[3625]: proxy keystone-1 has no server available!
<129>Oct 24 03:04:17 node-1 haproxy[3625]: 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>Oct 24 03:04:17 node-1 haproxy[3625]: Server keystone-2/node-2 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>Oct 24 03:04:17 node-1 haproxy[3625]: Server keystone-2/node-3 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>Oct 24 03:04:17 node-1 haproxy[3625]: proxy keystone-2 has no server available!
<129>Oct 24 03:04:17 node-1 haproxy[3625]: 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>Oct 24 03:04:17 node-1 haproxy[3625]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:17 node-1 haproxy[3625]: Server nova-api/node-3 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>Oct 24 03:04:17 node-1 haproxy[3625]: proxy nova-api has no server available!
<129>Oct 24 03:04:17 node-1 haproxy[3625]: 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>Oct 24 03:04:17 node-1 haproxy[3625]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:17 node-1 haproxy[3625]: Server nova-metadata-api/node-3 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>Oct 24 03:04:17 node-1 haproxy[3625]: proxy nova-metadata-api has no server available!
<129>Oct 24 03:04:17 node-1 haproxy[3625]: 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>Oct 24 03:04:17 node-1 haproxy[3625]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:17 node-1 haproxy[3625]: Backup Server cinder-api/node-3 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>Oct 24 03:04:17 node-1 haproxy[3625]: proxy cinder-api has no server available!
<129>Oct 24 03:04:17 node-1 haproxy[3625]: 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>Oct 24 03:04:18 node-1 haproxy[3631]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:18 node-1 haproxy[3631]: Server glance-api/node-3 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>Oct 24 03:04:18 node-1 haproxy[3631]: proxy glance-api has no server available!
<129>Oct 24 03:04:18 node-1 haproxy[3631]: 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>Oct 24 03:04:18 node-1 haproxy[3631]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:18 node-1 haproxy[3631]: Server glance-glare/node-3 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>Oct 24 03:04:18 node-1 haproxy[3631]: proxy glance-glare has no server available!
<129>Oct 24 03:04:18 node-1 haproxy[3631]: 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>Oct 24 03:04:18 node-1 haproxy[3631]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:18 node-1 haproxy[3631]: Server neutron/node-3 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>Oct 24 03:04:18 node-1 haproxy[3631]: proxy neutron has no server available!
<129>Oct 24 03:04:18 node-1 haproxy[3631]: 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>Oct 24 03:04:18 node-1 haproxy[3631]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:18 node-1 haproxy[3631]: Server glance-registry/node-3 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>Oct 24 03:04:18 node-1 haproxy[3631]: proxy glance-registry has no server available!
<129>Oct 24 03:04:18 node-1 haproxy[3631]: 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>Oct 24 03:04:18 node-1 haproxy[3631]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:18 node-1 haproxy[3631]: Backup Server mysqld/node-3 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>Oct 24 03:04:18 node-1 haproxy[3631]: proxy mysqld has no server available!
<129>Oct 24 03:04:18 node-1 haproxy[3631]: 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>Oct 24 03:04:18 node-1 haproxy[3631]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:18 node-1 haproxy[3631]: Server object-storage/node-3 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>Oct 24 03:04:18 node-1 haproxy[3631]: proxy object-storage has no server available!
<129>Oct 24 03:04:18 node-1 haproxy[3631]: 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>Oct 24 03:04:18 node-1 haproxy[3631]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:18 node-1 haproxy[3631]: Server aodh/node-3 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>Oct 24 03:04:18 node-1 haproxy[3631]: proxy aodh has no server available!
<129>Oct 24 03:04:18 node-1 haproxy[3631]: 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>Oct 24 03:04:18 node-1 haproxy[3631]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:18 node-1 haproxy[3631]: Server ceilometer/node-3 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>Oct 24 03:04:18 node-1 haproxy[3631]: proxy ceilometer has no server available!
<129>Oct 24 03:04:18 node-1 haproxy[3631]: 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>Oct 24 03:04:18 node-1 haproxy[3631]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:18 node-1 haproxy[3631]: Server heat-api/node-3 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>Oct 24 03:04:18 node-1 haproxy[3631]: proxy heat-api has no server available!
<129>Oct 24 03:04:18 node-1 haproxy[3631]: 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>Oct 24 03:04:18 node-1 haproxy[3631]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:19 node-1 haproxy[3631]: Server heat-api-cfn/node-3 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>Oct 24 03:04:19 node-1 haproxy[3631]: proxy heat-api-cfn has no server available!
<129>Oct 24 03:04:19 node-1 haproxy[3631]: 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>Oct 24 03:04:19 node-1 haproxy[3631]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:19 node-1 haproxy[3631]: Server heat-api-cloudwatch/node-3 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>Oct 24 03:04:19 node-1 haproxy[3631]: proxy heat-api-cloudwatch has no server available!
<129>Oct 24 03:04:19 node-1 haproxy[3631]: 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>Oct 24 03:04:19 node-1 haproxy[3631]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 24 03:04:19 node-1 haproxy[3631]: Server nova-novncproxy/node-3 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>Oct 24 03:04:19 node-1 haproxy[3631]: proxy nova-novncproxy has no server available!
<27>Oct 24 03:04:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:04:30 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 24 03:04:55 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>Oct 24 03:04:57 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 24 03:05:34 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 24 03:05:41 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 24 03:05:42 node-1 multipathd: uevent trigger error
<27>Oct 24 03:05:43 node-1 multipathd: uevent trigger error
<27>Oct 24 03:05:43 node-1 multipathd: uevent trigger error
<27>Oct 24 03:05:43 node-1 multipathd: uevent trigger error
<27>Oct 24 03:05:43 node-1 multipathd: uevent trigger error
<27>Oct 24 03:05:43 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:01 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:01 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:01 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:01 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:01 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:26 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:26 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:26 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:26 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:26 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:26 node-1 multipathd: uevent trigger error
<43>Oct 24 03:08:27 node-1 apache2_error [Mon Oct 24 03:08:17.938441 2016] [mpm_event:notice] [pid 11354:tid 139978319710080] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 24 03:08:27 node-1 apache2_error [Mon Oct 24 03:08:17.938581 2016] [core:notice] [pid 11354:tid 139978319710080] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 24 03:08:27 node-1 apache2_error [Mon Oct 24 03:08:20.934057 2016] [mpm_event:notice] [pid 11354:tid 139978319710080] AH00491: caught SIGTERM, shutting down
<43>Oct 24 03:08:27 node-1 apache2_error [Mon Oct 24 03:08:22.034669 2016] [mpm_worker:notice] [pid 12642:tid 139838588098432] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 24 03:08:27 node-1 apache2_error [Mon Oct 24 03:08:22.034694 2016] [core:notice] [pid 12642:tid 139838588098432] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 24 03:08:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:08:35 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 24 03:09:37 node-1 apache2_error [Mon Oct 24 03:09:35.964660 2016] [mpm_worker:notice] [pid 12642:tid 139838588098432] AH00295: caught SIGTERM, shutting down
<43>Oct 24 03:09:37 node-1 apache2_error [Mon Oct 24 03:09:36.712234 2016] [mpm_worker:notice] [pid 25557:tid 139802326833024] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 24 03:09:37 node-1 apache2_error [Mon Oct 24 03:09:36.712268 2016] [core:notice] [pid 25557:tid 139802326833024] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 24 03:10:27 node-1 apache2_error [Mon Oct 24 03:10:20.791758 2016] [mpm_worker:notice] [pid 25557:tid 139802326833024] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 24 03:10:27 node-1 apache2_error [Mon Oct 24 03:10:20.984982 2016] [mpm_worker:warn] [pid 25557:tid 139802326833024] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 24 03:10:27 node-1 apache2_error [Mon Oct 24 03:10:20.987700 2016] [mpm_worker:notice] [pid 25557:tid 139802326833024] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 24 03:10:27 node-1 apache2_error [Mon Oct 24 03:10:20.987713 2016] [core:notice] [pid 25557:tid 139802326833024] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 24 03:11:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:11 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:11 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:11 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:11 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:11 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:11 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:26 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:26 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:26 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:26 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:26 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:37 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 24 03:11:47 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:47 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:47 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:47 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:47 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:52 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:52 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:52 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:52 node-1 multipathd: uevent trigger error
<27>Oct 24 03:11:52 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:07 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:07 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:07 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:07 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:07 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:07 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:07 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:56 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:56 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:56 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:56 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:56 node-1 multipathd: uevent trigger error
<27>Oct 24 03:12:56 node-1 multipathd: uevent trigger error
<27>Oct 24 03:14:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:14:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:14:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:14:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:14:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:14:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 24 03:14:59 node-1 multipathd: uevent trigger error
<27>Oct 24 03:14:59 node-1 multipathd: uevent trigger error
<27>Oct 24 03:14:59 node-1 multipathd: uevent trigger error
<27>Oct 24 03:14:59 node-1 multipathd: uevent trigger error
<27>Oct 24 03:14:59 node-1 multipathd: uevent trigger error
<27>Oct 24 03:14:59 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:22 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:22 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:22 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:22 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:22 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:22 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:15:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:17:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 24 03:17:48 node-1 multipathd: uevent trigger error
<27>Oct 24 03:17:48 node-1 multipathd: uevent trigger error
<27>Oct 24 03:17:48 node-1 multipathd: uevent trigger error
<27>Oct 24 03:17:48 node-1 multipathd: uevent trigger error
<27>Oct 24 03:17:48 node-1 multipathd: uevent trigger error
<27>Oct 24 03:17:48 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:04 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:04 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:04 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:04 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:04 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:04 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:41 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:41 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:41 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:41 node-1 multipathd: uevent trigger error
<27>Oct 24 03:18:41 node-1 multipathd: uevent trigger error
<27>Oct 24 03:19:22 node-1 multipathd: uevent trigger error
<27>Oct 24 03:19:22 node-1 multipathd: uevent trigger error
<27>Oct 24 03:19:22 node-1 multipathd: uevent trigger error
<27>Oct 24 03:19:22 node-1 multipathd: uevent trigger error
<27>Oct 24 03:19:22 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:05 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:05 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:05 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:05 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:05 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:21 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:21 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:21 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:21 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:21 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:21 node-1 multipathd: uevent trigger error
<27>Oct 24 03:20:42 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 24 03:22:40 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:40 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:40 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:40 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:40 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:52 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:53 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:53 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:22:58 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Oct 24 03:23:43 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 24 03:23:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:23:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:23:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:23:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:23:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:23:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:02 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:02 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:02 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:02 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:44 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:44 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:44 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:44 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:44 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:48 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:48 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:48 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:48 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:48 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:53 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:53 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:53 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:53 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:53 node-1 multipathd: uevent trigger error
<27>Oct 24 03:24:53 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:04 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:04 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:04 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:04 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:04 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:11 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:11 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:11 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:11 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:11 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:36 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:36 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:36 node-1 multipathd: uevent trigger error
<27>Oct 24 03:25:36 node-1 multipathd: uevent trigger error
<27>Oct 24 03:26:38 node-1 multipathd: uevent trigger error
<27>Oct 24 03:26:38 node-1 multipathd: uevent trigger error
<27>Oct 24 03:26:38 node-1 multipathd: uevent trigger error
<27>Oct 24 03:26:38 node-1 multipathd: uevent trigger error
<27>Oct 24 03:26:38 node-1 multipathd: uevent trigger error
<27>Oct 24 03:26:45 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 24 03:26:54 node-1 multipathd: uevent trigger error
<27>Oct 24 03:26:54 node-1 multipathd: uevent trigger error
<27>Oct 24 03:26:54 node-1 multipathd: uevent trigger error
<27>Oct 24 03:26:54 node-1 multipathd: uevent trigger error
<27>Oct 24 03:26:54 node-1 multipathd: uevent trigger error
<11>Oct 24 03:27:07 node-1 liberasurecode[60158]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:07 node-1 liberasurecode[60158]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:07 node-1 liberasurecode[60158]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:07 node-1 liberasurecode[60158]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:07 node-1 liberasurecode[60182]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:07 node-1 liberasurecode[60182]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:07 node-1 liberasurecode[60182]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:07 node-1 liberasurecode[60182]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:09 node-1 liberasurecode[60572]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:09 node-1 liberasurecode[60572]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:09 node-1 liberasurecode[60572]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:09 node-1 liberasurecode[60572]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61094]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61094]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61094]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61094]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61135]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61135]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61135]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61135]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61177]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61177]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61177]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:13 node-1 liberasurecode[61177]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61249]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61249]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61249]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61249]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61276]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61276]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61276]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61276]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61288]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61288]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61288]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61288]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61305]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61305]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61305]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:14 node-1 liberasurecode[61305]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:22 node-1 liberasurecode[62735]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:22 node-1 liberasurecode[62735]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:22 node-1 liberasurecode[62735]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:27:22 node-1 liberasurecode[62735]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 24 03:27:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:27:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:27:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:27:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:27:31 node-1 multipathd: uevent trigger error
<43>Oct 24 03:28:19 node-1 apache2_error [Mon Oct 24 03:28:18.152621 2016] [mpm_worker:notice] [pid 25557:tid 139802326833024] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 24 03:28:19 node-1 apache2_error [Mon Oct 24 03:28:18.532747 2016] [mpm_worker:warn] [pid 25557:tid 139802326833024] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 24 03:28:19 node-1 apache2_error [Mon Oct 24 03:28:18.535694 2016] [mpm_worker:notice] [pid 25557:tid 139802326833024] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 24 03:28:19 node-1 apache2_error [Mon Oct 24 03:28:18.535707 2016] [core:notice] [pid 25557:tid 139802326833024] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 24 03:28:59 node-1 multipathd: uevent trigger error
<43>Oct 24 03:28:59 node-1 apache2_error [Mon Oct 24 03:28:55.343726 2016] [mpm_worker:notice] [pid 25557:tid 139802326833024] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 24 03:28:59 node-1 apache2_error [Mon Oct 24 03:28:55.728329 2016] [mpm_worker:warn] [pid 25557:tid 139802326833024] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 24 03:28:59 node-1 apache2_error [Mon Oct 24 03:28:55.735079 2016] [mpm_worker:notice] [pid 25557:tid 139802326833024] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 24 03:28:59 node-1 apache2_error [Mon Oct 24 03:28:55.735117 2016] [core:notice] [pid 25557:tid 139802326833024] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 24 03:28:59 node-1 multipathd: uevent trigger error
<27>Oct 24 03:28:59 node-1 multipathd: uevent trigger error
<27>Oct 24 03:28:59 node-1 multipathd: uevent trigger error
<27>Oct 24 03:28:59 node-1 multipathd: uevent trigger error
<27>Oct 24 03:28:59 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:06 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:44 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:44 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:44 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:44 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:44 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:45 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:47 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 24 03:29:49 node-1 apache2_error [Mon Oct 24 03:29:40.916107 2016] [mpm_worker:notice] [pid 25557:tid 139802326833024] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 24 03:29:49 node-1 apache2_error [Mon Oct 24 03:29:41.110565 2016] [mpm_worker:warn] [pid 25557:tid 139802326833024] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 24 03:29:49 node-1 apache2_error [Mon Oct 24 03:29:41.115767 2016] [mpm_worker:notice] [pid 25557:tid 139802326833024] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 24 03:29:49 node-1 apache2_error [Mon Oct 24 03:29:41.115790 2016] [core:notice] [pid 25557:tid 139802326833024] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 24 03:29:51 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:51 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:51 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:51 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:51 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:57 node-1 multipathd: uevent trigger error
<27>Oct 24 03:29:57 node-1 multipathd: uevent trigger error
<11>Oct 24 03:30:01 node-1 liberasurecode[89658]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:30:01 node-1 liberasurecode[89658]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:30:01 node-1 liberasurecode[89658]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:30:01 node-1 liberasurecode[89658]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 24 03:30:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:14 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:35 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:35 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:42 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:42 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:42 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:42 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:42 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:42 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:49 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 24 03:30:58 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:58 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:58 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:58 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:58 node-1 multipathd: uevent trigger error
<27>Oct 24 03:30:58 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:12 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:12 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:12 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:12 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:18 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:18 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:18 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:18 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:18 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:31 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:34 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 24 03:31:58 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:58 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:58 node-1 multipathd: uevent trigger error
<27>Oct 24 03:31:58 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:03 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:16 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:16 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:16 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:16 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:16 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:23 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:27 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:27 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:27 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:28 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:40 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:40 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:40 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:40 node-1 multipathd: uevent trigger error
<27>Oct 24 03:32:40 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:10 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:15 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:20 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:24 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:25 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:25 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:25 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:25 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:25 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:29 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:29 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:29 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:29 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:29 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:34 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:38 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:38 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:38 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:38 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:38 node-1 multipathd: uevent trigger error
<27>Oct 24 03:33:38 node-1 multipathd: uevent trigger error
<11>Oct 24 03:35:01 node-1 liberasurecode[154157]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:35:01 node-1 liberasurecode[154157]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:35:01 node-1 liberasurecode[154157]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 24 03:35:01 node-1 liberasurecode[154157]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
