Hi,
My system is taking too long to get read. How can I improve this?
When I check it:
viniciusbr@linux-hwbe:~> systemd-analyze blame
25.637s ModemManager.service
23.738s NetworkManager.service
18.045s systemd-journal-flush.service
7.682s dev-sda6.device
5.598s display-manager.service
5.129s polkit.service
4.894s postfix.service
2.676s warsaw.service
2.256s systemd-rfkill.service
2.207s home.mount
1.671s systemd-udevd.service
1.641s systemd-fsck@dev-disk-by\x2duuid-96650134\x2d5361\x2d413a\x2da7e3\x2da1d2bad0704a.service
1.433s systemd-backlight@backlight:intel_backlight.service
1.419s avahi-daemon.service
1.367s boot-efi.mount
1.198s var-tmp.mount
945ms var-log.mount
930ms iscsi.service
914ms systemd-journald.service
814ms var-lib-pgsql.mount
812ms usr-local.mount
811ms var-lib-machines.mount
810ms opt.mount
809ms var-lib-libvirt-images.mount
807ms var-opt.mount
807ms boot-grub2-i386\x2dpc.mount
806ms var-lib-mariadb.mount
805ms var-spool.mount
804ms var-lib-mailman.mount
802ms tmp.mount
802ms var-cache.mount
801ms var-crash.mount
799ms var-lib-mysql.mount
797ms var-lib-named.mount
770ms nscd.service
600ms auditd.service
544ms upower.service
542ms systemd-logind.service
531ms plymouth-read-write.service
390ms systemd-udev-trigger.service
359ms dev-disk-by\x2duuid-eb8d1b1a\x2d1b1f\x2d4dcd\x2d8c50\x2dde2b33580b61.swap
356ms systemd-tmpfiles-setup-dev.service
353ms dev-mqueue.mount
349ms dev-hugepages.mount
347ms sys-kernel-debug.mount
322ms srv.mount
lines 1-46
1-if you don’t directly connect to any kind of modem, uninstall ModemManager.
2-tell us about your PC, such as providing output from
lspci
and
inxi -G -c0
and telling how much RAM you have, whether you use a HD or SSD or both, your CPU model and speed, which WM or DE you use, and how and when you installed openSUSE.
mrmazda:
1-if you don’t directly connect to any kind of modem, uninstall ModemManager.
2-tell us about your PC, such as providing output from
lspci
and
inxi -G -c0
and telling how much RAM you have, whether you use a HD or SSD or both, your CPU model and speed, which WM or DE you use, and how and when you installed openSUSE.
I see. So, if I remove ModemManager, will it not damage my wifi and ethernet?
viniciusbr@linux-hwbe:~> lspci
Absolute path to 'lspci' is '/sbin/lspci', so running it may require superuser privileges (eg. root).
viniciusbr@linux-hwbe:~> sudo lspci
[sudo] senha para root:
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
02:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01)
03:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a)
viniciusbr@linux-hwbe:~> sudo inxi -G -c0
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: X.org 1.18.3 drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 158x23 Advanced Data: N/A for root out of X
I don’t think so.www.linux.com - cleaning your startup process)
Yeap, so I removed ModemManager and seems to have not problem so far. Thanks
And what is this:
19.149s systemd-journal-flush.service
19.149s systemd-journal-flush.service
It flush old logs. I think you can change the time with journalctl --vacuum-time=(3,4,5)d (will delete logs except that number of days).
I putted sudo journalctl --vacuum-time=5d
But it doesn’t change the blame time unfortunately:
19.876s systemd-journal-flush.service
6.203s display-manager.service
5.795s postfix.service
4.870s dev-sda6.device
3.137s NetworkManager.service
1.933s upower.service
1.769s home.mount
1.729s warsaw.service
1.666s var-spool.mount
1.493s boot-efi.mount
And now appeared a new stuff (rtkit-daemon.service):
19.774s systemd-journal-flush.service
16.598s rtkit-daemon.service
16.509s NetworkManager.service
7.940s postfix.service
6.947s display-manager.service
4.206s dev-sda6.device
1.731s warsaw.service
1.719s home.mount
1.458s udisks2.service
1.004s var-lib-machines.mount
Rtkit is a real time kernel scheduler.
It seems that, your system has quite a few things enabled which are possibly not needed:
> systemctl list-unit-files | grep -i 'rtkit'
rtkit-daemon.service disabled
>
> systemd-analyze
Startup finished in 2.038s (kernel) + 1.645s (initrd) + 10.655s (userspace) = 14.339s
> systemd-analyze blame | head
6.063s wicked.service
1.473s apparmor.service
1.332s mysql.service
1.194s display-manager.service
1.132s systemd-journal-flush.service
747ms home01.mount
639ms SuSEfirewall2.service
474ms home.mount
430ms vboxdrv.service
392ms apache2.service
>
Please execute, with the user “root”, ‘journalctl --verify’; for system journals which indicate errors, ‘journalctl --vacuum-time=1weeks’ (or less) is the only remedy that I’ve found; for user journals, currently, the only palliative AFAIK is to remove the offending journal file.
As to the overall miserable boot performance (booting is taking much, much, too long [with Leap 42.3 and updates/patches as of early March 2018]), please consider performing some housekeeping on the system partition’s file system – if it’s Btrfs, there’s some housekeeping tasks in “/etc/cron.weekly/” and “/etc/cron.monthly/” which need to be executed.
I saw a “home” mount in your reports which needed rather more than 1 second – if that “home” partition uses XFS, you’ll need to drop down to “systemctl rescue”; unmount that partition; and then ‘xfs_repair’ it …
Owwwwwwwwwwwww
Now we are talking!
systemd-analyze blame
4.842s dev-sda6.device
4.457s display-manager.service
3.871s postfix.service
2.882s NetworkManager.service
2.316s warsaw.service
2.009s systemd-journal-flush.service
1.278s boot-efi.mount
911ms var-lib-machines.mount
889ms var-opt.mount
882ms var-crash.mount
870ms upower.service
868ms mcelog.service
843ms systemd-udevd.service
714ms dev-disk-by\x2duuid-eb8d1b1a\x2d1b1f\x2d4dcd\x2d8c50\x2dde2b33580b61.swap
709ms avahi-daemon.service
706ms polkit.service
700ms plymouth-read-write.service
691ms systemd-remount-fs.service
687ms dev-mqueue.mount
685ms dev-hugepages.mount
681ms sys-kernel-debug.mount
648ms systemd-rfkill.service
Thank you everyone!
Hi, now I upgraded to Leap 15 Beta and my systemd-analyze blame is:
3min 1.633s backup-rpmdb.service
1min 8.702s ca-certificates.service
1min 2.796s btrfsmaintenance-refresh.service
58.580s display-manager.service
58.009s postfix.service
51.491s plymouth-quit-wait.service
51.383s backup-sysconfig.service
20.178s logrotate.service
What are these first stuffs?
Welcome to the openSUSE Leap 15 Beta Test team!!!
A Beta Test system is a Beta Test system is a Beta Test system …
Therefore, the upgrade of an existing production system to a Beta Test version is a part of the Beta Test …
So, if you can recall everything which happened during the upgrade from Leap 42.3 to Leap 15 Beta Test Build Number ???, please raise a Bug Report, reporting exactly what happened and the behaviour you’re now experiencing with your system.
dcurtisfra:
Welcome to the openSUSE Leap 15 Beta Test team!!!
A Beta Test system is a Beta Test system is a Beta Test system …
Therefore, the upgrade of an existing production system to a Beta Test version is a part of the Beta Test …
So, if you can recall everything which happened during the upgrade from Leap 42.3 to Leap 15 Beta Test Build Number ???, please raise a Bug Report, reporting exactly what happened and the behaviour you’re now experiencing with your system.
Hi, in fact I didn’t find nothing wrong yet (just lazier to initialize and I don’t know if its really a bug). The system is solid as always lol!.
If you have your root on btrfs, you should be able to boot into the last snapshot before the upgrade. But, just some systemd output doesn’t say enough, How did you upgrade? Please be precise in that you tell us.
The amount of time needed to boot the Leap 15 system indicated by “systemd-analyze” is indicating that something is **** VERY **** wrong:
3min 1.633s backup-rpmdb.service
1min 8.702s ca-certificates.service
1min 2.796s btrfsmaintenance-refresh.service
58.580s display-manager.service
58.009s postfix.service
51.491s plymouth-quit-wait.service
51.383s backup-sysconfig.service
20.178s logrotate.service
The times noted here are absolutely not acceptable!!
Please raise a Bug Report to document this unacceptable system quality.
Please install a package named “inxi” so we can quickly determine your system’s configuration and hardware – you’ll possibly need to install some addition packages based on the information “inxi --recommends” will provide to you.
We’ll need to output of “inxi -F” to determine the system’s configuration and hardware.
Please also ensure that, the systemd journals related to each Leap 15 Beta Test boot have been retained and archived.
dcurtisfra:
The amount of time needed to boot the Leap 15 system indicated by “systemd-analyze” is indicating that something is **** VERY **** wrong:
3min 1.633s backup-rpmdb.service
1min 8.702s ca-certificates.service
1min 2.796s btrfsmaintenance-refresh.service
58.580s display-manager.service
58.009s postfix.service
51.491s plymouth-quit-wait.service
51.383s backup-sysconfig.service
20.178s logrotate.service
The times noted here are absolutely not acceptable!!
Please raise a Bug Report to document this unacceptable system quality.
Please install a package named “inxi” so we can quickly determine your system’s configuration and hardware – you’ll possibly need to install some addition packages based on the information “inxi --recommends” will provide to you.
We’ll need to output of “inxi -F” to determine the system’s configuration and hardware.
Please also ensure that, the systemd journals related to each Leap 15 Beta Test boot have been retained and archived.
Hi,
After some update and reboots, the blame changed a bit:
systemd-analyze blame
1min 7.653s ca-certificates.service
52.298s btrfsmaintenance-refresh.service
40.955s NetworkManager.service
30.731s systemd-tmpfiles-clean.service
14.644s postfix.service
14.227s auditd.service
12.713s display-manager.service
10.979s lvm2-monitor.service
10.384s dev-sda6.device
9.413s kbdsettings.service
9.412s mcelog.service
9.399s avahi-daemon.service
9.396s alsa-restore.service
9.395s nscd.service
9.381s bluetooth.service
8.682s plymouth-quit-wait.service
7.885s systemd-rfkill.service
7.630s warsaw.service
5.649s home.mount
5.351s initrd-switch-root.service
5.314s systemd-backlight@backlight:intel_backlight.service
4.862s systemd-udevd.service
3.574s polkit.service
1.449s iscsi.service
1.430s systemd-journal-flush.service
1.423s systemd-fsck@dev-disk-by\x2duuid-96650134\x2d5361\x2d413a\x2da7e3\x2da1d2bad0704a.service
1.060s boot-efi.mount
996ms var-lib-machines.mount
886ms systemd-vconsole-setup.service
873ms usr-local.mount
795ms sysroot.mount
727ms plymouth-start.service
680ms sys-kernel-debug.mount
And here is the inxi:
Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
System: Host: linux-hwbe Kernel: 4.15.10-2-default x86_64 bits: 64 Desktop: KDE Plasma 5.12.4
Distro: openSUSE Leap 15.0 Beta
Machine: Device: laptop System: ASUSTeK product: K46CA v: 1.0 serial: N/A
Mobo: ASUSTeK model: K46CA v: 1.0 serial: N/A UEFI: American Megatrends v: K46CA.315 date: 05/17/2013
Battery BAT0: charge: 13.4 Wh 100.3% condition: 13.4/43.0 Wh (31%)
CPU: Dual core Intel Core i7-3517U (-HT-MCP-) cache: 4096 KB
clock speeds: max: 3000 MHz 1: 963 MHz 2: 904 MHz 3: 952 MHz 4: 892 MHz
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: x11 (X.org 1.19.6 ) drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 154x34
Audio: Card Intel 7 Series/C216 Family High Definition Audio Controller driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.15.10-2-default
Network: Card-1: Qualcomm Atheros AR9485 Wireless Network Adapter driver: ath9k
IF: wlan0 state: up mac: 5c:c9:d3:45:10:53
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
IF: eth0 state: down mac: 10:c3:7b:c2:1d:f8
Drives: HDD Total Size: 1022.7GB (79.0% used)
ID-1: /dev/sda model: TOSHIBA_MQ01ABD1 size: 1000.2GB
ID-2: /dev/sdb model: SG9MSM6D024GPM00 size: 22.5GB
Partition: ID-1: / size: 60G used: 41G (70%) fs: btrfs dev: /dev/sda6
ID-2: /tmp size: 60G used: 41G (70%) fs: btrfs dev: /dev/sda6
ID-3: /var/log size: 60G used: 41G (70%) fs: btrfs dev: /dev/sda6
ID-4: /var/tmp size: 60G used: 41G (70%) fs: btrfs dev: /dev/sda6
ID-5: /opt size: 60G used: 41G (70%) fs: btrfs dev: /dev/sda6
ID-6: /home size: 865G used: 711G (83%) fs: xfs dev: /dev/sda4
ID-7: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 211 Uptime: 1:55 Memory: 1841.1/5848.5MB Init: systemd runlevel: 5
Client: Shell (bash) inxi: 2.3.40
Knurpht:
If you have your root on btrfs, you should be able to boot into the last snapshot before the upgrade. But, just some systemd output doesn’t say enough, How did you upgrade? Please be precise in that you tell us.
First, I added the new repos:
# | Apelido | Nome | Habilitado | Verificação GPG | Atualizar | URI
---+---------------------------+-----------------------------------------+------------+-----------------+-----------+------------------------------------------------------------------------
1 | packman | packman | Sim | (r ) Sim | Sim | http://packman.inode.at/suse/openSUSE_Leap_15.0/
2 | repo-debug | openSUSE-Leap-15.0-Debug | Não | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.0/repo/oss/
3 | repo-debug-non-oss | openSUSE-Leap-15.0-Debug-Non-Oss | Não | ---- | ---- | http://download.opensuse.org/debug/distribution/leap/15.0/repo/non-oss/
4 | repo-debug-update | openSUSE-Leap-15.0-Update-Debug | Não | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.0/oss/
5 | repo-debug-update-non-oss | openSUSE-Leap-15.0-Update-Debug-Non-Oss | Não | ---- | ---- | http://download.opensuse.org/debug/update/leap/15.0/non-oss/
6 | repo-non-oss | openSUSE-Leap-15.0-Non-Oss | Sim | (r ) Sim | Sim | http://download.opensuse.org/distribution/leap/15.0/repo/non-oss/
7 | repo-oss | openSUSE-Leap-15.0-Oss | Sim | (r ) Sim | Sim | http://download.opensuse.org/distribution/leap/15.0/repo/oss/
8 | repo-source | openSUSE-Leap-15.0-Source | Não | ---- | ---- | http://download.opensuse.org/source/distribution/leap/15.0/repo/oss/
9 | repo-update | openSUSE-Leap-15.0-Update | Sim | (r ) Sim | Sim | http://download.opensuse.org/update/leap/15.0/oss/
10 | repo-update-non-oss | openSUSE-Leap-15.0-Update-Non-Oss | Sim | (r ) Sim | Sim | http://download.opensuse.org/update/leap/15.0/non-oss/
Then, I just “downloaded only” the dist-upgrade command. After that, I left out of the system to the console, change to “init 3” and apply the downloaded files (zypper --no-refresh dup).
