On Thursday 09 May 2019 08:20:11 pm Chris Hassell wrote: > That's pretty bonkers. There's nothing in the setup that I know of > that's been changed. Never happened to me. > > Try a "pstree -phul" to see if you can find wth it was trying to do. > Did htop show something spinning ... or a specific process going nuts? > > On 5/9/19 4:50 PM, Gene Heskett wrote: > > On Thursday 09 May 2019 04:58:20 pm Gene Heskett wrote: > >> On Thursday 09 May 2019 04:35:40 pm Chris Hassell wrote: > >>> > >>> amandabackup:x:112:65534::/home/amandabackup:/usr/sbin/nologin > >>> > >>> That's what I have for amandabackup. A no-frills-nothing and no > >>> password user. Don't get why it can't be a dup of your other one. > >>> Hrm.... > >>> > >>> Looks like the rest of the build was happy enough from the parts > >>> you gave. > >>> > >>> On 5/9/19 12:26 PM, Gene Heskett wrote: > >>> > >>> > >>> And, I'm looking at 4 debs: > >>> amanda@coyote:~/amanda$ ls -l *.deb > >>> -rw-r--r-- 1 amanda amanda 1298594 May 9 14:48 > >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> -rw-r--r-- 1 amanda amanda 101638 May 9 14:48 > >>> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> -rw-r--r-- 1 amanda amanda 2085650 May 9 14:48 > >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> -rw-r--r-- 1 amanda amanda 140310 May 9 14:48 > >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> > >>> Those are a good sign too. > >>> > >>> root@coyote:amanda$ dpkg -i *.deb > >>> > >>> Selecting previously unselected package amanda-backup-client. > >>> dpkg: regarding > >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> containing amanda-backup-client: > >>> amanda-backup-client conflicts with amanda-client > >>> amanda-client (version 1:3.3.9-5) is present and installed. > >>> > >>> dpkg: error processing archive > >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> (--install): conflicting packages - not installing > >>> amanda-backup-client > >>> > >>> > >>> One old package is still installed... and conflicts, so it needs a > >>> 'dpkg -r amanda-client'. > >>> > >>> Selecting previously unselected package > >>> amanda-backup-client-dbgsym. (Reading database ... 267815 files > >>> and directories currently installed.) Preparing to unpack > >>> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> ... Unpacking amanda-backup-client-dbgsym > >>> (3.5.1.git.19364c7b-1Debian99) ... > >>> > >>> Selecting previously unselected package amanda-backup-server. > >>> dpkg: regarding > >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> containing amanda-backup-server: > >>> amanda-backup-server conflicts with amanda-client > >>> amanda-client (version 1:3.3.9-5) is present and installed. > >>> > >>> dpkg: error processing archive > >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> (--install): conflicting packages - not installing > >>> amanda-backup-server > >>> > >>> Same problem, different attempt to install the server file instead > >>> and it refused. > >>> > >>> Selecting previously unselected package > >>> amanda-backup-server-dbgsym. Preparing to unpack > >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> ... Unpacking amanda-backup-server-dbgsym > >>> (3.5.1.git.19364c7b-1Debian99) ... dpkg: error processing archive > >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> (--install): > >>> trying to > >>> overwrite > >>> '/usr/lib/debug/.build-id/06/a6d45701283ff745c5ea6b44c461817e1288a > >>>5. de bug', which is also in package amanda-backup-client-dbgsym > >>> 3.5.1.git.19364c7b-1Debian99 > >>> > >>> Ahh... both the server and client packages can't be installed > >>> together and the same would go for its debug files. > >>> > >>> May want to run 'dpkg -l | grep amanda' to see what's on there and > >>> take off things that are old or that got in without cooperating > >>> yet. > >>> > >>> dpkg-deb: error: subprocess paste was killed by signal (Broken > >>> pipe) dpkg: dependency problems prevent configuration of > >>> amanda-backup-client-dbgsym: > >>> amanda-backup-client-dbgsym depends on amanda-backup-client (= > >>> 3.5.1.git.19364c7b-1Debian99); however: > >>> Package amanda-backup-client is not installed. > >>> > >>> dpkg: error processing package amanda-backup-client-dbgsym > >>> (--install): dependency problems - leaving unconfigured > >>> Errors were encountered while processing: > >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> > >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb > >>> amanda-backup-client-dbgsym > >>> > >>> > >>> That seems to be the sum of it: remove the old and install the > >>> *backup-server*deb files only. > >>> > >>> The only amanda stuff was /usr/local/etc/amanda/DAILY copied from > >>> the old disk to preserve my system, and about 20 files of the old > >>> amanda install in /usr/local/lib/amanda, all dated from Jan 2017 > >>> so they aren't precious now. But all the old installs using > >>> amanda's own Makefile, simply overwrote them instead of having a > >>> litter of calves. > >>> > >>> Kittens, calves, or piglets ... package systems are more > >>> consistent and complain if they leave their room messy. Much > >>> more uptight ... but then they get the job done with less > >>> guesswork. > >>> > >>> So I nuked what I could find of the january 2017 install the at > >>> may have been copied to the new drive. Getting essentially the > >>> same message from > >>> > >>> dpkg -i *.deb > >>> > >>> WTH is wrong now? Your turn Chris. > >>> > >>> That's what it is: cleaning is good but the meta-files (a database > >>> of what's in your linux system) have conflicts in them. Clean up > >>> the old "amanda-client" (using dpkg or apt-get remove > >>> amanda-client) and you'll probably be in better shape to install > >>> the new again. > >>> > >>> A minimal client-only system is great ... but you need a server > >>> system it seems. One or the other, at least. > >> > >> Both, this machine gets backed up too. > >> > >> I ewnt thru a couple cycles ov apt remove, then apt autoremove. and > >> the server start to install, but it been stuck at: > >> > >> root@coyote:amanda$ dpkg -i > >> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb > >> (Reading database ... 265705 files and directories currently > >> installed.) Preparing to unpack > >> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb ... > >> Unpacking amanda-backup-server (3.5.1.git.19364c7b-1Debian99) ... > >> Setting up amanda-backup-server (3.5.1.git.19364c7b-1Debian99) ... > >> for about 10 minutes now. > > > > Make it 3+ hours , so I killed it with htop since a ctl+c didn't. > > > > I might mess with it tomorrow, but this is obviously not ready for > > prime time yet. > > I may have found the showsropper. Wandering thru the generated files I came across some .png's, since I was doing the wandering with mc, when I hit a return on one of the achived png's, mc called gimp-2.8 to display it. Bad dog, no biscuit, gimp, scans for plugins, gets to xsane and locks, no progress, no cpu used. sane and xsane I have not succeeded in making them run yet and I will proably have to reboot to get rid of the attempts to run them as they do not respond to a SIGKILL from a root session of htop. However, gimp ran ok once I had SIGKILLed its attemps to contan xsane and scanimage -L, and I got my mc session back once gimp exited.
So I've got to figure out why sane is locking up. I have a bastard printer/scanner, a brother MFC-J6920DW, a monster that can handle 11x17 paper in both the printer and scanner although not thru the ADF it has. And in stretch, using the brother drivers I have managed to get the printer to work but I don't think sanes backends include a "net". The printer driver is setup to drive it at its local ipv4 address, but sane I think is looking for it on the usb buss. So I plugged that cable back in and it shows up in an lsusb -v: but scanimage -L locks up tight useing zero cpu and is unkillable, I'll have to reboot to get rid of it. This kernel is a preempt-rt kernel, and doesn't have some of a normal kernels bells and whistles, like usbhid-ups is missing, and that speaks to my ups. But since that too short usb cable wasn't plugged in, it may be that the driver installer didn't find the scanner. So I may have to rerun the installer again. Maybe, istr the scanner worked when only the cat5 was plugged in before with a more normal kernel. And synaptic just asked me to cleanup the cache with a dpkg --configure -a, which will make me reboot as its now locked up trying to configure amanda-backup-server. But I was able to kill it and run dpkg -r amanda-backup-server, so now syanaptic can run and its got about a dozen libs to update, so when its done and I have sent this, reboot time. > >>> Copyright 2019 by Maurice E. Heskett > >>> Cheers, Gene Heskett > >>> > >>> > >>> Hope this helps out. > >> > >> Copyright 2019 by Maurice E. Heskett > >> Cheers, Gene Heskett > > > > Copyright 2019 by Maurice E. Heskett > > Cheers, Gene Heskett Copyright 2019 by Maurice E. Heskett Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
