On Wed, 2016-08-03 at 17:43 +0200, Chris Lamb wrote: > Mark, > > Please retain CC's when replying, otherwise we lose history on the > bug > tracker. > > Please could you provide the output of: > > $ ps aux > > .. and also "strace -p" (as root) of the blocked process. > > > > > Of course, reinstalling also resulted in the hang, so I'm just > > giving > > up on it, yanking it as nothing is indicating a dependency on it, > > if > > only the system would let me get it off the machine. Once it is > > off, > > I'll put it back on from scratch, I just need this roadblock out of > > the > > way. > > I understand this is frustrating to you; I am trying to help debug it > which is difficult if I cannot reproduce it myself. > > > Regards, >
I found the problem - the searching for the pid gave me a couple ideas, and with htop in tree format I learned that it was stuck on trying to shut down redis-server properly. Since I'm purging and then reinstalling, with it reporting that it is sitting badly misconfigured, kill -s KILL `pidof redis-server` was sufficient to get it moving. Sounds like a systemd bug - systemctl should have some way of handling a potentially non-responsive server rather than sitting blocked for over 24 hours. Anyhow, the kill allowed the purge to complete, and then both server and tools reinstalled fine. I also learned that nowhere along the way had I installed strace, so that is going on once my system update is done. Chris, thanks for your time and knowledge on this. My programming days were back in the 70s and 80s, and while I did develop multitasking on a 64 KB Atari 6502 computer back in the 80s, I'm much more of a "more informed than the average data entry operator, but not really up-to- date" system user now. I can find the documentation and understand what is happening under the hood, but my days of writing that code have passed me by. My coding days were comparable with Mel as in The Story of Mel, in the Jargon files. Machine code, know which bit is where and what value is stored where.
