Hi,
on a MGA9x64 machine there shows up the following problem:
- /etc/urpmi/urpmi.cfg seems to be OK
and is like the ones on other machines
- when doing a urpmi --auto-update
it looks like:
$ urpmi --auto-update
medium "Core Release" is up-to-date
medium "Core Updates" is up-to-date
medium "Core Backports" is up-to-date
medium "Nonfree Release" is up-to-date
medium "Nonfree Updates" is up-to-date
medium "Nonfree Backports" is up-to-date
medium "Tainted Release" is up-to-date
medium "Tainted Updates" is up-to-date
medium "Tainted Backports" is up-to-date
where the above are the repos not remarked out with 'ignore' in urpmi.cfg.
But when the bottom is reached, urpmi process goes to 100%, i.e., it eats
up a whole cpu core, the fan blows and nothing goes ahead.
Someone already had this type of problem and knows how to solve?
Rebuild the rpm db?
On Fri, 09 Feb 2024 20:21:50 -0500, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
Hi,
on a MGA9x64 machine there shows up the following problem:
- /etc/urpmi/urpmi.cfg seems to be OK and is like the ones on other
machines
- when doing a urpmi --auto-update it looks like:
$ urpmi --auto-update medium "Core Release" is up-to-date medium "Core
Updates" is up-to-date medium "Core Backports" is up-to-date medium
"Nonfree Release" is up-to-date medium "Nonfree Updates" is up-to-date
medium "Nonfree Backports" is up-to-date medium "Tainted Release" is
up-to-date medium "Tainted Updates" is up-to-date medium "Tainted
Backports" is up-to-date
where the above are the repos not remarked out with 'ignore' in
urpmi.cfg.
That can be confirmed by showing "urpmq --list-media active".
But when the bottom is reached, urpmi process goes to 100%, i.e., it
eats up a whole cpu core, the fan blows and nothing goes ahead.
Someone already had this type of problem and knows how to solve?
Rebuild the rpm db?
As root, "rpm --rebuilddb".
Regards, Dave Hodgins
On Fri, 09 Feb 2024 20:21:50 -0500, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
Hi,
on a MGA9x64 machine there shows up the following problem:
- /etc/urpmi/urpmi.cfg seems to be OK and is like the ones on other
machines
- when doing a urpmi --auto-update it looks like:
$ urpmi --auto-update medium "Core Release" is up-to-date medium "Core
Updates" is up-to-date medium "Core Backports" is up-to-date medium
"Nonfree Release" is up-to-date medium "Nonfree Updates" is up-to-date
medium "Nonfree Backports" is up-to-date medium "Tainted Release" is
up-to-date medium "Tainted Updates" is up-to-date medium "Tainted
Backports" is up-to-date
where the above are the repos not remarked out with 'ignore' in
urpmi.cfg.
That can be confirmed by showing "urpmq --list-media active".
But when the bottom is reached, urpmi process goes to 100%, i.e., it
eats up a whole cpu core, the fan blows and nothing goes ahead.
Someone already had this type of problem and knows how to solve?
Rebuild the rpm db?
As root, "rpm --rebuilddb".
Regards, Dave Hodgins
On Fri, 09 Feb 2024 21:28:06 -0500 David W. Hodgins wrote:
On Fri, 09 Feb 2024 20:21:50 -0500, Markus Robert Kessler
<no_reply@dipl-ing-kessler.de> wrote:
Hi,
on a MGA9x64 machine there shows up the following problem:
- /etc/urpmi/urpmi.cfg seems to be OK and is like the ones on other
machines
- when doing a urpmi --auto-update it looks like:
$ urpmi --auto-update medium "Core Release" is up-to-date medium "Core
Updates" is up-to-date medium "Core Backports" is up-to-date medium
"Nonfree Release" is up-to-date medium "Nonfree Updates" is up-to-date
medium "Nonfree Backports" is up-to-date medium "Tainted Release" is
up-to-date medium "Tainted Updates" is up-to-date medium "Tainted
Backports" is up-to-date
where the above are the repos not remarked out with 'ignore' in
urpmi.cfg.
That can be confirmed by showing "urpmq --list-media active".
But when the bottom is reached, urpmi process goes to 100%, i.e., it
eats up a whole cpu core, the fan blows and nothing goes ahead.
Someone already had this type of problem and knows how to solve?
Rebuild the rpm db?
As root, "rpm --rebuilddb".
Regards, Dave Hodgins
Thanks!
Though, problem still persists.
What I've done so far:
- tried 'rpm --rebuilddb'
Same behaviour, 'urpmi --auto-update' leads to urpmi hanging after last
repo with 100% CPU load, and
when using mcc ==> update, then drakrpm-update hangs, also 100% CPU
load.
- deleted /etc/urpmi and selected different repo mirror in mcc
Same as above.
- checked every package with 'drak' in the name:
LIST=`rpm -qa | grep -i drak`
for i in $LIST ; do echo $i ; rpm -V $i ; done
and everything seems OK
- tested if updates are found anyway:
uninstalled muse 4.2.1 from core:updates and installed muse 4.1.0 from core:release instead
So, there is at least one candidate that can be updated. But:
'urpmi --auto-update' doesn't find the updated package,
and also mcc ==> update does not find it.
The funny thing is, that mcc ==> install and remove software shows both candidates, muse 4.1.0 which is still installed, and, ready for
upgrading muse 4.2.1
Strange.
What makes me nervous is that it seems that I will no longer be informed about bugfixes to install. That decreases security drastically.
On Fri, 09 Feb 2024 21:28:06 -0500 David W. Hodgins wrote:
On Fri, 09 Feb 2024 20:21:50 -0500, Markus Robert Kessler
<no_reply@dipl-ing-kessler.de> wrote:
Hi,
on a MGA9x64 machine there shows up the following problem:
- /etc/urpmi/urpmi.cfg seems to be OK and is like the ones on other
machines
- when doing a urpmi --auto-update it looks like:
$ urpmi --auto-update medium "Core Release" is up-to-date medium "Core
Updates" is up-to-date medium "Core Backports" is up-to-date medium
"Nonfree Release" is up-to-date medium "Nonfree Updates" is up-to-date
medium "Nonfree Backports" is up-to-date medium "Tainted Release" is
up-to-date medium "Tainted Updates" is up-to-date medium "Tainted
Backports" is up-to-date
where the above are the repos not remarked out with 'ignore' in
urpmi.cfg.
That can be confirmed by showing "urpmq --list-media active".
But when the bottom is reached, urpmi process goes to 100%, i.e., it
eats up a whole cpu core, the fan blows and nothing goes ahead.
Someone already had this type of problem and knows how to solve?
Rebuild the rpm db?
As root, "rpm --rebuilddb".
Regards, Dave Hodgins
Thanks!
Though, problem still persists.
What I've done so far:
- tried 'rpm --rebuilddb'
Same behaviour, 'urpmi --auto-update' leads to urpmi hanging after last
repo with 100% CPU load, and
when using mcc ==> update, then drakrpm-update hangs, also 100% CPU load.
- deleted /etc/urpmi and selected different repo mirror in mcc
Same as above.
- checked every package with 'drak' in the name:
LIST=`rpm -qa | grep -i drak`
for i in $LIST ; do echo $i ; rpm -V $i ; done
and everything seems OK
- tested if updates are found anyway:
uninstalled muse 4.2.1 from core:updates and
installed muse 4.1.0 from core:release instead
So, there is at least one candidate that can be updated. But:
'urpmi --auto-update' doesn't find the updated package,
and also mcc ==> update does not find it.
The funny thing is, that mcc ==> install and remove software
shows both candidates, muse 4.1.0 which is still installed, and, ready for upgrading muse 4.2.1
Strange.
What makes me nervous is that it seems that I will no longer be informed about bugfixes to install. That decreases security drastically.
On Sat, 10 Feb 2024 12:54:08 -0000 (UTC), Markus Robert Kessler wrote:
On Fri, 09 Feb 2024 21:28:06 -0500 David W. Hodgins wrote:
On Fri, 09 Feb 2024 20:21:50 -0500, Markus Robert Kessler
<no_reply@dipl-ing-kessler.de> wrote:
Hi,
on a MGA9x64 machine there shows up the following problem:
- /etc/urpmi/urpmi.cfg seems to be OK and is like the ones on other
machines
- when doing a urpmi --auto-update it looks like:
$ urpmi --auto-update medium "Core Release" is up-to-date medium
"Core Updates" is up-to-date medium "Core Backports" is up-to-date
medium "Nonfree Release" is up-to-date medium "Nonfree Updates" is
up-to-date medium "Nonfree Backports" is up-to-date medium "Tainted
Release" is up-to-date medium "Tainted Updates" is up-to-date medium
"Tainted Backports" is up-to-date
where the above are the repos not remarked out with 'ignore' in
urpmi.cfg.
That can be confirmed by showing "urpmq --list-media active".
But when the bottom is reached, urpmi process goes to 100%, i.e., it
eats up a whole cpu core, the fan blows and nothing goes ahead.
Someone already had this type of problem and knows how to solve?
Rebuild the rpm db?
As root, "rpm --rebuilddb".
Regards, Dave Hodgins
Thanks!
Though, problem still persists.
What I've done so far:
- tried 'rpm --rebuilddb'
Same behaviour, 'urpmi --auto-update' leads to urpmi hanging after last
repo with 100% CPU load, and
when using mcc ==> update, then drakrpm-update hangs, also 100% CPU
load.
- deleted /etc/urpmi and selected different repo mirror in mcc
Same as above.
- checked every package with 'drak' in the name:
LIST=`rpm -qa | grep -i drak`
for i in $LIST ; do echo $i ; rpm -V $i ; done
and everything seems OK
- tested if updates are found anyway:
uninstalled muse 4.2.1 from core:updates and installed muse 4.1.0 from
core:release instead
So, there is at least one candidate that can be updated. But:
'urpmi --auto-update' doesn't find the updated package,
and also mcc ==> update does not find it.
The funny thing is, that mcc ==> install and remove software shows both
candidates, muse 4.1.0 which is still installed, and, ready for
upgrading muse 4.2.1
Strange.
What makes me nervous is that it seems that I will no longer be
informed about bugfixes to install. That decreases security
drastically.
I speculate the problem might be in corruption of urpmi, or less likely
in rpm or urpmi.update and associated files.
Perhaps reinstall urpmi and maybe urpmi.update and rpm with options --downgrade and --replacepackages ? e.g. for urpmi:
urpmi --downgrade --replacepackages urpmi
Cheers!
jim b.
Hi Jim, thanks for that great hint!
And, yes, it's clear, you cannot remove and reinstall the installer
itself, but, as long as you have an alternative app by hand, it can be
done this way - I did this:
rpm -e urpmi --nodeps
it complained, but the whole urpmi.* package was removed.
Then I reinstalled it this way:
yum install urpmi
Now, 'urpmi --auto-update' runs - and ends - properly :-)
On Sat, 10 Feb 2024 11:14:27 -0500, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
<snip>
Hi Jim, thanks for that great hint!
And, yes, it's clear, you cannot remove and reinstall the installer
itself, but, as long as you have an alternative app by hand, it can be
done this way - I did this:
rpm -e urpmi --nodeps
it complained, but the whole urpmi.* package was removed.
Then I reinstalled it this way:
yum install urpmi
Now, 'urpmi --auto-update' runs - and ends - properly :-)
Now that's bizarre. Does dmesg show any i/o errors?
Regards, Dave Hodgins
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 300 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 38:42:04 |
| Calls: | 6,708 |
| Calls today: | 1 |
| Files: | 12,241 |
| Messages: | 5,353,575 |