Jul 28 06:02:51 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8370" x-info="http://www.rsyslog.com"] start
Jul 28 06:02:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 28 06:02:51 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 28 06:02:51 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 28 06:02:51 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 28 06:02:51 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 28 06:02:51 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 28 06:02:51 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 28 06:02:51 node-1 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 28 06:02:51 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=97a88fb5-a901-4eed-a9df-e90816d42415 nomdmonddf nomdmonisw
Jul 28 06:02:51 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 28 06:02:51 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 28 06:02:51 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 28 06:02:51 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 28 06:02:51 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 28 06:02:51 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 28 06:02:51 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 28 06:02:51 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 28 06:02:51 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 28 06:02:51 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 28 06:02:51 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 28 06:02:51 node-1 kernel: [    0.000000] No AGP bridge found
Jul 28 06:02:51 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 28 06:02:51 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 28 06:02:51 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 28 06:02:51 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 28 06:02:51 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 28 06:02:51 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 28 06:02:51 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 28 06:02:51 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 28 06:02:51 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 28 06:02:51 node-1 kernel: [    0.000000]   2 disabled
Jul 28 06:02:51 node-1 kernel: [    0.000000]   3 disabled
Jul 28 06:02:51 node-1 kernel: [    0.000000]   4 disabled
Jul 28 06:02:51 node-1 kernel: [    0.000000]   5 disabled
Jul 28 06:02:51 node-1 kernel: [    0.000000]   6 disabled
Jul 28 06:02:51 node-1 kernel: [    0.000000]   7 disabled
Jul 28 06:02:51 node-1 kernel: [    0.000000]   8 disabled
Jul 28 06:02:51 node-1 kernel: [    0.000000]   9 disabled
Jul 28 06:02:51 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 28 06:02:51 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 28 06:02:51 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 28 06:02:51 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 28 06:02:51 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 28 06:02:51 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 28 06:02:51 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 28 06:02:51 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 28 06:02:51 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 28 06:02:51 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 28 06:02:51 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 28 06:02:51 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 28 06:02:51 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 28 06:02:51 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 28 06:02:51 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 28 06:02:51 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 28 06:02:51 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 28 06:02:51 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 28 06:02:51 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 28 06:02:51 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 28 06:02:51 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 28 06:02:51 node-1 kernel: [    0.000000] Zone ranges:
Jul 28 06:02:51 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 28 06:02:51 node-1 kernel: [    0.000000] Early memory node ranges
Jul 28 06:02:51 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 28 06:02:51 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 28 06:02:51 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 28 06:02:51 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 28 06:02:51 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 28 06:02:51 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 28 06:02:51 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 28 06:02:51 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 28 06:02:51 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 28 06:02:51 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 28 06:02:51 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 28 06:02:51 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 28 06:02:51 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 28 06:02:51 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 28 06:02:51 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 28 06:02:51 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 28 06:02:51 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 28 06:02:51 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 28 06:02:51 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 28 06:02:51 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 28 06:02:51 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 28 06:02:51 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 28 06:02:51 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 28 06:02:51 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 28 06:02:51 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 28 06:02:51 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 28 06:02:51 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=97a88fb5-a901-4eed-a9df-e90816d42415 nomdmonddf nomdmonisw
Jul 28 06:02:51 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 28 06:02:51 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 28 06:02:51 node-1 kernel: [    0.000000] Checking aperture...
Jul 28 06:02:51 node-1 kernel: [    0.000000] No AGP bridge found
Jul 28 06:02:51 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 28 06:02:51 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 28 06:02:51 node-1 kernel: [    0.000000] Memory: 32653452K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Jul 28 06:02:51 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 28 06:02:51 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 28 06:02:51 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 28 06:02:51 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 28 06:02:51 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 28 06:02:51 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 28 06:02:51 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 28 06:02:51 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 28 06:02:51 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 28 06:02:51 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 28 06:02:51 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 28 06:02:51 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 28 06:02:51 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 28 06:02:51 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 28 06:02:51 node-1 kernel: [    0.004000] tsc: Detected 3491.910 MHz processor
Jul 28 06:02:51 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.82 BogoMIPS (lpj=13967640)
Jul 28 06:02:51 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 28 06:02:51 node-1 kernel: [    0.000047] Security Framework initialized
Jul 28 06:02:51 node-1 kernel: [    0.000065] AppArmor: AppArmor initialized
Jul 28 06:02:51 node-1 kernel: [    0.000066] Yama: becoming mindful.
Jul 28 06:02:51 node-1 kernel: [    0.001453] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 28 06:02:51 node-1 kernel: [    0.006312] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 28 06:02:51 node-1 kernel: [    0.008239] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 06:02:51 node-1 kernel: [    0.008267] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 06:02:51 node-1 kernel: [    0.008555] Initializing cgroup subsys memory
Jul 28 06:02:51 node-1 kernel: [    0.008563] Initializing cgroup subsys devices
Jul 28 06:02:51 node-1 kernel: [    0.008565] Initializing cgroup subsys freezer
Jul 28 06:02:51 node-1 kernel: [    0.008567] Initializing cgroup subsys blkio
Jul 28 06:02:51 node-1 kernel: [    0.008568] Initializing cgroup subsys perf_event
Jul 28 06:02:51 node-1 kernel: [    0.008571] Initializing cgroup subsys hugetlb
Jul 28 06:02:51 node-1 kernel: [    0.008590] CPU: Physical Processor ID: 0
Jul 28 06:02:51 node-1 kernel: [    0.008592] CPU: Processor Core ID: 0
Jul 28 06:02:51 node-1 kernel: [    0.008595] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 28 06:02:51 node-1 kernel: [    0.008595] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 28 06:02:51 node-1 kernel: [    0.009289] mce: CPU supports 22 MCE banks
Jul 28 06:02:51 node-1 kernel: [    0.009316] CPU0: Thermal monitoring enabled (TM1)
Jul 28 06:02:51 node-1 kernel: [    0.009337] process: using mwait in idle threads
Jul 28 06:02:51 node-1 kernel: [    0.009340] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 28 06:02:51 node-1 kernel: [    0.009340] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 28 06:02:51 node-1 kernel: [    0.009340] tlb_flushall_shift: 6
Jul 28 06:02:51 node-1 kernel: [    0.009429] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 28 06:02:51 node-1 kernel: [    0.010154] ACPI: Core revision 20131115
Jul 28 06:02:51 node-1 kernel: [    0.022843] ACPI: All ACPI Tables successfully acquired
Jul 28 06:02:51 node-1 kernel: [    0.023019] ftrace: allocating 28617 entries in 112 pages
Jul 28 06:02:51 node-1 kernel: [    0.031832] dmar: Host address width 46
Jul 28 06:02:51 node-1 kernel: [    0.031834] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 28 06:02:51 node-1 kernel: [    0.031840] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 06:02:51 node-1 kernel: [    0.031842] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 28 06:02:51 node-1 kernel: [    0.031846] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 06:02:51 node-1 kernel: [    0.031847] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 28 06:02:51 node-1 kernel: [    0.031849] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 28 06:02:51 node-1 kernel: [    0.031850] dmar: ATSR flags: 0x0
Jul 28 06:02:51 node-1 kernel: [    0.031851] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 28 06:02:51 node-1 kernel: [    0.031852] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 28 06:02:51 node-1 kernel: [    0.031968] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 28 06:02:51 node-1 kernel: [    0.031969] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 06:02:51 node-1 kernel: [    0.031970] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 06:02:51 node-1 kernel: [    0.031971] HPET id 0 under DRHD base 0xc7ffc000
Jul 28 06:02:51 node-1 kernel: [    0.031972] Your BIOS is broken and requested that x2apic be disabled.
Jul 28 06:02:51 node-1 kernel: [    0.031972] This will slightly decrease performance.
Jul 28 06:02:51 node-1 kernel: [    0.031972] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 28 06:02:51 node-1 kernel: [    0.032404] Enabled IRQ remapping in xapic mode
Jul 28 06:02:51 node-1 kernel: [    0.032405] x2apic not enabled, IRQ remapping is in xapic mode
Jul 28 06:02:51 node-1 kernel: [    0.032409] Switched APIC routing to physical flat.
Jul 28 06:02:51 node-1 kernel: [    0.033034] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 28 06:02:51 node-1 kernel: [    0.072684] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 28 06:02:51 node-1 kernel: [    0.072689] TSC deadline timer enabled
Jul 28 06:02:51 node-1 kernel: [    0.072697] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 28 06:02:51 node-1 kernel: [    0.072703] ... version:                3
Jul 28 06:02:51 node-1 kernel: [    0.072703] ... bit width:              48
Jul 28 06:02:51 node-1 kernel: [    0.072704] ... generic registers:      4
Jul 28 06:02:51 node-1 kernel: [    0.072705] ... value mask:             0000ffffffffffff
Jul 28 06:02:51 node-1 kernel: [    0.072706] ... max period:             0000ffffffffffff
Jul 28 06:02:51 node-1 kernel: [    0.072707] ... fixed-purpose events:   3
Jul 28 06:02:51 node-1 kernel: [    0.072708] ... event mask:             000000070000000f
Jul 28 06:02:51 node-1 kernel: [    0.074117] x86: Booting SMP configuration:
Jul 28 06:02:51 node-1 kernel: [    0.088222] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 28 06:02:51 node-1 kernel: [    0.074119] .... node  #0, CPUs:        #1  #2  #3
Jul 28 06:02:51 node-1 kernel: [    0.116131] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 28 06:02:51 node-1 kernel: [    0.270279] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 28 06:02:51 node-1 kernel: [    0.325895] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 28 06:02:51 node-1 kernel: [    0.382545] x86: Booted up 2 nodes, 16 CPUs
Jul 28 06:02:51 node-1 kernel: [    0.382548] smpboot: Total of 16 processors activated (111753.37 BogoMIPS)
Jul 28 06:02:51 node-1 kernel: [    0.406079] devtmpfs: initialized
Jul 28 06:02:51 node-1 kernel: [    0.409160] EVM: security.selinux
Jul 28 06:02:51 node-1 kernel: [    0.409162] EVM: security.SMACK64
Jul 28 06:02:51 node-1 kernel: [    0.409163] EVM: security.ima
Jul 28 06:02:51 node-1 kernel: [    0.409164] EVM: security.capability
Jul 28 06:02:51 node-1 kernel: [    0.409214] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 28 06:02:51 node-1 kernel: [    0.409891] pinctrl core: initialized pinctrl subsystem
Jul 28 06:02:51 node-1 kernel: [    0.409952] regulator-dummy: no parameters
Jul 28 06:02:51 node-1 kernel: [    0.409983] RTC time:  6:02:14, date: 07/28/16
Jul 28 06:02:51 node-1 kernel: [    0.410017] NET: Registered protocol family 16
Jul 28 06:02:51 node-1 kernel: [    0.410100] cpuidle: using governor ladder
Jul 28 06:02:51 node-1 kernel: [    0.410102] cpuidle: using governor menu
Jul 28 06:02:51 node-1 kernel: [    0.410136] ACPI: bus type PCI registered
Jul 28 06:02:51 node-1 kernel: [    0.410138] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 28 06:02:51 node-1 kernel: [    0.410183] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 28 06:02:51 node-1 kernel: [    0.410185] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 28 06:02:51 node-1 kernel: [    0.423918] PCI: Using configuration type 1 for base access
Jul 28 06:02:51 node-1 kernel: [    0.424909] bio: create slab <bio-0> at 0
Jul 28 06:02:51 node-1 kernel: [    0.425187] ACPI: Added _OSI(Module Device)
Jul 28 06:02:51 node-1 kernel: [    0.425189] ACPI: Added _OSI(Processor Device)
Jul 28 06:02:51 node-1 kernel: [    0.425190] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 28 06:02:51 node-1 kernel: [    0.425191] ACPI: Added _OSI(Processor Aggregator Device)
Jul 28 06:02:51 node-1 kernel: [    0.437829] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 28 06:02:51 node-1 kernel: [    0.448475] ACPI: Interpreter enabled
Jul 28 06:02:51 node-1 kernel: [    0.448480] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 28 06:02:51 node-1 kernel: [    0.448484] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 28 06:02:51 node-1 kernel: [    0.448487] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 28 06:02:51 node-1 kernel: [    0.448494] ACPI: (supports S0 S4 S5)
Jul 28 06:02:51 node-1 kernel: [    0.448495] ACPI: Using IOAPIC for interrupt routing
Jul 28 06:02:51 node-1 kernel: [    0.448535] HEST: Table parsing has been initialized.
Jul 28 06:02:51 node-1 kernel: [    0.448538] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 28 06:02:51 node-1 kernel: [    0.449089] ACPI: No dock devices found.
Jul 28 06:02:51 node-1 kernel: [    0.460628] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 28 06:02:51 node-1 kernel: [    0.460632] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 06:02:51 node-1 kernel: [    0.460636] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 06:02:51 node-1 kernel: [    0.460662] PCI host bridge to bus 0000:ff
Jul 28 06:02:51 node-1 kernel: [    0.460664] pci_bus 0000:ff: root bus resource [bus ff]
Jul 28 06:02:51 node-1 kernel: [    0.460672] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.460709] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.460739] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.460773] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.460803] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.460832] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.460863] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.460891] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.460921] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.460951] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.460977] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461005] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461034] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461062] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461088] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461117] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461145] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461172] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461198] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.461226] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461252] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.461277] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461303] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461332] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.461366] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461396] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461425] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461457] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461489] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461521] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461551] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461580] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461610] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461641] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461674] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461705] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461736] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461764] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461791] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461823] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461857] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461893] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461927] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461959] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.461989] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462017] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462048] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462076] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462107] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462137] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462168] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462195] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462223] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462252] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462280] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462311] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462343] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462399] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 28 06:02:51 node-1 kernel: [    0.462402] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 06:02:51 node-1 kernel: [    0.462405] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 06:02:51 node-1 kernel: [    0.462422] PCI host bridge to bus 0000:7f
Jul 28 06:02:51 node-1 kernel: [    0.462424] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 28 06:02:51 node-1 kernel: [    0.462429] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462457] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.462485] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462515] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462537] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.462561] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.462588] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462618] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462642] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462667] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462692] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462716] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462742] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462767] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462791] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462819] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462840] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462863] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462886] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.462909] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462932] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.462953] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.462976] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463003] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 06:02:51 node-1 kernel: [    0.463036] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463063] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463089] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463117] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463142] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463170] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463198] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463226] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463250] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463278] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463306] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463335] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463363] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463390] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463416] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463444] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463469] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463495] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463523] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463550] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463574] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463599] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463625] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463654] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463683] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463710] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463740] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463766] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463789] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463815] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463841] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463870] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.463896] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.465136] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 28 06:02:51 node-1 kernel: [    0.465139] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 06:02:51 node-1 kernel: [    0.466264] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 06:02:51 node-1 kernel: [    0.466776] PCI host bridge to bus 0000:00
Jul 28 06:02:51 node-1 kernel: [    0.466778] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 28 06:02:51 node-1 kernel: [    0.466780] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 28 06:02:51 node-1 kernel: [    0.466781] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 28 06:02:51 node-1 kernel: [    0.466782] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 28 06:02:51 node-1 kernel: [    0.466784] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 28 06:02:51 node-1 kernel: [    0.466785] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 28 06:02:51 node-1 kernel: [    0.466787] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 28 06:02:51 node-1 kernel: [    0.466793] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 28 06:02:51 node-1 kernel: [    0.466875] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.466906] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.466947] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 28 06:02:51 node-1 kernel: [    0.466967] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.466996] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.467036] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 28 06:02:51 node-1 kernel: [    0.467055] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.467085] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.467128] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 28 06:02:51 node-1 kernel: [    0.467145] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.467214] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.467290] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.467365] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 06:02:51 node-1 kernel: [    0.467369] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 28 06:02:51 node-1 kernel: [    0.467454] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 28 06:02:51 node-1 kernel: [    0.467600] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 28 06:02:51 node-1 kernel: [    0.467618] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 28 06:02:51 node-1 kernel: [    0.467695] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.467750] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 28 06:02:51 node-1 kernel: [    0.467771] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.467826] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.467870] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 28 06:02:51 node-1 kernel: [    0.467898] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.467954] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.467997] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 28 06:02:51 node-1 kernel: [    0.468021] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 28 06:02:51 node-1 kernel: [    0.468039] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 28 06:02:51 node-1 kernel: [    0.468116] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.468166] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 28 06:02:51 node-1 kernel: [    0.468193] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 28 06:02:51 node-1 kernel: [    0.468441] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 28 06:02:51 node-1 kernel: [    0.468447] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 28 06:02:51 node-1 kernel: [    0.468453] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 28 06:02:51 node-1 kernel: [    0.468458] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 28 06:02:51 node-1 kernel: [    0.468466] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 28 06:02:51 node-1 kernel: [    0.468496] pci 0000:01:00.0: supports D1 D2
Jul 28 06:02:51 node-1 kernel: [    0.478623] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 06:02:51 node-1 kernel: [    0.478630] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 06:02:51 node-1 kernel: [    0.478634] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 06:02:51 node-1 kernel: [    0.478780] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.478814] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 28 06:02:51 node-1 kernel: [    0.490619] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 06:02:51 node-1 kernel: [    0.490625] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.490629] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 06:02:51 node-1 kernel: [    0.490713] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.490786] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 28 06:02:51 node-1 kernel: [    0.490881] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.490965] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 06:02:51 node-1 kernel: [    0.490969] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.490971] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 06:02:51 node-1 kernel: [    0.491024] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.491146] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.491200] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 06:02:51 node-1 kernel: [    0.491203] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.491205] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 06:02:51 node-1 kernel: [    0.491270] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.491391] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.491430] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.491553] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.491591] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.491711] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.491749] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 28 06:02:51 node-1 kernel: [    0.491868] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 28 06:02:51 node-1 kernel: [    0.491912] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 06:02:51 node-1 kernel: [    0.491915] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.491917] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 06:02:51 node-1 kernel: [    0.491975] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 28 06:02:51 node-1 kernel: [    0.492037] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 28 06:02:51 node-1 kernel: [    0.492089] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 28 06:02:51 node-1 kernel: [    0.492131] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 28 06:02:51 node-1 kernel: [    0.492213] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 28 06:02:51 node-1 kernel: [    0.492340] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 06:02:51 node-1 kernel: [    0.492343] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.492345] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 06:02:51 node-1 kernel: [    0.492400] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 28 06:02:51 node-1 kernel: [    0.492458] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 28 06:02:51 node-1 kernel: [    0.492509] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 28 06:02:51 node-1 kernel: [    0.492722] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 06:02:51 node-1 kernel: [    0.492725] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 06:02:51 node-1 kernel: [    0.492789] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 28 06:02:51 node-1 kernel: [    0.492841] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 28 06:02:51 node-1 kernel: [    0.492890] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 28 06:02:51 node-1 kernel: [    0.493101] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 06:02:51 node-1 kernel: [    0.493105] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 06:02:51 node-1 kernel: [    0.493164] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 28 06:02:51 node-1 kernel: [    0.493224] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 28 06:02:51 node-1 kernel: [    0.493301] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 28 06:02:51 node-1 kernel: [    0.493523] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 06:02:51 node-1 kernel: [    0.493527] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 06:02:51 node-1 kernel: [    0.493700] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 06:02:51 node-1 kernel: [    0.493739] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 06:02:51 node-1 kernel: [    0.493814] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 28 06:02:51 node-1 kernel: [    0.493833] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 28 06:02:51 node-1 kernel: [    0.493846] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 28 06:02:51 node-1 kernel: [    0.493859] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 28 06:02:51 node-1 kernel: [    0.493909] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 28 06:02:51 node-1 kernel: [    0.498626] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 06:02:51 node-1 kernel: [    0.498635] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 06:02:51 node-1 kernel: [    0.498695] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 28 06:02:51 node-1 kernel: [    0.499184] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 28 06:02:51 node-1 kernel: [    0.499187] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 06:02:51 node-1 kernel: [    0.499312] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 06:02:51 node-1 kernel: [    0.499417] PCI host bridge to bus 0000:80
Jul 28 06:02:51 node-1 kernel: [    0.499419] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 28 06:02:51 node-1 kernel: [    0.499421] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 28 06:02:51 node-1 kernel: [    0.499422] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 28 06:02:51 node-1 kernel: [    0.499430] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.499493] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.499560] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 06:02:51 node-1 kernel: [    0.499621] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 06:02:51 node-1 kernel: [    0.499626] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 28 06:02:51 node-1 kernel: [    0.499696] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 28 06:02:51 node-1 kernel: [    0.499996] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 28 06:02:51 node-1 kernel: [    0.500028] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 28 06:02:51 node-1 kernel: [    0.500057] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 28 06:02:51 node-1 kernel: [    0.500087] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 28 06:02:51 node-1 kernel: [    0.500116] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 06:02:51 node-1 kernel: [    0.500146] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 06:02:51 node-1 kernel: [    0.500175] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 06:02:51 node-1 kernel: [    0.500205] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 06:02:51 node-1 kernel: [    0.500289] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 28 06:02:51 node-1 kernel: [    0.500293] ACPI: \_SB_.UNC1: notify handler is installed
Jul 28 06:02:51 node-1 kernel: [    0.500294] ACPI: \_SB_.UNC0: notify handler is installed
Jul 28 06:02:51 node-1 kernel: [    0.500310] ACPI: \_SB_.PCI0: notify handler is installed
Jul 28 06:02:51 node-1 kernel: [    0.500363] ACPI: \_SB_.PCI1: notify handler is installed
Jul 28 06:02:51 node-1 kernel: [    0.500443] Found 4 acpi root devices
Jul 28 06:02:51 node-1 kernel: [    0.500550] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 28 06:02:51 node-1 kernel: [    0.500552] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 28 06:02:51 node-1 kernel: [    0.500554] vgaarb: loaded
Jul 28 06:02:51 node-1 kernel: [    0.500555] vgaarb: bridge control possible 0000:0c:00.0
Jul 28 06:02:51 node-1 kernel: [    0.500668] SCSI subsystem initialized
Jul 28 06:02:51 node-1 kernel: [    0.500731] libata version 3.00 loaded.
Jul 28 06:02:51 node-1 kernel: [    0.500746] ACPI: bus type USB registered
Jul 28 06:02:51 node-1 kernel: [    0.500756] usbcore: registered new interface driver usbfs
Jul 28 06:02:51 node-1 kernel: [    0.500761] usbcore: registered new interface driver hub
Jul 28 06:02:51 node-1 kernel: [    0.500800] usbcore: registered new device driver usb
Jul 28 06:02:51 node-1 kernel: [    0.500962] PCI: Using ACPI for IRQ routing
Jul 28 06:02:51 node-1 kernel: [    0.504575] PCI: pci_cache_line_size set to 64 bytes
Jul 28 06:02:51 node-1 kernel: [    0.504783] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 28 06:02:51 node-1 kernel: [    0.504784] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 28 06:02:51 node-1 kernel: [    0.504785] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 28 06:02:51 node-1 kernel: [    0.504848] NetLabel: Initializing
Jul 28 06:02:51 node-1 kernel: [    0.504850] NetLabel:  domain hash size = 128
Jul 28 06:02:51 node-1 kernel: [    0.504850] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 28 06:02:51 node-1 kernel: [    0.504859] NetLabel:  unlabeled traffic allowed by default
Jul 28 06:02:51 node-1 kernel: [    0.504915] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 28 06:02:51 node-1 kernel: [    0.504919] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 28 06:02:51 node-1 kernel: [    0.506988] Switched to clocksource hpet
Jul 28 06:02:51 node-1 kernel: [    0.511540] AppArmor: AppArmor Filesystem Enabled
Jul 28 06:02:51 node-1 kernel: [    0.511579] pnp: PnP ACPI init
Jul 28 06:02:51 node-1 kernel: [    0.511592] ACPI: bus type PNP registered
Jul 28 06:02:51 node-1 kernel: [    0.511769] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 28 06:02:51 node-1 kernel: [    0.511780] pnp 00:01: [dma 4]
Jul 28 06:02:51 node-1 kernel: [    0.511799] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 28 06:02:51 node-1 kernel: [    0.511833] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 28 06:02:51 node-1 kernel: [    0.511858] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 28 06:02:51 node-1 kernel: [    0.511879] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 28 06:02:51 node-1 kernel: [    0.511925] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 28 06:02:51 node-1 kernel: [    0.512038] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 28 06:02:51 node-1 kernel: [    0.512040] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 28 06:02:51 node-1 kernel: [    0.512042] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 28 06:02:51 node-1 kernel: [    0.512043] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 28 06:02:51 node-1 kernel: [    0.512045] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 28 06:02:51 node-1 kernel: [    0.512046] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 28 06:02:51 node-1 kernel: [    0.512050] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 28 06:02:51 node-1 kernel: [    0.512051] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 28 06:02:51 node-1 kernel: [    0.512053] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 28 06:02:51 node-1 kernel: [    0.512054] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 28 06:02:51 node-1 kernel: [    0.512056] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 28 06:02:51 node-1 kernel: [    0.512057] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 28 06:02:51 node-1 kernel: [    0.512059] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 28 06:02:51 node-1 kernel: [    0.512062] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 28 06:02:51 node-1 kernel: [    0.512163] pnp 00:07: [dma 0 disabled]
Jul 28 06:02:51 node-1 kernel: [    0.512196] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 06:02:51 node-1 kernel: [    0.512278] pnp 00:08: [dma 0 disabled]
Jul 28 06:02:51 node-1 kernel: [    0.512318] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 06:02:51 node-1 kernel: [    0.512377] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 28 06:02:51 node-1 kernel: [    0.512819] pnp: PnP ACPI: found 10 devices
Jul 28 06:02:51 node-1 kernel: [    0.512821] ACPI: bus type PNP unregistered
Jul 28 06:02:51 node-1 kernel: [    0.518845] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 06:02:51 node-1 kernel: [    0.518849] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 06:02:51 node-1 kernel: [    0.518852] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 06:02:51 node-1 kernel: [    0.518857] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 06:02:51 node-1 kernel: [    0.518859] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.518874] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 06:02:51 node-1 kernel: [    0.518903] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 06:02:51 node-1 kernel: [    0.518918] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 06:02:51 node-1 kernel: [    0.518946] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 06:02:51 node-1 kernel: [    0.518965] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 06:02:51 node-1 kernel: [    0.518995] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 06:02:51 node-1 kernel: [    0.519009] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 06:02:51 node-1 kernel: [    0.519038] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 06:02:51 node-1 kernel: [    0.519040] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.519055] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 06:02:51 node-1 kernel: [    0.519084] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 06:02:51 node-1 kernel: [    0.519086] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.519100] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 06:02:51 node-1 kernel: [    0.519130] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 06:02:51 node-1 kernel: [    0.519131] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.519134] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 06:02:51 node-1 kernel: [    0.519139] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 06:02:51 node-1 kernel: [    0.519141] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.519144] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 06:02:51 node-1 kernel: [    0.519148] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 06:02:51 node-1 kernel: [    0.519154] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 06:02:51 node-1 kernel: [    0.519163] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 06:02:51 node-1 kernel: [    0.519167] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 06:02:51 node-1 kernel: [    0.519174] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 28 06:02:51 node-1 kernel: [    0.519175] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 28 06:02:51 node-1 kernel: [    0.519176] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 28 06:02:51 node-1 kernel: [    0.519177] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 28 06:02:51 node-1 kernel: [    0.519177] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 28 06:02:51 node-1 kernel: [    0.519178] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 28 06:02:51 node-1 kernel: [    0.519179] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 28 06:02:51 node-1 kernel: [    0.519180] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 28 06:02:51 node-1 kernel: [    0.519181] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.519182] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 06:02:51 node-1 kernel: [    0.519183] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.519184] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 06:02:51 node-1 kernel: [    0.519185] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.519186] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 06:02:51 node-1 kernel: [    0.519187] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.519188] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 06:02:51 node-1 kernel: [    0.519189] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 28 06:02:51 node-1 kernel: [    0.519190] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 28 06:02:51 node-1 kernel: [    0.519191] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 28 06:02:51 node-1 kernel: [    0.519192] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 28 06:02:51 node-1 kernel: [    0.519194] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 28 06:02:51 node-1 kernel: [    0.519195] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 28 06:02:51 node-1 kernel: [    0.519197] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 28 06:02:51 node-1 kernel: [    0.519198] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 28 06:02:51 node-1 kernel: [    0.519241] NET: Registered protocol family 2
Jul 28 06:02:51 node-1 kernel: [    0.519537] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 28 06:02:51 node-1 kernel: [    0.519906] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 28 06:02:51 node-1 kernel: [    0.520073] TCP: Hash tables configured (established 262144 bind 65536)
Jul 28 06:02:51 node-1 kernel: [    0.520126] TCP: reno registered
Jul 28 06:02:51 node-1 kernel: [    0.520156] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 06:02:51 node-1 kernel: [    0.520264] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 06:02:51 node-1 kernel: [    0.520423] NET: Registered protocol family 1
Jul 28 06:02:51 node-1 kernel: [    0.555078] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 28 06:02:51 node-1 kernel: [    0.555086] PCI: CLS 64 bytes, default 64
Jul 28 06:02:51 node-1 kernel: [    0.555130] Trying to unpack rootfs image as initramfs...
Jul 28 06:02:51 node-1 kernel: [    0.776889] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Jul 28 06:02:51 node-1 kernel: [    0.776938] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 28 06:02:51 node-1 kernel: [    0.776940] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 28 06:02:51 node-1 kernel: [    0.777365] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777374] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777399] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777406] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777414] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777419] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777425] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777432] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777438] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777445] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777455] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777461] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777468] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777475] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777481] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777486] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 06:02:51 node-1 kernel: [    0.777542] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 28 06:02:51 node-1 kernel: [    0.777545] Scanning for low memory corruption every 60 seconds
Jul 28 06:02:51 node-1 kernel: [    0.777846] Initialise system trusted keyring
Jul 28 06:02:51 node-1 kernel: [    0.777894] audit: initializing netlink socket (disabled)
Jul 28 06:02:51 node-1 kernel: [    0.777905] type=2000 audit(1469685734.732:1): initialized
Jul 28 06:02:51 node-1 kernel: [    0.795875] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 28 06:02:51 node-1 kernel: [    0.797363] zbud: loaded
Jul 28 06:02:51 node-1 kernel: [    0.797492] VFS: Disk quotas dquot_6.5.2
Jul 28 06:02:51 node-1 kernel: [    0.797536] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 28 06:02:51 node-1 kernel: [    0.797916] fuse init (API version 7.22)
Jul 28 06:02:51 node-1 kernel: [    0.797967] msgmni has been set to 32768
Jul 28 06:02:51 node-1 kernel: [    0.798011] Key type big_key registered
Jul 28 06:02:51 node-1 kernel: [    0.798516] Key type asymmetric registered
Jul 28 06:02:51 node-1 kernel: [    0.798518] Asymmetric key parser 'x509' registered
Jul 28 06:02:51 node-1 kernel: [    0.798542] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 28 06:02:51 node-1 kernel: [    0.798608] io scheduler noop registered
Jul 28 06:02:51 node-1 kernel: [    0.798610] io scheduler deadline registered (default)
Jul 28 06:02:51 node-1 kernel: [    0.798635] io scheduler cfq registered
Jul 28 06:02:51 node-1 kernel: [    0.799152] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    0.799283] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    0.799404] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    0.799519] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    0.799637] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    0.799741] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    0.800143] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 28 06:02:51 node-1 kernel: [    0.800182] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 28 06:02:51 node-1 kernel: [    0.800213] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 28 06:02:51 node-1 kernel: [    0.800236] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800241] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800247] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 28 06:02:51 node-1 kernel: [    0.800257] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800261] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800265] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800269] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800273] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800276] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800280] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800284] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800287] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800291] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800295] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800298] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800304] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 28 06:02:51 node-1 kernel: [    0.800314] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800319] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 28 06:02:51 node-1 kernel: [    0.800346] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800352] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 28 06:02:51 node-1 kernel: [    0.800371] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800375] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 28 06:02:51 node-1 kernel: [    0.800381] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 28 06:02:51 node-1 kernel: [    0.800431] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 28 06:02:51 node-1 kernel: [    0.800450] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 28 06:02:51 node-1 kernel: [    0.800454] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 28 06:02:51 node-1 kernel: [    0.800463] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 28 06:02:51 node-1 kernel: [    0.800500] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 28 06:02:51 node-1 kernel: [    0.800501] vesafb: scrolling: redraw
Jul 28 06:02:51 node-1 kernel: [    0.800502] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 28 06:02:51 node-1 kernel: [    0.820885] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 28 06:02:51 node-1 kernel: [    0.829399] Console: switching to colour frame buffer device 80x30
Jul 28 06:02:51 node-1 kernel: [    0.838155] fb0: VESA VGA frame buffer device
Jul 28 06:02:51 node-1 kernel: [    0.838354] intel_idle: MWAIT substates: 0x2120
Jul 28 06:02:51 node-1 kernel: [    0.838355] intel_idle: v0.4 model 0x3F
Jul 28 06:02:51 node-1 kernel: [    0.838356] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 28 06:02:51 node-1 kernel: [    0.838582] ipmi message handler version 39.2
Jul 28 06:02:51 node-1 kernel: [    0.838869] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 28 06:02:51 node-1 kernel: [    0.839302] ACPI: AC Adapter [P111] (on-line)
Jul 28 06:02:51 node-1 kernel: [    0.844538] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 28 06:02:51 node-1 kernel: [    0.855560] ACPI: Power Button [PWRB]
Jul 28 06:02:51 node-1 kernel: [    0.861342] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 28 06:02:51 node-1 kernel: [    0.872995] ACPI: Power Button [PWRF]
Jul 28 06:02:51 node-1 kernel: [    0.888516] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 28 06:02:51 node-1 kernel: [    0.900176] pstore: Registered erst as persistent store backend
Jul 28 06:02:51 node-1 kernel: [    0.906379] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 28 06:02:51 node-1 kernel: [    0.918303] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 28 06:02:51 node-1 kernel: [    0.945031] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 28 06:02:51 node-1 kernel: [    0.978325] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 28 06:02:51 node-1 kernel: [    0.992383] Linux agpgart interface v0.103
Jul 28 06:02:51 node-1 kernel: [    1.000017] brd: module loaded
Jul 28 06:02:51 node-1 kernel: [    1.007115] loop: module loaded
Jul 28 06:02:51 node-1 kernel: [    1.013829] libphy: Fixed MDIO Bus: probed
Jul 28 06:02:51 node-1 kernel: [    1.020300] tun: Universal TUN/TAP device driver, 1.6
Jul 28 06:02:51 node-1 kernel: [    1.026771] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 28 06:02:51 node-1 kernel: [    1.033293] PPP generic driver version 2.4.2
Jul 28 06:02:51 node-1 kernel: [    1.039690] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 28 06:02:51 node-1 kernel: [    1.046116] ehci-pci: EHCI PCI platform driver
Jul 28 06:02:51 node-1 kernel: [    1.052639] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 28 06:02:51 node-1 kernel: [    1.059064] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 28 06:02:51 node-1 kernel: [    1.071588] ehci-pci 0000:00:1a.0: debug port 2
Jul 28 06:02:51 node-1 kernel: [    1.081781] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 28 06:02:51 node-1 kernel: [    1.081799] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 28 06:02:51 node-1 kernel: [    1.098478] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 28 06:02:51 node-1 kernel: [    1.104575] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 06:02:51 node-1 kernel: [    1.110755] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 06:02:51 node-1 kernel: [    1.122642] usb usb1: Product: EHCI Host Controller
Jul 28 06:02:51 node-1 kernel: [    1.128792] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 06:02:51 node-1 kernel: [    1.134914] usb usb1: SerialNumber: 0000:00:1a.0
Jul 28 06:02:51 node-1 kernel: [    1.140939] hub 1-0:1.0: USB hub found
Jul 28 06:02:51 node-1 kernel: [    1.146796] hub 1-0:1.0: 2 ports detected
Jul 28 06:02:51 node-1 kernel: [    1.152667] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 28 06:02:51 node-1 kernel: [    1.158328] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 28 06:02:51 node-1 kernel: [    1.169416] ehci-pci 0000:00:1d.0: debug port 2
Jul 28 06:02:51 node-1 kernel: [    1.178804] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 28 06:02:51 node-1 kernel: [    1.178807] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 28 06:02:51 node-1 kernel: [    1.194396] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 28 06:02:51 node-1 kernel: [    1.199660] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 06:02:51 node-1 kernel: [    1.205012] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 06:02:51 node-1 kernel: [    1.215754] usb usb2: Product: EHCI Host Controller
Jul 28 06:02:51 node-1 kernel: [    1.221273] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 06:02:51 node-1 kernel: [    1.226850] usb usb2: SerialNumber: 0000:00:1d.0
Jul 28 06:02:51 node-1 kernel: [    1.232403] hub 2-0:1.0: USB hub found
Jul 28 06:02:51 node-1 kernel: [    1.237775] hub 2-0:1.0: 2 ports detected
Jul 28 06:02:51 node-1 kernel: [    1.243098] ehci-platform: EHCI generic platform driver
Jul 28 06:02:51 node-1 kernel: [    1.248366] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 28 06:02:51 node-1 kernel: [    1.253695] ohci-pci: OHCI PCI platform driver
Jul 28 06:02:51 node-1 kernel: [    1.259022] ohci-platform: OHCI generic platform driver
Jul 28 06:02:51 node-1 kernel: [    1.264256] uhci_hcd: USB Universal Host Controller Interface driver
Jul 28 06:02:51 node-1 kernel: [    1.269640] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 28 06:02:51 node-1 kernel: [    1.462174] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 28 06:02:51 node-1 kernel: [    1.773926] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 28 06:02:51 node-1 kernel: [    1.790190] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 28 06:02:51 node-1 kernel: [    1.795805] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 06:02:51 node-1 kernel: [    1.801583] hub 1-1:1.0: USB hub found
Jul 28 06:02:51 node-1 kernel: [    1.807176] hub 1-1:1.0: 6 ports detected
Jul 28 06:02:51 node-1 kernel: [    1.921805] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 28 06:02:51 node-1 kernel: [    2.308552] i8042: No controller found
Jul 28 06:02:51 node-1 kernel: [    2.314159] mousedev: PS/2 mouse device common for all mice
Jul 28 06:02:51 node-1 kernel: [    2.319914] rtc_cmos 00:02: RTC can wake from S4
Jul 28 06:02:51 node-1 kernel: [    2.325645] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 28 06:02:51 node-1 kernel: [    2.326050] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 28 06:02:51 node-1 kernel: [    2.326051] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 06:02:51 node-1 kernel: [    2.326561] hub 2-1:1.0: USB hub found
Jul 28 06:02:51 node-1 kernel: [    2.326801] hub 2-1:1.0: 8 ports detected
Jul 28 06:02:51 node-1 kernel: [    2.353974] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 28 06:02:51 node-1 kernel: [    2.365378] device-mapper: uevent: version 1.0.3
Jul 28 06:02:51 node-1 kernel: [    2.371139] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 28 06:02:51 node-1 kernel: [    2.382642] ledtrig-cpu: registered to indicate activity on CPUs
Jul 28 06:02:51 node-1 kernel: [    2.388642] TCP: cubic registered
Jul 28 06:02:51 node-1 kernel: [    2.394509] NET: Registered protocol family 10
Jul 28 06:02:51 node-1 kernel: [    2.400532] NET: Registered protocol family 17
Jul 28 06:02:51 node-1 kernel: [    2.406270] Key type dns_resolver registered
Jul 28 06:02:51 node-1 kernel: [    2.412298] Loading compiled-in X.509 certificates
Jul 28 06:02:51 node-1 kernel: [    2.418481] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 28 06:02:51 node-1 kernel: [    2.430166] registered taskstats version 1
Jul 28 06:02:51 node-1 kernel: [    2.438308] Key type trusted registered
Jul 28 06:02:51 node-1 kernel: [    2.445960] Key type encrypted registered
Jul 28 06:02:51 node-1 kernel: [    2.451439] AppArmor: AppArmor sha1 policy hashing enabled
Jul 28 06:02:51 node-1 kernel: [    2.456927] IMA: No TPM chip found, activating TPM-bypass!
Jul 28 06:02:51 node-1 kernel: [    2.462963] regulator-dummy: disabling
Jul 28 06:02:51 node-1 kernel: [    2.468429]   Magic number: 8:705:14
Jul 28 06:02:51 node-1 kernel: [    2.474060] memory memory58: hash matches
Jul 28 06:02:51 node-1 kernel: [    2.479501] rtc_cmos 00:02: setting system clock to 2016-07-28 06:02:16 UTC (1469685736)
Jul 28 06:02:51 node-1 kernel: [    2.491745] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 28 06:02:51 node-1 kernel: [    2.497331] EDD information not available.
Jul 28 06:02:51 node-1 kernel: [    2.502937] PM: Hibernation image not present or could not be loaded.
Jul 28 06:02:51 node-1 kernel: [    2.503787] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 28 06:02:51 node-1 kernel: [    2.515060] Write protecting the kernel read-only data: 12288k
Jul 28 06:02:51 node-1 kernel: [    2.521344] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 28 06:02:51 node-1 kernel: [    2.534227] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 28 06:02:51 node-1 kernel: [    2.565885] device-mapper: multipath: version 1.6.0 loaded
Jul 28 06:02:51 node-1 kernel: [    2.573655] systemd-udevd[216]: starting version 204
Jul 28 06:02:51 node-1 kernel: [    2.598570] md: linear personality registered for level -1
Jul 28 06:02:51 node-1 kernel: [    2.601316] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 28 06:02:51 node-1 kernel: [    2.619213] md: multipath personality registered for level -4
Jul 28 06:02:51 node-1 kernel: [    2.627341] md: raid0 personality registered for level 0
Jul 28 06:02:51 node-1 kernel: [    2.635581] md: raid1 personality registered for level 1
Jul 28 06:02:51 node-1 kernel: [    2.642045] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 28 06:02:51 node-1 kernel: [    2.648301] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 28 06:02:51 node-1 kernel: [    2.648506] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 28 06:02:51 node-1 kernel: [    2.660754] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 28 06:02:51 node-1 kernel: [    2.660755] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 06:02:51 node-1 kernel: [    2.660759] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 06:02:51 node-1 kernel: [    2.660953] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.661066] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.661376] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.661490] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.661778] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.679736] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 28 06:02:51 node-1 kernel: [    2.679741] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 06:02:51 node-1 kernel: [    2.679742] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 06:02:51 node-1 kernel: [    2.680078] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.680256] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.680347] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.680478] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.680770] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.694393] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 28 06:02:51 node-1 kernel: [    2.694394] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 06:02:51 node-1 kernel: [    2.694404] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 06:02:51 node-1 kernel: [    2.694658] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.694710] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.694854] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.694953] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.695235] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.707944] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 28 06:02:51 node-1 kernel: [    2.707945] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 06:02:51 node-1 kernel: [    2.707946] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 06:02:51 node-1 kernel: [    2.708178] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.708305] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.708446] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.708545] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.708825] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 06:02:51 node-1 kernel: [    2.738460] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 28 06:02:51 node-1 kernel: [    2.738461] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 28 06:02:51 node-1 kernel: [    2.738473] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 28 06:02:51 node-1 kernel: [    2.738483] usb 2-1.4: Manufacturer: Avocent
Jul 28 06:02:51 node-1 kernel: [    2.738484] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 28 06:02:51 node-1 kernel: [    2.956909] raid6: sse2x1    7966 MB/s
Jul 28 06:02:51 node-1 kernel: [    3.028854] raid6: sse2x2    9781 MB/s
Jul 28 06:02:51 node-1 kernel: [    3.100795] raid6: sse2x4   10137 MB/s
Jul 28 06:02:51 node-1 kernel: [    3.172730] raid6: avx2x1   14945 MB/s
Jul 28 06:02:51 node-1 kernel: [    3.244667] raid6: avx2x2   18864 MB/s
Jul 28 06:02:51 node-1 kernel: [    3.316608] raid6: avx2x4   21366 MB/s
Jul 28 06:02:51 node-1 kernel: [    3.322208] raid6: using algorithm avx2x4 (21366 MB/s)
Jul 28 06:02:51 node-1 kernel: [    3.327756] raid6: using avx2x2 recovery algorithm
Jul 28 06:02:51 node-1 kernel: [    3.333370] Switched to clocksource tsc
Jul 28 06:02:51 node-1 kernel: [    3.333416] megasas: FW now in Ready state
Jul 28 06:02:51 node-1 kernel: [    3.333502] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333524] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333570] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333614] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333652] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333687] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333735] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333770] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333811] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333848] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333891] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333927] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333962] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.333999] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.334039] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.334083] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 28 06:02:51 node-1 kernel: [    3.334240] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 28 06:02:51 node-1 kernel: [    3.355715] xor: automatically using best checksumming function:
Jul 28 06:02:51 node-1 kernel: [    3.364451] hidraw: raw HID events driver (C) Jiri Kosina
Jul 28 06:02:51 node-1 kernel: [    3.372642] usbcore: registered new interface driver usbhid
Jul 28 06:02:51 node-1 kernel: [    3.378089] usbhid: USB HID core driver
Jul 28 06:02:51 node-1 kernel: [    3.384316] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 28 06:02:51 node-1 kernel: [    3.395120] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 28 06:02:51 node-1 kernel: [    3.400514]    avx       : 35726.000 MB/sec
Jul 28 06:02:51 node-1 kernel: [    3.411361] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 28 06:02:51 node-1 kernel: [    3.422668] async_tx: api initialized (async)
Jul 28 06:02:51 node-1 kernel: [    3.422838] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 28 06:02:51 node-1 kernel: [    3.422896] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 28 06:02:51 node-1 kernel: [    3.423302] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 28 06:02:51 node-1 kernel: [    3.467276] md: raid6 personality registered for level 6
Jul 28 06:02:51 node-1 kernel: [    3.473709] md: raid5 personality registered for level 5
Jul 28 06:02:51 node-1 kernel: [    3.480085] md: raid4 personality registered for level 4
Jul 28 06:02:51 node-1 kernel: [    3.489424] md: raid10 personality registered for level 10
Jul 28 06:02:51 node-1 kernel: [    3.545249] multipathd (356): /proc/356/oom_adj is deprecated, please use /proc/356/oom_score_adj instead.
Jul 28 06:02:51 node-1 kernel: [    3.668338] megasas:IOC Init cmd success
Jul 28 06:02:51 node-1 kernel: [    3.696330] megasas: INIT adapter done
Jul 28 06:02:51 node-1 kernel: [    3.772263] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 28 06:02:51 node-1 kernel: [    3.779172] scsi0 : LSI SAS based MegaRAID driver
Jul 28 06:02:51 node-1 kernel: [    3.786593] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 06:02:51 node-1 kernel: [    3.808640] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 06:02:51 node-1 kernel: [    3.824900] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 28 06:02:51 node-1 kernel: [    3.825654] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 28 06:02:51 node-1 kernel: [    3.826429] sd 0:2:0:0: [sda] Write Protect is off
Jul 28 06:02:51 node-1 kernel: [    3.826453] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 28 06:02:51 node-1 kernel: [    3.826902] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 28 06:02:51 node-1 kernel: [    3.860289]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 28 06:02:51 node-1 kernel: [    3.864440] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 28 06:02:51 node-1 kernel: [    3.987833] random: lvm urandom read with 26 bits of entropy available
Jul 28 06:02:51 node-1 kernel: [    4.119397] bio: create slab <bio-1> at 1
Jul 28 06:02:51 node-1 kernel: [    4.928726] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 06:02:51 node-1 kernel: [    5.517818] random: nonblocking pool is initialized
Jul 28 06:02:51 node-1 kernel: [    5.605230] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 28 06:02:51 node-1 kernel: [    5.634042] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 28 06:02:51 node-1 kernel: [    5.722226] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 28 06:02:51 node-1 kernel: [    5.806037] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 28 06:02:51 node-1 kernel: [    5.869216] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 06:02:51 node-1 kernel: [    6.049459] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 28 06:02:51 node-1 kernel: [    6.098567] XFS (dm-0): Mounting Filesystem
Jul 28 06:02:51 node-1 kernel: [    6.388542] XFS (dm-0): Ending clean mount
Jul 28 06:02:51 node-1 kernel: [    6.456195] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 06:02:51 node-1 kernel: [    6.481528] XFS (dm-1): Mounting Filesystem
Jul 28 06:02:51 node-1 kernel: [    6.620320] XFS (dm-1): Ending clean mount
Jul 28 06:02:51 node-1 kernel: [    8.375591] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 28 06:02:51 node-1 kernel: [    8.399696] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 28 06:02:51 node-1 kernel: [    8.572815] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 28 06:02:51 node-1 kernel: [    8.572819] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 28 06:02:51 node-1 kernel: [    8.572822] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 28 06:02:51 node-1 kernel: [    8.572826] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 28 06:02:51 node-1 kernel: [    8.606808] systemd-udevd[778]: starting version 204
Jul 28 06:02:51 node-1 kernel: [    8.811812] power_meter ACPI000D:00: Found ACPI power meter.
Jul 28 06:02:51 node-1 kernel: [    8.811842] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 28 06:02:51 node-1 kernel: [    8.818687] wmi: Mapper loaded
Jul 28 06:02:51 node-1 kernel: [    8.837336] IPMI System Interface driver.
Jul 28 06:02:51 node-1 kernel: [    8.837393] ipmi_si: probing via ACPI
Jul 28 06:02:51 node-1 kernel: [    8.837408] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 28 06:02:51 node-1 kernel: [    8.837409] ipmi_si: Adding ACPI-specified kcs state machine
Jul 28 06:02:51 node-1 kernel: [    8.837418] ipmi_si: probing via SMBIOS
Jul 28 06:02:51 node-1 kernel: [    8.837419] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 06:02:51 node-1 kernel: [    8.837420] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 28 06:02:51 node-1 kernel: [    8.837421] ipmi_si: probing via SPMI
Jul 28 06:02:51 node-1 kernel: [    8.837422] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 06:02:51 node-1 kernel: [    8.837422] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 28 06:02:51 node-1 kernel: [    8.837423] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 28 06:02:51 node-1 kernel: [    8.864063] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 28 06:02:51 node-1 kernel: [    8.867385] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 28 06:02:51 node-1 kernel: [    8.867390] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 06:02:51 node-1 kernel: [    8.867392] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 28 06:02:51 node-1 kernel: [    8.867394] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 06:02:51 node-1 kernel: [    8.867410] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 28 06:02:51 node-1 kernel: [    8.940338] systemd-udevd[795]: renamed network interface eth1 to enp7s0
Jul 28 06:02:51 node-1 kernel: [    8.964222] systemd-udevd[806]: renamed network interface eth2 to enp8s0
Jul 28 06:02:51 node-1 kernel: [    8.992190] systemd-udevd[807]: renamed network interface eth0 to enp6s0
Jul 28 06:02:51 node-1 kernel: [    8.993972] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 28 06:02:51 node-1 kernel: [    8.993978] ipmi_si 00:09: IPMI kcs interface initialized
Jul 28 06:02:51 node-1 kernel: [    9.012177] systemd-udevd[796]: renamed network interface eth3 to enp9s0
Jul 28 06:02:51 node-1 kernel: [    9.338596] type=1400 audit(1469685743.358:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1043 comm="apparmor_parser"
Jul 28 06:02:51 node-1 kernel: [    9.338741] type=1400 audit(1469685743.358:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1043 comm="apparmor_parser"
Jul 28 06:02:51 node-1 kernel: [    9.338859] type=1400 audit(1469685743.358:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1043 comm="apparmor_parser"
Jul 28 06:02:51 node-1 kernel: [    9.344020] type=1400 audit(1469685743.366:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1042 comm="apparmor_parser"
Jul 28 06:02:51 node-1 kernel: [    9.344169] type=1400 audit(1469685743.366:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1042 comm="apparmor_parser"
Jul 28 06:02:51 node-1 kernel: [    9.344292] type=1400 audit(1469685743.366:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1042 comm="apparmor_parser"
Jul 28 06:02:51 node-1 kernel: [    9.356446] type=1400 audit(1469685743.378:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1040 comm="apparmor_parser"
Jul 28 06:02:51 node-1 kernel: [    9.356591] type=1400 audit(1469685743.378:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1040 comm="apparmor_parser"
Jul 28 06:02:51 node-1 kernel: [    9.356713] type=1400 audit(1469685743.378:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1040 comm="apparmor_parser"
Jul 28 06:02:51 node-1 kernel: [    9.371913] type=1400 audit(1469685743.394:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1041 comm="apparmor_parser"
Jul 28 06:02:51 node-1 kernel: [   10.012087] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 28 06:02:51 node-1 kernel: [   10.015073] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 28 06:02:51 node-1 kernel: [   10.215047] enic 0000:06:00.0 enp6s0: Link UP
Jul 28 06:02:51 node-1 kernel: [   10.216169] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 28 06:02:51 node-1 kernel: [   10.216175] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 28 06:02:51 node-1 kernel: [   19.623294] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 28 06:02:52 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 28 06:02:53 node-1 kernel: [   38.607486] init: failsafe main process (8397) killed by TERM signal
Jul 28 06:02:53 node-1 dbus[8443]: [system] AppArmor D-Bus mediation is enabled
Jul 28 06:02:53 node-1 kernel: [   38.782220] audit_printk_skb: 30 callbacks suppressed
Jul 28 06:02:53 node-1 kernel: [   38.782222] type=1400 audit(1469685773.287:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8523 comm="apparmor_parser"
Jul 28 06:02:53 node-1 kernel: [   38.782495] type=1400 audit(1469685773.287:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8522 comm="apparmor_parser"
Jul 28 06:02:53 node-1 kernel: [   38.782585] type=1400 audit(1469685773.287:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8522 comm="apparmor_parser"
Jul 28 06:02:53 node-1 kernel: [   38.782619] type=1400 audit(1469685773.287:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 28 06:02:53 node-1 kernel: [   38.783903] type=1400 audit(1469685773.287:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8522 comm="apparmor_parser"
Jul 28 06:02:53 node-1 kernel: [   38.783936] type=1400 audit(1469685773.287:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 28 06:02:53 node-1 kernel: [   38.784338] type=1400 audit(1469685773.287:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 28 06:02:53 node-1 kernel: [   38.850670] type=1400 audit(1469685773.355:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8525 comm="apparmor_parser"
Jul 28 06:02:53 node-1 anacron[8589]: Anacron 2.3 started on 2016-07-28
Jul 28 06:02:53 node-1 cron[8554]: (CRON) INFO (pidfile fd = 3)
Jul 28 06:02:53 node-1 anacron[8589]: Will run job `cron.daily' in 5 min.
Jul 28 06:02:53 node-1 anacron[8589]: Will run job `cron.weekly' in 10 min.
Jul 28 06:02:53 node-1 anacron[8589]: Will run job `cron.monthly' in 15 min.
Jul 28 06:02:53 node-1 anacron[8589]: Jobs will be executed sequentially
Jul 28 06:02:53 node-1 cron[8595]: (CRON) STARTUP (fork ok)
Jul 28 06:02:53 node-1 cron[8595]: (CRON) INFO (Running @reboot jobs)
Jul 28 06:02:53 node-1 multipathd: path checkers start up
Jul 28 06:02:53 node-1 postfix/master[8734]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 28 06:02:57 node-1 puppet-agent[9048]: Reopening log files
Jul 28 06:02:58 node-1 puppet-agent[9048]: Could not request certificate: Connection refused - connect(2)
Jul 28 06:03:01 node-1 CRON[9079]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 28 06:03:11 node-1 puppet-user[9318]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 28 06:03:11 node-1 puppet-user[9318]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 28 06:03:12 node-1 puppet-user[9318]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 28 06:03:12 node-1 puppet-user[9318]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 28 06:03:12 node-1 puppet-user[9318]: Finished catalog run in 0.96 seconds
Jul 28 06:03:14 node-1 multipathd: uevent trigger error
Jul 28 06:03:14 node-1 puppet-user[9743]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 06:03:14 node-1 puppet-user[9743]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 28 06:03:14 node-1 puppet-user[9743]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 28 06:03:14 node-1 puppet-user[9743]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 28 06:03:14 node-1 puppet-user[9743]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 28 06:03:14 node-1 puppet-user[9743]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 28 06:03:14 node-1 puppet-user[9743]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 28 06:03:14 node-1 puppet-user[9743]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 28 06:03:14 node-1 puppet-user[9743]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 28 06:03:14 node-1 puppet-user[9743]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 28 06:03:14 node-1 puppet-user[9743]: Finished catalog run in 0.06 seconds
Jul 28 06:03:15 node-1 puppet-user[10208]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 28 06:03:15 node-1 puppet-user[10208]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 28 06:03:16 node-1 puppet-user[10208]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 28 06:03:16 node-1 puppet-user[10208]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 28 06:03:16 node-1 puppet-user[10208]: Finished catalog run in 0.14 seconds
Jul 28 06:03:16 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 06:03:16 node-1 nailgun-agent: D, [2016-07-28T06:03:01.684456 #9082] DEBUG -- : Sleep for 15 seconds before sending request
Jul 28 06:03:16 node-1 nailgun-agent: I, [2016-07-28T06:03:16.696177 #9082]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 06:03:17 node-1 nailgun-agent: D, [2016-07-28T06:03:17.131041 #9082] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 28 06:03:17 node-1 puppet-user[10675]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 28 06:03:17 node-1 puppet-user[10675]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 28 06:03:17 node-1 puppet-user[10675]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 28 06:03:17 node-1 puppet-user[10675]: Finished catalog run in 0.03 seconds
Jul 28 06:03:18 node-1 puppet-user[11260]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 28 06:03:19 node-1 puppet-user[11260]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Jul 28 06:03:19 node-1 puppet-user[11260]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 28 06:03:20 node-1 puppet-user[11260]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Jul 28 06:03:21 node-1 puppet-user[11260]: Finished catalog run in 1.82 seconds
Jul 28 06:03:21 node-1 kernel: [   66.572204] init: plymouth-upstart-bridge main process ended, respawning
Jul 28 06:03:21 node-1 puppet-agent[9048]: Could not run: SIGTERM
Jul 28 06:03:21 node-1 kernel: [   66.918379] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 28 06:03:21 node-1 ec2: 
Jul 28 06:03:21 node-1 ec2: #############################################################
Jul 28 06:03:21 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 28 06:03:21 node-1 ec2: 1024 74:87:b8:16:24:bd:a0:8c:f6:13:ef:b3:56:f5:73:01  root@node-1.domain.tld (DSA)
Jul 28 06:03:21 node-1 ec2: 256 2e:9f:6b:dc:8f:9b:de:04:29:e4:99:c7:ac:62:b1:bb  root@node-1.domain.tld (ECDSA)
Jul 28 06:03:21 node-1 ec2: 256 5b:7d:07:31:5a:5b:f1:f7:e1:48:83:f0:43:51:cc:18  root@node-1.domain.tld (ED25519)
Jul 28 06:03:21 node-1 ec2: 2048 7c:94:48:31:6c:12:9c:5c:52:0e:74:90:c0:c9:95:76  root@node-1.domain.tld (RSA)
Jul 28 06:03:21 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 28 06:03:21 node-1 ec2: #############################################################
Jul 28 06:03:22 node-1 puppet-user[11927]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 28 06:03:22 node-1 puppet-user[11927]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Jul 28 06:03:22 node-1 puppet-user[11927]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 28 06:03:22 node-1 puppet-user[11927]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Jul 28 06:03:22 node-1 puppet-user[11927]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 28 06:03:23 node-1 puppet-user[11927]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 28 06:03:23 node-1 puppet-user[11927]: Finished catalog run in 0.21 seconds
Jul 28 06:03:24 node-1 puppet-user[12455]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 28 06:03:24 node-1 puppet-user[12455]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Jul 28 06:03:24 node-1 puppet-user[12455]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 28 06:03:24 node-1 kernel: [   70.248669] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 28 06:03:24 node-1 kernel: [   70.248721] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 28 06:03:24 node-1 puppet-user[12455]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 28 06:03:24 node-1 puppet-user[12455]: Finished catalog run in 0.05 seconds
Jul 28 06:03:26 node-1 puppet-user[12921]: (Scope(Class[main])) MODULAR: sync_time
Jul 28 06:03:26 node-1 puppet-user[12921]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 28 06:03:26 node-1 ntpdate[13340]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.214969 #9082] DEBUG -- : Trying to find block devices
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.215089 #9082] DEBUG -- : Found block device: sda
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.215197 #9082] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.215220 #9082] DEBUG -- : Trying to get list of physical devices
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.215410 #9082] DEBUG -- : Getting udev properties for device: sda
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.217420 #9082] 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
Jul 28 06:03:29 node-1 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22420", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.217443 #9082] DEBUG -- : Trying to find out if device sda is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.217486 #9082] DEBUG -- : Device sda removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.217501 #9082] DEBUG -- : Device sda seems to be appropriate
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.217930 #9082] DEBUG -- : Getting udev properties for device: dm-0
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.219804 #9082] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-omeQDRAf1wMFF4YgbxfJlZ1Umm31l0FabA5s1z360cUEDJw7suIhRvEPjolL6h3Y /dev/disk/by-uuid/608dbe81-3de6-491e-ae77-41e7d0938c2e /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-omeQDRAf1wMFF4YgbxfJlZ1Umm31l0FabA5s1z360cUEDJw7suIhRvEPjolL6h3Y", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"608dbe81-3de6-491e-ae77-41e7d0938c2e", "ID_FS_UUID_ENC"=>"608dbe81-3de6-491e-ae77-41e7d0938c2e", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79367", "nomdmonddf"=>"1", "nomd
Jul 28 06:03:29 node-1 nailgun-agent: monisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.219840 #9082] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.219868 #9082] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.219881 #9082] DEBUG -- : Device dm-0 seems to be appropriate
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.219895 #9082] DEBUG -- : Getting udev properties for device: dm-1
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.221650 #9082] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-zr41UEdeqMwjTJ6fH9pLTJY9inRwlDX8z6xipXBigFUZgYLuFfa1GQp8L9cblISZ /dev/disk/by-uuid/46d6bf64-6f8b-4a9a-a2a3-c996dd06bace /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-zr41UEdeqMwjTJ6fH9pLTJY9inRwlDX8z6xipXBigFUZgYLuFfa1GQp8L9cblISZ", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"46d6bf64-6f8b-4a9a-a2a3-c996dd06bace", "ID_FS_UUID_ENC"=>"46d6bf64-6f8b-4a9a-a2a3-c996dd06bace", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14
Jul 28 06:03:29 node-1 nailgun-agent: 73", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.221674 #9082] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.221732 #9082] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.221793 #9082] DEBUG -- : Device dm-1 seems to be appropriate
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.221806 #9082] DEBUG -- : Getting udev properties for device: dm-2
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.223417 #9082] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-AIwt8qsZqiAyALOCGer8HD9dezVKvbKFfrek9XyZMfNnu72N0CRYEp1Qqd8mHgEm /dev/disk/by-uuid/9bf61cc4-9a0e-43fa-89c6-bd892df3ee96 /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-AIwt8qsZqiAyALOCGer8HD9dezVKvbKFfrek9XyZMfNnu72N0CRYEp1Qqd8mHgEm", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9bf61cc4-9a0e-43fa-89c6-bd892df3ee96", "ID_FS_UUID_ENC"=>"9bf61cc4-9a0e-43fa-89c6-bd892df3ee96", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"8347", "nomdmondd
Jul 28 06:03:29 node-1 nailgun-agent: f"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.223442 #9082] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.223496 #9082] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.223510 #9082] DEBUG -- : Device dm-2 seems to be appropriate
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.223525 #9082] DEBUG -- : Getting udev properties for device: dm-3
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.225193 #9082] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-pyHY03kfEtVd1qxjQoctzYUfMcQGA9bKsA3AyKHeDOimfrxfdmtnMDwLSjRGXKP6 /dev/disk/by-uuid/24404931-be30-417c-a5d4-a3f1e7954da2 /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-pyHY03kfEtVd1qxjQoctzYUfMcQGA9bKsA3AyKHeDOimfrxfdmtnMDwLSjRGXKP6", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"24404931-be30-417c-a5d4-a3f1e7954da2", "ID_FS_UUID_ENC"=>"24404931-be30-417c-a5d4-a3f1e7954da2", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96519", "nomdmonddf"=>"1", 
Jul 28 06:03:29 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.225229 #9082] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.225270 #9082] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.225283 #9082] DEBUG -- : Device dm-3 seems to be appropriate
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.225297 #9082] DEBUG -- : Getting udev properties for device: dm-4
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.226966 #9082] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-mK3cCgujH0sPMquPYu6BKlGTSbNQt1WW2heWkkapFwI3S9bcNZOMUyF561xeioAu /dev/disk/by-uuid/97a88fb5-a901-4eed-a9df-e90816d42415 /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-mK3cCgujH0sPMquPYu6BKlGTSbNQt1WW2heWkkapFwI3S9bcNZOMUyF561xeioAu", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"97a88fb5-a901-4eed-a9df-e90816d42415", "ID_FS_UUID_ENC"=>"97a88fb5-a901-4eed-a9df-e90816d42415", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1806", "nomdmonddf"=>"1", "nomdm
Jul 28 06:03:29 node-1 nailgun-agent: onisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.226992 #9082] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.227030 #9082] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.227044 #9082] DEBUG -- : Device dm-4 seems to be appropriate
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.227070 #9082] DEBUG -- : Getting udev properties for device: dm-5
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.228683 #9082] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-mK3cCgujH0sPMquPYu6BKlGTSbNQt1WW71BQH1nu43TfZmwWTJjPefvaQp77uvzy /dev/disk/by-uuid/c49a62e8-470e-4332-98a4-ce5ddd7ce7ba /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-mK3cCgujH0sPMquPYu6BKlGTSbNQt1WW71BQH1nu43TfZmwWTJjPefvaQp77uvzy", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"c49a62e8-470e-4332-98a4-ce5ddd7ce7ba", "ID_FS_UUID_ENC"=>"c49a62e8-470e-4332-98a4-ce5ddd7ce7ba", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2387", "nomdmonddf"=>"1", "nomdmonisw"=
Jul 28 06:03:29 node-1 nailgun-agent: >"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.228708 #9082] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.228747 #9082] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.228805 #9082] DEBUG -- : Device dm-5 seems to be appropriate
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.228820 #9082] DEBUG -- : Getting udev properties for device: ram0
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.230475 #9082] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15301", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.230495 #9082] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.230528 #9082] DEBUG -- : Device ram0 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.230546 #9082] DEBUG -- : Getting udev properties for device: ram1
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.232085 #9082] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15310", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.232105 #9082] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.232136 #9082] DEBUG -- : Device ram1 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.232177 #9082] DEBUG -- : Getting udev properties for device: ram2
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.233635 #9082] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15478", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.233707 #9082] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.233754 #9082] DEBUG -- : Device ram2 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.233772 #9082] DEBUG -- : Getting udev properties for device: ram3
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.235240 #9082] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15493", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.235261 #9082] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.235298 #9082] DEBUG -- : Device ram3 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.235317 #9082] DEBUG -- : Getting udev properties for device: ram4
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.236803 #9082] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15507", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.236824 #9082] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.236853 #9082] DEBUG -- : Device ram4 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.236889 #9082] DEBUG -- : Getting udev properties for device: ram5
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.238462 #9082] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15521", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.238483 #9082] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.238514 #9082] DEBUG -- : Device ram5 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.238558 #9082] DEBUG -- : Getting udev properties for device: ram6
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.240109 #9082] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15535", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.240130 #9082] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.240159 #9082] DEBUG -- : Device ram6 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.240179 #9082] DEBUG -- : Getting udev properties for device: ram7
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.241733 #9082] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15552", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.241753 #9082] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.241781 #9082] DEBUG -- : Device ram7 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.241816 #9082] DEBUG -- : Getting udev properties for device: ram8
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.243419 #9082] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15568", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.243470 #9082] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.243504 #9082] DEBUG -- : Device ram8 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.243522 #9082] DEBUG -- : Getting udev properties for device: ram9
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.244996 #9082] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15584", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.245017 #9082] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.245061 #9082] DEBUG -- : Device ram9 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.245080 #9082] DEBUG -- : Getting udev properties for device: loop0
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.246544 #9082] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15239", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.246566 #9082] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.246617 #9082] DEBUG -- : Device loop0 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.246635 #9082] DEBUG -- : Getting udev properties for device: loop1
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.248236 #9082] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15248", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.248256 #9082] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.248291 #9082] DEBUG -- : Device loop1 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.248310 #9082] DEBUG -- : Getting udev properties for device: loop2
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.249797 #9082] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15255", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.249818 #9082] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.249847 #9082] DEBUG -- : Device loop2 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.249902 #9082] DEBUG -- : Getting udev properties for device: loop3
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.251515 #9082] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15264", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.251535 #9082] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.251566 #9082] DEBUG -- : Device loop3 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.251584 #9082] DEBUG -- : Getting udev properties for device: loop4
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.253283 #9082] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15272", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.253303 #9082] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.253340 #9082] DEBUG -- : Device loop4 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.253359 #9082] DEBUG -- : Getting udev properties for device: loop5
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.254834 #9082] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15279", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.254854 #9082] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.254891 #9082] DEBUG -- : Device loop5 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.254909 #9082] DEBUG -- : Getting udev properties for device: loop6
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.256396 #9082] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15287", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.256418 #9082] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.256448 #9082] DEBUG -- : Device loop6 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.256487 #9082] DEBUG -- : Getting udev properties for device: loop7
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.258328 #9082] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15294", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.258379 #9082] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.258408 #9082] DEBUG -- : Device loop7 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.258424 #9082] DEBUG -- : Getting udev properties for device: ram10
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.259964 #9082] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15394", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.259986 #9082] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.260041 #9082] DEBUG -- : Device ram10 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.260059 #9082] DEBUG -- : Getting udev properties for device: ram11
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.261631 #9082] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15413", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.261651 #9082] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.261689 #9082] DEBUG -- : Device ram11 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.261707 #9082] DEBUG -- : Getting udev properties for device: ram12
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.263237 #9082] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15425", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.263257 #9082] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.263288 #9082] DEBUG -- : Device ram12 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.263324 #9082] DEBUG -- : Getting udev properties for device: ram13
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.264885 #9082] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15438", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.264906 #9082] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.264934 #9082] DEBUG -- : Device ram13 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.264953 #9082] DEBUG -- : Getting udev properties for device: ram14
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.266521 #9082] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15449", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.266542 #9082] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.266576 #9082] DEBUG -- : Device ram14 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.266643 #9082] DEBUG -- : Getting udev properties for device: ram15
Jul 28 06:03:29 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268163 #9082] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15463", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268184 #9082] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268270 #9082] DEBUG -- : Device ram15 removable parameter: "0"
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268305 #9082] 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"}]
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268318 #9082] DEBUG -- : Block device seems to be physical data storage: sda
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268361 #9082] DEBUG -- : Found block device: dm-0
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268375 #9082] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268387 #9082] DEBUG -- : Found block device: dm-1
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268428 #9082] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268438 #9082] DEBUG -- : Found block device: dm-2
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268449 #9082] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268457 #9082] DEBUG -- : Found block device: dm-3
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268490 #9082] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268499 #9082] DEBUG -- : Found block device: dm-4
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268508 #9082] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268554 #9082] DEBUG -- : Found block device: dm-5
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268565 #9082] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268574 #9082] DEBUG -- : Found block device: ram0
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268584 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268592 #9082] DEBUG -- : Found block device: ram1
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268603 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268651 #9082] DEBUG -- : Found block device: ram2
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268663 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268671 #9082] DEBUG -- : Found block device: ram3
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268680 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268688 #9082] DEBUG -- : Found block device: ram4
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268737 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268745 #9082] DEBUG -- : Found block device: ram5
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268758 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268766 #9082] DEBUG -- : Found block device: ram6
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268777 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268786 #9082] DEBUG -- : Found block device: ram7
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268797 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268835 #9082] DEBUG -- : Found block device: ram8
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268845 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268854 #9082] DEBUG -- : Found block device: ram9
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268864 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268873 #9082] DEBUG -- : Found block device: loop0
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268907 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268915 #9082] DEBUG -- : Found block device: loop1
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268926 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268934 #9082] DEBUG -- : Found block device: loop2
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268967 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268976 #9082] DEBUG -- : Found block device: loop3
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.268987 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269018 #9082] DEBUG -- : Found block device: loop4
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269029 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269039 #9082] DEBUG -- : Found block device: loop5
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269049 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269072 #9082] DEBUG -- : Found block device: loop6
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269083 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269092 #9082] DEBUG -- : Found block device: loop7
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269111 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269120 #9082] DEBUG -- : Found block device: ram10
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269145 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269154 #9082] DEBUG -- : Found block device: ram11
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269171 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269201 #9082] DEBUG -- : Found block device: ram12
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269212 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269242 #9082] DEBUG -- : Found block device: ram13
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269252 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269261 #9082] DEBUG -- : Found block device: ram14
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269283 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269291 #9082] DEBUG -- : Found block device: ram15
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269302 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.269331 #9082] 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}]
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.330432 #9082] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 28 06:03:29 node-1 nailgun-agent: D, [2016-07-28T06:03:29.330496 #9082] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 28 06:03:32 node-1 ntpdate[13340]: adjust time server 10.20.0.2 offset -0.000533 sec
Jul 28 06:03:32 node-1 puppet-user[12921]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 28 06:03:32 node-1 puppet-user[12921]: Finished catalog run in 6.16 seconds
Jul 28 06:03:38 node-1 puppet-user[13722]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 06:03:38 node-1 puppet-user[13722]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 28 06:03:38 node-1 puppet-user[13722]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 28 06:03:38 node-1 puppet-user[13722]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Jul 28 06:03:38 node-1 puppet-user[13722]: Finished catalog run in 0.07 seconds
Jul 28 06:03:39 node-1 puppet-user[14174]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 28 06:03:40 node-1 puppet-user[14174]: Compiled catalog for node-1.domain.tld in environment production in 1.37 seconds
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 28 06:03:41 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315118 #9082] DEBUG -- : Trying to find block devices
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315178 #9082] DEBUG -- : Found block device: sda
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315255 #9082] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315277 #9082] DEBUG -- : Block device seems to be physical data storage: sda
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315304 #9082] DEBUG -- : Found block device: dm-0
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315318 #9082] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315330 #9082] DEBUG -- : Found block device: dm-1
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315378 #9082] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315388 #9082] DEBUG -- : Found block device: dm-2
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315398 #9082] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315407 #9082] DEBUG -- : Found block device: dm-3
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315416 #9082] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315426 #9082] DEBUG -- : Found block device: dm-4
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315435 #9082] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315443 #9082] DEBUG -- : Found block device: dm-5
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315453 #9082] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315461 #9082] DEBUG -- : Found block device: ram0
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315488 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315497 #9082] DEBUG -- : Found block device: ram1
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315506 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315515 #9082] DEBUG -- : Found block device: ram2
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315525 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315533 #9082] DEBUG -- : Found block device: ram3
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315542 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315550 #9082] DEBUG -- : Found block device: ram4
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315559 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315567 #9082] DEBUG -- : Found block device: ram5
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315576 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315608 #9082] DEBUG -- : Found block device: ram6
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315628 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315636 #9082] DEBUG -- : Found block device: ram7
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315645 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315653 #9082] DEBUG -- : Found block device: ram8
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315662 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315669 #9082] DEBUG -- : Found block device: ram9
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315678 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315686 #9082] DEBUG -- : Found block device: loop0
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315695 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315702 #9082] DEBUG -- : Found block device: loop1
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315730 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315739 #9082] DEBUG -- : Found block device: loop2
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315748 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315756 #9082] DEBUG -- : Found block device: loop3
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315765 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315772 #9082] DEBUG -- : Found block device: loop4
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315781 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315789 #9082] DEBUG -- : Found block device: loop5
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315799 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315806 #9082] DEBUG -- : Found block device: loop6
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315837 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315846 #9082] DEBUG -- : Found block device: loop7
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315855 #9082] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315863 #9082] DEBUG -- : Found block device: ram10
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315871 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315879 #9082] DEBUG -- : Found block device: ram11
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315888 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315896 #9082] DEBUG -- : Found block device: ram12
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315904 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315912 #9082] DEBUG -- : Found block device: ram13
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315940 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315948 #9082] DEBUG -- : Found block device: ram14
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315972 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315980 #9082] DEBUG -- : Found block device: ram15
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.315989 #9082] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.316018 #9082] 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}]
Jul 28 06:03:41 node-1 nailgun-agent: D, [2016-07-28T06:03:41.486604 #9082] DEBUG -- : Response: status: 200 body: {"id": 1}
Jul 28 06:03:41 node-1 nailgun-agent: I, [2016-07-28T06:03:41.548235 #9082]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 28 06:03:41 node-1 puppet-user[14174]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 28 06:03:58 node-1 puppet-user[14174]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 28 06:03:58 node-1 puppet-user[14174]: Finished catalog run in 17.01 seconds
Jul 28 06:04:00 node-1 puppet-user[15313]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 28 06:04:00 node-1 puppet-user[15313]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Jul 28 06:04:01 node-1 CRON[15772]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 28 06:04:04 node-1 puppet-user[15313]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 28 06:04:28 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 06:04:28 node-1 nailgun-agent: I, [2016-07-28T06:04:28.720533 #15775]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 06:04:35 node-1 puppet-user[15313]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 28 06:04:35 node-1 puppet-user[15313]: Finished catalog run in 35.18 seconds
Jul 28 06:04:37 node-1 puppet-user[17912]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 28 06:04:38 node-1 puppet-user[17912]: Compiled catalog for node-1.domain.tld in environment production in 0.52 seconds
Jul 28 06:04:38 node-1 puppet-user[17912]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 28 06:04:38 node-1 puppet-user[17912]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 28 06:04:38 node-1 puppet-user[17912]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 28 06:04:38 node-1 puppet-user[17912]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 28 06:04:38 node-1 puppet-user[17912]: Finished catalog run in 0.09 seconds
Jul 28 06:04:40 node-1 puppet-user[18379]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 28 06:04:40 node-1 puppet-user[18379]: Compiled catalog for node-1.domain.tld in environment production in 0.78 seconds
Jul 28 06:04:41 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 28 06:04:41 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 28 06:04:41 node-1 crontab[18826]: (root) LIST (root)
Jul 28 06:04:41 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 28 06:04:41 node-1 crontab[18827]: (root) REPLACE (root)
Jul 28 06:04:41 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 06:04:41 node-1 nailgun-agent: I, [2016-07-28T06:04:41.864018 #15775]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 28 06:04:43 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 28 06:04:44 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 28 06:04:44 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 28 06:04:44 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 28 06:04:44 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 28 06:04:44 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 28 06:04:44 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 28 06:04:44 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 28 06:04:44 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 28 06:04:45 node-1 puppet-user[18379]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 28 06:04:46 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8370" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 06:04:46 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 28 06:04:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:04:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:04:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:04:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:04:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:05:06 node-1 multipathd: uevent trigger error
<27>Jul 28 06:05:06 node-1 multipathd: uevent trigger error
<27>Jul 28 06:05:06 node-1 multipathd: uevent trigger error
<27>Jul 28 06:05:06 node-1 multipathd: uevent trigger error
<27>Jul 28 06:05:06 node-1 multipathd: uevent trigger error
<27>Jul 28 06:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:06:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:06:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:06:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:06:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:06:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:06:43 node-1 ntpdate[2959]: no servers can be used, exiting
<27>Jul 28 06:07:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:18 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:18 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:18 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:18 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:18 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:18 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:07:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:42 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:42 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:42 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:42 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:42 node-1 multipathd: uevent trigger error
<27>Jul 28 06:08:44 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 06:08:45 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 06:08:51 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 06:08:51 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 06:08:56 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 06:09:02 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 06:09:02 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 06:09:09 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:09 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:09 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:09 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:09 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:09 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:09 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:22 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:22 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:22 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:22 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:22 node-1 multipathd: uevent trigger error
<129>Jul 28 06:09:24 node-1 haproxy[23044]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:25 node-1 haproxy[23049]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:25 node-1 haproxy[23049]: 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>Jul 28 06:09:25 node-1 haproxy[23049]: proxy mysqld has no server available!
<27>Jul 28 06:09:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:31 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:31 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:31 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:31 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:31 node-1 multipathd: uevent trigger error
<129>Jul 28 06:09:33 node-1 haproxy[25617]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:34 node-1 haproxy[25621]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:34 node-1 haproxy[25621]: 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>Jul 28 06:09:34 node-1 haproxy[25621]: proxy mysqld has no server available!
<129>Jul 28 06:09:34 node-1 haproxy[25621]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:35 node-1 haproxy[25621]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:35 node-1 haproxy[25621]: 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>Jul 28 06:09:35 node-1 haproxy[25621]: proxy object-storage has no server available!
<27>Jul 28 06:09:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:36 node-1 multipathd: uevent trigger error
<129>Jul 28 06:09:39 node-1 haproxy[27180]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:39 node-1 haproxy[27180]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:39 node-1 haproxy[27180]: 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>Jul 28 06:09:39 node-1 haproxy[27180]: proxy neutron has no server available!
<129>Jul 28 06:09:39 node-1 haproxy[27180]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:39 node-1 haproxy[27180]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:40 node-1 haproxy[27184]: 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>Jul 28 06:09:40 node-1 haproxy[27184]: proxy mysqld has no server available!
<129>Jul 28 06:09:40 node-1 haproxy[27184]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:40 node-1 haproxy[27184]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:40 node-1 haproxy[27184]: 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>Jul 28 06:09:40 node-1 haproxy[27184]: proxy object-storage has no server available!
<27>Jul 28 06:09:42 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:42 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:42 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:42 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:42 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:42 node-1 multipathd: uevent trigger error
<129>Jul 28 06:09:44 node-1 haproxy[28637]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:44 node-1 haproxy[28637]: 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>Jul 28 06:09:44 node-1 haproxy[28637]: 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>Jul 28 06:09:44 node-1 haproxy[28637]: proxy keystone-1 has no server available!
<129>Jul 28 06:09:44 node-1 haproxy[28637]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:45 node-1 haproxy[28641]: 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>Jul 28 06:09:45 node-1 haproxy[28641]: 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>Jul 28 06:09:45 node-1 haproxy[28641]: proxy keystone-2 has no server available!
<129>Jul 28 06:09:45 node-1 haproxy[28641]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:45 node-1 haproxy[28641]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:45 node-1 haproxy[28641]: 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>Jul 28 06:09:45 node-1 haproxy[28641]: proxy neutron has no server available!
<129>Jul 28 06:09:45 node-1 haproxy[28641]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:45 node-1 haproxy[28641]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:46 node-1 haproxy[28641]: 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>Jul 28 06:09:46 node-1 haproxy[28641]: proxy mysqld has no server available!
<129>Jul 28 06:09:46 node-1 haproxy[28641]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:46 node-1 haproxy[28641]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:46 node-1 haproxy[28641]: 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>Jul 28 06:09:46 node-1 haproxy[28641]: proxy object-storage has no server available!
<27>Jul 28 06:09:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:47 node-1 multipathd: uevent trigger error
<129>Jul 28 06:09:49 node-1 haproxy[29967]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:49 node-1 haproxy[29967]: 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>Jul 28 06:09:50 node-1 haproxy[29977]: 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>Jul 28 06:09:50 node-1 haproxy[29977]: proxy keystone-1 has no server available!
<129>Jul 28 06:09:50 node-1 haproxy[29977]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:50 node-1 haproxy[29977]: 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>Jul 28 06:09:50 node-1 haproxy[29977]: 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>Jul 28 06:09:50 node-1 haproxy[29977]: proxy keystone-2 has no server available!
<129>Jul 28 06:09:50 node-1 haproxy[29977]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:50 node-1 haproxy[29977]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:50 node-1 haproxy[29977]: 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>Jul 28 06:09:50 node-1 haproxy[29977]: proxy neutron has no server available!
<129>Jul 28 06:09:50 node-1 haproxy[29977]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:50 node-1 haproxy[29977]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:51 node-1 haproxy[29977]: 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>Jul 28 06:09:51 node-1 haproxy[29977]: proxy mysqld has no server available!
<129>Jul 28 06:09:51 node-1 haproxy[29977]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:51 node-1 haproxy[29977]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:51 node-1 haproxy[29977]: 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>Jul 28 06:09:51 node-1 haproxy[29977]: proxy object-storage has no server available!
<129>Jul 28 06:09:51 node-1 haproxy[29977]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:51 node-1 haproxy[29977]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:51 node-1 haproxy[29977]: 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>Jul 28 06:09:51 node-1 haproxy[29977]: proxy aodh has no server available!
<27>Jul 28 06:09:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:53 node-1 multipathd: uevent trigger error
<129>Jul 28 06:09:55 node-1 haproxy[31342]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:55 node-1 haproxy[31342]: 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>Jul 28 06:09:55 node-1 haproxy[31342]: 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>Jul 28 06:09:55 node-1 haproxy[31342]: proxy keystone-1 has no server available!
<129>Jul 28 06:09:55 node-1 haproxy[31342]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:55 node-1 haproxy[31342]: 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>Jul 28 06:09:55 node-1 haproxy[31342]: 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>Jul 28 06:09:55 node-1 haproxy[31342]: proxy keystone-2 has no server available!
<129>Jul 28 06:09:55 node-1 haproxy[31342]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:55 node-1 haproxy[31342]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:56 node-1 haproxy[31346]: 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>Jul 28 06:09:56 node-1 haproxy[31346]: proxy neutron has no server available!
<129>Jul 28 06:09:56 node-1 haproxy[31346]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:56 node-1 haproxy[31346]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:56 node-1 haproxy[31346]: 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>Jul 28 06:09:56 node-1 haproxy[31346]: proxy mysqld has no server available!
<129>Jul 28 06:09:56 node-1 haproxy[31346]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:56 node-1 haproxy[31346]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:56 node-1 haproxy[31346]: 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>Jul 28 06:09:56 node-1 haproxy[31346]: proxy object-storage has no server available!
<129>Jul 28 06:09:56 node-1 haproxy[31346]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:56 node-1 haproxy[31346]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:56 node-1 haproxy[31346]: 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>Jul 28 06:09:56 node-1 haproxy[31346]: proxy aodh has no server available!
<129>Jul 28 06:09:56 node-1 haproxy[31346]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:57 node-1 haproxy[31346]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:09:57 node-1 haproxy[31346]: 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>Jul 28 06:09:57 node-1 haproxy[31346]: proxy ceilometer has no server available!
<27>Jul 28 06:09:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:09:58 node-1 multipathd: uevent trigger error
<129>Jul 28 06:10:00 node-1 haproxy[32690]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:00 node-1 haproxy[32690]: 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>Jul 28 06:10:01 node-1 haproxy[32694]: 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>Jul 28 06:10:01 node-1 haproxy[32694]: proxy keystone-1 has no server available!
<129>Jul 28 06:10:01 node-1 haproxy[32694]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:01 node-1 haproxy[32694]: 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>Jul 28 06:10:01 node-1 haproxy[32694]: 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>Jul 28 06:10:01 node-1 haproxy[32694]: proxy keystone-2 has no server available!
<129>Jul 28 06:10:01 node-1 haproxy[32694]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:01 node-1 haproxy[32694]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:01 node-1 haproxy[32694]: 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>Jul 28 06:10:01 node-1 haproxy[32694]: proxy neutron has no server available!
<129>Jul 28 06:10:01 node-1 haproxy[32694]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:01 node-1 haproxy[32694]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:01 node-1 haproxy[32694]: 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>Jul 28 06:10:01 node-1 haproxy[32694]: proxy mysqld has no server available!
<129>Jul 28 06:10:01 node-1 haproxy[32694]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:02 node-1 haproxy[32694]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:02 node-1 haproxy[32694]: 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>Jul 28 06:10:02 node-1 haproxy[32694]: proxy object-storage has no server available!
<129>Jul 28 06:10:02 node-1 haproxy[32694]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:02 node-1 haproxy[32694]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:02 node-1 haproxy[32694]: 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>Jul 28 06:10:02 node-1 haproxy[32694]: proxy aodh has no server available!
<129>Jul 28 06:10:02 node-1 haproxy[32694]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:02 node-1 haproxy[32694]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:02 node-1 haproxy[32694]: 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>Jul 28 06:10:02 node-1 haproxy[32694]: proxy ceilometer has no server available!
<27>Jul 28 06:10:03 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:03 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:03 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:03 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:04 node-1 multipathd: uevent trigger error
<129>Jul 28 06:10:06 node-1 haproxy[1660]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:06 node-1 haproxy[1660]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:06 node-1 haproxy[1660]: 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>Jul 28 06:10:06 node-1 haproxy[1660]: 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>Jul 28 06:10:06 node-1 haproxy[1660]: proxy keystone-1 has no server available!
<129>Jul 28 06:10:06 node-1 haproxy[1660]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:06 node-1 haproxy[1660]: 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>Jul 28 06:10:06 node-1 haproxy[1660]: 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>Jul 28 06:10:06 node-1 haproxy[1660]: proxy keystone-2 has no server available!
<129>Jul 28 06:10:07 node-1 haproxy[1664]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:07 node-1 haproxy[1664]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:07 node-1 haproxy[1664]: 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>Jul 28 06:10:07 node-1 haproxy[1664]: proxy neutron has no server available!
<129>Jul 28 06:10:07 node-1 haproxy[1664]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:07 node-1 haproxy[1664]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:07 node-1 haproxy[1664]: 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>Jul 28 06:10:07 node-1 haproxy[1664]: proxy mysqld has no server available!
<129>Jul 28 06:10:07 node-1 haproxy[1664]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:07 node-1 haproxy[1664]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:07 node-1 haproxy[1664]: 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>Jul 28 06:10:07 node-1 haproxy[1664]: proxy object-storage has no server available!
<129>Jul 28 06:10:07 node-1 haproxy[1664]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:07 node-1 haproxy[1664]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:07 node-1 haproxy[1664]: 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>Jul 28 06:10:07 node-1 haproxy[1664]: proxy aodh has no server available!
<129>Jul 28 06:10:08 node-1 haproxy[1664]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:08 node-1 haproxy[1664]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:08 node-1 haproxy[1664]: 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>Jul 28 06:10:08 node-1 haproxy[1664]: proxy ceilometer has no server available!
<27>Jul 28 06:10:09 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:09 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:09 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:09 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:09 node-1 multipathd: uevent trigger error
<129>Jul 28 06:10:12 node-1 haproxy[3034]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:12 node-1 haproxy[3034]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:12 node-1 haproxy[3034]: 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>Jul 28 06:10:12 node-1 haproxy[3034]: 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>Jul 28 06:10:12 node-1 haproxy[3034]: proxy keystone-1 has no server available!
<129>Jul 28 06:10:12 node-1 haproxy[3034]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:12 node-1 haproxy[3034]: 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>Jul 28 06:10:12 node-1 haproxy[3034]: 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>Jul 28 06:10:12 node-1 haproxy[3034]: proxy keystone-2 has no server available!
<129>Jul 28 06:10:12 node-1 haproxy[3034]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:12 node-1 haproxy[3034]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:12 node-1 haproxy[3034]: 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>Jul 28 06:10:12 node-1 haproxy[3034]: proxy glance-api has no server available!
<129>Jul 28 06:10:12 node-1 haproxy[3034]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:12 node-1 haproxy[3034]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:12 node-1 haproxy[3034]: 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>Jul 28 06:10:12 node-1 haproxy[3034]: proxy glance-glare has no server available!
<129>Jul 28 06:10:12 node-1 haproxy[3034]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:12 node-1 haproxy[3034]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:13 node-1 haproxy[3041]: 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>Jul 28 06:10:13 node-1 haproxy[3041]: proxy neutron has no server available!
<129>Jul 28 06:10:13 node-1 haproxy[3041]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:13 node-1 haproxy[3041]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:13 node-1 haproxy[3041]: 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>Jul 28 06:10:13 node-1 haproxy[3041]: proxy glance-registry has no server available!
<129>Jul 28 06:10:13 node-1 haproxy[3041]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:13 node-1 haproxy[3041]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:13 node-1 haproxy[3041]: 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>Jul 28 06:10:13 node-1 haproxy[3041]: proxy mysqld has no server available!
<129>Jul 28 06:10:13 node-1 haproxy[3041]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:13 node-1 haproxy[3041]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:13 node-1 haproxy[3041]: 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>Jul 28 06:10:13 node-1 haproxy[3041]: proxy object-storage has no server available!
<129>Jul 28 06:10:13 node-1 haproxy[3041]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:13 node-1 haproxy[3041]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:13 node-1 haproxy[3041]: 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>Jul 28 06:10:13 node-1 haproxy[3041]: proxy aodh has no server available!
<129>Jul 28 06:10:13 node-1 haproxy[3041]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:13 node-1 haproxy[3041]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:13 node-1 haproxy[3041]: 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>Jul 28 06:10:13 node-1 haproxy[3041]: proxy ceilometer has no server available!
<27>Jul 28 06:10:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:15 node-1 multipathd: uevent trigger error
<129>Jul 28 06:10:17 node-1 haproxy[4462]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: 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>Jul 28 06:10:18 node-1 haproxy[4466]: 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>Jul 28 06:10:18 node-1 haproxy[4466]: proxy keystone-1 has no server available!
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: 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>Jul 28 06:10:18 node-1 haproxy[4466]: 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>Jul 28 06:10:18 node-1 haproxy[4466]: proxy keystone-2 has no server available!
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: 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>Jul 28 06:10:18 node-1 haproxy[4466]: proxy nova-api has no server available!
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: 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>Jul 28 06:10:18 node-1 haproxy[4466]: proxy nova-metadata-api has no server available!
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: 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>Jul 28 06:10:18 node-1 haproxy[4466]: proxy glance-api has no server available!
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: 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>Jul 28 06:10:18 node-1 haproxy[4466]: proxy glance-glare has no server available!
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:18 node-1 haproxy[4466]: 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>Jul 28 06:10:18 node-1 haproxy[4466]: proxy neutron has no server available!
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: 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>Jul 28 06:10:19 node-1 haproxy[4466]: proxy glance-registry has no server available!
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: 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>Jul 28 06:10:19 node-1 haproxy[4466]: proxy mysqld has no server available!
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: 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>Jul 28 06:10:19 node-1 haproxy[4466]: proxy object-storage has no server available!
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: 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>Jul 28 06:10:19 node-1 haproxy[4466]: proxy aodh has no server available!
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: 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>Jul 28 06:10:19 node-1 haproxy[4466]: proxy ceilometer has no server available!
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:19 node-1 haproxy[4466]: 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>Jul 28 06:10:19 node-1 haproxy[4466]: proxy nova-novncproxy has no server available!
<27>Jul 28 06:10:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:21 node-1 multipathd: uevent trigger error
<129>Jul 28 06:10:23 node-1 haproxy[5944]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:23 node-1 haproxy[5944]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:23 node-1 haproxy[5944]: 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>Jul 28 06:10:23 node-1 haproxy[5944]: 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>Jul 28 06:10:23 node-1 haproxy[5944]: proxy keystone-1 has no server available!
<129>Jul 28 06:10:23 node-1 haproxy[5944]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:23 node-1 haproxy[5944]: 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>Jul 28 06:10:23 node-1 haproxy[5944]: 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>Jul 28 06:10:23 node-1 haproxy[5944]: proxy keystone-2 has no server available!
<129>Jul 28 06:10:23 node-1 haproxy[5944]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:23 node-1 haproxy[5944]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:23 node-1 haproxy[5944]: 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>Jul 28 06:10:23 node-1 haproxy[5944]: proxy nova-api has no server available!
<129>Jul 28 06:10:23 node-1 haproxy[5944]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:23 node-1 haproxy[5944]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: 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>Jul 28 06:10:24 node-1 haproxy[5950]: proxy nova-metadata-api has no server available!
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: 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>Jul 28 06:10:24 node-1 haproxy[5950]: proxy cinder-api has no server available!
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: 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>Jul 28 06:10:24 node-1 haproxy[5950]: proxy glance-api has no server available!
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: 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>Jul 28 06:10:24 node-1 haproxy[5950]: proxy glance-glare has no server available!
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: 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>Jul 28 06:10:24 node-1 haproxy[5950]: proxy neutron has no server available!
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: 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>Jul 28 06:10:24 node-1 haproxy[5950]: proxy glance-registry has no server available!
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: 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>Jul 28 06:10:24 node-1 haproxy[5950]: proxy mysqld has no server available!
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:24 node-1 haproxy[5950]: 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>Jul 28 06:10:24 node-1 haproxy[5950]: proxy object-storage has no server available!
<129>Jul 28 06:10:25 node-1 haproxy[5950]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:25 node-1 haproxy[5950]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:25 node-1 haproxy[5950]: 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>Jul 28 06:10:25 node-1 haproxy[5950]: proxy aodh has no server available!
<129>Jul 28 06:10:25 node-1 haproxy[5950]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:25 node-1 haproxy[5950]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:25 node-1 haproxy[5950]: 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>Jul 28 06:10:25 node-1 haproxy[5950]: proxy ceilometer has no server available!
<129>Jul 28 06:10:25 node-1 haproxy[5950]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:25 node-1 haproxy[5950]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:25 node-1 haproxy[5950]: 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>Jul 28 06:10:25 node-1 haproxy[5950]: proxy nova-novncproxy has no server available!
<27>Jul 28 06:10:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:27 node-1 multipathd: uevent trigger error
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: 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>Jul 28 06:10:30 node-1 haproxy[7342]: 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>Jul 28 06:10:30 node-1 haproxy[7342]: proxy keystone-1 has no server available!
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: 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>Jul 28 06:10:30 node-1 haproxy[7342]: 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>Jul 28 06:10:30 node-1 haproxy[7342]: proxy keystone-2 has no server available!
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: 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>Jul 28 06:10:30 node-1 haproxy[7342]: proxy nova-api has no server available!
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: 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>Jul 28 06:10:30 node-1 haproxy[7342]: proxy nova-metadata-api has no server available!
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: 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>Jul 28 06:10:30 node-1 haproxy[7342]: proxy cinder-api has no server available!
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: 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>Jul 28 06:10:30 node-1 haproxy[7342]: proxy glance-api has no server available!
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: 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>Jul 28 06:10:30 node-1 haproxy[7342]: proxy glance-glare has no server available!
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:30 node-1 haproxy[7342]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: 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>Jul 28 06:10:31 node-1 haproxy[7346]: proxy neutron has no server available!
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: 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>Jul 28 06:10:31 node-1 haproxy[7346]: proxy glance-registry has no server available!
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: 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>Jul 28 06:10:31 node-1 haproxy[7346]: proxy mysqld has no server available!
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: 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>Jul 28 06:10:31 node-1 haproxy[7346]: proxy object-storage has no server available!
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: 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>Jul 28 06:10:31 node-1 haproxy[7346]: proxy aodh has no server available!
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: 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>Jul 28 06:10:31 node-1 haproxy[7346]: proxy ceilometer has no server available!
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: 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>Jul 28 06:10:31 node-1 haproxy[7346]: proxy heat-api has no server available!
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: 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>Jul 28 06:10:31 node-1 haproxy[7346]: proxy heat-api-cfn has no server available!
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: 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>Jul 28 06:10:31 node-1 haproxy[7346]: proxy heat-api-cloudwatch has no server available!
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:31 node-1 haproxy[7346]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:10:32 node-1 haproxy[7346]: 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>Jul 28 06:10:32 node-1 haproxy[7346]: proxy nova-novncproxy has no server available!
<27>Jul 28 06:10:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:10:46 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 28 06:11:11 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 28 06:11:13 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 28 06:11:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 06:11:46 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 06:12:05 node-1 multipathd: uevent trigger error
<27>Jul 28 06:12:05 node-1 multipathd: uevent trigger error
<27>Jul 28 06:12:05 node-1 multipathd: uevent trigger error
<27>Jul 28 06:12:05 node-1 multipathd: uevent trigger error
<27>Jul 28 06:12:05 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:32 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:32 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:32 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:32 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:32 node-1 multipathd: uevent trigger error
<43>Jul 28 06:14:46 node-1 apache2_error [Thu Jul 28 06:14:45.135216 2016] [mpm_event:notice] [pid 16640:tid 140355897067392] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 06:14:46 node-1 apache2_error [Thu Jul 28 06:14:45.135355 2016] [core:notice] [pid 16640:tid 140355897067392] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 06:14:47 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 06:14:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:53 node-1 multipathd: uevent trigger error
<43>Jul 28 06:14:56 node-1 apache2_error [Thu Jul 28 06:14:48.137481 2016] [mpm_event:notice] [pid 16640:tid 140355897067392] AH00491: caught SIGTERM, shutting down
<43>Jul 28 06:14:56 node-1 apache2_error [Thu Jul 28 06:14:49.234042 2016] [mpm_worker:notice] [pid 17268:tid 140224381826944] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 06:14:56 node-1 apache2_error [Thu Jul 28 06:14:49.234100 2016] [core:notice] [pid 17268:tid 140224381826944] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 06:14:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:14:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:15:01 node-1 multipathd: uevent trigger error
<27>Jul 28 06:15:01 node-1 multipathd: uevent trigger error
<27>Jul 28 06:15:01 node-1 multipathd: uevent trigger error
<27>Jul 28 06:15:01 node-1 multipathd: uevent trigger error
<27>Jul 28 06:15:01 node-1 multipathd: uevent trigger error
<27>Jul 28 06:15:01 node-1 multipathd: uevent trigger error
<43>Jul 28 06:16:17 node-1 apache2_error [Thu Jul 28 06:16:11.443121 2016] [mpm_worker:notice] [pid 17268:tid 140224381826944] AH00295: caught SIGTERM, shutting down
<43>Jul 28 06:16:17 node-1 apache2_error [Thu Jul 28 06:16:12.207154 2016] [mpm_worker:notice] [pid 31844:tid 140436357392256] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 06:16:17 node-1 apache2_error [Thu Jul 28 06:16:12.207183 2016] [core:notice] [pid 31844:tid 140436357392256] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 06:16:57 node-1 apache2_error [Thu Jul 28 06:16:55.859914 2016] [mpm_worker:notice] [pid 31844:tid 140436357392256] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 06:16:57 node-1 apache2_error [Thu Jul 28 06:16:56.053836 2016] [mpm_worker:warn] [pid 31844:tid 140436357392256] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 06:16:57 node-1 apache2_error [Thu Jul 28 06:16:56.058507 2016] [mpm_worker:notice] [pid 31844:tid 140436357392256] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 06:16:57 node-1 apache2_error [Thu Jul 28 06:16:56.058536 2016] [core:notice] [pid 31844:tid 140436357392256] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 06:17:41 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:41 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:41 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:41 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:41 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:17:48 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 06:18:02 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:02 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:02 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:02 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:02 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:23 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:23 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:23 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:23 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:23 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:18:46 node-1 multipathd: uevent trigger error
<27>Jul 28 06:19:43 node-1 multipathd: uevent trigger error
<27>Jul 28 06:19:43 node-1 multipathd: uevent trigger error
<27>Jul 28 06:19:43 node-1 multipathd: uevent trigger error
<27>Jul 28 06:19:43 node-1 multipathd: uevent trigger error
<27>Jul 28 06:19:43 node-1 multipathd: uevent trigger error
<27>Jul 28 06:20:49 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 06:20:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:20:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:20:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:20:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:20:58 node-1 multipathd: uevent trigger error
<27>Jul 28 06:21:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:21:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:21:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:21:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:21:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:21:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:21:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:22:03 node-1 multipathd: uevent trigger error
<27>Jul 28 06:22:03 node-1 multipathd: uevent trigger error
<27>Jul 28 06:22:03 node-1 multipathd: uevent trigger error
<27>Jul 28 06:22:03 node-1 multipathd: uevent trigger error
<27>Jul 28 06:22:03 node-1 multipathd: uevent trigger error
<27>Jul 28 06:22:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:22:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:22:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:22:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:22:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:23:55 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 06:24:52 node-1 multipathd: uevent trigger error
<27>Jul 28 06:24:52 node-1 multipathd: uevent trigger error
<27>Jul 28 06:24:52 node-1 multipathd: uevent trigger error
<27>Jul 28 06:24:52 node-1 multipathd: uevent trigger error
<27>Jul 28 06:24:52 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:08 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:08 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:08 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:08 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:08 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:13 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:13 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:13 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:13 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:13 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:13 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:55 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:55 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:55 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:55 node-1 multipathd: uevent trigger error
<27>Jul 28 06:25:55 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:00 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:26:57 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 06:27:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:17 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Jul 28 06:27:18 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Jul 28 06:27:18 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Jul 28 06:27:19 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Jul 28 06:27:19 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Jul 28 06:27:19 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:19 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:20 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:20 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:20 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:20 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:32 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:32 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:32 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:32 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:32 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:32 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:32 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:47 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:48 node-1 multipathd: uevent trigger error
<27>Jul 28 06:27:48 node-1 multipathd: uevent trigger error
<27>Jul 28 06:28:06 node-1 multipathd: uevent trigger error
<27>Jul 28 06:28:06 node-1 multipathd: uevent trigger error
<27>Jul 28 06:28:06 node-1 multipathd: uevent trigger error
<27>Jul 28 06:28:06 node-1 multipathd: uevent trigger error
<27>Jul 28 06:28:06 node-1 multipathd: uevent trigger error
<27>Jul 28 06:29:58 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 06:30:29 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:29 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:29 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:29 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:29 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:29 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:44 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:45 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:45 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:59 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:59 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:59 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:59 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:59 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:59 node-1 multipathd: uevent trigger error
<27>Jul 28 06:30:59 node-1 multipathd: uevent trigger error
<27>Jul 28 06:31:00 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 28 06:32:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:32:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:32:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:32:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:32:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:32:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:32:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:32:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:32:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:32:27 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 06:33:07 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:07 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:07 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:07 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:34 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:34 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:34 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:34 node-1 multipathd: uevent trigger error
<27>Jul 28 06:33:34 node-1 multipathd: uevent trigger error
<27>Jul 28 06:34:04 node-1 multipathd: uevent trigger error
<27>Jul 28 06:34:04 node-1 multipathd: uevent trigger error
<27>Jul 28 06:34:04 node-1 multipathd: uevent trigger error
<27>Jul 28 06:34:04 node-1 multipathd: uevent trigger error
<27>Jul 28 06:34:04 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:30 node-1 multipathd: uevent trigger error
<27>Jul 28 06:35:30 node-1 multipathd: uevent trigger error
<11>Jul 28 06:35:43 node-1 liberasurecode[64375]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:43 node-1 liberasurecode[64375]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:43 node-1 liberasurecode[64375]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:43 node-1 liberasurecode[64375]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:43 node-1 liberasurecode[64404]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:43 node-1 liberasurecode[64404]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:43 node-1 liberasurecode[64404]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:43 node-1 liberasurecode[64404]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:46 node-1 liberasurecode[64922]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:46 node-1 liberasurecode[64922]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:46 node-1 liberasurecode[64922]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:46 node-1 liberasurecode[64922]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[65807]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[65807]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[65807]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[65807]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[65931]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[65931]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[65931]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[65931]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66067]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66067]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66067]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66067]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66288]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66288]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66288]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66288]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66303]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66303]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66303]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66303]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66319]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66319]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66319]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:51 node-1 liberasurecode[66319]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:52 node-1 liberasurecode[66369]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:52 node-1 liberasurecode[66369]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:52 node-1 liberasurecode[66369]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:35:52 node-1 liberasurecode[66369]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 06:36:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Jul 28 06:36:08 node-1 liberasurecode[68035]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:36:08 node-1 liberasurecode[68035]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:36:08 node-1 liberasurecode[68035]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:36:08 node-1 liberasurecode[68035]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 06:36:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:36:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:36:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:36:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:36:16 node-1 multipathd: uevent trigger error
<43>Jul 28 06:37:08 node-1 apache2_error [Thu Jul 28 06:37:03.584728 2016] [mpm_worker:notice] [pid 31844:tid 140436357392256] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 06:37:08 node-1 apache2_error [Thu Jul 28 06:37:03.970471 2016] [mpm_worker:warn] [pid 31844:tid 140436357392256] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 06:37:08 node-1 apache2_error [Thu Jul 28 06:37:03.975588 2016] [mpm_worker:notice] [pid 31844:tid 140436357392256] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 06:37:08 node-1 apache2_error [Thu Jul 28 06:37:03.975615 2016] [core:notice] [pid 31844:tid 140436357392256] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 06:37:45 node-1 multipathd: uevent trigger error
<27>Jul 28 06:37:45 node-1 multipathd: uevent trigger error
<27>Jul 28 06:37:45 node-1 multipathd: uevent trigger error
<27>Jul 28 06:37:45 node-1 multipathd: uevent trigger error
<27>Jul 28 06:37:45 node-1 multipathd: uevent trigger error
<27>Jul 28 06:37:45 node-1 multipathd: uevent trigger error
<43>Jul 28 06:37:48 node-1 apache2_error [Thu Jul 28 06:37:41.289551 2016] [mpm_worker:notice] [pid 31844:tid 140436357392256] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 06:37:48 node-1 apache2_error [Thu Jul 28 06:37:41.486455 2016] [mpm_worker:warn] [pid 31844:tid 140436357392256] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 06:37:48 node-1 apache2_error [Thu Jul 28 06:37:41.495223 2016] [mpm_worker:notice] [pid 31844:tid 140436357392256] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 06:37:48 node-1 apache2_error [Thu Jul 28 06:37:41.495251 2016] [core:notice] [pid 31844:tid 140436357392256] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 06:37:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:37:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:37:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:37:53 node-1 multipathd: uevent trigger error
<27>Jul 28 06:37:53 node-1 multipathd: uevent trigger error
<43>Jul 28 06:38:29 node-1 apache2_error [Thu Jul 28 06:38:27.614358 2016] [mpm_worker:notice] [pid 31844:tid 140436357392256] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 06:38:29 node-1 apache2_error [Thu Jul 28 06:38:27.810094 2016] [mpm_worker:warn] [pid 31844:tid 140436357392256] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 06:38:29 node-1 apache2_error [Thu Jul 28 06:38:27.818605 2016] [mpm_worker:notice] [pid 31844:tid 140436357392256] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 06:38:29 node-1 apache2_error [Thu Jul 28 06:38:27.818628 2016] [core:notice] [pid 31844:tid 140436357392256] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 06:38:31 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:31 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:31 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:31 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:31 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:31 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:38 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:38 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:38 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:38 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:38 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:44 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:44 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:44 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:44 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:44 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:54 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:54 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:54 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:55 node-1 multipathd: uevent trigger error
<27>Jul 28 06:38:55 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:03 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 06:39:12 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:12 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:12 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:12 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:12 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:33 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:40 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 28 06:39:49 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:49 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:49 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:49 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:49 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:54 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:54 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:54 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:54 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:54 node-1 multipathd: uevent trigger error
<27>Jul 28 06:39:54 node-1 multipathd: uevent trigger error
<11>Jul 28 06:40:01 node-1 liberasurecode[118011]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:40:01 node-1 liberasurecode[118011]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:40:01 node-1 liberasurecode[118011]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:40:01 node-1 liberasurecode[118011]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 06:40:04 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:04 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:04 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:04 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:04 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:10 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:10 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:10 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:10 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:10 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:23 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:23 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:23 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:23 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:23 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:23 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:28 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:43 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:43 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:43 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:43 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:43 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:47 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 06:40:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:40:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:02 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:02 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:02 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:02 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:02 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:07 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:07 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:07 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:07 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:11 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:16 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:41:21 node-1 multipathd: uevent trigger error
<27>Jul 28 06:42:56 node-1 multipathd: uevent trigger error
<27>Jul 28 06:42:56 node-1 multipathd: uevent trigger error
<27>Jul 28 06:42:56 node-1 multipathd: uevent trigger error
<27>Jul 28 06:42:56 node-1 multipathd: uevent trigger error
<27>Jul 28 06:42:57 node-1 multipathd: uevent trigger error
<27>Jul 28 06:43:05 node-1 multipathd: uevent trigger error
<27>Jul 28 06:43:05 node-1 multipathd: uevent trigger error
<27>Jul 28 06:43:05 node-1 multipathd: uevent trigger error
<27>Jul 28 06:43:05 node-1 multipathd: uevent trigger error
<27>Jul 28 06:43:05 node-1 multipathd: uevent trigger error
<27>Jul 28 06:43:17 node-1 multipathd: uevent trigger error
<27>Jul 28 06:43:17 node-1 multipathd: uevent trigger error
<27>Jul 28 06:43:17 node-1 multipathd: uevent trigger error
<27>Jul 28 06:43:17 node-1 multipathd: uevent trigger error
<27>Jul 28 06:43:17 node-1 multipathd: uevent trigger error
<129>Jul 28 06:43:25 node-1 haproxy[150149]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:43:26 node-1 haproxy[150149]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 06:44:06 node-1 haproxy[150149]: 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.
<27>Jul 28 06:44:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:15 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:20 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:20 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:20 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:20 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:20 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:25 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:36 node-1 multipathd: uevent trigger error
<27>Jul 28 06:44:36 node-1 multipathd: uevent trigger error
<11>Jul 28 06:45:01 node-1 liberasurecode[174260]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:45:01 node-1 liberasurecode[174260]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:45:01 node-1 liberasurecode[174260]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 06:45:01 node-1 liberasurecode[174260]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
