Very long time to clean up after update

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

Very long time to clean up after update

Postby janpihlgren » Jul 12th, '18, 05:57

I have a ThinkPad W701 with 16 GB RAM, 320 GB hd with /usr-partition 16 GB with 1.8 GB free space.
I'm running Mageia 6 with dkms 2.0.19, dkms-nvidia340 340.106, KDE plasma, plasma-desktop 5.12.2

After last update the cleaning up take about 30 minutes. For me it takes longer and longer time to clean up after update.
Why will the clean up take as long time?
Last edited by janpihlgren on Jul 26th, '18, 07:05, edited 2 times in total.
User avatar
janpihlgren
 
Posts: 253
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden

Re: Very long time to clean up after update

Postby doktor5000 » Jul 12th, '18, 13:20

What cleanup are you talking about in particular, using what tool?
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 14539
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Very long time to clean up after update

Postby janpihlgren » Jul 12th, '18, 14:56

The clean up/removing that mcc does after the upgrade is done.
User avatar
janpihlgren
 
Posts: 253
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden

Re: Very long time to clean up after update

Postby doktor5000 » Jul 12th, '18, 16:57

So you use MCC to do your regular updates? Does the same happen with the mga-applet that regularly checks for updates? Does it also happen when using urpmi?
Can you please also add the output as root of
Code: Select all
rpm -qa|sort|grep -iE "kernel|dkms"
dkms status


You can also check the journalctl logs for what is happening during that cleanup, if you said it took 30 minutes then you should have the timeframe to look up in the logs and post here.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 14539
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Very long time to clean up after update

Postby janpihlgren » Jul 13th, '18, 04:29

Code: Select all
[root@Humlan jan]# rpm -qa | sort | grep -iE "kernel|dkms"
dkms-2.0.19-39.mga6
dkms-minimal-2.0.19-39.mga6
dkms-nvidia340-340.106-1.mga6.nonfree
dkms-virtualbox-5.2.14-1.mga6
kernel-desktop-4.14.10-1.mga6-1-1.mga6
kernel-desktop-4.14.13-1.mga6-1-1.mga6
kernel-desktop-4.14.16-1.mga6-1-1.mga6
kernel-desktop-4.14.18-1.mga6-1-1.mga6
kernel-desktop-4.14.20-1.mga6-1-1.mga6
kernel-desktop-4.14.25-1.mga6-1-1.mga6
kernel-desktop-4.14.30-3.mga6-1-1.mga6
kernel-desktop-4.14.40-1.mga6-1-1.mga6
kernel-desktop-4.14.44-2.mga6-1-1.mga6
kernel-desktop-4.14.50-2.mga6-1-1.mga6
kernel-desktop-4.4.74-1.mga5-1-1.mga5
kernel-desktop-4.9.35-1.mga6-1-1.mga6
kernel-desktop-4.9.40-1.mga6-1-1.mga6
kernel-desktop-4.9.43-1.mga6-1-1.mga6
kernel-desktop-4.9.50-1.mga6-1-1.mga6
kernel-desktop-4.9.56-1.mga6-1-1.mga6
kernel-desktop-devel-4.14.10-1.mga6-1-1.mga6
kernel-desktop-devel-4.14.13-1.mga6-1-1.mga6
kernel-desktop-devel-4.14.16-1.mga6-1-1.mga6
kernel-desktop-devel-4.14.18-1.mga6-1-1.mga6
kernel-desktop-devel-4.14.20-1.mga6-1-1.mga6
kernel-desktop-devel-4.14.25-1.mga6-1-1.mga6
kernel-desktop-devel-4.14.30-3.mga6-1-1.mga6
kernel-desktop-devel-4.14.40-1.mga6-1-1.mga6
kernel-desktop-devel-4.14.44-2.mga6-1-1.mga6
kernel-desktop-devel-4.14.50-2.mga6-1-1.mga6
kernel-desktop-devel-4.4.74-1.mga5-1-1.mga5
kernel-desktop-devel-4.9.35-1.mga6-1-1.mga6
kernel-desktop-devel-4.9.40-1.mga6-1-1.mga6
kernel-desktop-devel-4.9.43-1.mga6-1-1.mga6
kernel-desktop-devel-4.9.50-1.mga6-1-1.mga6
kernel-desktop-devel-4.9.56-1.mga6-1-1.mga6
kernel-desktop-devel-latest-4.14.50-2.mga6
kernel-desktop-latest-4.14.50-2.mga6
kernel-firmware-20170531-1.mga6
kernel-firmware-nonfree-20180518-1.mga6.nonfree
kernel-server-4.14.10-1.mga6-1-1.mga6
kernel-server-4.14.13-1.mga6-1-1.mga6
kernel-server-4.14.16-1.mga6-1-1.mga6
kernel-server-4.14.18-1.mga6-1-1.mga6
kernel-server-4.14.20-1.mga6-1-1.mga6
kernel-server-4.14.25-1.mga6-1-1.mga6
kernel-server-4.14.30-3.mga6-1-1.mga6
kernel-server-4.14.40-1.mga6-1-1.mga6
kernel-server-4.14.44-2.mga6-1-1.mga6
kernel-server-4.14.50-2.mga6-1-1.mga6
kernel-server-4.4.74-1.mga5-1-1.mga5
kernel-server-4.9.35-1.mga6-1-1.mga6
kernel-server-4.9.40-1.mga6-1-1.mga6
kernel-server-4.9.43-1.mga6-1-1.mga6
kernel-server-4.9.50-1.mga6-1-1.mga6
kernel-server-4.9.56-1.mga6-1-1.mga6
kernel-server-devel-4.14.10-1.mga6-1-1.mga6
kernel-server-devel-4.14.13-1.mga6-1-1.mga6
kernel-server-devel-4.14.16-1.mga6-1-1.mga6
kernel-server-devel-4.14.18-1.mga6-1-1.mga6
kernel-server-devel-4.14.20-1.mga6-1-1.mga6
kernel-server-devel-4.14.25-1.mga6-1-1.mga6
kernel-server-devel-4.14.30-3.mga6-1-1.mga6
kernel-server-devel-4.14.40-1.mga6-1-1.mga6
kernel-server-devel-4.14.44-2.mga6-1-1.mga6
kernel-server-devel-4.14.50-2.mga6-1-1.mga6
kernel-server-devel-4.9.50-1.mga6-1-1.mga6
kernel-server-devel-4.9.56-1.mga6-1-1.mga6
kernel-server-devel-latest-4.14.50-2.mga6
kernel-server-latest-4.14.50-2.mga6
kernel-userspace-headers-4.14.50-2.mga6
vboxadditions-kernel-4.14.10-desktop-1.mga6-5.2.2-5.mga6
vboxadditions-kernel-4.14.10-server-1.mga6-5.2.2-5.mga6
vboxadditions-kernel-4.14.13-desktop-1.mga6-5.2.6-1.mga6
vboxadditions-kernel-4.14.13-server-1.mga6-5.2.6-1.mga6
vboxadditions-kernel-4.14.16-desktop-1.mga6-5.2.6-4.mga6
vboxadditions-kernel-4.14.16-server-1.mga6-5.2.6-4.mga6
vboxadditions-kernel-4.14.18-desktop-1.mga6-5.2.6-6.mga6
vboxadditions-kernel-4.14.18-server-1.mga6-5.2.6-6.mga6
vboxadditions-kernel-4.14.20-desktop-1.mga6-5.2.8-1.mga6
vboxadditions-kernel-4.14.20-server-1.mga6-5.2.8-1.mga6
vboxadditions-kernel-4.14.25-desktop-1.mga6-5.2.8-5.mga6
vboxadditions-kernel-4.14.25-server-1.mga6-5.2.8-5.mga6
vboxadditions-kernel-4.14.30-desktop-3.mga6-5.2.8-6.mga6
vboxadditions-kernel-4.14.30-server-3.mga6-5.2.8-6.mga6
vboxadditions-kernel-4.14.40-desktop-1.mga6-5.2.12-1.mga6
vboxadditions-kernel-4.14.40-server-1.mga6-5.2.12-1.mga6
vboxadditions-kernel-4.14.44-desktop-2.mga6-5.2.12-2.mga6
vboxadditions-kernel-4.14.44-server-2.mga6-5.2.12-2.mga6
vboxadditions-kernel-4.14.50-desktop-2.mga6-5.2.14-1.mga6
vboxadditions-kernel-4.14.50-server-2.mga6-5.2.14-1.mga6
vboxadditions-kernel-4.4.74-desktop-1.mga5-5.1.22-7.mga5
vboxadditions-kernel-4.9.35-desktop-1.mga6-5.1.22-20.mga6
vboxadditions-kernel-4.9.40-desktop-1.mga6-5.1.26-1.mga6
vboxadditions-kernel-4.9.43-desktop-1.mga6-5.1.26-2.mga6
vboxadditions-kernel-4.9.50-desktop-1.mga6-5.1.26-4.mga6
vboxadditions-kernel-4.9.50-server-1.mga6-5.1.26-4.mga6
vboxadditions-kernel-4.9.56-desktop-1.mga6-5.2.2-1.mga6
vboxadditions-kernel-4.9.56-server-1.mga6-5.2.2-1.mga6
vboxadditions-kernel-desktop-latest-5.2.14-1.mga6
vboxadditions-kernel-server-latest-5.2.14-1.mga6
virtualbox-kernel-4.14.10-desktop-1.mga6-5.2.2-5.mga6
virtualbox-kernel-4.14.10-server-1.mga6-5.2.2-5.mga6
virtualbox-kernel-4.14.13-desktop-1.mga6-5.2.6-1.mga6
virtualbox-kernel-4.14.13-server-1.mga6-5.2.6-1.mga6
virtualbox-kernel-4.14.16-desktop-1.mga6-5.2.6-4.mga6
virtualbox-kernel-4.14.16-server-1.mga6-5.2.6-4.mga6
virtualbox-kernel-4.14.18-desktop-1.mga6-5.2.6-6.mga6
virtualbox-kernel-4.14.18-server-1.mga6-5.2.6-6.mga6
virtualbox-kernel-4.14.20-desktop-1.mga6-5.2.8-1.mga6
virtualbox-kernel-4.14.20-server-1.mga6-5.2.8-1.mga6
virtualbox-kernel-4.14.25-desktop-1.mga6-5.2.8-5.mga6
virtualbox-kernel-4.14.25-server-1.mga6-5.2.8-5.mga6
virtualbox-kernel-4.14.30-desktop-3.mga6-5.2.8-6.mga6
virtualbox-kernel-4.14.30-server-3.mga6-5.2.8-6.mga6
virtualbox-kernel-4.14.40-desktop-1.mga6-5.2.12-1.mga6
virtualbox-kernel-4.14.40-server-1.mga6-5.2.12-1.mga6
virtualbox-kernel-4.14.44-desktop-2.mga6-5.2.12-2.mga6
virtualbox-kernel-4.14.44-server-2.mga6-5.2.12-2.mga6
virtualbox-kernel-4.14.50-desktop-2.mga6-5.2.14-1.mga6
virtualbox-kernel-4.14.50-server-2.mga6-5.2.14-1.mga6
virtualbox-kernel-4.4.74-desktop-1.mga5-5.1.22-7.mga5
virtualbox-kernel-4.4.74-server-1.mga5-5.1.22-7.mga5
virtualbox-kernel-4.9.35-desktop-1.mga6-5.1.22-20.mga6
virtualbox-kernel-4.9.35-server-1.mga6-5.1.22-20.mga6
virtualbox-kernel-4.9.40-desktop-1.mga6-5.1.26-1.mga6
virtualbox-kernel-4.9.40-server-1.mga6-5.1.26-1.mga6
virtualbox-kernel-4.9.43-desktop-1.mga6-5.1.26-2.mga6
virtualbox-kernel-4.9.43-server-1.mga6-5.1.26-2.mga6
virtualbox-kernel-4.9.50-desktop-1.mga6-5.1.26-4.mga6
virtualbox-kernel-4.9.50-server-1.mga6-5.1.26-4.mga6
virtualbox-kernel-4.9.56-desktop-1.mga6-5.2.2-1.mga6
virtualbox-kernel-4.9.56-server-1.mga6-5.2.2-1.mga6
virtualbox-kernel-desktop-latest-5.2.14-1.mga6
virtualbox-kernel-server-latest-5.2.14-1.mga6
xtables-addons-kernel-4.14.10-server-1.mga6-2.13-8.mga6
xtables-addons-kernel-4.14.13-server-1.mga6-2.13-10.mga6
xtables-addons-kernel-4.14.16-server-1.mga6-2.13-14.mga6
xtables-addons-kernel-4.14.18-server-1.mga6-2.13-16.mga6
xtables-addons-kernel-4.14.20-server-1.mga6-2.13-20.mga6
xtables-addons-kernel-4.14.25-server-1.mga6-2.13-25.mga6
xtables-addons-kernel-4.14.30-server-3.mga6-2.13-26.mga6
xtables-addons-kernel-4.14.40-server-1.mga6-2.13-34.mga6
xtables-addons-kernel-4.14.44-server-2.mga6-2.13-38.mga6
xtables-addons-kernel-4.14.50-server-2.mga6-2.13-42.mga6
xtables-addons-kernel-4.9.50-server-1.mga6-2.12-43.mga6
xtables-addons-kernel-4.9.56-server-1.mga6-2.13-3.mga6
xtables-addons-kernel-server-latest-2.13-42.mga6


==================================================================

Code: Select all
[root@Humlan jan]# dkms status
virtualbox, 5.2.14-1.mga6, 4.14.50-server-2.mga6, x86_64: installed
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
virtualbox, 5.1.22-1.mga6, 4.4.74-desktop-1.mga5, x86_64: built
nvidia340, 340.106-1.mga6.nonfree, 4.14.30-server-3.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.18-desktop-1.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.18-server-1.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.50-server-2.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.16-server-1.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.20-desktop-1.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.44-desktop-2.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.25-desktop-1.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.25-server-1.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.50-desktop-2.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.40-desktop-1.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.30-desktop-3.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.20-server-1.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.40-server-1.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.16-desktop-1.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.44-server-2.mga6, x86_64: installed
nvidia340, 340.106-1.mga6.nonfree, 4.14.13-server-1.mga6, x86_64: installed
Last edited by doktor5000 on Jul 13th, '18, 10:38, edited 2 times in total.
Reason: added code tags
User avatar
janpihlgren
 
Posts: 253
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden

Re: Very long time to clean up after update

Postby morgano » Jul 13th, '18, 09:29

Hej Jan :)
1) You really should remove a lot of the old kernels you do not use and related packages with same version numbers. And related nvidia from dkms will get removed automatically then.
2) For the dkms Error i have no idea.
Mandriva since 2006, then Mageia since 2011 at home & work. Thinkpad T40 T42p T43 T60 T61 T400. Aspire 7. Fileserver. Workstation using LVM, LUKS, VirtualBox, BOINC, Dropbox, CAD, urpmi-proxy, NextCloud...
morgano
 
Posts: 556
Joined: Jun 15th, '11, 17:51
Location: Kivik, Sweden

Re: Very long time to clean up after update

Postby doktor5000 » Jul 13th, '18, 11:00

For the dkms error, you seem to have some dkms.conf file which is broken. You would need to find out which that is, and then either fix it or remove the offending directory.
As root run either
Code: Select all
find / -type f -iname dkms.conf

or
Code: Select all
locate dkms.conf

if you have locate installed and and recent locate cache. Then post the output here.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 14539
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Very long time to clean up after update

Postby janpihlgren » Jul 24th, '18, 09:13

morgano:
I removed a lot of kernel* program.
Now when there come a new update I find that after update the moment "removing" older versions run much faster.
Thanks for info morgano.
User avatar
janpihlgren
 
Posts: 253
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden

Re: Very long time to clean up after update

Postby janpihlgren » Jul 26th, '18, 07:11

I was too fast when I said that the problem was solved.
Todays update get this data:
Update start: 02:04 (m:s)
Install start: 03:20
Remove start: 04:17
Last pkg start removing: 04:32 (cpupower 4.14.50-2)
So far I will accept the time it takes but the next 8 minutes I think is too loong time.
Removing ended: 12:04
Total time = 10 minutes.
User avatar
janpihlgren
 
Posts: 253
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden

Re: Very long time to clean up after update

Postby doktor5000 » Jul 26th, '18, 09:48

FWIW, you did not provide the information requested earlier, and you still don't mention what actual tool you are doing the updates with.

doktor5000 wrote:So you use MCC to do your regular updates? Does the same happen with the mga-applet that regularly checks for updates? Does it also happen when using urpmi?
[...]
You can also check the journalctl logs for what is happening during that cleanup, if you said it took 30 minutes then you should have the timeframe to look up in the logs and post here.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 14539
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Very long time to clean up after update

Postby janpihlgren » Jul 26th, '18, 10:25

I use mcc (graphic) when doing upgrade.


Code: Select all
[root@Humlan jan]# locate dkms.conf
/etc/depmod.d/dkms.conf
[root@Humlan jan]#


Code: Select all
[root@Humlan jan]# find / -type f -iname dkms.conf
/etc/depmod.d/dkms.conf
/var/lib/dkms/virtualbox/5.2.14-1.mga6/build/dkms.conf
/var/lib/dkms/virtualbox/5.1.22-1.mga6/build/dkms.conf
/var/lib/dkms/nvidia340/340.106-1.mga6.nonfree/build/dkms.conf
/var/lib/dkms-binary/virtualbox/5.2.14-1.mga6/4.14.50-server-2.mga6/dkms.conf
/var/lib/dkms-binary/virtualbox/5.2.14-1.mga6/4.14.56-desktop-1.mga6/dkms.conf
/var/lib/dkms-binary/virtualbox/5.2.14-1.mga6/4.14.50-desktop-2.mga6/dkms.conf
/var/lib/dkms-binary/virtualbox/5.2.14-1.mga6/4.14.56-server-1.mga6/dkms.conf
/var/lib/dkms-binary/vboxadditions/5.2.14-1.mga6/4.14.50-server-2.mga6/dkms.conf
/var/lib/dkms-binary/vboxadditions/5.2.14-1.mga6/4.14.56-desktop-1.mga6/dkms.conf
/var/lib/dkms-binary/vboxadditions/5.2.14-1.mga6/4.14.50-desktop-2.mga6/dkms.conf
/var/lib/dkms-binary/vboxadditions/5.2.14-1.mga6/4.14.56-server-1.mga6/dkms.conf
/var/lib/dkms-binary/xtables-addons/2.13-3.mga6/4.14.50-server-2.mga6/dkms.conf
/var/lib/dkms-binary/xtables-addons/2.13-3.mga6/4.14.56-server-1.mga6/dkms.conf
find: ‘/run/user/10001/gvfs’: Åtkomst nekas
/usr/src/virtualbox-5.2.14-1.mga6/dkms.conf
/usr/src/nvidia340-340.106-1.mga6.nonfree/dkms.conf
[root@Humlan jan]#


Code: Select all
[root@Humlan jan]# rpm -qa|sort|grep -iE "kernel|dkms"
dkms-2.0.19-39.mga6
dkms-minimal-2.0.19-39.mga6
dkms-nvidia340-340.106-1.mga6.nonfree
dkms-virtualbox-5.2.14-1.mga6
kernel-desktop-4.14.50-2.mga6-1-1.mga6
kernel-desktop-4.14.56-1.mga6-1-1.mga6
kernel-desktop-devel-4.14.50-2.mga6-1-1.mga6
kernel-desktop-devel-4.14.56-1.mga6-1-1.mga6
kernel-desktop-devel-latest-4.14.56-1.mga6
kernel-desktop-latest-4.14.56-1.mga6
kernel-firmware-20170531-1.mga6
kernel-firmware-nonfree-20180606-1.mga6.nonfree
kernel-server-4.14.50-2.mga6-1-1.mga6
kernel-server-4.14.56-1.mga6-1-1.mga6
kernel-server-devel-4.14.50-2.mga6-1-1.mga6
kernel-server-devel-4.14.56-1.mga6-1-1.mga6
kernel-server-devel-latest-4.14.56-1.mga6
kernel-server-latest-4.14.56-1.mga6
kernel-userspace-headers-4.14.56-1.mga6
vboxadditions-kernel-4.14.50-desktop-2.mga6-5.2.14-1.mga6
vboxadditions-kernel-4.14.50-server-2.mga6-5.2.14-1.mga6
vboxadditions-kernel-4.14.56-desktop-1.mga6-5.2.14-6.mga6
vboxadditions-kernel-4.14.56-server-1.mga6-5.2.14-6.mga6
vboxadditions-kernel-desktop-latest-5.2.14-6.mga6
vboxadditions-kernel-server-latest-5.2.14-6.mga6
virtualbox-kernel-4.14.50-desktop-2.mga6-5.2.14-1.mga6
virtualbox-kernel-4.14.50-server-2.mga6-5.2.14-1.mga6
virtualbox-kernel-4.14.56-desktop-1.mga6-5.2.14-6.mga6
virtualbox-kernel-4.14.56-server-1.mga6-5.2.14-6.mga6
virtualbox-kernel-desktop-latest-5.2.14-6.mga6
virtualbox-kernel-server-latest-5.2.14-6.mga6
xtables-addons-kernel-4.14.50-server-2.mga6-2.13-42.mga6
xtables-addons-kernel-4.14.56-server-1.mga6-2.13-48.mga6
xtables-addons-kernel-server-latest-2.13-48.mga6
[root@Humlan jan]#
Last edited by janpihlgren on Jul 26th, '18, 10:56, edited 1 time in total.
User avatar
janpihlgren
 
Posts: 253
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden

Re: Very long time to clean up after update

Postby isadora » Jul 26th, '18, 10:53

Please janpihlgren, place command-output between [CODE]-tags, to improve readability, thanks ahead!!! ;)
Demo: ftp://ftp5.gwdg.de/pub/linux/mandriva/m ... e_tags.ogv
..........bird from paradise..........

Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
—Antoine de Saint-Exupéry
User avatar
isadora
 
Posts: 2386
Joined: Mar 25th, '11, 16:03
Location: Amsterdam, the Netherlands

Re: Very long time to clean up after update

Postby janpihlgren » Jul 26th, '18, 10:56

Done
User avatar
janpihlgren
 
Posts: 253
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden

Re: Very long time to clean up after update

Postby isadora » Jul 26th, '18, 11:23

Thanks Jan, there is a slight difference between quote- and code-tags however, so i retouched your message. ;)
..........bird from paradise..........

Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
—Antoine de Saint-Exupéry
User avatar
isadora
 
Posts: 2386
Joined: Mar 25th, '11, 16:03
Location: Amsterdam, the Netherlands

Re: Very long time to clean up after update

Postby doktor5000 » Jul 26th, '18, 21:57

You still did not provide the information requested earlier

doktor5000 wrote:Does the same happen with the mga-applet that regularly checks for updates? Does it also happen when using urpmi?
[...]
You can also check the journalctl logs for what is happening during that cleanup, if you said it took 30 minutes then you should have the timeframe to look up in the logs and post here.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 14539
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Very long time to clean up after update

Postby janpihlgren » Jul 27th, '18, 04:58

The same happends when usingmga-applet.
I have never used urpmi when I update .
I have to wait to next update to use journalctl.
User avatar
janpihlgren
 
Posts: 253
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden

Re: Very long time to clean up after update

Postby morgano » Jul 27th, '18, 10:22

janpihlgren wrote:I have to wait to next update to use journalctl.

The journal is recorded and stored for long time, and journalctl is the tool to read it.
So you can any time see what have happened before.
Here is a good article to start with: https://www.loggly.com/ultimate-guide/using-journalctl/
Mandriva since 2006, then Mageia since 2011 at home & work. Thinkpad T40 T42p T43 T60 T61 T400. Aspire 7. Fileserver. Workstation using LVM, LUKS, VirtualBox, BOINC, Dropbox, CAD, urpmi-proxy, NextCloud...
morgano
 
Posts: 556
Joined: Jun 15th, '11, 17:51
Location: Kivik, Sweden

Re: Very long time to clean up after update

Postby janpihlgren » Jul 27th, '18, 11:22

I'm not familiare with journalctl but this is what I think is the log about upgrading.
Attachments
log-b.txt
part log of journalctl
(140.08 KiB) Downloaded 2 times
User avatar
janpihlgren
 
Posts: 253
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden

Re: Very long time to clean up after update

Postby doktor5000 » Jul 27th, '18, 21:51

I don't see any huge delays. I see that the kernel resets your hardisk via hard link reset, there might be some issue with your harddrive.

Code: Select all
jul 26 05:08:05 Humlan.localdomain kernel: ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
jul 26 05:08:05 Humlan.localdomain kernel: ata1.01: failed command: CHECK POWER MODE
jul 26 05:08:05 Humlan.localdomain kernel: ata1.01: cmd e5/00:00:00:00:00/00:00:00:00:00/10 tag 0
                                                    res 00/00:00:00:00:00/00:00:00:00:00/10 Emask 0x2 (HSM violation)
jul 26 05:08:05 Humlan.localdomain kernel: ata1.00: hard resetting link
jul 26 05:08:05 Humlan.localdomain kernel: ata1.01: hard resetting link
jul 26 05:08:06 Humlan.localdomain kernel: ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
jul 26 05:08:06 Humlan.localdomain kernel: ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
jul 26 05:08:06 Humlan.localdomain udisksd[7320]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/HGST_HTS541010A9E680_JB1000132V00TR: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:
                                                  0000: 70 00 0b 00  00 00 00 0a  00 00 10 00  00 00 00 00    p...............
                                                  0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
                                                   (g-io-error-quark, 0)
jul 26 05:08:06 Humlan.localdomain kernel: ata1.00: configured for UDMA/100
jul 26 05:08:06 Humlan.localdomain kernel: ata1.01: configured for UDMA/133
jul 26 05:08:06 Humlan.localdomain kernel: ata1: EH complete


Apart from that, for each kernel package that is installed, bootloader-config is called automatically which checks and updates your bootloader configuration, so the more times that takes and the more kernel packages are updated ...

Code: Select all
jul 26 05:01:41 Humlan.localdomain drakrpm-update[11352]: ### Program is starting ###

[...]

jul 26 05:06:21 Humlan.localdomain bootloader-config[27506]

[...]

jul 26 05:10:49 Humlan.localdomain bootloader-config[28961]: running: grub2-set-default gnulinux-simple-4a60ad22-fc85-418c-9bb1-559f16d53f35
jul 26 05:10:49 Humlan.localdomain [RPM][11352]: install kernel-desktop-4.14.56-1.mga6-1-1.mga6.x86_64: success

[...]

jul 26 05:11:57 Humlan.localdomain [RPM][11352]: Transaction ID 5b5939e0 finished: 0


afterwards mga-applet restarts and searches again for updates
Code: Select all
jul 26 05:12:26 Humlan.localdomain perl[11352]: ### Program is exiting ###
jul 26 05:12:26 Humlan.localdomain mgaapplet[7718]: Computing new updates...
jul 26 05:12:26 Humlan.localdomain mgaapplet[7718]: running: mgaapplet-update-checker

[...]

jul 26 05:12:33 Humlan.localdomain mgaapplet[7718]: Packages are up to date
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 14539
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Very long time to clean up after update

Postby janpihlgren » Jul 28th, '18, 05:08

OK.
Thanks for help and the explanation.
User avatar
janpihlgren
 
Posts: 253
Joined: Mar 30th, '11, 12:23
Location: Marsta, Sweden


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest

cron