Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #245052 > unrolled thread
| Started by | Dennis Wicks <wix@mgssub.com> |
|---|---|
| First post | 2022-02-06 19:20 +0100 |
| Last post | 2022-02-08 10:30 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.user
dpkg --configure -a crashes system Dennis Wicks <wix@mgssub.com> - 2022-02-06 19:20 +0100
Re: dpkg --configure -a crashes system Anders Andersson <pipatron@gmail.com> - 2022-02-08 10:30 +0100
| From | Dennis Wicks <wix@mgssub.com> |
|---|---|
| Date | 2022-02-06 19:20 +0100 |
| Subject | dpkg --configure -a crashes system |
| Message-ID | <DNUiJ-4GA-3@gated-at.bofh.it> |
I can't install/upgrade because I get the message > E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. When I run the dpkg command I get one message > Setting up linux-image-4.19.0-18-amd64 (4.19.208-1) then within a few seconds the system crashes. Any ideas? Is there a log file I can look in that might contain something useful? Any help is appreciated! TIA!! Dennis
[toc] | [next] | [standalone]
| From | Anders Andersson <pipatron@gmail.com> |
|---|---|
| Date | 2022-02-08 10:30 +0100 |
| Message-ID | <DOuYV-mPn-7@gated-at.bofh.it> |
| In reply to | #245052 |
On Sun, Feb 6, 2022 at 7:13 PM Dennis Wicks <wix@mgssub.com> wrote: > > I can't install/upgrade because I get the message > > > E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. > > When I run the dpkg command I get one message > > Setting up linux-image-4.19.0-18-amd64 (4.19.208-1) > > then within a few seconds the system crashes. > > Any ideas? Is there a log file I can look in that might > contain something useful? Any help is appreciated! > > TIA!! > Dennis If I had this problem I would assume a hardware fault - dpkg shouldn't crash the whole system. To debug it I would open up three terminals that you can monitor, running these three: 1. sudo journalctl -f 2. sudo dmesg -Hw 3. sudo dpkg --configure -a (or whatever) Hopefully any of those might give you a clue. If not, check "sudo journalctl -b -1 -e" after the next crash, and see if something was logged.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web