| 1 |
Hello list, |
| 2 |
|
| 3 |
I'm wearying of this chroot operation, and I must be sounding like a tyro. |
| 4 |
|
| 5 |
The other day emerge started hanging at the end of compilation, thus: |
| 6 |
|
| 7 |
# emerge -1 apache-tools |
| 8 |
|
| 9 |
[,,,] |
| 10 |
make[1]: Leaving directory `/var/tmp/portage/app-admin/apache- |
| 11 |
tools-2.2.25/work/httpd-2.2.25/support' |
| 12 |
>>> Source compiled. |
| 13 |
* Skipping make test/check due to ebuild restriction. |
| 14 |
>>> Test phase [disabled because of RESTRICT=test]: app-admin/apache- |
| 15 |
tools-2.2.25 |
| 16 |
|
| 17 |
>>> Install apache-tools-2.2.25 into /var/tmp/portage/app-admin/apache- |
| 18 |
tools-2.2.25/image/ category app-admin |
| 19 |
make[1]: Entering directory `/var/tmp/portage/app-admin/apache- |
| 20 |
tools-2.2.25/work/httpd-2.2.25/support' |
| 21 |
mkdir /var/tmp/portage/app-admin/apache-tools-2.2.25/image/usr |
| 22 |
mkdir /var/tmp/portage/app-admin/apache-tools-2.2.25/image/usr/sbin |
| 23 |
make[1]: Leaving directory `/var/tmp/portage/app-admin/apache- |
| 24 |
tools-2.2.25/work/httpd-2.2.25/support' |
| 25 |
>>> Completed installing apache-tools-2.2.25 into /var/tmp/portage/app- |
| 26 |
admin/apache-tools-2.2.25/image/ |
| 27 |
|
| 28 |
strip: i686-pc-linux-gnu-strip --strip-unneeded -R .comment -R |
| 29 |
.GCC.command.line -R .note.gnu.gold-version |
| 30 |
usr/sbin/htpasswd |
| 31 |
usr/sbin/ab |
| 32 |
usr/sbin/rotatelogs |
| 33 |
usr/sbin/logresolve |
| 34 |
usr/sbin/htdigest |
| 35 |
usr/sbin/htdbm |
| 36 |
usr/sbin/htcacheclean |
| 37 |
usr/sbin/httxt2dbm |
| 38 |
usr/sbin/checkgid |
| 39 |
>>> Done. |
| 40 |
|
| 41 |
It never comes back from there, not even with a CTRL-C; I have to "kill -9" |
| 42 |
from another Konsole. |
| 43 |
|
| 44 |
Grepping ps for emerge (before the kill!) shows: |
| 45 |
|
| 46 |
20749 pts/1 DN+ 0:03 /usr/bin/python3 /usr/bin/emerge --nospinner -1 |
| 47 |
apache-tools |
| 48 |
|
| 49 |
Man ps says that the D means "uninterruptible sleep (usually IO)" |
| 50 |
|
| 51 |
So far I've done these things: |
| 52 |
|
| 53 |
1. Wiped the whole system and restored from backup (heavy overkill, but I |
| 54 |
wanted everything to be in the same, consistent state). |
| 55 |
2. Run bad-blocks tests on all partitions (though all but / and /boot are in |
| 56 |
logical volumes - I don't know to what extent that will have affected the |
| 57 |
results). |
| 58 |
3. Remerged portage. |
| 59 |
4. Recompiled the kernel, 3.12.13. |
| 60 |
5. Booted previous good kernel,3.10.32. |
| 61 |
6. Emerged natively on the Atom box for which the chroot is a build host. |
| 62 |
|
| 63 |
At various stages I got bizarreness like the kernel panicking at boot on a |
| 64 |
previously good kernel config, before it even switched to the frame buffer; or, |
| 65 |
during shutdown, "exiting from KVM" or some such, even though I've never used |
| 66 |
KVM. |
| 67 |
|
| 68 |
Portage works fine outside the chroot and is at the same version, 2.2.8-r1. It |
| 69 |
has python3 set in package.use in both cases, so I also tried: |
| 70 |
|
| 71 |
7. Removed python3 USE flag from sys-apps/portage. |
| 72 |
|
| 73 |
Is my hardware dying? Or maybe I am. Time to seek intelligent conversation |
| 74 |
down the pub. :-( |
| 75 |
|
| 76 |
-- |
| 77 |
Regards |
| 78 |
Peter |
Archives