Linux Mint Türkiye
Linux Mint Destek => Açılış, Kapanış ve Oturum Açma => Konuyu başlatan: Elysion59 - 30 Kasım 2018, 01:16:07
-
İlk formatladığında bilgisayarım systemd-analyze da total süre olarak 14sn alıyordu. Mysql yükledikten sonra açılış hızım yavaşladı ve 26sn de açılmakta.
Tek sistem olarak kullanmaktayım işletim sistemi ssd üzerine kurulu.
Ssd =>SanDisk Ultra II 120GB 550MB-500MB/s
System Analizim ;
Startup finished in 3.847s (firmware) + 3.612s (loader) + 5.667s (kernel) + 13.327s (userspace) = 26.455s
graphical.target reached after 13.316s in userspace
Düzenleme: Konu başlığı ve kod etiketi
-
Aşağıdaki komutların çıktılarını da kod etiketi (https://forum.linuxmint.net.tr/index.php?topic=2629.0) içinde paylaşınız.
systemd-analyze --no-pager blame
journalctl --no-pager -b -p3
systemctl --no-pager --state=failed
systemd-analyze --no-pager critical-chain
-
systemd-analyze --no-pager blame
6.285s NetworkManager-wait-online.service
5.067s tomcat8.service
1.127s keyboard-setup.service
1.009s ufw.service
833ms dev-sda2.device
494ms systemd-journal-flush.service
429ms mysql.service
309ms NetworkManager.service
304ms upower.service
251ms networkd-dispatcher.service
236ms systemd-logind.service
225ms ubuntu-system-adjustments.service
223ms udisks2.service
221ms systemd-udev-trigger.service
198ms systemd-resolved.service
160ms ModemManager.service
133ms accounts-daemon.service
132ms systemd-timesyncd.service
128ms thermald.service
126ms apport.service
125ms swapfile.swap
124ms avahi-daemon.service
111ms lvm2-monitor.service
104ms wpa_supplicant.service
103ms speech-dispatcher.service
98ms bluetooth.service
95ms systemd-udevd.service
94ms systemd-journald.service
93ms gpu-manager.service
92ms lightdm.service
90ms plymouth-quit-wait.service
86ms grub-common.service
77ms systemd-fsck[member=2665]Dev[/member]-disk-by\x2duuid-7606\x2d9407.service
77ms alsa-restore.service
75ms apparmor.service
74ms user[member=3516]1[/member]000.service
67ms pppd-dns.service
65ms systemd-tmpfiles-setup-dev.service
64ms dns-clean.service
56ms user@0.service
52ms lm-sensors.service
48ms systemd-modules-load.service
43ms systemd-sysctl.service
42ms networking.service
38ms systemd-tmpfiles-setup.service
37ms packagekit.service
33ms rsyslog.service
31ms colord.service
25ms blk-availability.service
25ms plymouth-start.service
25ms sys-kernel-debug.mount
24ms systemd-tmpfiles-clean.service
23ms dev-hugepages.mount
21ms hddtemp.service
20ms systemd-remount-fs.service
18ms polkit.service
16ms plymouth-read-write.service
16ms binfmt-support.service
15ms boot-efi.mount
13ms kerneloops.service
12ms dev-mqueue.mount
12ms ureadahead-stop.service
12ms console-setup.service
11ms setvtrgb.service
11ms systemd-random-seed.service
10ms systemd-update-utmp.service
9ms proc-sys-fs-binfmt_misc.mount
9ms kmod-static-nodes.service
9ms systemd-update-utmp-runlevel.service
7ms sys-fs-fuse-connections.mount
7ms systemd-user-sessions.service
6ms systemd-backlight@backlight:intel_backlight.service
5ms openvpn.service
5ms sys-kernel-config.mount
4ms rtkit-daemon.service
4ms motd-news.service
journalctl --no-pager -b -p3
-- Logs begin at Wed 2018-11-28 22:16:01 +03, end at Fri 2018-11-30 02:19:29 +03. --
Kas 30 00:44:38 SKYLINE kernel: ipmi:dmi: Invalid offset: 0
Kas 30 00:44:38 SKYLINE kernel: Couldn't get size: 0x800000000000000e
Kas 30 00:44:38 SKYLINE kernel: radeon 0000:01:00.0: failed VCE resume (-110).
Kas 30 00:44:38 SKYLINE kernel: ACPI Error: [\_SB_.PCI0.GFX0.DD02._BCL] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
Kas 30 00:44:38 SKYLINE kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.DD02._BCL, AE_NOT_FOUND (20170831/psparse-550)
Kas 30 00:44:39 SKYLINE bluetoothd[870]: Failed to set mode: Blocked through rfkill (0x12)
Kas 30 00:44:40 SKYLINE wpa_supplicant[864]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Kas 30 00:44:40 SKYLINE wpa_supplicant[864]: dbus: Failed to construct signal
Kas 30 00:44:40 SKYLINE lightdm[1040]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Kas 30 00:44:40 SKYLINE lightdm[1040]: PAM adding faulty module: pam_kwallet.so
Kas 30 00:44:40 SKYLINE lightdm[1040]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Kas 30 00:44:40 SKYLINE lightdm[1040]: PAM adding faulty module: pam_kwallet5.so
Kas 30 00:44:41 SKYLINE lightdm[1236]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Kas 30 00:44:41 SKYLINE lightdm[1236]: PAM adding faulty module: pam_kwallet.so
Kas 30 00:44:41 SKYLINE lightdm[1236]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Kas 30 00:44:41 SKYLINE lightdm[1236]: PAM adding faulty module: pam_kwallet5.so
Kas 30 00:44:47 SKYLINE pulseaudio[1540]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
Kas 30 00:44:56 SKYLINE bluetoothd[870]: Failed to set mode: Blocked through rfkill (0x12)
Kas 30 00:46:18 SKYLINE wpa_supplicant[864]: random: Cannot read from /dev/random: Resource temporarily unavailable
Kas 30 00:46:22 SKYLINE wpa_supplicant[864]: random: Cannot read from /dev/random: Resource temporarily unavailable
Kas 30 00:57:24 SKYLINE dhclient[1057]: receive_packet failed on wlp8s0: Network is down
Kas 30 00:57:32 SKYLINE wpa_supplicant[864]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Kas 30 00:57:32 SKYLINE wpa_supplicant[864]: dbus: Failed to construct signal
Kas 30 01:05:52 SKYLINE wpa_supplicant[864]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Kas 30 01:05:52 SKYLINE wpa_supplicant[864]: dbus: Failed to construct signal
Kas 30 01:43:02 SKYLINE bluetoothd[870]: Failed to set mode: Blocked through rfkill (0x12)
Kas 30 01:43:02 SKYLINE bluetoothd[870]: Failed to set mode: Blocked through rfkill (0x12)
Kas 30 01:49:46 SKYLINE sudo[11693]: umutpamuk : a password is required ; TTY=pts/0 ; PWD=/home/umutpamuk ; USER=root ; COMMAND=/usr/sbin/hddtemp -nq -u C /dev/sda
Kas 30 01:49:46 SKYLINE sudo[11710]: umutpamuk : a password is required ; TTY=pts/0 ; PWD=/home/umutpamuk ; USER=root ; COMMAND=/usr/sbin/hddtemp -nq -u C /dev/sdb
Kas 30 02:11:12 SKYLINE systemd[12879]: Failed to start Portal service (GTK+/GNOME implementation).
Kas 30 02:11:38 SKYLINE systemd[12879]: Failed to start Portal service.
systemctl --no-pager --state=failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
systemd-analyze --no-pager critical-chain
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
root[member=2501]skyline[/member]:/home/umutpamuk# systemd-analyze --no-pager critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target [member=3516]1[/member]3.316s
└─multi-user.target [member=3516]1[/member]3.316s
└─tomcat8.service @8.248s +5.067s
└─network-online.target @8.247s
└─NetworkManager-wait-online.service [member=3516]1[/member].961s +6.285s
└─NetworkManager.service [member=3516]1[/member].648s +309ms
└─dbus.service [member=3516]1[/member].632s
└─basic.target [member=3516]1[/member].627s
└─sockets.target [member=3516]1[/member].627s
└─dbus.socket [member=3516]1[/member].627s
└─sysinit.target [member=3516]1[/member].625s
└─systemd-timesyncd.service [member=3516]1[/member].492s +132ms
└─systemd-tmpfiles-setup.service [member=3516]1[/member].447s +38ms
└─local-fs.target [member=3516]1[/member].444s
└─run-user-1000-gvfs.mount @9.418s
└─run-user-1000.mount @8.715s
└─local-fs-pre.target [member=3516]1[/member].349s
└─keyboard-setup.service @221ms +1.127s
└─systemd-journald.socket @214ms
└─system.slice @213ms
└─-.slice @211ms
Tüm çıktılar bunlar umarım doğru şekilde yaza bilmişimdir.
-
Mysql servisi ile ilgili sorun görünmüyor, Tomcat ve NetworkManager-wait-online servislerini açılışta pasifleştirmeyi deneyebilirsiniz.
sudo systemctl disable NetworkManager-wait-online.service
sudo systemctl disable tomcat8.service
İhtiyacınız olduğunda tomcat servisini aşağıdaki komutla başlatabilirsiniz.
sudo systemctl start tomcat8.service
-
Yeni analizim bu şekilde 10sn lik bir düşüş oldu sanırım bundan daha da aşağısı olmazdır.
vede kronometre ile öldüğümde 18sn de şifre giriş ekranım gelmektedir.
Kod Çıktılarım aşağıdadır
systemd-analyze time Startup finished in 3.831s (firmware) + 3.622s (loader) + 5.277s (kernel) + 2.632s (userspace) = 15.364s
graphical.target reached after 2.423s in userspace
systemd-analyze --no-pager blame
1.111s keyboard-setup.service
736ms ufw.service
718ms systemd-journal-flush.service
703ms dev-sda2.device
506ms mysql.service
326ms upower.service
324ms NetworkManager.service
312ms udisks2.service
245ms ubuntu-system-adjustments.service
242ms networkd-dispatcher.service
235ms accounts-daemon.service
221ms systemd-udev-trigger.service
218ms systemd-logind.service
213ms systemd-resolved.service
205ms ModemManager.service
190ms tlp.service
165ms grub-common.service
145ms colord.service
137ms systemd-udevd.service
133ms thermald.service
126ms swapfile.swap
120ms wpa_supplicant.service
110ms systemd-timesyncd.service
110ms hddtemp.service
103ms lvm2-monitor.service
101ms avahi-daemon.service
99ms apport.service
99ms systemd-journald.service
95ms rsyslog.service
89ms lm-sensors.service
80ms lightdm.service
79ms speech-dispatcher.service
78ms plymouth-quit-wait.service
68ms apparmor.service
63ms gpu-manager.service
60ms alsa-restore.service
54ms systemd-modules-load.service
51ms systemd-tmpfiles-setup-dev.service
50ms pppd-dns.service
48ms systemd-sysctl.service
43ms user@1000.service
38ms kerneloops.service
34ms polkit.service
34ms networking.service
32ms systemd-fsck[member=2665]Dev[/member]-disk-by\x2duuid-7606\x2d9407.service
32ms dns-clean.service
24ms dev-mqueue.mount
23ms kmod-static-nodes.service
19ms plymouth-start.service
18ms systemd-remount-fs.service
18ms binfmt-support.service
17ms dev-hugepages.mount
17ms systemd-tmpfiles-setup.service
13ms bluetooth.service
13ms sys-fs-fuse-connections.mount
13ms plymouth-read-write.service
13ms sys-kernel-debug.mount
12ms ureadahead-stop.service
10ms sys-kernel-config.mount
9ms systemd-update-utmp.service
9ms blk-availability.service
8ms boot-efi.mount
8ms proc-sys-fs-binfmt_misc.mount
8ms systemd-random-seed.service
8ms rtkit-daemon.service
6ms systemd-update-utmp-runlevel.service
5ms systemd-user-sessions.service
5ms systemd-backlight@backlight:intel_backlight.service
5ms console-setup.service
3ms openvpn.service
2ms setvtrgb.service
Forumda gezinirken görmüştüm
sudo xed /lib/systemd/system/NetworkManager-wait-online.serviceExecStart=/usr/bin/nm-online -s -q --timeout=30ExecStart=/usr/bin/nm-online -s -q --timeout=10bu şekilde de değişiklik yaptım ama bir fark olmadı acaba 10 olarak kalsa problem olur mu yoksa eski haline mi getirmeliyim?
-
Bence yapılan düzenlemeler olumlu. NetworkManager-wait-online.service ile ilgili yaptığınız düzenlemeyi ister geri alın isterseniz olduğu gibi bırakın, ama etkisi olmadığını söylediğinize göre düzenlemeyi geri olmak daha uygun olabilir.
Ayrıca Systemd başlatma ve sonlandırma zaman aşımı süresi azaltmakta denenebilir. Bunun için aşağıdaki komutu uçbirimde çalıştırın.
sudo xed /etc/systemd/system.conf
Açılan dosyada aşağıdaki satırları bulup,
#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90s
başlarındaki # işaretini de kaldırarak aşağıdaki şekilde düzenleyin.
#DefaultTimeoutStartSec=15s
#DefaultTimeoutStopSec=15s
Konu sonuca ulaştıysa, başlığı etiketlediğinizde konuyu kilitleyebiliriz.
[okay]Çözülen başlıkların etiketlenmesi hakkında. (https://forum.linuxmint.net.tr/index.php?topic=2058.0)[/okay]
-
systemd-analyze çıktısını 15.5 sn alırken 15.45 sn falan almaya başladım çok gözle görünür bir değişim olmadı bu sefer ve eski haline döndürdüm.
Totalde benim ölçümüme göre 25 sn de analyze çıktısına göre 15 sn de sistemim açılmaktadır.
Sorun çözülmüştür ,Teşekkürler.