Attachment 592534 Details for Bug 832877 – syslog

syslog

syslog (text/plain), 145.75 KB, created by IBM Bug Proxy on 2012-06-18 06:03:01 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: IBM Bug Proxy

Created: 2012-06-18 06:03:01 UTC

Size: 145.75 KB

patch

obsolete

>11:02:12,169 INFO kernel:imklog 5.8.10, log source = /proc/kmsg started.
>11:02:12,170 INFO rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="632" x-info="http://www.rsyslog.com"] start
>11:02:12,170 INFO systemd-fsck: Root directory is writable, skipping check.
>11:02:12,170 ERR systemd-remount: Failed to open /etc/fstab: No such file or directory
>11:02:12,170 INFO lvm: No volume groups found
>11:02:12,170 WARNING (plymouth): Failed at step EXEC spawning /bin/plymouth: No such file or directory
>11:02:12,170 INFO systemd-tmpfile: Successfully loaded SELinux database in 32ms 145us, size on heap is 535K.
>11:02:12,170 WARNING (lymouthd): Failed at step EXEC spawning /sbin/plymouthd: No such file or directory
>11:02:12,170 WARNING (plymouth): Failed at step EXEC spawning /bin/plymouth: No such file or directory
>11:02:12,170 WARNING (plymouth): Failed at step EXEC spawning /bin/plymouth: No such file or directory
>11:02:12,170 INFO NetworkManager: <info> NetworkManager (version 0.9.4.0-7.git20120403.fc17) is starting...
>11:02:12,170 INFO NetworkManager: <info> Read config file /etc/NetworkManager/NetworkManager.conf
>11:02:12,171 INFO kernel:0 -> 0x00008000
>11:02:12,171 WARNING kernel:[    0.000000]   Normal   empty
>11:02:12,171 WARNING kernel:[    0.000000] Movable zone start PFN for each node
>11:02:12,171 WARNING kernel:[    0.000000] Early memory PFN ranges
>11:02:12,171 WARNING kernel:[    0.000000]     1: 0x00000000 -> 0x00008000
>11:02:12,171 WARNING kernel:[    0.000000] Could not find start_pfn for node 0
>11:02:12,171 DEBUG kernel:[    0.000000] On node 0 totalpages: 0
>11:02:12,171 DEBUG kernel:[    0.000000] On node 1 totalpages: 32768
>11:02:12,171 DEBUG kernel:[    0.000000]   DMA zone: 28 pages used for memmap
>11:02:12,171 DEBUG kernel:[    0.000000]   DMA zone: 0 pages reserved
>11:02:12,171 DEBUG kernel:[    0.000000]   DMA zone: 32740 pages, LIFO batch:1
>11:02:12,171 WARNING kernel:[    0.000000] [boot]0015 Setup Done
>11:02:12,171 INFO kernel:[    0.000000] PERCPU: Embedded 2 pages/cpu @c000000001700000 s84608 r0 d46464 u131072
>11:02:12,171 DEBUG kernel:[    0.000000] pcpu-alloc: s84608 r0 d46464 u131072 alloc=1*1048576
>11:02:12,171 DEBUG kernel:[    0.000000] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15 
>11:02:12,171 DEBUG kernel:[    0.000000] pcpu-alloc: [0] 16 17 18 19 20 21 22 23 [0] 24 25 26 27 28 29 30 31 
>11:02:12,171 DEBUG kernel:[    0.000000] pcpu-alloc: [0] 32 33 34 35 36 37 38 39 [0] 40 41 42 43 44 45 46 47 
>11:02:12,171 WARNING kernel:[    0.000000] Built 2 zonelists in Node order, mobility grouping on.  Total pages: 32740
>11:02:12,171 WARNING kernel:[    0.000000] Policy zone: DMA
>11:02:12,171 NOTICE kernel:[    0.000000] Kernel command line: ro root=live:CDLABEL=Fedora_17_ppc64 ip=9.3.110.175::9.3.110.1:255.255.255.0:miz03.austin.ibm.com:eth0:none nameserver=9.0.9.1 debug rd.debug sshd vnc
>11:02:12,171 INFO kernel:[    0.000000] PID hash table entries: 4096 (order: -1, 32768 bytes)
>11:02:12,171 WARNING kernel:[    0.000000] freeing bootmem node 1
>11:02:12,171 INFO kernel:[    0.000000] Memory: 2007232k/2097152k available (17920k kernel code, 89920k reserved, 1856k data, 2952k bss, 6656k init)
>11:02:12,171 INFO kernel:[    0.000000] SLUB: Genslabs=19, HWalign=128, Order=0-3, MinObjects=0, CPUs=48, Nodes=256
>11:02:12,171 INFO kernel:[    0.000000] Hierarchical RCU implementation.
>11:02:12,171 INFO kernel:[    0.000000] NR_IRQS:512 nr_irqs:512 16
>11:02:12,171 DEBUG kernel:[    0.000000] pic: no ISA interrupt controller
>11:02:12,171 DEBUG kernel:[    0.000000] time_init: decrementer frequency = 512.000000 MHz
>11:02:12,171 DEBUG kernel:[    0.000000] time_init: processor frequency   = 3720.000000 MHz
>11:02:12,171 INFO kernel:[    0.000000] clocksource: timebase mult[1f40000] shift[24] registered
>11:02:12,171 DEBUG kernel:[    0.000000] clockevent: decrementer mult[83126e98] shift[32] cpu[0]
>11:02:12,171 INFO kernel:[    0.000000] Console: colour dummy device 80x25
>11:02:12,171 INFO kernel:[    0.000000] console [hvc0] enabled, bootconsole disabled
>11:02:12,171 INFO kernel:[    0.000000] allocated 524288 bytes of page_cgroup
>11:02:12,171 INFO kernel:[    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
>11:02:12,171 INFO kernel:[    0.001697] pid_max: default: 49152 minimum: 384
>11:02:12,171 INFO kernel:[    0.001832] Security Framework initialized
>11:02:12,171 INFO kernel:[    0.001843] SELinux:  Initializing.
>11:02:12,171 DEBUG kernel:[    0.001852] SELinux:  Starting in permissive mode
>11:02:12,171 INFO kernel:[    0.002008] Dentry cache hash table entries: 262144 (order: 5, 2097152 bytes)
>11:02:12,171 INFO kernel:[    0.002516] Inode-cache hash table entries: 131072 (order: 4, 1048576 bytes)
>11:02:12,171 INFO kernel:[    0.003272] Mount-cache hash table entries: 4096
>11:02:12,171 INFO kernel:[    0.004788] Initializing cgroup subsys cpuacct
>11:02:12,171 INFO kernel:[    0.004796] Initializing cgroup subsys memory
>11:02:12,171 INFO kernel:[    0.004888] Initializing cgroup subsys devices
>11:02:12,171 INFO kernel:[    0.004892] Initializing cgroup subsys freezer
>11:02:12,171 INFO kernel:[    0.004896] Initializing cgroup subsys net_cls
>11:02:12,171 INFO kernel:[    0.004899] Initializing cgroup subsys blkio
>11:02:12,171 INFO kernel:[    0.004905] Initializing cgroup subsys perf_event
>11:02:12,171 INFO kernel:[    0.004983] ftrace: allocating 21118 entries in 8 pages
>11:02:12,171 INFO kernel:[    0.014319] POWER7 performance monitor hardware support registered
>11:02:12,171 INFO kernel:[    0.017179] Brought up 4 CPUs
>11:02:12,171 DEBUG kernel:[    0.017194] Node 0 CPUs: 0-3
>11:02:12,171 DEBUG kernel:[    0.017201] Node 1 CPUs:
>11:02:12,171 INFO kernel:[    0.025806] Enabling Asymmetric SMT scheduling
>11:02:12,171 INFO kernel:[    0.028376] devtmpfs: initialized
>11:02:12,171 INFO kernel:[    0.035056] atomic64 test passed
>11:02:12,171 INFO kernel:[    0.035263] NET: Registered protocol family 16
>11:02:12,171 INFO kernel:[    0.035296] IBM eBus Device Driver
>11:02:12,171 INFO kernel:[    0.040475] PCI: Probing PCI hardware
>11:02:12,171 DEBUG kernel:[    0.040489] PCI: Probing PCI hardware done
>11:02:12,171 WARNING kernel:[    0.040504] opal: Node not found
>11:02:12,171 INFO kernel:[    0.042895] bio: create slab <bio-0> at 0
>11:02:12,171 INFO kernel:[    0.043339] vgaarb: loaded
>11:02:12,171 NOTICE kernel:[    0.043506] SCSI subsystem initialized
>11:02:12,171 DEBUG kernel:[    0.043622] libata version 3.00 loaded.
>11:02:12,171 INFO kernel:[    0.043710] usbcore: registered new interface driver usbfs
>11:02:12,171 INFO kernel:[    0.043727] usbcore: registered new interface driver hub
>11:02:12,171 INFO kernel:[    0.043772] usbcore: registered new device driver usb
>11:02:12,171 INFO kernel:[    0.044082] NetLabel: Initializing
>11:02:12,171 INFO kernel:[    0.044086] NetLabel:  domain hash size = 128
>11:02:12,171 INFO kernel:[    0.044090] NetLabel:  protocols = UNLABELED CIPSOv4
>11:02:12,171 INFO kernel:[    0.044110] NetLabel:  unlabeled traffic allowed by default
>11:02:12,171 INFO kernel:[    0.044136] Switching to clocksource timebase
>11:02:12,171 INFO kernel:[    0.066562] NET: Registered protocol family 2
>11:02:12,171 INFO kernel:[    0.066709] IP route cache hash table entries: 16384 (order: 1, 131072 bytes)
>11:02:12,171 INFO kernel:[    0.067097] TCP established hash table entries: 65536 (order: 4, 1048576 bytes)
>11:02:12,171 INFO kernel:[    0.068298] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes)
>11:02:12,171 INFO kernel:[    0.069104] TCP: Hash tables configured (established 65536 bind 65536)
>11:02:12,171 INFO kernel:[    0.069115] TCP reno registered
>11:02:12,171 INFO kernel:[    0.069132] UDP hash table entries: 2048 (order: 0, 65536 bytes)
>11:02:12,171 INFO kernel:[    0.069213] UDP-Lite hash table entries: 2048 (order: 0, 65536 bytes)
>11:02:12,171 INFO kernel:[    0.069579] NET: Registered protocol family 1
>11:02:12,171 DEBUG kernel:[    0.069595] PCI: CLS 0 bytes, default 128
>11:02:12,171 INFO kernel:[    0.069681] Unpacking initramfs...
>11:02:12,171 INFO kernel:[    5.665969] Freeing initrd memory: 23168k freed
>11:02:12,171 DEBUG kernel:[    5.666500] RTAS daemon started
>11:02:12,171 DEBUG kernel:[    5.667411] RTAS: event: 19, Type: Platform Error, Severity: 2
>11:02:12,171 INFO kernel:[    5.667636] vio 30000000: Warning: IOMMU dma not supported: mask 0xffffffffffffffff, table unavailable
>11:02:12,171 INFO kernel:[    5.685216] IOMMU table initialized, virtual merging enabled
>11:02:12,171 INFO kernel:[    5.709911] vio 4000: Warning: IOMMU dma not supported: mask 0xffffffffffffffff, table unavailable
>11:02:12,171 INFO kernel:[    5.709949] vio 4001: Warning: IOMMU dma not supported: mask 0xffffffffffffffff, table unavailable
>11:02:12,171 INFO kernel:[    5.709976] vio 4002: Warning: IOMMU dma not supported: mask 0xffffffffffffffff, table unavailable
>11:02:12,171 INFO kernel:[    5.710002] vio 4004: Warning: IOMMU dma not supported: mask 0xffffffffffffffff, table unavailable
>11:02:12,171 INFO kernel:[    5.712138] audit: initializing netlink socket (disabled)
>11:02:12,171 NOTICE kernel:[    5.712176] type=2000 audit(1339498910.700:1): initialized
>11:02:12,171 INFO kernel:[    5.871447] HugeTLB registered 16 MB page size, pre-allocated 0 pages
>11:02:12,171 INFO kernel:[    5.871464] HugeTLB registered 16 GB page size, pre-allocated 0 pages
>11:02:12,171 NOTICE kernel:[    5.874982] VFS: Disk quotas dquot_6.5.2
>11:02:12,171 WARNING kernel:[    5.875167] Dquot-cache hash table entries: 8192 (order 0, 65536 bytes)
>11:02:12,178 INFO kernel:[    5.876709] msgmni has been set to 3964
>11:02:12,178 DEBUG kernel:[    5.876848] SELinux:  Registering netfilter hooks
>11:02:12,178 INFO kernel:[    5.877618] alg: No test for stdrng (krng)
>11:02:12,178 INFO kernel:[    5.877639] NET: Registered protocol family 38
>11:02:12,178 INFO kernel:[    5.877879] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
>11:02:12,178 INFO kernel:[    5.877962] io scheduler noop registered
>11:02:12,178 INFO kernel:[    5.877967] io scheduler deadline registered
>11:02:12,178 INFO kernel:[    5.878097] io scheduler cfq registered (default)
>11:02:12,178 INFO kernel:[    5.878194] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
>11:02:12,178 DEBUG kernel:[    5.878585] vio_register_driver: driver hvc_console registering
>11:02:12,178 INFO kernel:[    5.878946] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>11:02:12,178 INFO kernel:[    5.879493] Linux agpgart interface v0.103
>11:02:12,178 INFO kernel:[    5.883214] loop: module loaded
>11:02:12,178 INFO kernel:[    5.883270] Uniform Multi-Platform E-IDE driver
>11:02:12,178 INFO kernel:[    5.883311] ide-gd driver 1.18
>11:02:12,178 INFO kernel:[    5.883439] Fixed MDIO Bus: probed
>11:02:12,178 INFO kernel:[    5.883520] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
>11:02:12,178 INFO kernel:[    5.883546] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
>11:02:12,178 INFO kernel:[    5.883566] uhci_hcd: USB Universal Host Controller Interface driver
>11:02:12,178 INFO kernel:[    5.883627] usbcore: registered new interface driver usbserial
>11:02:12,178 INFO kernel:[    5.883639] USB Serial support registered for generic
>11:02:12,178 INFO kernel:[    5.883654] usbcore: registered new interface driver usbserial_generic
>11:02:12,178 INFO kernel:[    5.883769] usbserial: USB Serial Driver core
>11:02:12,178 INFO kernel:[    5.883910] mousedev: PS/2 mouse device common for all mice
>11:02:12,178 INFO kernel:[    5.884409] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0
>11:02:12,178 INFO kernel:[    5.884549] device-mapper: uevent: version 1.0.3
>11:02:12,178 INFO kernel:[    5.884679] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
>11:02:12,178 INFO kernel:[    5.885443] usbcore: registered new interface driver usbhid
>11:02:12,178 INFO kernel:[    5.885452] usbhid: USB HID core driver
>11:02:12,178 INFO kernel:[    5.885604] ip_tables: (C) 2000-2006 Netfilter Core Team
>11:02:12,178 INFO kernel:[    5.905332] TCP cubic registered
>11:02:12,178 INFO kernel:[    5.905352] Initializing XFRM netlink socket
>11:02:12,178 INFO kernel:[    5.905619] NET: Registered protocol family 10
>11:02:12,178 INFO kernel:[    5.906068] Mobile IPv6
>11:02:12,178 INFO kernel:[    5.906078] NET: Registered protocol family 17
>11:02:12,178 NOTICE kernel:[    5.906087] Registering the dns_resolver key type
>11:02:12,178 DEBUG kernel:[    5.906121] Running MSI bitmap self-tests ...
>11:02:12,178 DEBUG kernel:[    5.909694] PM: Hibernation image not present or could not be loaded.
>11:02:12,178 INFO kernel:[    5.909755] registered taskstats version 1
>11:02:12,178 INFO kernel:[    5.910024] rtc-generic rtc-generic: setting system clock to 2012-06-12 11:01:51 UTC (1339498911)
>11:02:12,178 INFO kernel:[    5.910041] Initializing network drop monitor service
>11:02:12,178 INFO kernel:[    5.912446] Freeing unused kernel memory: 6656k freed
>11:02:12,182 INFO kernel:[    6.489065] squashfs: version 4.0 (2009/01/31) Phillip Lougher
>11:02:12,182 INFO kernel:[    6.493895] Loading iSCSI transport class v2.0-870.
>11:02:12,182 NOTICE kernel:[    6.496726] iscsi: registered transport (tcp)
>11:02:12,182 INFO kernel:[    6.500846] alua: device handler registered
>11:02:12,182 INFO kernel:[    6.505596] emc: device handler registered
>11:02:12,182 INFO kernel:[    6.510933] hp_sw: device handler registered
>11:02:12,182 INFO kernel:[    6.515326] rdac: device handler registered
>11:02:12,185 INFO dbus-daemon: dbus[628]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
>11:02:12,185 NOTICE dbus: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
>11:02:12,185 INFO kernel:[    6.628125] md: raid0 personality registered for level 0
>11:02:12,185 INFO kernel:[    6.632970] md: raid1 personality registered for level 1
>11:02:12,185 INFO kernel:[    6.637622] async_tx: api initialized (async)
>11:02:12,185 INFO kernel:[    6.637819] xor: measuring software checksum speed
>11:02:12,185 INFO kernel:[    6.684179]    8regs     :  5561.600 MB/sec
>11:02:12,185 INFO kernel:[    6.734705]    8regs_prefetch:  5190.400 MB/sec
>11:02:12,185 INFO kernel:[    6.784206]    32regs    :  5792.000 MB/sec
>11:02:12,185 INFO kernel:[    6.834210]    32regs_prefetch:  4979.200 MB/sec
>11:02:12,185 INFO kernel:[    6.834218] xor: using function: 32regs (5792.000 MB/sec)
>11:02:12,185 WARNING kernel:[    7.004214] raid6: int64x1   1058 MB/s
>11:02:12,185 WARNING kernel:[    7.174315] raid6: int64x2   2009 MB/s
>11:02:12,185 WARNING kernel:[    7.344265] raid6: int64x4   2135 MB/s
>11:02:12,185 WARNING kernel:[    7.514219] raid6: int64x8   1204 MB/s
>11:02:12,185 WARNING kernel:[    7.684213] raid6: altivecx1  2674 MB/s
>11:02:12,185 WARNING kernel:[    7.855206] raid6: altivecx2  4288 MB/s
>11:02:12,185 WARNING kernel:[    8.024211] raid6: altivecx4  5129 MB/s
>11:02:12,185 WARNING kernel:[    8.194214] raid6: altivecx8  4853 MB/s
>11:02:12,185 WARNING kernel:[    8.194231] raid6: using algorithm altivecx4 (5129 MB/s)
>11:02:12,185 INFO kernel:[    8.199610] md: raid6 personality registered for level 6
>11:02:12,185 INFO kernel:[    8.199619] md: raid5 personality registered for level 5
>11:02:12,185 INFO kernel:[    8.199624] md: raid4 personality registered for level 4
>11:02:12,185 INFO kernel:[    8.217552] md: raid10 personality registered for level 10
>11:02:12,185 INFO kernel:[    8.221700] md: linear personality registered for level -1
>11:02:12,185 INFO kernel:[    8.244944] device-mapper: multipath: version 1.3.0 loaded
>11:02:12,185 INFO kernel:[    8.250840] device-mapper: multipath round-robin: version 1.0.0 loaded
>11:02:12,189 INFO kernel:[    8.687578] RPC: Registered named UNIX socket transport module.
>11:02:12,189 INFO kernel:[    8.687583] RPC: Registered udp transport module.
>11:02:12,189 INFO kernel:[    8.687586] RPC: Registered tcp transport module.
>11:02:12,189 INFO kernel:[    8.687589] RPC: Registered tcp NFSv4.1 backchannel transport module.
>11:02:12,193 DEBUG kernel:[    9.200971] ibmveth: IBM Power Virtual Ethernet Driver 1.04
>11:02:12,193 DEBUG kernel:[    9.200982] vio_register_driver: driver ibmveth registering
>11:02:12,194 DEBUG kernel:[    9.208340] vio_register_driver: driver ibmvscsi registering
>11:02:12,194 INFO kernel:[    9.217732] ibmvscsi 30000002: SRP_VERSION: 16.a
>11:02:12,194 INFO kernel:[    9.218086] scsi0 : IBM POWER Virtual SCSI Adapter 1.5.9
>11:02:12,194 INFO kernel:[    9.263614] ibmvscsi 30000002: partner initialization complete
>11:02:12,194 INFO kernel:[    9.263719] ibmvscsi 30000002: host srp version: 16.a, host partition miz01 (1), OS 3, max io 262144
>11:02:12,194 INFO kernel:[    9.264736] ibmvscsi 30000002: Client reserve enabled
>11:02:12,194 INFO kernel:[    9.264753] ibmvscsi 30000002: sent SRP login
>11:02:12,194 INFO kernel:[    9.264834] ibmvscsi 30000002: SRP_LOGIN succeeded
>11:02:12,194 INFO kernel:[    9.276515] ibmvscsi 30000005: SRP_VERSION: 16.a
>11:02:12,194 INFO kernel:[    9.276850] scsi1 : IBM POWER Virtual SCSI Adapter 1.5.9
>11:02:12,194 INFO kernel:[    9.277503] ibmvscsi 30000005: partner initialization complete
>11:02:12,194 INFO kernel:[    9.277758] ibmvscsi 30000005: host srp version: 16.a, host partition miz01 (1), OS 3, max io 262144
>11:02:12,194 INFO kernel:[    9.277854] ibmvscsi 30000005: Client reserve enabled
>11:02:12,194 INFO kernel:[    9.277871] ibmvscsi 30000005: sent SRP login
>11:02:12,194 INFO kernel:[    9.278380] ibmvscsi 30000005: SRP_LOGIN succeeded
>11:02:12,194 NOTICE kernel:[    9.278387] scsi 0:0:1:0: Direct-Access     AIX      VDASD            0001 PQ: 0 ANSI: 3
>11:02:12,194 NOTICE kernel:[    9.281958] scsi 0:0:2:0: Direct-Access     AIX      VDASD            0001 PQ: 0 ANSI: 3
>11:02:12,194 NOTICE kernel:[    9.404878] scsi 0:0:3:0: Direct-Access     AIX      VDASD            0001 PQ: 0 ANSI: 3
>11:02:12,195 NOTICE kernel:[    9.408257] scsi 1:0:1:0: Direct-Access     AIX      VDASD            0001 PQ: 0 ANSI: 3
>11:02:12,195 NOTICE kernel:[    9.408941] scsi 0:0:4:0: Direct-Access     AIX      VDASD            0001 PQ: 0 ANSI: 3
>11:02:12,195 NOTICE kernel:[    9.410660] scsi 1:0:2:0: Direct-Access     AIX      VDASD            0001 PQ: 0 ANSI: 3
>11:02:12,195 NOTICE kernel:[    9.412026] scsi 0:0:5:0: Direct-Access     AIX      VDASD            0001 PQ: 0 ANSI: 3
>11:02:12,195 NOTICE kernel:[    9.412692] scsi 0:0:6:0: CD-ROM            AIX      VOPTA                 PQ: 0 ANSI: 4
>11:02:12,195 NOTICE kernel:[    9.414442] scsi 1:0:3:0: Direct-Access     AIX      VDASD            0001 PQ: 0 ANSI: 3
>11:02:12,195 NOTICE kernel:[    9.416384] scsi 1:0:4:0: Direct-Access     AIX      VDASD            0001 PQ: 0 ANSI: 3
>11:02:12,200 NOTICE kernel:[   10.302083] sd 0:0:1:0: Attached scsi generic sg0 type 0
>11:02:12,200 NOTICE kernel:[   10.302350] sd 0:0:1:0: [sda] 44040192 512-byte logical blocks: (22.5 GB/21.0 GiB)
>11:02:12,200 NOTICE kernel:[   10.302708] sd 0:0:1:0: [sda] Write Protect is off
>11:02:12,200 DEBUG kernel:[   10.302718] sd 0:0:1:0: [sda] Mode Sense: 17 00 00 08
>11:02:12,200 NOTICE kernel:[   10.302759] sd 0:0:2:0: Attached scsi generic sg1 type 0
>11:02:12,201 NOTICE kernel:[   10.302884] sd 0:0:1:0: [sda] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.302901] sd 0:0:1:0: [sda] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.303006] sd 0:0:2:0: [sdb] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
>11:02:12,201 NOTICE kernel:[   10.303317] sd 0:0:2:0: [sdb] Write Protect is off
>11:02:12,201 DEBUG kernel:[   10.303332] sd 0:0:2:0: [sdb] Mode Sense: 2f 00 00 08
>11:02:12,201 NOTICE kernel:[   10.303449] sd 0:0:2:0: [sdb] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.303458] sd 0:0:2:0: [sdb] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.303956] sd 0:0:1:0: [sda] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.303965] sd 0:0:1:0: [sda] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.304293] sd 0:0:2:0: [sdb] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.304315] sd 0:0:2:0: [sdb] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.305223] sd 0:0:3:0: Attached scsi generic sg2 type 0
>11:02:12,201 NOTICE kernel:[   10.305912] sd 0:0:3:0: [sdc] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
>11:02:12,201 NOTICE kernel:[   10.306047] sd 0:0:3:0: [sdc] Write Protect is off
>11:02:12,201 DEBUG kernel:[   10.306058] sd 0:0:3:0: [sdc] Mode Sense: 2f 00 00 08
>11:02:12,201 NOTICE kernel:[   10.306212] sd 0:0:4:0: Attached scsi generic sg3 type 0
>11:02:12,201 NOTICE kernel:[   10.306276] sd 0:0:3:0: [sdc] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.306284] sd 0:0:3:0: [sdc] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.306598] sd 0:0:5:0: Attached scsi generic sg4 type 0
>11:02:12,201 NOTICE kernel:[   10.306951] sd 0:0:4:0: [sdd] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
>11:02:12,201 NOTICE kernel:[   10.307127] sd 0:0:3:0: [sdc] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.307138] sd 0:0:3:0: [sdc] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.307164] sd 0:0:5:0: [sde] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
>11:02:12,201 NOTICE kernel:[   10.307318] sd 0:0:5:0: [sde] Write Protect is off
>11:02:12,201 DEBUG kernel:[   10.307331] sd 0:0:5:0: [sde] Mode Sense: 2f 00 00 08
>11:02:12,201 NOTICE kernel:[   10.307415] sd 0:0:5:0: [sde] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.307424] sd 0:0:5:0: [sde] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.307530] sd 0:0:4:0: [sdd] Write Protect is off
>11:02:12,201 DEBUG kernel:[   10.307540] sd 0:0:4:0: [sdd] Mode Sense: 2f 00 00 08
>11:02:12,201 NOTICE kernel:[   10.307685] sd 0:0:4:0: [sdd] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.307698] sd 0:0:4:0: [sdd] Assuming drive cache: write through
>11:02:12,201 WARNING kernel:[   10.312256] sr0: scsi-1 drive
>11:02:12,201 INFO kernel:[   10.312268] cdrom: Uniform CD-ROM driver Revision: 3.20
>11:02:12,201 DEBUG kernel:[   10.312541] sr 0:0:6:0: Attached scsi CD-ROM sr0
>11:02:12,201 NOTICE kernel:[   10.313273] sr 0:0:6:0: Attached scsi generic sg5 type 5
>11:02:12,201 NOTICE kernel:[   10.313356] sd 0:0:4:0: [sdd] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.313365] sd 0:0:4:0: [sdd] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.313880] sd 0:0:5:0: [sde] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.313896] sd 0:0:5:0: [sde] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.313970] sd 1:0:1:0: Attached scsi generic sg6 type 0
>11:02:12,201 NOTICE kernel:[   10.314287] sd 1:0:1:0: [sdf] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
>11:02:12,201 NOTICE kernel:[   10.315277] sd 1:0:1:0: [sdf] Write Protect is off
>11:02:12,201 DEBUG kernel:[   10.315288] sd 1:0:1:0: [sdf] Mode Sense: 2f 00 00 08
>11:02:12,201 NOTICE kernel:[   10.315337] sd 1:0:2:0: Attached scsi generic sg7 type 0
>11:02:12,201 NOTICE kernel:[   10.315411] sd 1:0:1:0: [sdf] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.315421] sd 1:0:1:0: [sdf] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.316266] sd 1:0:3:0: Attached scsi generic sg8 type 0
>11:02:12,201 NOTICE kernel:[   10.316491] sd 1:0:2:0: [sdg] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
>11:02:12,201 NOTICE kernel:[   10.316514] sd 1:0:3:0: [sdh] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
>11:02:12,201 NOTICE kernel:[   10.316522] sd 1:0:1:0: [sdf] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.316525] sd 1:0:1:0: [sdf] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.316654] sd 1:0:3:0: [sdh] Write Protect is off
>11:02:12,201 DEBUG kernel:[   10.316663] sd 1:0:3:0: [sdh] Mode Sense: 2f 00 00 08
>11:02:12,201 NOTICE kernel:[   10.316685] sd 1:0:2:0: [sdg] Write Protect is off
>11:02:12,201 DEBUG kernel:[   10.316693] sd 1:0:2:0: [sdg] Mode Sense: 2f 00 00 08
>11:02:12,201 NOTICE kernel:[   10.316819] sd 1:0:4:0: Attached scsi generic sg9 type 0
>11:02:12,201 NOTICE kernel:[   10.316840] sd 1:0:3:0: [sdh] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.316849] sd 1:0:3:0: [sdh] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.316853] sd 1:0:2:0: [sdg] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.316856] sd 1:0:2:0: [sdg] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.317079] sd 1:0:4:0: [sdi] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
>11:02:12,201 NOTICE kernel:[   10.317200] sd 1:0:4:0: [sdi] Write Protect is off
>11:02:12,201 DEBUG kernel:[   10.317207] sd 1:0:4:0: [sdi] Mode Sense: 2f 00 00 08
>11:02:12,201 NOTICE kernel:[   10.317330] sd 1:0:4:0: [sdi] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.317351] sd 1:0:4:0: [sdi] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.317617] sd 1:0:3:0: [sdh] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.317627] sd 1:0:3:0: [sdh] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.318018] sd 1:0:2:0: [sdg] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.318030] sd 1:0:2:0: [sdg] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.318416] sd 1:0:4:0: [sdi] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.318422] sd 1:0:4:0: [sdi] Assuming drive cache: write through
>11:02:12,201 INFO kernel:[   10.321945]  sdb: sdb1
>11:02:12,201 NOTICE kernel:[   10.324731] sd 0:0:2:0: [sdb] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.324749] sd 0:0:2:0: [sdb] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.324761] sd 0:0:2:0: [sdb] Attached SCSI disk
>11:02:12,201 INFO kernel:[   10.340168]  sde: sde1
>11:02:12,201 INFO kernel:[   10.340227]  sdi: sdi1
>11:02:12,201 NOTICE kernel:[   10.343468] sd 1:0:4:0: [sdi] Cache data unavailable
>11:02:12,201 NOTICE kernel:[   10.343476] sd 0:0:5:0: [sde] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.343479] sd 0:0:5:0: [sde] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.343483] sd 0:0:5:0: [sde] Attached SCSI disk
>11:02:12,201 ERR kernel:[   10.343499] sd 1:0:4:0: [sdi] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.343507] sd 1:0:4:0: [sdi] Attached SCSI disk
>11:02:12,201 INFO kernel:[   10.377094]  sdg: sdg1
>11:02:12,201 INFO kernel:[   10.377097]  sdc: sdc1
>11:02:12,201 NOTICE kernel:[   10.378374] sd 0:0:3:0: [sdc] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.378384] sd 0:0:3:0: [sdc] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.378407] sd 0:0:3:0: [sdc] Attached SCSI disk
>11:02:12,201 NOTICE kernel:[   10.378421] sd 1:0:2:0: [sdg] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.378428] sd 1:0:2:0: [sdg] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.378435] sd 1:0:2:0: [sdg] Attached SCSI disk
>11:02:12,201 INFO kernel:[   10.382347]  sdf: sdf1
>11:02:12,201 NOTICE kernel:[   10.383451] sd 1:0:1:0: [sdf] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.383466] sd 1:0:1:0: [sdf] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.383476] sd 1:0:1:0: [sdf] Attached SCSI disk
>11:02:12,201 INFO kernel:[   10.395404]  sdh: sdh1 sdh2 sdh3 sdh4 < sdh5 >
>11:02:12,201 INFO kernel:[   10.395515]  sdd: sdd1 sdd2 sdd3 sdd4 < sdd5 >
>11:02:12,201 NOTICE kernel:[   10.398425] sd 1:0:3:0: [sdh] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.398439] sd 1:0:3:0: [sdh] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.398450] sd 1:0:3:0: [sdh] Attached SCSI disk
>11:02:12,201 NOTICE kernel:[   10.398832] sd 0:0:4:0: [sdd] Cache data unavailable
>11:02:12,201 ERR kernel:[   10.398848] sd 0:0:4:0: [sdd] Assuming drive cache: write through
>11:02:12,201 NOTICE kernel:[   10.398869] sd 0:0:4:0: [sdd] Attached SCSI disk
>11:02:12,205 INFO kernel:[   10.826137]  sda: sda1 sda2 sda3 sda4 < sda5 >
>11:02:12,205 NOTICE kernel:[   10.854883] sd 0:0:1:0: [sda] Cache data unavailable
>11:02:12,205 ERR kernel:[   10.854894] sd 0:0:1:0: [sda] Assuming drive cache: write through
>11:02:12,205 NOTICE kernel:[   10.854904] sd 0:0:1:0: [sda] Attached SCSI disk
>11:02:12,205 DEBUG kernel:[   10.936847] ISO 9660 Extensions: Microsoft Joliet Level 3
>11:02:12,206 DEBUG kernel:[   10.943526] ISO 9660 Extensions: RRIP_1991A
>11:02:12,207 INFO kernel:[   11.122206] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
>11:02:12,210 DEBUG kernel:[   14.025530] SELinux: 2048 avtab hash slots, 99000 rules.
>11:02:12,210 DEBUG kernel:[   14.064105] SELinux: 2048 avtab hash slots, 99000 rules.
>11:02:12,210 DEBUG kernel:[   14.321550] SELinux:  9 users, 15 roles, 4112 types, 222 bools, 1 sens, 1024 cats
>11:02:12,210 DEBUG kernel:[   14.321576] SELinux:  83 classes, 99000 rules
>11:02:12,210 INFO kernel:[   14.330334] SELinux:  Permission ptrace_child in class process not defined in policy.
>11:02:12,210 INFO kernel:[   14.330503] SELinux: the above unknown classes and permissions will be allowed
>11:02:12,210 DEBUG kernel:[   14.330519] SELinux:  Completing initialization.
>11:02:12,210 DEBUG kernel:[   14.330523] SELinux:  Setting up existing superblocks.
>11:02:12,210 DEBUG kernel:[   14.330541] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
>11:02:12,210 DEBUG kernel:[   14.330555] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
>11:02:12,210 DEBUG kernel:[   14.330566] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
>11:02:12,210 DEBUG kernel:[   14.330576] SELinux: initialized (dev proc, type proc), uses genfs_contexts
>11:02:12,210 DEBUG kernel:[   14.330599] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
>11:02:12,210 DEBUG kernel:[   14.330622] SELinux: initialized (dev devtmpfs, type devtmpfs), uses transition SIDs
>11:02:12,210 DEBUG kernel:[   14.331532] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
>11:02:12,210 DEBUG kernel:[   14.331542] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
>11:02:12,210 DEBUG kernel:[   14.334786] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
>11:02:12,210 DEBUG kernel:[   14.334798] SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts
>11:02:12,210 DEBUG kernel:[   14.334807] SELinux: initialized (dev devpts, type devpts), uses transition SIDs
>11:02:12,210 DEBUG kernel:[   14.334826] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs
>11:02:12,210 DEBUG kernel:[   14.334837] SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
>11:02:12,210 DEBUG kernel:[   14.334848] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
>11:02:12,210 DEBUG kernel:[   14.334888] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   14.336466] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
>11:02:12,211 DEBUG kernel:[   14.336477] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
>11:02:12,211 DEBUG kernel:[   14.342361] SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   14.342391] SELinux: initialized (dev sr0, type iso9660), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   14.342426] SELinux: initialized (dev loop0, type squashfs), uses xattr
>11:02:12,211 DEBUG kernel:[   14.342469] SELinux: initialized (dev dm-0, type ext4), uses xattr
>11:02:12,211 NOTICE kernel:[   14.628018] type=1403 audit(1339498920.210:2): policy loaded auid=4294967295 ses=4294967295
>11:02:12,211 DEBUG kernel:[   14.751502] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
>11:02:12,211 DEBUG kernel:[   14.824337] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   15.024398] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   15.105845] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   15.184842] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   15.264801] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   15.344826] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   15.464778] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   15.544349] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   15.664318] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   16.260002] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   16.893373] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
>11:02:12,211 DEBUG kernel:[   17.820027] SELinux: initialized (dev securityfs, type securityfs), uses genfs_contexts
>11:02:12,211 DEBUG kernel:[   18.361251] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs
>11:02:12,211 DEBUG kernel:[   18.529601] SELinux: initialized (dev configfs, type configfs), uses genfs_contexts
>11:02:12,211 INFO kernel:[   20.793838] EXT4-fs (dm-0): re-mounted. Opts: user_xattr,barrier=1,data=ordered
>11:02:12,211 NOTICE kernel:[   22.756840] type=1400 audit(1339498928.340:3): avc:  denied  { create } for  pid=609 comm="systemd-tmpfile" name="tmp" scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir
>11:02:12,211 NOTICE kernel:[   22.760803] type=1400 audit(1339498928.340:4): avc:  denied  { setattr } for  pid=609 comm="systemd-tmpfile" name="tmp" dev="dm-0" ino=17504 scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir
>11:02:12,211 NOTICE kernel:[   22.761173] type=1400 audit(1339498928.340:5): avc:  denied  { relabelfrom } for  pid=609 comm="systemd-tmpfile" name="tmp" dev="dm-0" ino=17504 scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir
>11:02:12,211 NOTICE kernel:[   26.052151] type=1400 audit(1339498931.630:6): avc:  denied  { execute } for  pid=630 comm="bash" name="hostname" dev="dm-0" ino=8456 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:hostname_exec_t:s0 tclass=file
>11:02:12,211 NOTICE kernel:[   26.052191] type=1400 audit(1339498931.630:7): avc:  denied  { read open } for  pid=630 comm="bash" name="hostname" dev="dm-0" ino=8456 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:hostname_exec_t:s0 tclass=file
>11:02:12,211 NOTICE kernel:[   26.052289] type=1400 audit(1339498931.630:8): avc:  denied  { execute_no_trans } for  pid=630 comm="bash" path="/usr/bin/hostname" dev="dm-0" ino=8456 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:hostname_exec_t:s0 tclass=file
>11:02:12,211 NOTICE kernel:[   26.079968] type=1400 audit(1339498931.660:9): avc:  denied  { read } for  pid=625 comm="bash" name=".profile" dev="dm-0" ino=40962 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:admin_home_t:s0 tclass=file
>11:02:12,211 NOTICE kernel:[   26.079988] type=1400 audit(1339498931.660:10): avc:  denied  { open } for  pid=625 comm="bash" name=".profile" dev="dm-0" ino=40962 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:admin_home_t:s0 tclass=file
>11:02:12,211 NOTICE kernel:[   26.091348] type=1400 audit(1339498931.670:11): avc:  denied  { read } for  pid=625 comm="bash" name="linux" dev="dm-0" ino=25379 scontext=system_u:system_r:getty_t:s0 tcontext=unconfined_u:object_r:usr_t:s0 tclass=file
>11:02:12,277 INFO polkitd: started daemon version 0.104 using authority implementation `local' version `0.104'
>11:02:12,279 NOTICE dbus: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
>11:02:12,280 INFO dbus-daemon: dbus[628]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
>11:02:12,354 WARNING NetworkManager:    ifcfg-rh: Could not get hostname: failed to read /etc/sysconfig/network
>11:02:12,357 NOTICE NetworkManager:    ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1
>11:02:12,358 INFO NetworkManager: <info> Loaded plugin ifcfg-rh: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
>11:02:12,359 INFO NetworkManager: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
>11:02:12,360 NOTICE NetworkManager:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ...
>11:02:12,362 NOTICE NetworkManager:    ifcfg-rh:     read connection 'Boot Disk'
>11:02:12,364 NOTICE NetworkManager:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...
>11:02:12,374 INFO NetworkManager: <info> trying to start the modem manager...
>11:02:12,377 NOTICE dbus: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
>11:02:12,378 INFO NetworkManager: <info> monitoring kernel firmware directory '/lib/firmware'.
>11:02:12,380 INFO dbus-daemon: dbus[628]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
>11:02:12,390 INFO NetworkManager: <info> WiFi enabled by radio killswitch; enabled by state file
>11:02:12,407 INFO NetworkManager: <info> WWAN enabled by radio killswitch; enabled by state file
>11:02:12,409 INFO NetworkManager: <info> WiMAX enabled by radio killswitch; enabled by state file
>11:02:12,413 INFO NetworkManager: <info> Networking is enabled by state file
>11:02:12,485 WARNING NetworkManager: <warn> failed to allocate link cache: (-10) Operation not supported
>11:02:12,555 INFO NetworkManager: <info> (eth0): carrier is ON
>11:02:12,567 ERR NetworkManager: <error> [1339498932.417346] [nm-device-ethernet.c:456] real_update_permanent_hw_address(): (eth0): unable to read permanent MAC address (error 0)
>11:02:12,571 INFO NetworkManager: <info> (eth0): new Ethernet device (driver: 'ibmveth' ifindex: 2)
>11:02:12,571 INFO NetworkManager: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
>11:02:12,572 INFO NetworkManager: <info> (eth0): now managed
>11:02:12,575 INFO NetworkManager: <info> (eth0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
>11:02:12,576 INFO NetworkManager: <info> (eth0): preparing device.
>11:02:12,578 INFO NetworkManager: <info> Activation (eth0) starting connection 'Boot Disk'
>11:02:12,578 INFO NetworkManager: <info> (eth0): device state change: unavailable -> ip-config (reason 'none') [20 70 0]
>11:02:12,579 WARNING NetworkManager: (nm-device.c:2343):nm_device_activate_schedule_stage3_ip_config_start: runtime check failed: (state >= NM_DEVICE_STATE_PREPARE && state <= NM_DEVICE_STATE_NEED_AUTH)
>11:02:12,581 INFO NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
>11:02:12,583 INFO modem-manager: <info>  ModemManager (version 0.5.2.0-1.fc17) starting...
>11:02:12,585 WARNING NetworkManager: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
>11:02:12,586 NOTICE dbus: [system] Successfully activated service 'org.freedesktop.ModemManager'
>11:02:12,587 INFO NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
>11:02:12,588 INFO NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
>11:02:12,590 INFO NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
>11:02:12,591 INFO NetworkManager: <info> modem-manager is now available
>11:02:12,591 INFO NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
>11:02:12,593 INFO dbus-daemon: modem-manager[644]: <info>  ModemManager (version 0.5.2.0-1.fc17) starting...
>11:02:12,594 INFO dbus-daemon: dbus[628]: [system] Successfully activated service 'org.freedesktop.ModemManager'
>11:02:12,595 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Gobi
>11:02:12,596 INFO NetworkManager: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0]
>11:02:12,597 INFO modem-manager: <info>  Loaded plugin Gobi
>11:02:12,602 INFO NetworkManager: <info> Policy set 'Boot Disk' (eth0) as default for IPv4 routing and DNS.
>11:02:12,602 INFO NetworkManager: <info> Activation (eth0) successful, device activated.
>11:02:12,605 INFO NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
>11:02:12,614 NOTICE dbus: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
>11:02:12,614 INFO modem-manager: <info>  Loaded plugin Novatel
>11:02:12,614 INFO dbus-daemon: dbus[628]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
>11:02:12,614 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Novatel
>11:02:12,616 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin SimTech
>11:02:12,617 INFO modem-manager: <info>  Loaded plugin SimTech
>11:02:12,629 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Generic
>11:02:12,632 INFO modem-manager: <info>  Loaded plugin Generic
>11:02:12,637 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Samsung
>11:02:12,639 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Nokia
>11:02:12,640 INFO modem-manager: <info>  Loaded plugin Samsung
>11:02:12,641 INFO modem-manager: <info>  Loaded plugin Nokia
>11:02:12,643 INFO modem-manager: <info>  Loaded plugin AnyData
>11:02:12,645 INFO modem-manager: <info>  Loaded plugin Option
>11:02:12,646 INFO modem-manager: <info>  Loaded plugin MotoC
>11:02:12,648 INFO modem-manager: <info>  Loaded plugin Linktop
>11:02:12,650 NOTICE dbus: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
>11:02:12,652 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin AnyData
>11:02:12,654 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Option
>11:02:12,656 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin MotoC
>11:02:12,659 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Linktop
>11:02:12,659 INFO dbus-daemon: dbus[628]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
>11:02:12,662 INFO modem-manager: <info>  Loaded plugin Sierra
>11:02:12,663 INFO modem-manager: <info>  Loaded plugin Ericsson MBM
>11:02:12,664 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Sierra
>11:02:12,666 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Ericsson MBM
>11:02:12,667 INFO modem-manager: <info>  Loaded plugin Option High-Speed
>11:02:12,670 INFO modem-manager: <info>  Loaded plugin Longcheer
>11:02:12,671 INFO modem-manager: <info>  Loaded plugin Wavecom
>11:02:12,674 INFO modem-manager: <info>  Loaded plugin ZTE
>11:02:12,675 INFO modem-manager: <info>  Loaded plugin X22X
>11:02:12,676 INFO modem-manager: <info>  Loaded plugin Huawei
>11:02:12,679 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Option High-Speed
>11:02:12,680 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Longcheer
>11:02:12,680 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Wavecom
>11:02:12,683 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin ZTE
>11:02:12,684 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin X22X
>11:02:12,685 INFO dbus-daemon: modem-manager[644]: <info>  Loaded plugin Huawei
>11:02:12,742 INFO dbus-daemon: /etc/NetworkManager/dispatcher.d/04-iscsi: line 13: /sbin/ip: No such file or directory
>11:02:20,726 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:02:20,885 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:02:21,084 WARNING kernel:[   35.488489] audit_printk_skb: 6 callbacks suppressed
>11:02:21,084 NOTICE kernel:[   35.488496] type=1400 audit(1339498941.070:14): avc:  denied  { append } for  pid=676 comm="auditd" path="/tmp/anaconda.log" dev="dm-0" ino=74625 scontext=system_u:system_r:auditd_t:s0 tcontext=system_u:object_r:initrc_tmp_t:s0 tclass=file
>11:02:21,084 NOTICE kernel:[   35.488694] type=1400 audit(1339498941.070:15): avc:  denied  { read write } for  pid=676 comm="auditd" path="/dev/mapper/control" dev="devtmpfs" ino=8037 scontext=system_u:system_r:auditd_t:s0 tcontext=system_u:object_r:lvm_control_t:s0 tclass=chr_file
>11:02:21,084 WARNING kernel:[   35.494324] auditd (677): /proc/677/oom_adj is deprecated, please use /proc/677/oom_score_adj instead.
>11:02:31,097 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:02:31,248 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:02:41,404 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:02:41,546 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:02:51,716 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:02:51,815 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:03:01,967 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:03:02,165 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:03:12,334 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:03:12,444 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:03:22,613 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:03:22,745 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:03:24,074 INFO kernel:[   98.476070] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
>11:03:24,074 DEBUG kernel:[   98.477984] SELinux: initialized (dev sda2, type ext4), uses xattr
>11:03:25,114 INFO kernel:[   99.516633] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
>11:03:25,114 DEBUG kernel:[   99.516653] SELinux: initialized (dev sda3, type ext4), uses xattr
>11:03:27,124 INFO kernel:[  101.531293] EXT4-fs (dm-7): mounted filesystem with ordered data mode. Opts: (null)
>11:03:27,134 DEBUG kernel:[  101.539929] SELinux: initialized (dev dm-7, type ext4), uses xattr
>11:03:29,254 INFO kernel:[  103.655546] EXT4-fs (dm-8): mounted filesystem with ordered data mode. Opts: (null)
>11:03:29,254 DEBUG kernel:[  103.655714] SELinux: initialized (dev dm-8, type ext4), uses xattr
>11:03:31,544 DEBUG kernel:[  105.945140] RTAS: event: 20, Type: Platform Error, Severity: 2
>11:03:32,944 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:03:33,105 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:03:43,325 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:03:43,445 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:03:53,631 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:03:53,765 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:04:03,931 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:04:04,105 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:04:14,261 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:04:14,365 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:04:24,492 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:04:24,645 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:04:34,813 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:04:34,975 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:04:45,193 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:04:45,325 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:04:55,473 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:04:55,615 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:05:05,771 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:05:05,885 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:05:16,031 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:05:16,185 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:05:26,321 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:05:26,486 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:05:36,663 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:05:36,785 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:05:46,953 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:05:47,045 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:05:57,190 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:05:57,324 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:06:07,491 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:06:07,635 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:06:17,804 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:06:17,945 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:06:28,112 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:06:28,255 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:06:38,471 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:06:38,615 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:06:48,792 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:06:48,905 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:06:59,081 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:06:59,225 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:07:09,372 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:07:09,485 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:07:19,661 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:07:19,815 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:07:29,983 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:07:30,115 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:07:40,290 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:07:40,445 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:07:50,622 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:07:50,745 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:08:00,921 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:08:01,065 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:08:11,272 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:08:11,395 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:08:21,560 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:08:21,685 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:08:31,850 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:08:32,025 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:08:42,203 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:08:42,336 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:08:52,543 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:08:52,625 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:09:02,819 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:09:03,015 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:09:13,232 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:09:13,325 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:09:23,490 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:09:23,656 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:09:33,823 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:09:33,985 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:09:44,162 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:09:44,255 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:09:54,433 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:09:54,556 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:10:04,732 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:10:04,844 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:10:15,032 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:10:15,115 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:10:25,283 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:10:25,425 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:10:35,652 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:10:35,815 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:10:46,023 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:10:46,135 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:10:56,340 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:10:56,515 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:11:06,683 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:11:06,845 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:11:17,062 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:11:17,226 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:11:27,431 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:11:27,596 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:11:37,752 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:11:37,906 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:11:48,072 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:11:48,185 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:11:58,361 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:11:58,515 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:12:08,684 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:12:08,825 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:12:19,033 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:12:19,155 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:12:29,324 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:12:29,496 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:12:39,662 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:12:39,815 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:12:49,970 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:12:50,115 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:13:00,270 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:13:00,425 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:13:10,604 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:13:10,726 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:13:20,930 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:13:21,095 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:13:31,261 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:13:31,395 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:13:41,584 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:13:41,715 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:13:51,933 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:13:52,056 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:14:02,235 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:14:02,395 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:14:12,572 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:14:12,694 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:14:22,882 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:14:23,035 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:14:33,202 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:14:33,335 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:14:43,513 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:14:43,665 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:14:53,820 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:14:53,965 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:15:04,162 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:15:04,286 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:15:14,484 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:15:14,596 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:15:24,784 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:15:24,925 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:15:35,092 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:15:35,226 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:15:45,396 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:15:45,515 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:15:55,672 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:15:55,815 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:16:06,023 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:16:06,155 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:16:16,312 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:16:16,435 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:16:26,623 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:16:26,755 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:16:36,893 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:16:36,975 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:16:45,815 INFO systemd-tmpfile: Successfully loaded SELinux database in 34ms 280us, size on heap is 535K.
>11:16:47,122 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:16:47,295 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:16:57,513 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:16:57,614 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:17:07,770 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:17:07,955 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:17:18,104 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:17:18,236 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:17:28,404 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:17:28,536 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:17:38,703 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:17:38,835 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:17:49,002 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:17:49,215 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:17:59,382 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:17:59,545 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:18:09,712 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:18:09,865 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:18:20,034 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:18:20,205 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:18:30,403 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:18:30,536 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:18:40,731 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:18:40,826 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:18:50,993 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:18:51,105 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:19:01,292 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:19:01,415 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:19:11,591 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:19:11,716 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:19:21,889 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:19:22,045 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:19:28,124 ERR udevd: sender uid=-1, message ignored
>11:19:32,231 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:19:32,395 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:19:32,574 INFO kernel:[ 1066.975874] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
>11:19:32,574 DEBUG kernel:[ 1066.976338] SELinux: initialized (dev dm-3, type ext4), uses xattr
>11:19:34,174 INFO kernel:[ 1068.580421] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
>11:19:34,174 DEBUG kernel:[ 1068.580438] SELinux: initialized (dev dm-4, type ext4), uses xattr
>11:19:42,523 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:19:42,615 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:19:52,785 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:19:52,895 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:20:03,071 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:20:03,246 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:20:13,454 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:20:13,655 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:20:23,861 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:20:23,995 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:20:34,151 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:20:34,315 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:20:44,481 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:20:44,604 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:20:54,745 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:20:54,875 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:21:05,040 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:21:05,135 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:21:15,293 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:21:15,365 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:21:25,513 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:21:25,685 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:21:35,852 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:21:35,995 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:21:46,173 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:21:46,274 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:21:56,451 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:21:56,645 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:22:06,812 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:22:06,935 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:22:17,113 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:22:17,246 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:22:27,244 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:22:27,387 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:22:37,553 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:22:37,707 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:22:47,874 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:22:47,967 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:22:58,136 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:22:58,257 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:23:08,464 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:23:08,636 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:23:18,804 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:23:18,967 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:23:29,134 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:23:29,277 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:23:39,524 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:23:39,608 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:23:49,764 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:23:49,877 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:24:00,033 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:24:00,227 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:24:10,395 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:24:10,527 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:24:20,694 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:24:20,817 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:24:30,982 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:24:31,097 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:24:41,285 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:24:41,356 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:24:51,584 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:24:51,687 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:25:01,856 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:25:02,017 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:25:12,215 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:25:12,398 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:25:22,563 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:25:22,666 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:25:32,822 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:25:32,977 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:25:43,132 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:25:43,307 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:25:53,462 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:25:53,577 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:26:03,803 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:26:03,986 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:26:14,195 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:26:14,367 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:26:24,574 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:26:24,737 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:26:34,904 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:26:35,026 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:26:45,203 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:26:45,317 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:26:55,505 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:26:55,578 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:27:05,754 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:27:05,908 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:27:16,083 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:27:16,237 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:27:26,404 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:27:26,517 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:27:36,683 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:27:36,807 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:27:47,012 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:27:47,116 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:27:57,294 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:27:57,446 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:28:07,653 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:28:07,787 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:28:17,965 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:28:18,077 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:28:28,243 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:28:28,386 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:28:38,543 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:28:38,657 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:28:48,816 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:28:48,937 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:28:59,105 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:28:59,266 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:29:09,434 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:29:09,557 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:29:19,764 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:29:19,897 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:29:30,093 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:29:30,267 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:29:40,433 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:29:40,567 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:29:50,736 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:29:50,896 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:30:01,103 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:30:01,267 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:30:11,426 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:30:11,557 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:30:21,733 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:30:21,878 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:30:32,124 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:30:32,257 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:30:42,464 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:30:42,647 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:30:52,813 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:30:52,926 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:31:03,086 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:31:03,236 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:31:13,433 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:31:13,577 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:31:23,744 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:31:23,866 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:31:34,044 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:31:34,197 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:31:44,371 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:31:44,537 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:31:54,712 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:31:54,877 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:32:05,043 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:32:05,217 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:32:15,436 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:32:15,558 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:32:25,716 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:32:25,857 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:32:36,073 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:32:36,226 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:32:46,375 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:32:46,557 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:32:56,734 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:32:56,887 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:32:58,346 WARNING kernel:[ 1872.915580] device-mapper: table: 253:7: dm-5 too small for target: start=2048, len=8192, dev_size=2
>11:32:58,346 DEBUG kernel:[ 1872.917052] device-mapper: ioctl: device doesn't appear to be in the dev hash table.
>11:32:58,346 WARNING kernel:[ 1872.918525] device-mapper: table: 253:7: dm-5 too small for target: start=10240, len=1024000, dev_size=2
>11:32:58,346 DEBUG kernel:[ 1872.919851] device-mapper: ioctl: device doesn't appear to be in the dev hash table.
>11:32:58,346 WARNING kernel:[ 1872.921054] device-mapper: table: 253:7: dm-5 too small for target: start=1034240, len=17889280, dev_size=2
>11:32:58,346 DEBUG kernel:[ 1872.921699] device-mapper: ioctl: device doesn't appear to be in the dev hash table.
>11:32:58,346 WARNING kernel:[ 1872.923178] device-mapper: table: 253:7: dm-5 too small for target: start=18923520, len=2048000, dev_size=2
>11:32:58,346 DEBUG kernel:[ 1872.923833] device-mapper: ioctl: device doesn't appear to be in the dev hash table.
>11:32:58,357 ERR udevd: setfilecon /dev/dm-7 failed: No such file or directory
>11:33:00,036 WARNING kernel:[ 1874.611589] device-mapper: table: 253:7: dm-5 too small for target: start=2048, len=8192, dev_size=2
>11:33:00,036 DEBUG kernel:[ 1874.612492] device-mapper: ioctl: device doesn't appear to be in the dev hash table.
>11:33:00,036 WARNING kernel:[ 1874.613359] device-mapper: table: 253:7: dm-5 too small for target: start=10240, len=1024000, dev_size=2
>11:33:00,046 DEBUG kernel:[ 1874.615314] device-mapper: ioctl: device doesn't appear to be in the dev hash table.
>11:33:00,046 WARNING kernel:[ 1874.616267] device-mapper: table: 253:7: dm-5 too small for target: start=1034240, len=17889280, dev_size=2
>11:33:00,046 DEBUG kernel:[ 1874.617554] device-mapper: ioctl: device doesn't appear to be in the dev hash table.
>11:33:00,046 WARNING kernel:[ 1874.618197] device-mapper: table: 253:7: dm-5 too small for target: start=18923520, len=2048000, dev_size=2
>11:33:00,046 DEBUG kernel:[ 1874.619338] device-mapper: ioctl: device doesn't appear to be in the dev hash table.
>11:33:07,103 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:33:07,188 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:33:17,326 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:33:17,437 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:33:27,623 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:33:27,747 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:33:37,912 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:33:38,067 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:33:48,234 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:33:48,427 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:33:58,625 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:33:58,747 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:34:08,912 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:34:09,016 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:34:19,194 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:34:19,308 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:34:29,488 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:34:29,617 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:34:39,800 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:34:39,969 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:34:50,169 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:34:50,287 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:35:00,464 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:35:00,607 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:35:10,763 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:35:10,877 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:35:21,063 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:35:21,178 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:35:31,343 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:35:31,467 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:35:41,644 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:35:41,727 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:35:51,876 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:35:51,997 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:36:02,165 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:36:02,247 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:36:12,414 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:36:12,567 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:36:22,725 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:36:22,868 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:36:33,064 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:36:33,187 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:36:43,355 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:36:43,437 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:36:53,614 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:36:53,726 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:37:03,904 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:37:04,087 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:37:14,252 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:37:14,438 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:37:24,615 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:37:24,736 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:37:34,893 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:37:35,007 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:37:45,212 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:37:45,388 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:37:55,553 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:37:55,706 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:38:05,883 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:38:05,987 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:38:16,137 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:38:16,257 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:38:26,384 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:38:26,477 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:38:36,693 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:38:36,818 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:38:46,982 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:38:47,167 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:38:57,345 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:38:57,426 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:39:07,595 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:39:07,736 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:39:17,904 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:39:18,047 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:39:28,204 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:39:28,347 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:39:38,514 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:39:38,637 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:39:48,804 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:39:48,917 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:39:59,083 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:39:59,177 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:40:09,344 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:40:09,426 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:40:19,556 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:40:19,687 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:40:29,854 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:40:29,986 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:40:40,185 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:40:40,267 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:40:50,434 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:40:50,597 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:41:00,766 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:41:00,917 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:41:11,072 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:41:11,206 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:41:21,384 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:41:21,536 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:41:31,714 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:41:31,827 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:41:42,004 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:41:42,117 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:41:52,293 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:41:52,446 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:42:02,634 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:42:02,768 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:42:12,905 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:42:13,077 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:42:23,296 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:42:23,466 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:42:33,644 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:42:33,767 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:42:43,946 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:42:44,076 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:42:54,245 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:42:54,376 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:43:04,584 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:43:04,697 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:43:14,864 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:43:14,947 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:43:25,154 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:43:25,297 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:43:35,494 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:43:35,637 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:43:45,806 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:43:45,937 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:43:56,094 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:43:56,237 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:44:06,435 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:44:06,517 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:44:16,672 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:44:16,817 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:44:26,993 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:44:27,137 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:44:37,304 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:44:37,376 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:44:47,545 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:44:47,698 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:44:57,904 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:44:58,047 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:45:08,214 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:45:08,337 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:45:18,544 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:45:18,687 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:45:28,852 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:45:29,017 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:45:39,196 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:45:39,317 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:45:49,515 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:45:49,657 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:45:59,867 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:45:59,997 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:46:10,203 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:46:10,307 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:46:20,484 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:46:20,627 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:46:30,794 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:46:30,897 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:46:41,093 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:46:41,257 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:46:51,421 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:46:51,577 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:47:01,735 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:47:01,849 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:47:12,013 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:47:12,166 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:47:22,322 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:47:22,446 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:47:32,614 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:47:32,716 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:47:42,904 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:47:43,107 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:47:53,285 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:47:53,407 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:48:03,642 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:48:03,777 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:48:13,944 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:48:14,067 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:48:24,233 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:48:24,367 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:48:34,545 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:48:34,667 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:48:44,866 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:48:44,996 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:48:55,173 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:48:55,297 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:49:05,473 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:49:05,617 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:49:15,782 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:49:15,887 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:49:26,052 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:49:26,237 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:49:36,444 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:49:36,557 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:49:46,724 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:49:46,887 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:49:57,065 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:49:57,167 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:50:07,335 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:50:07,468 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:50:17,633 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:50:17,718 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:50:27,883 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:50:28,057 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:50:38,222 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:50:38,337 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:50:48,496 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:50:48,617 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:50:58,765 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:50:58,887 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:51:09,103 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:51:09,196 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:51:19,374 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:51:19,518 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:51:29,694 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:51:29,827 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:51:39,993 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:51:40,147 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:51:50,294 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:51:50,427 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:52:00,594 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:52:00,757 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:52:10,923 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:52:11,096 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:52:21,252 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:52:21,407 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:52:31,533 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:52:31,647 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:52:41,854 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:52:41,967 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:52:52,135 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:52:52,267 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:53:02,434 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:53:02,586 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:53:12,743 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:53:12,877 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:53:23,084 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:53:23,226 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:53:33,433 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:53:33,597 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:53:43,817 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:53:43,937 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:53:54,103 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:53:54,257 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:54:04,463 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:54:04,627 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:54:14,792 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:54:14,937 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:54:25,115 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:54:25,266 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:54:35,433 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:54:35,597 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:54:45,752 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:54:45,917 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:54:56,075 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:54:56,207 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:55:06,415 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:55:06,537 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:55:16,756 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:55:16,907 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:55:27,072 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:55:27,237 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:55:37,417 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:55:37,537 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:55:47,709 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:55:47,848 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
>11:55:58,066 INFO systemd: anaconda-shell@hvc1.service holdoff time over, scheduling restart.
>11:55:58,227 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.

Actions: View

Attachments on bug 832877: 592528 | 592529 | 592530 | 592531 | 592532 | 592533 | 592534 | 592535