Creeping system failure since update.

[TenderFoot]

On 17 Nov I updated for the first time since Feb. At the time, there were no apparent problems.

However, since then - though I don't think immediately - selecting shutdown/restart would only drop me down to the login screen and even logging back in and trying again the same thing happened. Each time had to resort to short press of power button at which it seemed to resume a "clean" shutdown.

Today, no WiFi. Persistent high cpu usage. Synaptic won't launch (nor much else). Shutdown and Restart greyed out.

Could this be down to latest update or creeping corruption? Fortunately took snapshot before update.

[Posted here as a possible "bug" rather than MX Modified (due to Kwin)]

[entropyfoe]

Run top from the terminal?

Code: Select all

top

Then you can see what programs are using all the CPU cycles and RAM.

[dolphin_oracle]

Sounds like an incomplete update to me.

Try

sudo apt-get install -f

And see if anything happens. Posting any outpit feom there would be beneficial.

The package gurus may be able to offer further advice.

[TenderFoot]

Thanks for the responses.

I'll try your suggestions but lack of internet access means printing this page and hope that terminal launches (or can drop a level).

[TenderFoot]

I am unable to copy and paste top output but taking notes the first 3 cpu hoggers accounting for ~70%

Code: Select all

message+        >    dbusdaemon
root            >    NetworkManager
root            >    syslogd

sudo apt-get install (given lack of wifi) produces

Code: Select all

/usr/bin/sudo must be owned by uid 0 and have the setuid bit set

[entropyfoe]

message+ > dbusdaemon
root > NetworkManager
root > syslogd

Those don't seem like they should use 70% CPU. Which machine from your signature are you seeing this on?
not sure about the dbus stuff,maybe this?
http://codeverge.com/opensuse.org.help. ... pu/1918844

But syslogd? Maybe look into /var/log/syslog (I think as root) to see if it is filling with some kind of errors???

Why would network manager be so loaded? The network connection, it can be full, but the manager? Is this a wifi connection?

[Stevo]

Odds are it's particular to your machine, not due to updates that many others have already installed. Can you boot with to a live session and check the health of your hard drive with either smartmontools or gsmartcontrol?

[TenderFoot]

The smart report on the hdd is healthy. I don't have sufficient access for further forensics from within or without even as root.

In the circumstances I'll reinstall from pre-update snapshot, update again (having sorted gpg first) then see how it goes from there...

[TenderFoot]

On 23rd, reinstalled from snapshot created on 16th prior to updating. Immediately updated fresh install.

Slight(?) differences between the experiences, mostly with gpg.

On the first occasion (16th Nov) it was (apparently!) resolved by running Checkaptgpg from MX Tools.

With this install that was not successful yet trying again from terminal did not report any errors. So this time decided to update antix-archive-keyring (20015.3.14) to 20017.3.14 first then reload which seemed to relieve the constipation! Yet the package count was the same. I didn't observe whether this occurred the first time but noted that 4 packages were to be removed

Code: Select all

mx-broadcom-manager to be removed
mx-debian-backport-installer
mx-panel-orientation
mx-test-repo-installer

In the meantime all seems to be running smoothly once more....