1 |
On 2013-04-15 2:02 PM, Michael Mol <mikemol@×××××.com> wrote: |
2 |
> Were this one of my systems (none of which is in a prod scenario, so |
3 |
> take it with a grain of salt), I'd emerge -e --keep-going @system, and |
4 |
> then emerge --resume a few times. You're stuck in something not unlike a |
5 |
> bootstrap scenario. |
6 |
|
7 |
Ok, well, the DB was down, and I had the data backed up, so last resort, |
8 |
I switched back to the 32bit kernel, rebooted, and started the first |
9 |
emerge -e --keep-going @system, and left for home to continue working on |
10 |
it from there... |
11 |
|
12 |
It was done by the time I got home (about 25 minute drive), so didn't |
13 |
take nearly as long as I had feared - mostly because about 28 packages - |
14 |
most of them the ones that take a really long time (like glib, glibc and |
15 |
gcc) died almost immediately... |
16 |
|
17 |
After the first one completed, I did emerge --resume until everything |
18 |
was emerged. |
19 |
|
20 |
Then I started it all over again, and this time, *everything* recompiled |
21 |
successfully! |
22 |
|
23 |
But, apache still wouldn't start up. The error was PHP related, so, I |
24 |
rebuilt that with emerge -vu (with 5.4 masked so it would pull in the |
25 |
latest update to 5.3 since emerging -vuk (reinstalling the quickpkg'd |
26 |
masked version) didn't work - and this time PHP successfully updated, |
27 |
and presto, everything is now working as expected! |
28 |
|
29 |
I'm still planning on finishing up the new server (had already started |
30 |
on it) and migrating the DB to it, but now the pressure is off. |
31 |
|
32 |
So, massive thanks! to Michael for the suggestion (had heard of totally |
33 |
rebuilding the entire system using -e and --keep-going, but never done |
34 |
it)... and of course, gentoo is amazing. |
35 |
|
36 |
Charles |