LINUX.ORG.RU

Долго выключается система

 , ,


0

1

Debian Jessie, на SSD и HDD по физическому тому шифрования, на них - по физическому тому LVM и группа томов, корень - на ssd, хомяк - на hdd.

Система долго выключается, вот лог выключения: http://pastebin.com/rUbLHCp3

Вызывают сомнения вот эти строки (сужу по разнице во времени):

июл 19 18:25:55 debian pulseaudio[1735]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-Ko4zjgJp5e: В соединении отказано
июл 19 18:26:16 debian networking[1751]: Deconfiguring network interfaces...done.

Как вылечить эту проблему? Заранее спасибо.

★★

suspend to ram

problem solved

anonymous ()
Ответ на: комментарий от anonymous

Доктор, у меня онемели обе руки! - Пользуйтесь ногами.

Valdor ★★ ()
Ответ на: комментарий от Deathstalker
июл 19 18:25:52 debian systemd-logind[615]: System is rebooting.
июл 19 18:25:52 debian sshd[611]: Received signal 15; terminating.
июл 19 18:25:52 debian lightdm[706]: Failed to get D-Bus connection
июл 19 18:25:52 debian systemd-logind[615]: Failed to abandon session scope: Transport endpoint is not connected
июл 19 18:25:52 debian systemd[908]: Stopping Sockets.
июл 19 18:25:52 debian systemd[908]: Stopped target Sockets.
июл 19 18:25:52 debian systemd[908]: Starting Shutdown.
июл 19 18:25:52 debian systemd[908]: Reached target Shutdown.
июл 19 18:25:52 debian systemd[908]: Starting Exit the Session...
июл 19 18:25:52 debian systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
июл 19 18:25:52 debian gpm[1695]: Stopping mouse interface server: gpm.
июл 19 18:25:52 debian systemd[908]: Received SIGRTMIN+24 from PID 1704 (kill).
июл 19 18:25:52 debian systemd[936]: Received SIGRTMIN+24 from PID 1702 (kill).
июл 19 18:25:52 debian systemd[909]: pam_unix(systemd-user:session): session closed for user lightdm
июл 19 18:25:52 debian systemd[938]: pam_unix(systemd-user:session): session closed for user sergey
июл 19 18:25:52 debian exim4[1697]: Stopping MTA: exim4_listener.
июл 19 18:25:53 debian pulseaudio[1732]: [pulseaudio] client-conf-x11.c: Вызов xcb_connection_has_error() вернул «true».
июл 19 18:25:53 debian pulseaudio[1735]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, th
июл 19 18:25:53 debian pulseaudio[1735]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, th
июл 19 18:25:53 debian pulseaudio[1735]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, th
июл 19 18:25:53 debian pulseaudio[1735]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, th
июл 19 18:25:53 debian pulseaudio[1735]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, th
июл 19 18:25:53 debian pulseaudio[1735]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, th
июл 19 18:25:53 debian pulseaudio[1735]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, th
июл 19 18:25:53 debian pulseaudio[1735]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, th
июл 19 18:25:53 debian pulseaudio[1735]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, th
июл 19 18:25:53 debian pulseaudio[1735]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, th
июл 19 18:25:53 debian pulseaudio[1735]: [pulseaudio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, th
июл 19 18:25:53 debian systemd[1]: Unit lightdm.service entered failed state.
июл 19 18:25:53 debian hwclock[1691]: hwclock from util-linux 2.25.2
июл 19 18:25:53 debian hwclock[1691]: Using the /dev interface to the clock.
июл 19 18:25:53 debian hwclock[1691]: Last drift adjustment done at 1437319430 seconds after 1969
июл 19 18:25:53 debian hwclock[1691]: Last calibration done at 1437319430 seconds after 1969
июл 19 18:25:53 debian hwclock[1691]: Hardware clock is on UTC time
июл 19 18:25:53 debian hwclock[1691]: Assuming hardware clock is kept in UTC time.
июл 19 18:25:53 debian hwclock[1691]: Waiting for clock tick...
июл 19 18:25:53 debian hwclock[1691]: ...got clock tick
июл 19 18:25:53 debian hwclock[1691]: Time read from Hardware Clock: 2015/07/19 15:25:53
июл 19 18:25:53 debian hwclock[1691]: Hw clock time : 2015/07/19 15:25:53 = 1437319553 seconds since 1969
июл 19 18:25:53 debian hwclock[1691]: 1437319553.500000 is close enough to 1437319553.500000 (0.000000 < 0.001000)
июл 19 18:25:53 debian hwclock[1691]: Set RTC to 1437319553 (1437319553 + 0; refsystime = 1437319553.000000)
июл 19 18:25:53 debian hwclock[1691]: Setting Hardware Clock to 15:25:53 = 1437319553 seconds since 1969
июл 19 18:25:53 debian hwclock[1691]: ioctl(RTC_SET_TIME) was successful.
июл 19 18:25:53 debian hwclock[1691]: Not adjusting drift factor because it has been less than a day since the last calibration.
июл 19 18:25:53 debian tor[1696]: Stopping tor daemon...done.
июл 19 18:25:55 debian pulseaudio[1735]: [alsa-sink-USB Audio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a 
июл 19 18:25:55 debian pulseaudio[1735]: [alsa-sink-USB Audio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a 
июл 19 18:25:55 debian pulseaudio[1735]: [alsa-sink-USB Audio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a 
июл 19 18:25:55 debian pulseaudio[1735]: [alsa-sink-USB Audio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a 
июл 19 18:25:55 debian pulseaudio[1735]: [alsa-sink-USB Audio] core-util.c: Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a 
июл 19 18:25:55 debian pulseaudio[1735]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-Ko4zjgJp5e: В соединении о
июл 19 18:25:55 debian pulseaudio[1735]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-Ko4zjgJp5e: В соединении отказано
июл 19 18:26:16 debian networking[1751]: Deconfiguring network interfaces...done.
июл 19 18:26:16 debian kernel: e1000e: eth0 NIC Link is Down
июл 19 18:26:16 debian lvm[1785]: 2 logical volume(s) in volume group "crypt-vg" unmonitored
июл 19 18:26:21 debian systemd-cryptsetup[1748]: Failed to deactivate: Device or resource busy
июл 19 18:26:21 debian systemd[1]: systemd-cryptsetup@sda3_crypt.service: control process exited, code=exited status=1
июл 19 18:26:21 debian systemd[1]: Unit systemd-cryptsetup@sda3_crypt.service entered failed state.
июл 19 18:26:21 debian systemd-cryptsetup[1747]: Failed to deactivate: Device or resource busy
июл 19 18:26:21 debian systemd[1]: systemd-cryptsetup@sdb1_crypt.service: control process exited, code=exited status=1
июл 19 18:26:21 debian systemd[1]: Unit systemd-cryptsetup@sdb1_crypt.service entered failed state.
июл 19 18:26:21 debian systemd[1]: Shutting down.
июл 19 18:26:21 debian systemd-journal[324]: Journal stopped



там у него вообще борода

smilessss ★★★★★ ()
Ответ на: комментарий от smilessss

Я немного разобрался, в чём вопрос. systemd-cryptsetup пытается закрыть тома, прописанные в crypttab и ВНЕЗАПНО обламывается, ибо там lvm с /. Нашёл решение (http://www.freedesktop.org/software/systemd/man/systemd-cryptsetup-generator....): ядерный параметр luks.crypttab=no, но буду искать нечто более изящное, потому что так не читается вообще весь crypttab (сейчас у меня там кроме двух томов lvm ничего нет, так что, не страшно).

Valdor ★★ ()
Ответ на: комментарий от Valdor

Столкнулся с похожей проблемой. Удалось решить. Есть рецепт.

pvvking ★★ ()
Ответ на: комментарий от pvvking

Отвечу себе сам.
Вроде как помогло убрать из fstab и crypttab все что идет на /dev/... заменил на UUID=0dx47371-8x3b-4ab1-8e6d-3ba6ff58c30f так сказать на UUID и все встало на свои места норм выключение и перезагрузка.

pvvking ★★ ()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.