dpkg prob Rpi3

Hello, every now and then i run in a prob with dpkg when doing updates. It´s always to be solved by dpkg --configure -a', but i would like to analyze it and remove the cause. How can i do that?

Thanx in advance, Klaus

Zitat von KM0201

That command comes up when dpkg is interrupted and does not complete an upgrade process. Do you have a cron job to shut the server down after it updates, or are you powering off after upgrades for some reason?

If it is happening regularly to you, it sounds like aren't finishing before the machine is shut down.

Thank you for answering. But I am not aware to have any cron job, at least none installed by myself. And the system is on 24/7....

Zitat von votdev

You may have a look into /var/log/apt/term.log and /var/log/dpkg.log if there is a hint what happens.

Could not see a hint. Both with date from today. But i realized, dpkg has 0644 rights, while term.log has 0640. Could that be a hint?

Btw, tried to upload logs, but failed (The file extension is invalid.)

Still got this update prob.´To give some further informations to potential helpers:

When updating via gui process will crash (loosing connection) at "Setting up Salt environment". Dashboards "System Information" shows update itself installed, however, it still announces "Update available".

Annoying being forced to run dpkg --configure -a after every update...

update: Dashboards "System Information" changed status after some time, "No update available". So, everything's fine but the "crash" (loosing connection) while updating. Maybe it's due to Rpi3 limitations needing more time to write?

update2. Confusing. Dashboards "System Information" showed update as installed (6.7.1-2 (Shaitan), but email notifications still warned about updates available and

E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to co=
rrect the problem.

So i logged in and ran 'dpkg --configure -a'. It crashed. Power off/Power on: no boot.

Glad to have a second sdcard being halfway up to date. But obviously i got a real problem.

Could anyone be so kind to help me with troubleshooting?

Am I asking the wrong questions here? It can't be due to a lack of politeness that no one responds...

If someone should be found, here is the latest status:

I have run a search in the gui because of the reported updates. Very long lasting, and in between, it looked like a crash (several points in the dashboard completely red). But then came to end, dashboard was ok.

The updates themselves I then made via putty, to see possible errors immediately. I discovered the following:

Setting up salt-minion (3006.0+ds-1+191.1) ...
salt-minion.service is a disabled or a static unit not running, not starting it.
Setting up openmediavault (6.8.0-1) ...

I don't know if this could have anything to do with my problem....

Thank you for answering, Chente. Just writing alone here all the time is a bit lonely

My second Rpi is a 2b. Running omv6 without probs, it contains docker for pihole e.g.

The one with that dpkg prob (Rpi3b) has indeed some more docker containers running (on SSD). Do you think, that's the point?

Zitat von chente

I'm not an expert on Raspberrys, there are people here who know a lot more about Raspberrys than I do. I'm only saying this from what I've been able to read.

Thank you for that.

I could have a try to stop containers in compose before executing updates

I suppose I found a solution without making any changes to my configuration (e.g. running docker images). Maybe it is useful for other rpi users.

I avoid to execute updates shown in the gui directly . First I run the update search. The installation is done afterwards.

So basically apt update and apt upgrade separately.

Since I choose this procedure, no more problems with crashing dpkg.