Автор Тема: При выключении всех гостевых вм через shutdown -h now все выключаются, кроме одной  (Прочитано 1055 раз)

Оффлайн PSV

  • Давно тут
  • **
  • Сообщений: 361
Что бы не плодить тем, напишу проблему тут.
Железный сервак с qemu и несколькими вир. вм на р7.
Гашу все гостевые вм через shutdown -h now. Все гасятся, кроме одной.
На ней завершаются процессы, остается висеть черный экран. После этого её можно погасить только принудительный power off.
В логах ничего интересного не нашел, или плохо искал.
Куда посоветуете смотреть?

Инфлэйм

  • Гость
В логах ничего интересного не нашел, или плохо искал.
логи в студию

Оффлайн PSV

  • Давно тут
  • **
  • Сообщений: 361
вырезка из /var/log/messages с парой гашений
Jul 27 19:34:20 vmldb sshd[15582]: Accepted publickey for ROOT USER root from 192.168.1.11 port 39796 ssh2: RSA

9c:db:89:0f:94:27:3d:d2:e4:a1:35:46:cb:78:d9:ad
Jul 27 19:37:13 vmldb to_forum: before_shutdown
Jul 27 19:37:42 vmldb shutdown[15788]: shutting down for system halt
Jul 27 19:37:42 vmldb init: Switching to runlevel: 0
Jul 27 19:37:43 vmldb alteratord: alteratord shutdown succeeded
Jul 27 19:37:43 vmldb plymouth: Activating splash succeeded
Jul 27 19:37:43 vmldb postgresql: Stopping postgresql service:
Jul 27 19:37:43 vmldb sshd[15582]: Received disconnect from 192.168.1.11: 11: disconnected by user
Jul 27 19:37:43 vmldb postgresql: ^[[73G
Jul 27 19:37:43 vmldb postgresql: [
Jul 27 19:37:43 vmldb postgresql: ^[[1m^[[32m
Jul 27 19:37:43 vmldb postgresql: DONE
Jul 27 19:37:43 vmldb postgresql: ^[[39;49m^[[0;10m
Jul 27 19:37:43 vmldb rc: Stopping postgresql: succeeded
Jul 27 19:37:43 vmldb sshd[2399]: Received signal 15; terminating.
Jul 27 19:37:43 vmldb sshd: sshd shutdown succeeded
Jul 27 19:37:44 vmldb postfix: Shutting down postfix: succeeded
Jul 27 19:37:44 vmldb smb: smbd shutdown succeeded
Jul 27 19:37:44 vmldb crond: crond shutdown succeeded
Jul 27 19:37:44 vmldb gpm: gpm shutdown succeeded
Jul 27 19:37:44 vmldb acpid: exiting
Jul 27 19:37:44 vmldb acpid: acpid shutdown succeeded
Jul 27 19:37:44 vmldb rc: Stopping keytable: succeeded
Jul 27 19:37:44 vmldb rc: Stopping fbsetfont: succeeded
Jul 27 19:37:44 vmldb idmapd: rpc.idmapd shutdown succeeded
Jul 27 19:37:44 vmldb blkdeactivate: Deactivating block devices:
Jul 27 19:37:44 vmldb blkdeactivate: /sbin/blkdeactivate: line 241: /bin/lsblk: No such file or directory
Jul 27 19:37:44 vmldb blk-availability: Stopping block device availability: succeeded
Jul 27 19:37:44 vmldb dd: 1+0 records in
Jul 27 19:37:44 vmldb dd: 1+0 records out
Jul 27 19:37:44 vmldb dd: 512 bytes (512 B) copied, 0.000101543 s, 5.0 MB/s
Jul 27 19:37:44 vmldb random: Saving random seed: succeeded
Jul 27 19:37:45 vmldb nfslock: rpc.statd shutdown succeeded
Jul 27 19:37:45 vmldb rpcbind: rpcbind shutdown succeeded
Jul 27 19:37:45 vmldb network: Computing interface groups:
Jul 27 19:37:45 vmldb network: .
Jul 27 19:37:45 vmldb network: .
Jul 27 19:37:45 vmldb network:  2 interfaces found
Jul 27 19:37:45 vmldb network: Processing /etc/net/vlantab: empty.
Jul 27 19:37:45 vmldb network: Stopping group 1/realphys (1 interfaces)
Jul 27 19:37:45 vmldb network: ^IStopping eth0:
Jul 27 19:37:45 vmldb dhcpcd[16275]: sending signal 1 to pid 1712
Jul 27 19:37:45 vmldb dhcpcd[1712]: received SIGHUP, releasing
Jul 27 19:37:45 vmldb dhcpcd[1712]: eth0: releasing lease of 192.168.1.89
Jul 27 19:37:45 vmldb dhcpcd[16275]: waiting for pid 1712 to exit
Jul 27 19:37:45 vmldb dhcpcd[1712]: eth0: removing interface
Jul 27 19:37:45 vmldb network: .
Jul 27 19:37:45 vmldb last message repeated 2 times
Jul 27 19:37:45 vmldb network: OK
Jul 27 19:37:45 vmldb network: Stopping group 0/virtual (1 interfaces)
Jul 27 19:37:45 vmldb network: ^IStopping lo:
Jul 27 19:37:45 vmldb network: .
Jul 27 19:37:45 vmldb network: .OK
Jul 27 19:37:45 vmldb rc: Stopping network: succeeded
Jul 27 19:37:45 vmldb messagebus: dbus-daemon shutdown succeeded
Jul 27 19:37:45 vmldb udevd: systemd-udevd shutdown succeeded
Jul 27 19:37:45 vmldb kernel: Kernel logging (proc) stopped.
Jul 27 19:37:46 vmldb kernel: Kernel log daemon terminating.
Jul 27 19:37:47 vmldb klogd: klogd shutdown succeeded
Jul 27 19:37:47 vmldb exiting on signal 15
Jul 27 13:38:41 vmldb syslogd 1.4.1: restart.
Jul 27 13:38:41 vmldb syslogd: syslogd startup succeeded
Jul 27 13:38:41 vmldb kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jul 27 13:38:41 vmldb kernel: [    1.746581] tun: Universal TUN/TAP device driver, 1.6
Jul 27 13:38:41 vmldb kernel: [    1.746583] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 27 13:38:41 vmldb kernel: <30>[    1.872711] systemd-udevd[638]: starting version 201
Jul 27 13:38:41 vmldb kernel: [    2.205518] microcode: CPU0 sig=0x206c1, pf=0x1, revision=0x1
Jul 27 13:38:41 vmldb kernel: [    2.237219] input: PC Speaker as /devices/platform/pcspkr/input/input1
Jul 27 13:38:41 vmldb kernel: [    2.250174] device-mapper: uevent: version 1.0.3
Jul 27 13:38:41 vmldb kernel: [    2.250215] device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-devel@redhat.com
Jul 27 13:38:41 vmldb kernel: [    2.255563] ACPI Exception: AE_BAD_PARAMETER, Thread 418809920 could not acquire Mutex [0x1] (20130328/utmutex-285)
Jul 27 13:38:41 vmldb kernel: [    2.255585] piix4_smbus 0000:00:01.3: SMBus Host Controller at 0xb100, revision 0
Jul 27 13:38:41 vmldb kernel: [    2.282768] usbcore: registered new interface driver usbfs
Jul 27 13:38:41 vmldb kernel: [    2.282776] usbcore: registered new interface driver hub
Jul 27 13:38:41 vmldb kernel: [    2.283222] usbcore: registered new device driver usb
Jul 27 13:38:41 vmldb kernel: [    2.300289] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 27 13:38:41 vmldb kernel: [    2.300777] ehci-pci: EHCI PCI platform driver
Jul 27 13:38:41 vmldb kernel: [    2.300820] ehci-pci 0000:00:04.7: found PCI INT D -> IRQ 11
Jul 27 13:38:41 vmldb kernel: [    2.300861] ehci-pci 0000:00:04.7: sharing IRQ 11 with 0000:00:03.0
Jul 27 13:38:41 vmldb kernel: [    2.301817] ehci-pci 0000:00:04.7: EHCI Host Controller
Jul 27 13:38:41 vmldb kernel: [    2.301821] ehci-pci 0000:00:04.7: new USB bus registered, assigned bus number 1
Jul 27 13:38:41 vmldb kernel: [    2.301928] ehci-pci 0000:00:04.7: irq 11, io mem 0xfebf2000
Jul 27 13:38:41 vmldb kernel: [    2.312084] ehci-pci 0000:00:04.7: USB 2.0 started, EHCI 1.00
Jul 27 13:38:41 vmldb kernel: [    2.312190] hub 1-0:1.0: USB hub found
Jul 27 13:38:41 vmldb kernel: [    2.312194] hub 1-0:1.0: 6 ports detected
Jul 27 13:38:41 vmldb kernel: [    2.326518] [drm] Initialized drm 1.1.0 20060810
Jul 27 13:38:41 vmldb kernel: [    2.336414] uhci_hcd: USB Universal Host Controller Interface driver
Jul 27 13:38:41 vmldb kernel: [    2.336479] uhci_hcd 0000:00:04.0: found PCI INT A -> IRQ 11
Jul 27 13:38:41 vmldb kernel: [    2.337738] uhci_hcd 0000:00:04.0: UHCI Host Controller
Jul 27 13:38:41 vmldb kernel: [    2.337743] uhci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2
Jul 27 13:38:41 vmldb kernel: [    2.337810] uhci_hcd 0000:00:04.0: irq 11, io base 0x0000c060
Jul 27 13:38:41 vmldb kernel: [    2.338004] hub 2-0:1.0: USB hub found
Jul 27 13:38:41 vmldb kernel: [    2.338007] hub 2-0:1.0: 2 ports detected
Jul 27 13:38:41 vmldb kernel: [    2.338100] uhci_hcd 0000:00:04.1: found PCI INT B -> IRQ 10
Jul 27 13:38:41 vmldb kernel: [    2.338169] uhci_hcd 0000:00:04.1: sharing IRQ 10 with 0000:00:05.0
Jul 27 13:38:41 vmldb kernel: [    2.339345] uhci_hcd 0000:00:04.1: UHCI Host Controller
Jul 27 13:38:41 vmldb kernel: [    2.339357] uhci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 3
Jul 27 13:38:41 vmldb kernel: [    2.339410] uhci_hcd 0000:00:04.1: irq 10, io base 0x0000c080
Jul 27 13:38:41 vmldb kernel: [    2.339562] hub 3-0:1.0: USB hub found
Jul 27 13:38:41 vmldb kernel: [    2.339564] hub 3-0:1.0: 2 ports detected
Jul 27 13:38:41 vmldb kernel: [    2.339653] uhci_hcd 0000:00:04.2: found PCI INT C -> IRQ 10
Jul 27 13:38:41 vmldb kernel: [    2.339935] uhci_hcd 0000:00:04.2: sharing IRQ 10 with 0000:00:06.0
Jul 27 13:38:41 vmldb kernel: [    2.341234] uhci_hcd 0000:00:04.2: UHCI Host Controller
Jul 27 13:38:41 vmldb kernel: [    2.341238] uhci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 4
Jul 27 13:38:41 vmldb kernel: [    2.341292] uhci_hcd 0000:00:04.2: irq 10, io base 0x0000c0a0
Jul 27 13:38:41 vmldb kernel: [    2.341397] hub 4-0:1.0: USB hub found
Jul 27 13:38:41 vmldb kernel: [    2.341400] hub 4-0:1.0: 2 ports detected
Jul 27 13:38:41 vmldb kernel: [    2.363674] microcode: CPU1 sig=0x206c1, pf=0x1, revision=0x1
Jul 27 13:38:41 vmldb kernel: [    2.364237] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 27 13:38:41 vmldb kernel: [    2.371601] [TTM] Zone  kernel: Available graphics memory: 2029538 kiB
Jul 27 13:38:41 vmldb kernel: [    2.371603] [TTM] Initializing pool allocator
Jul 27 13:38:41 vmldb klogd: klogd startup succeeded
Jul 27 13:38:41 vmldb kernel: [    2.371607] [TTM] Initializing DMA pool allocator
Jul 27 13:38:41 vmldb kernel: [    2.371821] [drm] fb mappable at 0x0
Jul 27 13:38:41 vmldb kernel: [    2.371823] [drm] vram aper at 0x0
Jul 27 13:38:41 vmldb kernel: [    2.371823] [drm] size 0
Jul 27 13:38:41 vmldb kernel: [    2.371824] [drm] fb depth is 24
Jul 27 13:38:41 vmldb kernel: [    2.371825] [drm]    pitch is 3072
Jul 27 13:38:41 vmldb kernel: [    2.371927] fbcon: cirrusdrmfb (fb0) is primary device
Jul 27 13:38:41 vmldb kernel: [    2.385964] Console: switching to colour frame buffer device 128x48
Jul 27 13:38:41 vmldb kernel: [    2.396249] cirrus 0000:00:02.0: fb0: cirrusdrmfb frame buffer device
Jul 27 13:38:41 vmldb kernel: [    2.396251] cirrus 0000:00:02.0: registered panic notifier
Jul 27 13:38:41 vmldb kernel: [    2.396254] [drm] Initialized cirrus 1.0.0 20110418 for 0000:00:02.0 on minor 0
Jul 27 13:38:41 vmldb kernel: [    2.573650] EXT4-fs (vda1): re-mounted. Opts: (null)
Jul 27 13:38:41 vmldb kernel: [    2.624051] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 27 13:38:41 vmldb kernel: [    2.808511] hidraw: raw HID events driver (C) Jiri Kosina
Jul 27 13:38:41 vmldb kernel: [    2.821720] usbcore: registered new interface driver usbhid
Jul 27 13:38:41 vmldb kernel: [    2.821722] usbhid: USB HID core driver
Jul 27 13:38:41 vmldb kernel: [    2.836095] input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:04.7/usb1/1-1/1-1:1.0/input/input2
Jul 27 13:38:41 vmldb kernel: [    2.837045] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Pointer [QEMU QEMU USB Tablet] on usb-

0000:00:04.7-1/input0
Jul 27 13:38:41 vmldb kernel: [    3.081616] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
Jul 27 13:38:41 vmldb kernel: [    4.128930] device-mapper: multipath: version 1.6.0 loaded
Jul 27 13:38:41 vmldb kernel: [    4.227624] EXT4-fs (vda2): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 13:38:41 vmldb kernel: [    6.772288] NET: Registered protocol family 17
Jul 27 13:38:41 vmldb kernel: [    8.042879] NET: Registered protocol family 10
Jul 27 13:38:41 vmldb kernel: [    8.181574] RPC: Registered named UNIX socket transport module.
Jul 27 13:38:41 vmldb kernel: [    8.181576] RPC: Registered udp transport module.
Jul 27 13:38:41 vmldb kernel: [    8.181577] RPC: Registered tcp transport module.
Jul 27 13:38:41 vmldb kernel: [    8.181578] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jul 27 13:38:41 vmldb rc: Starting fbsetfont: succeeded
Jul 27 13:38:41 vmldb keytable: Loading keymap: ruwin_ct_sh-UTF-8
Jul 27 13:38:41 vmldb loadkeys: Loading /lib/kbd/keymaps/i386/qwerty/ruwin_ct_sh-UTF-8.map.gz
Jul 27 13:38:41 vmldb setsyskeytable: Loading keymap: ruwin_ct_sh-UTF-8 succeeded
Jul 27 13:38:41 vmldb keytable: ^[[73G
Jul 27 13:38:41 vmldb keytable: [
Jul 27 13:38:41 vmldb keytable: ^[[1m^[[32m
Jul 27 13:38:41 vmldb keytable: DONE
Jul 27 13:38:41 vmldb keytable: ^[[39;49m^[[0;10m
Jul 27 13:38:41 vmldb keytable: Loading compose keys: compose.latin
Jul 27 13:38:41 vmldb loadkeys: Loading /lib/kbd/keymaps/include/compose.latin
Jul 27 13:38:41 vmldb setsyskeytable: Loading compose keys: compose.latin succeeded
Jul 27 13:38:41 vmldb keytable: ^[[73G
Jul 27 13:38:41 vmldb keytable: [
Jul 27 13:38:41 vmldb keytable: ^[[1m^[[32m
Jul 27 13:38:41 vmldb keytable: DONE
Jul 27 13:38:41 vmldb keytable: ^[[39;49m^[[0;10m
Jul 27 13:38:41 vmldb keytable: Binding extra Win keys, loading: windowkeys-compose.inc
Jul 27 13:38:41 vmldb loadkeys: Loading /lib/kbd/keymaps/i386/include/windowkeys-compose.inc.gz
Jul 27 13:38:41 vmldb setsyskeytable: Binding extra Win keys, loading: windowkeys-compose.inc succeeded
Jul 27 13:38:41 vmldb keytable: ^[[73G
Jul 27 13:38:41 vmldb keytable: [
Jul 27 13:38:41 vmldb keytable: ^[[1m^[[32m
Jul 27 13:38:41 vmldb keytable: DONE
Jul 27 13:38:41 vmldb keytable: ^[[39;49m^[[0;10m
Jul 27 13:38:41 vmldb keytable: The BackSpace key sends: ^? loading delete.inc
Jul 27 13:38:41 vmldb loadkeys: Loading /lib/kbd/keymaps/i386/include/delete.inc.gz
Jul 27 13:38:41 vmldb setsyskeytable: The BackSpace key sends: ^? loading delete.inc succeeded
Jul 27 13:38:41 vmldb keytable: ^[[73G
Jul 27 13:38:41 vmldb keytable: [
Jul 27 13:38:41 vmldb keytable: ^[[1m^[[32m
Jul 27 13:38:41 vmldb keytable: DONE
Jul 27 13:38:41 vmldb keytable: ^[[39;49m^[[0;10m
Jul 27 13:38:41 vmldb rc: Starting keytable: succeeded
Jul 27 13:38:41 vmldb gpm[2137]: Started gpm successfully. Entered daemon mode.
Jul 27 13:38:41 vmldb gpm: gpm startup succeeded
Jul 27 13:38:42 vmldb crond[2194]: (CRON) STARTUP (V5.0)
Jul 27 13:38:42 vmldb crond: crond startup succeeded
Jul 27 13:38:42 vmldb crond[2246]: (root) CMD (ntpdate ntp0.zenon.net)
Jul 27 13:38:42 vmldb smartd[2212]: smartd 6.2 2013-07-26 r3841 [x86_64-linux-3.10.32-std-def-alt1] (ALT Linux 6.2-alt0.M70P.1)
Jul 27 13:38:42 vmldb smartd[2212]: Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
Jul 27 13:38:42 vmldb smartd[2212]: Opened configuration file /etc/smartd.conf
Jul 27 13:38:42 vmldb smartd[2212]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Jul 27 13:38:42 vmldb smartd[2212]: Problem creating device name scan list
Jul 27 13:38:42 vmldb smartd[2212]: In the system's table of devices NO devices found to scan
Jul 27 13:38:42 vmldb smartd[2212]: Unable to monitor any SMART enabled devices. Try debug (-d) option. Exiting...
Jul 27 13:38:42 vmldb smartd: smartd startup failed
Jul 27 13:38:42 vmldb anacron[2299]: Anacron 2.3 started on `2016-07-27 13:38:42'
Jul 27 13:38:42 vmldb anacron: anacron startup succeeded
Jul 27 13:38:42 vmldb anacron[2299]: Normal exit (0 jobs run)
Jul 27 13:38:42 vmldb sshd[2350]: Server listening on 0.0.0.0 port 22.
Jul 27 13:38:42 vmldb sshd[2350]: Server listening on :: port 22.
Jul 27 13:38:42 vmldb sshd: sshd startup succeeded
Jul 27 13:38:42 vmldb postfix: Adjusting environment for postfix: succeeded
Jul 27 13:38:42 vmldb postfix: postfix check succeeded
Jul 27 13:38:42 vmldb postfix: Starting postfix: succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Mounting proc filesystem: succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Mounting sys filesystem: succeeded
Jul 27 13:38:44 vmldb load_modules: Loading module tun: succeeded
Jul 27 13:38:44 vmldb udevd: systemd-udevd startup succeeded
Jul 27 13:38:44 vmldb udevd: Populating /dev: succeeded
Jul 27 13:38:44 vmldb clock: Setting system clock (localtime): succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Activating swap partitions: succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Setting hostname vmldb.apika: succeeded
Jul 27 13:38:44 vmldb fsck: /dev/vda1: clean, 34922/640848 files, 1305737/2559744 blocks
Jul 27 13:38:44 vmldb rc.sysinit: Checking root filesystem succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Remounting root filesystem in read/write mode: succeeded
Jul 27 13:38:44 vmldb clock: Today's date: Wed Jul 27 13:38:37 NOVT 2016 succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Finding module dependencies: succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Configuring kernel parameters: succeeded
Jul 27 13:38:44 vmldb vgchange:   No volume groups found
Jul 27 13:38:44 vmldb lvm_start: Setting up LVM2: succeeded
Jul 27 13:38:44 vmldb fsck: /dev/vda2: Superblock last write time is in the future.
Jul 27 13:38:44 vmldb fsck: ^I(by less than a day, probably due to the hardware clock being incorrectly set).  FIXED.
Jul 27 13:38:44 vmldb fsck: /dev/vda2: clean, 25020/1982464 files, 6659943/7924224 blocks
Jul 27 13:38:44 vmldb rc.sysinit: Checking filesystems succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Mounting local filesystems: succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Checking loopback filesystems: succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Mounting loopback filesystems: succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Turning on user and group quotas for local filesystems: succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Cleaning up temporary files from previous boot: succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Activating swap space: succeeded
Jul 27 13:38:44 vmldb rc.sysinit: Updating chrooted environments: succeeded
Jul 27 13:38:44 vmldb init: Entering runlevel: 3
Jul 27 13:38:44 vmldb sysstat: Resetting the system activity logs: succeeded
Jul 27 13:38:44 vmldb lvm2-lvmetad: lvmetad startup succeeded
Jul 27 13:38:44 vmldb rc: Starting bridge: succeeded
Jul 27 13:38:44 vmldb acpid: starting up with netlink and the input layer
Jul 27 13:38:44 vmldb acpid: RTNETLINK1 answers: No such file or directory
Jul 27 13:38:44 vmldb acpid: acpid: error talking to the kernel via netlink
Jul 27 13:38:44 vmldb acpid: acpid startup succeeded
Jul 27 13:38:44 vmldb acpid: 0 rules loaded
Jul 27 13:38:44 vmldb messagebus: dbus-daemon startup succeeded
Jul 27 13:38:44 vmldb network: Computing interface groups:
Jul 27 13:38:44 vmldb network: .
Jul 27 13:38:44 vmldb network: .
Jul 27 13:38:44 vmldb network:  2 interfaces found
Jul 27 13:38:44 vmldb network: Starting group 0/virtual (1 interfaces)
Jul 27 13:38:44 vmldb network: ^IStarting lo:
Jul 27 13:38:44 vmldb network: .
Jul 27 13:38:44 vmldb last message repeated 3 times
Jul 27 13:38:44 vmldb network: OK
Jul 27 13:38:44 vmldb network: Starting group 1/realphys (1 interfaces)
Jul 27 13:38:44 vmldb network: ^IStarting eth0:
Jul 27 13:38:44 vmldb network: .
Jul 27 13:38:44 vmldb last message repeated 2 times
Jul 27 13:38:44 vmldb network: dhcpcd[1476]: version 5.6.8 starting
Jul 27 13:38:44 vmldb dhcpcd[1476]: version 5.6.8 starting
Jul 27 13:38:44 vmldb dhcpcd[1476]: eth0: broadcasting for a lease
Jul 27 13:38:44 vmldb network: dhcpcd[1476]: eth0: broadcasting for a lease
Jul 27 13:38:44 vmldb dhcpcd[1476]: eth0: offered 192.168.1.89 from 192.168.1.11
Jul 27 13:38:44 vmldb network: dhcpcd[1476]: eth0: offered 192.168.1.89 from 192.168.1.11
Jul 27 13:38:44 vmldb dhcpcd[1476]: eth0: acknowledged 192.168.1.89 from 192.168.1.11
Jul 27 13:38:44 vmldb network: dhcpcd[1476]: eth0: acknowledged 192.168.1.89 from 192.168.1.11
Jul 27 13:38:44 vmldb dhcpcd[1476]: eth0: leased 192.168.1.89 for 14600 seconds
Jul 27 13:38:44 vmldb network: dhcpcd[1476]: eth0: leased 192.168.1.89 for 14600 seconds
Jul 27 13:38:44 vmldb dhcpcd[1476]: forked to background, child pid 1663
Jul 27 13:38:44 vmldb network: dhcpcd[1476]: forked to background, child pid 1663
Jul 27 13:38:44 vmldb network: .
Jul 27 13:38:44 vmldb network: .
Jul 27 13:38:44 vmldb network: OK
Jul 27 13:38:44 vmldb network: Processing /etc/net/vlantab: empty.
Jul 27 13:38:44 vmldb rc: Starting network: succeeded
Jul 27 13:38:44 vmldb rpcbind: rpcbind startup succeeded
Jul 27 13:38:44 vmldb rpc.statd[1780]: Version 1.2.7 starting
Jul 27 13:38:44 vmldb sm-notify[1781]: Version 1.2.7 starting
Jul 27 13:38:44 vmldb nfslock: rpc.statd startup succeeded
Jul 27 13:38:44 vmldb dd: 1+0 records in
Jul 27 13:38:44 vmldb dd: 1+0 records out
Jul 27 13:38:44 vmldb dd: 512 bytes (512 B) copied, 0.00011609 s, 4.4 MB/s
Jul 27 13:38:44 vmldb random: Initializing random number generator: succeeded
Jul 27 13:38:44 vmldb idmapd: rpc.idmapd startup succeeded
Jul 27 13:38:44 vmldb postgresql:  succeeded
Jul 27 13:38:45 vmldb smb: smbd startup succeeded
Jul 27 13:38:45 vmldb alteratord: alteratord startup succeeded
Jul 27 13:38:45 vmldb plymouth: Deactivating splash failed
Jul 27 13:38:45 vmldb smbd[2747]: [2016/07/27 13:38:45.381801,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Jul 27 13:38:45 vmldb smbd[2747]:   STATUS=daemon 'smbd' finished starting up and ready to serve connections
Jul 27 19:39:55 vmldb sshd[2923]: Accepted publickey for ROOT USER root from 192.168.1.11 port 39799 ssh2: RSA

9c:db:89:0f:94:27:3d:d2:e4:a1:35:46:cb:78:d9:ad
Jul 27 19:40:01 vmldb crond[3022]: (root) CMD (/usr/lib64/sa/sa1 -S DISK 1 1)
Jul 27 19:40:51 vmldb sshd[3086]: Accepted publickey for ROOT USER root from 192.168.1.11 port 39800 ssh2: RSA

9c:db:89:0f:94:27:3d:d2:e4:a1:35:46:cb:78:d9:ad
Jul 27 19:48:27 vmldb apt-get: tzdata-2016f-alt1 installed
Jul 27 20:48:27 vmldb apt-get: tzdata-2016d-alt1 removed
Jul 27 20:48:28 vmldb apt-get: pciids-20160723-alt1 installed
Jul 27 20:48:28 vmldb apt-get: pciids-20160716-alt1 removed

Оффлайн PSV

  • Давно тут
  • **
  • Сообщений: 361
написало, что сообщение сильно длинное, вот концовка лога
Jul 27 20:49:17 vmldb shutdown[3412]: shutting down for system halt
Jul 27 20:49:17 vmldb init: Switching to runlevel: 0
Jul 27 20:49:17 vmldb sshd[3086]: Received disconnect from 192.168.1.11: 11: disconnected by user
Jul 27 20:49:19 vmldb alteratord: alteratord shutdown succeeded
Jul 27 20:49:19 vmldb plymouth: Activating splash succeeded
Jul 27 20:49:19 vmldb postgresql: Stopping postgresql service:
Jul 27 20:49:20 vmldb postgresql: ^[[73G
Jul 27 20:49:20 vmldb postgresql: [
Jul 27 20:49:20 vmldb postgresql: ^[[1m^[[32m
Jul 27 20:49:20 vmldb postgresql: DONE
Jul 27 20:49:20 vmldb postgresql: ^[[39;49m^[[0;10m
Jul 27 20:49:20 vmldb rc: Stopping postgresql: succeeded
Jul 27 20:49:20 vmldb sshd[2350]: Received signal 15; terminating.
Jul 27 20:49:20 vmldb sshd: sshd shutdown succeeded
Jul 27 20:49:20 vmldb postfix: Shutting down postfix: succeeded
Jul 27 20:49:20 vmldb smb: smbd shutdown succeeded
Jul 27 20:49:20 vmldb crond: crond shutdown succeeded
Jul 27 20:49:20 vmldb gpm: gpm shutdown succeeded
Jul 27 20:49:20 vmldb acpid: exiting
Jul 27 20:49:20 vmldb acpid: acpid shutdown succeeded
Jul 27 20:49:20 vmldb rc: Stopping keytable: succeeded
Jul 27 20:49:20 vmldb rc: Stopping fbsetfont: succeeded
Jul 27 20:49:20 vmldb idmapd: rpc.idmapd shutdown succeeded
Jul 27 20:49:20 vmldb blkdeactivate: Deactivating block devices:
Jul 27 20:49:20 vmldb blkdeactivate: /sbin/blkdeactivate: line 241: /bin/lsblk: No such file or directory
Jul 27 20:49:20 vmldb blk-availability: Stopping block device availability: succeeded
Jul 27 20:49:21 vmldb dd: 1+0 records in
Jul 27 20:49:21 vmldb dd: 1+0 records out
Jul 27 20:49:21 vmldb dd: 512 bytes (512 B) copied
Jul 27 20:49:21 vmldb dd: , 0.000109474 s, 4.7 MB/s
Jul 27 20:49:21 vmldb random: Saving random seed: succeeded
Jul 27 20:49:21 vmldb nfslock: rpc.statd shutdown succeeded
Jul 27 20:49:21 vmldb rpcbind: rpcbind shutdown succeeded
Jul 27 20:49:21 vmldb network: Computing interface groups:
Jul 27 20:49:21 vmldb network: .
Jul 27 20:49:21 vmldb network: .
Jul 27 20:49:21 vmldb network:  2 interfaces found
Jul 27 20:49:21 vmldb network: Processing /etc/net/vlantab: empty.
Jul 27 20:49:21 vmldb network: Stopping group 1/realphys (1 interfaces)
Jul 27 20:49:21 vmldb network: ^IStopping eth0:
Jul 27 20:49:21 vmldb dhcpcd[3898]: sending signal 1 to pid 1663
Jul 27 20:49:21 vmldb dhcpcd[3898]: waiting for pid 1663 to exit
Jul 27 20:49:21 vmldb dhcpcd[1663]: received SIGHUP, releasing
Jul 27 20:49:21 vmldb dhcpcd[1663]: eth0: releasing lease of 192.168.1.89
Jul 27 20:49:21 vmldb dhcpcd[1663]: eth0: removing interface
Jul 27 20:49:21 vmldb network: .
Jul 27 20:49:21 vmldb last message repeated 2 times
Jul 27 20:49:21 vmldb network: OK
Jul 27 20:49:21 vmldb network: Stopping group 0/virtual (1 interfaces)
Jul 27 20:49:21 vmldb network: ^IStopping lo:
Jul 27 20:49:21 vmldb network: .
Jul 27 20:49:21 vmldb network: .OK
Jul 27 20:49:21 vmldb rc: Stopping network: succeeded
Jul 27 20:49:21 vmldb messagebus: dbus-daemon shutdown succeeded
Jul 27 20:49:21 vmldb udevd: systemd-udevd shutdown succeeded
Jul 27 20:49:21 vmldb kernel: Kernel logging (proc) stopped.
Jul 27 20:49:21 vmldb kernel: Kernel log daemon terminating.
Jul 27 20:49:22 vmldb klogd: klogd shutdown succeeded
Jul 27 20:49:22 vmldb exiting on signal 15

Инфлэйм

  • Гость
Цитировать
написало, что сообщение сильно длинное
может просто приложить файлик  команды от пользователя cat /var/log/messages>log.txt

Оффлайн Speccyfighter

  • Мастер
  • ***
  • Сообщений: 10 259
Дело хозяйское, но я бы гуглил багтрекеры usnet на предмет:
acpi exception ae_bad_parameter thread could not acquire mutex
и
acpid: error talking to the kernel via netlink

Оффлайн PSV

  • Давно тут
  • **
  • Сообщений: 361
Цитировать
написало, что сообщение сильно длинное
может просто приложить файлик  команды от пользователя cat /var/log/messages>log.txt
Выложил
Дело хозяйское, но я бы гуглил багтрекеры usnet на предмет:
acpi exception ae_bad_parameter thread could not acquire mutex
и
acpid: error talking to the kernel via netlink
Погуглил. Основные сообщения в гугле: что биос не дружит с ACPI. Что не так, так как другие ВМ гасятся на отлично.

Оффлайн ruslandh

  • Поспешай не торопясь !
  • Модератор глобальный
  • *****
  • Сообщений: 32 258
  • Учиться .... Телепатами не рождаются, ими ....
    • Email
другие ВМ гасятся на отлично
Так, может в этом acpi выключен (не установлен и т.п.)

Оффлайн ruslandh

  • Поспешай не торопясь !
  • Модератор глобальный
  • *****
  • Сообщений: 32 258
  • Учиться .... Телепатами не рождаются, ими ....
    • Email
Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No such file or directory
А это почему? Куда подевался /var/run/cups/cups.sock:631 ?

Оффлайн ruslandh

  • Поспешай не торопясь !
  • Модератор глобальный
  • *****
  • Сообщений: 32 258
  • Учиться .... Телепатами не рождаются, ими ....
    • Email
Вы-бы хоть время перезагрузки показали - это ?
Цитировать
Jul 27 19:37:45 vmldb udevd: systemd-udevd shutdown succeeded
Jul 27 19:37:45 vmldb kernel: Kernel logging (proc) stopped.
Jul 27 19:37:46 vmldb kernel: Kernel log daemon terminating.
Jul 27 19:37:47 vmldb klogd: klogd shutdown succeeded
Jul 27 19:37:47 vmldb exiting on signal 15
Jul 27 13:38:41 vmldb syslogd 1.4.1: restart.
Jul 27 13:38:41 vmldb syslogd: syslogd startup succeeded
Jul 27 13:38:41 vmldb kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jul 27 13:38:41 vmldb kernel: [    1.746581] tun: Universal TUN/TAP device driver, 1.6

Оффлайн ruslandh

  • Поспешай не торопясь !
  • Модератор глобальный
  • *****
  • Сообщений: 32 258
  • Учиться .... Телепатами не рождаются, ими ....
    • Email
Jul 27 13:38:44 vmldb acpid: starting up with netlink and the input layer
Jul 27 13:38:44 vmldb acpid: RTNETLINK1 answers: No such file or directory
Jul 27 13:38:44 vmldb acpid: acpid: error talking to the kernel via netlink
Jul 27 13:38:44 vmldb acpid: acpid startup succeeded
ACPI?

Оффлайн PSV

  • Давно тут
  • **
  • Сообщений: 361
Добрый день!
Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No such file or directory
А это почему? Куда подевался /var/run/cups/cups.sock:631 ?
Установка была из коробки, ничего связанного с принтерами не убирал и не добавлял и не трогал.

Вы-бы хоть время перезагрузки показали - это ?
Цитировать
Jul 27 19:37:45 vmldb udevd: systemd-udevd shutdown succeeded
Jul 27 19:37:45 vmldb kernel: Kernel logging (proc) stopped.
Jul 27 19:37:46 vmldb kernel: Kernel log daemon terminating.
Jul 27 19:37:47 vmldb klogd: klogd shutdown succeeded
Jul 27 19:37:47 vmldb exiting on signal 15
Jul 27 13:38:41 vmldb syslogd 1.4.1: restart.
Jul 27 13:38:41 vmldb syslogd: syslogd startup succeeded
Jul 27 13:38:41 vmldb kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jul 27 13:38:41 vmldb kernel: [    1.746581] tun: Universal TUN/TAP device driver, 1.6
Там несколько гашений.
Jul 27 19:37:13 vmldb to_forum: before_shutdown - тут я специально гасил, что бы запостить сюда лог

Jul 27 13:38:44 vmldb acpid: starting up with netlink and the input layer
Jul 27 13:38:44 vmldb acpid: RTNETLINK1 answers: No such file or directory
Jul 27 13:38:44 vmldb acpid: acpid: error talking to the kernel via netlink
Jul 27 13:38:44 vmldb acpid: acpid startup succeeded
ACPI?
Повторяюсь: установка из дистриба с сервера альтов. Единственное, возможно установка была с 7.0.2 или подобное, а потом apt-get dist-upgrade. Если в этот момент что-то сломалось, то мог и не заметить сразу. Серваки очень редко гашу.

Оффлайн ruslandh

  • Поспешай не торопясь !
  • Модератор глобальный
  • *****
  • Сообщений: 32 258
  • Учиться .... Телепатами не рождаются, ими ....
    • Email
Установка была из коробки, ничего связанного с принтерами не убирал и не добавлял и не трогал.
Ну, никто не мешает проверить. Или вы хотите отладить работу именно из-коробки?

Оффлайн ruslandh

  • Поспешай не торопясь !
  • Модератор глобальный
  • *****
  • Сообщений: 32 258
  • Учиться .... Телепатами не рождаются, ими ....
    • Email