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