Считаете, что Ubuntu недостаточно дружелюбна к новичкам? Помогите создать новое Руководство для новичков!
0 Пользователей и 1 Гость просматривают эту тему.
Я думаю, товарищ имел в виду tail -f /var/log/syslog
Можно смешной вопрос? Галочку "Автоматическое подключение" на соединении не снимали?Попробуйте передёрнуть (снять галку, сохранить, перезагрузиться, поставить галку, сохранить, перехагрудиться)
Sep 17 11:15:44 pc NetworkManager: <info> DHCP: device eth0 state changed normal exit -> preinitSep 17 11:15:44 pc dhclient: Listening on LPF/eth0/00:22:b0:03:ab:ceSep 17 11:15:44 pc dhclient: Sending on LPF/eth0/00:22:b0:03:ab:ceSep 17 11:15:44 pc dhclient: Sending on Socket/fallbackSep 17 11:15:48 pc dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8Sep 17 11:15:56 pc dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13Sep 17 11:16:09 pc dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21Sep 17 11:16:09 pc gnome-session[2509]: WARNING: Could not launch application 'evolution-alarm-notify.desktop': Unable to start application: Не удалось выполнить процесс-потомок «/usr/lib/evolution/2.28/evolution-alarm-notify» (Нет такого файла или каталога)Sep 17 11:16:16 pc AptDaemon: INFO: Quiting due to inactivitySep 17 11:16:16 pc AptDaemon: INFO: Shutdown was requestedSep 17 11:16:30 pc NetworkManager: <info> (eth0): DHCP transaction took too long, stopping it.Sep 17 11:16:30 pc NetworkManager: <info> (eth0): canceled DHCP transaction, dhcp client pid 2699Sep 17 11:16:30 pc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Timeout) scheduled...Sep 17 11:16:30 pc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Timeout) started...Sep 17 11:16:30 pc NetworkManager: <info> (eth0): device state change: 7 -> 9 (reason 5)Sep 17 11:16:30 pc NetworkManager: <info> Marking connection 'Автоматическое (Ethernet)' invalid.Sep 17 11:16:30 pc NetworkManager: <info> Activation (eth0) failed.Sep 17 11:16:30 pc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Timeout) complete.Sep 17 11:16:30 pc NetworkManager: <info> (eth0): device state change: 9 -> 3 (reason 0)Sep 17 11:16:30 pc NetworkManager: <info> (eth0): deactivating device (reason: 0).
Sep 17 11:18:42 pc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.Sep 17 11:18:42 pc NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...Sep 17 11:18:42 pc avahi-daemon[929]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.98.14.238.Sep 17 11:18:42 pc avahi-daemon[929]: New relevant interface eth0.IPv4 for mDNS.Sep 17 11:18:42 pc avahi-daemon[929]: Registering new address record for 10.98.14.238 on eth0.IPv4.Sep 17 11:18:43 pc NetworkManager: <info> (eth0): device state change: 7 -> 8 (reason 0)Sep 17 11:18:43 pc NetworkManager: <info> Policy set 'Автоматическое (Ethernet)' (eth0) as default for routing and DNS.Sep 17 11:18:43 pc NetworkManager: <info> Activation (eth0) successful, device activated.Sep 17 11:18:43 pc NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.Sep 17 11:18:44 pc ntpdate[3110]: adjust time server 91.189.94.4 offset 0.018019 sec
tail -f /var/log/syslog > ~/log4ubuntu.forum
Sep 17 11:39:07 pc NetworkManager: <info> (eth0): device state change: 8 -> 3 (reason 38)Sep 17 11:39:07 pc NetworkManager: <info> (eth0): deactivating device (reason: 38).Sep 17 11:39:07 pc NetworkManager: <info> (eth0): canceled DHCP transaction, dhcp client pid 3064Sep 17 11:39:07 pc NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess#012Sep 17 11:39:07 pc avahi-daemon[929]: Withdrawing address record for 10.98.14.238 on eth0.Sep 17 11:39:07 pc avahi-daemon[929]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.98.14.238.Sep 17 11:39:07 pc avahi-daemon[929]: Interface eth0.IPv4 no longer relevant for mDNS.Sep 17 11:39:08 pc acpid: client 2436[0:0] has disconnectedSep 17 11:39:08 pc acpid: client 2436[0:0] has disconnectedSep 17 11:39:08 pc acpid: client connected from 3935[0:0]Sep 17 11:39:08 pc acpid: 1 client rule loadedSep 17 11:39:09 pc acpid: client connected from 3935[0:0]Sep 17 11:39:09 pc acpid: 1 client rule loadedSep 17 11:39:10 pc gdm-simple-greeter[3971]: Gtk-WARNING: /build/buildd/gtk+2.0-2.20.1/gtk/gtkwidget.c:5636: widget not within a GtkWindowSep 17 11:39:12 pc bonobo-activation-server (gritsov-3986): could not associate with desktop session: Failed to connect to socket /tmp/dbus-RlnzyEiVJN: В соединении отказаноSep 17 11:39:12 pc gdm-session-worker[3972]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failedSep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) starting connection 'Автоматическое (Ethernet)'Sep 17 11:39:18 pc NetworkManager: <info> (eth0): device state change: 3 -> 4 (reason 0)Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...Sep 17 11:39:18 pc NetworkManager: <info> (eth0): device state change: 4 -> 5 (reason 0)Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...Sep 17 11:39:18 pc NetworkManager: <info> (eth0): device state change: 5 -> 7 (reason 0)Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Beginning DHCP transaction (timeout in 45 seconds)Sep 17 11:39:18 pc NetworkManager: <info> dhclient started with pid 4095Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) scheduled...Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) started...Sep 17 11:39:18 pc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP6 Configure Get) complete.Sep 17 11:39:18 pc dhclient: Internet Systems Consortium DHCP Client V3.1.3Sep 17 11:39:18 pc dhclient: Copyright 2004-2009 Internet Systems Consortium.Sep 17 11:39:18 pc dhclient: All rights reserved.Sep 17 11:39:18 pc dhclient: For info, please visit https://www.isc.org/software/dhcp/Sep 17 11:39:18 pc dhclient: Sep 17 11:39:18 pc NetworkManager: <info> DHCP: device eth0 state changed normal exit -> preinitSep 17 11:39:18 pc dhclient: Listening on LPF/eth0/00:22:b0:03:ab:ceSep 17 11:39:18 pc dhclient: Sending on LPF/eth0/00:22:b0:03:ab:ceSep 17 11:39:18 pc dhclient: Sending on Socket/fallbackSep 17 11:39:20 pc dhclient: DHCPREQUEST of 10.98.14.238 on eth0 to 255.255.255.255 port 67Sep 17 11:39:20 pc dhclient: DHCPACK of 10.98.14.238 from 10.98.0.1Sep 17 11:39:20 pc NetworkManager: <info> DHCP: device eth0 state changed preinit -> rebootSep 17 11:39:20 pc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...Sep 17 11:39:20 pc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...Sep 17 11:39:20 pc NetworkManager: <info> address 10.98.14.238Sep 17 11:39:20 pc NetworkManager: <info> prefix 16 (255.255.0.0)Sep 17 11:39:20 pc NetworkManager: <info> gateway 10.98.0.1Sep 17 11:39:20 pc NetworkManager: <info> nameserver '77.232.128.1'Sep 17 11:39:20 pc NetworkManager: <info> nameserver '77.232.135.1'Sep 17 11:39:20 pc NetworkManager: <info> domain name 'bks-tv.ru'Sep 17 11:39:20 pc NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...Sep 17 11:39:20 pc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.Sep 17 11:39:20 pc NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...Sep 17 11:39:20 pc avahi-daemon[929]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.98.14.238.Sep 17 11:39:20 pc avahi-daemon[929]: New relevant interface eth0.IPv4 for mDNS.Sep 17 11:39:20 pc avahi-daemon[929]: Registering new address record for 10.98.14.238 on eth0.IPv4.Sep 17 11:39:20 pc dhclient: bound to 10.98.14.238 -- renewal in 33953 seconds.Sep 17 11:39:21 pc NetworkManager: <info> (eth0): device state change: 7 -> 8 (reason 0)Sep 17 11:39:21 pc NetworkManager: <info> Policy set 'Автоматическое (Ethernet)' (eth0) as default for routing and DNS.Sep 17 11:39:21 pc NetworkManager: <info> Activation (eth0) successful, device activated.Sep 17 11:39:21 pc NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.Sep 17 11:39:21 pc ntpdate[4232]: adjust time server 91.189.94.4 offset 0.024869 secSep 17 11:39:45 pc kernel: [ 1817.988201] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...Sep 17 11:39:45 pc kernel: [ 1817.988846] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:39:48 pc gnome-session[4013]: WARNING: Could not launch application 'evolution-alarm-notify.desktop': Unable to start application: Не удалось выполнить процесс-потомок «/usr/lib/evolution/2.28/evolution-alarm-notify» (Нет такого файла или каталога)Sep 17 11:39:51 pc kernel: [ 1823.989156] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...Sep 17 11:39:51 pc kernel: [ 1823.989795] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:39:55 pc kernel: [ 1827.989158] eth0: Transmit timed out, status 0003, PHY status 786d, resetting...Sep 17 11:39:55 pc kernel: [ 1827.989801] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:39:59 pc kernel: [ 1831.988772] eth0: Transmit timed out, status 0003, PHY status 786d, resetting...Sep 17 11:39:59 pc kernel: [ 1831.989421] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:40:03 pc kernel: [ 1835.989172] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...Sep 17 11:40:03 pc kernel: [ 1835.989815] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:40:07 pc kernel: [ 1839.988161] eth0: Transmit timed out, status 0003, PHY status 786d, resetting...Sep 17 11:40:07 pc kernel: [ 1839.988805] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:40:11 pc kernel: [ 1843.989157] eth0: Transmit timed out, status 0003, PHY status 786d, resetting...Sep 17 11:40:11 pc kernel: [ 1843.989804] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:40:15 pc kernel: [ 1847.989168] eth0: Transmit timed out, status 0003, PHY status 786d, resetting...Sep 17 11:40:15 pc kernel: [ 1847.989814] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:40:20 pc AptDaemon: INFO: Initializing daemonSep 17 11:40:21 pc kernel: [ 1853.989162] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...Sep 17 11:40:21 pc kernel: [ 1853.989810] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:40:53 pc kernel: [ 1885.988159] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...Sep 17 11:40:53 pc kernel: [ 1885.988801] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:41:01 pc kernel: [ 1893.988154] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...Sep 17 11:41:01 pc kernel: [ 1893.988797] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:41:07 pc kernel: [ 1899.988162] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...Sep 17 11:41:07 pc kernel: [ 1899.988808] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1Sep 17 11:41:13 pc kernel: [ 1905.988161] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...Sep 17 11:41:13 pc kernel: [ 1905.988811] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
не уверен, что всё правильно сделал.
Выкладываю логи:/var/log/syslog: (Нажмите, чтобы показать/скрыть)Длинный syslog, который можно прикрепить к сообщению отдельным файлом, за 10 минутСоответственно, каждая строка будет с указанием времени/var/log/other.log (Нажмите, чтобы показать/скрыть)Длинный other.log, который можно прикрепить к сообщению отдельным файлом, за 10 минутСоответственно, каждая строка будет с указанием времениВремя:в 00.21 я запустил tail -fв 00.22 я попинговал 8.8.8.8в 00.25 я включил видеов 00.28 я попинговал 8.8.8.8в 00.30 я выключил видеов 00.35 я попинговал 8.8.8.8в 00.36 я остановил tail -f
Страница сгенерирована за 0.019 секунд. Запросов: 21.