1 |
Ok, was just doing a "fsck.ext3 -c -c -C 1 /dev/xvda" from within a |
2 |
rescue OS provided by my VPS provider... and it froze at the middle |
3 |
of it!!! |
4 |
|
5 |
So I guess Gentoo is not responsible after all... I've opened a |
6 |
support ticket with them... I'll let you know how it turns out. |
7 |
|
8 |
Simon |
9 |
|
10 |
On Fri, Jan 7, 2011 at 2:42 PM, Simon <turner25@×××××.com> wrote: |
11 |
> Ok, it actually just "froze" again after the output below... |
12 |
> |
13 |
> ///////////////////////////////////////////// |
14 |
>>>> Emerging (42 of 151) sys-devel/autoconf-2.65-r1 |
15 |
> * autoconf-2.65.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] |
16 |
> * Package: sys-devel/autoconf-2.65-r1 |
17 |
> * Repository: gentoo |
18 |
> * Maintainer: base-system@g.o |
19 |
> * USE: elibc_glibc kernel_linux userland_GNU x86 |
20 |
>>>> Unpacking source... |
21 |
>>>> Unpacking autoconf-2.65.tar.bz2 to /mnt/tmp/portage/sys-devel/autoconf-2.65-r1/work |
22 |
> * Applying autoconf-2.65-AC_TYPE_INT_T.patch ... [ ok ] |
23 |
>>>> Source unpacked in /mnt/tmp/portage/sys-devel/autoconf-2.65-r1/work |
24 |
>>>> Compiling source in /mnt/tmp/portage/sys-devel/autoconf-2.65-r1/work/autoconf-2.65 ... |
25 |
> * econf: updating autoconf-2.65/build-aux/config.guess with |
26 |
> /usr/share/gnuconfig/config.guess |
27 |
> * econf: updating autoconf-2.65/build-aux/config.sub with |
28 |
> /usr/share/gnuconfig/config.sub |
29 |
> ./configure --prefix=/usr --build=i686-pc-linux-gnu |
30 |
> --host=i686-pc-linux-gnu --mandir=/usr/share/man |
31 |
> --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc |
32 |
> --localstatedir=/var/lib --program-suffix=-2.65 |
33 |
> checking for a BSD-compatible install... /usr/bin/install -c |
34 |
> checking whether build environment is sane... yes |
35 |
> checking for a thread-safe mkdir -p... /bin/mkdir -p |
36 |
> checking for gawk... gawk |
37 |
> checking whether make sets $(MAKE)... yes |
38 |
> checking whether /bin/sh -n is known to work... yes |
39 |
> checking for characters that cannot appear in file names... none |
40 |
> checking whether directories can have trailing spaces... yes |
41 |
> checking for expr... /usr/bin/expr |
42 |
> checking for GNU M4 that supports accurate traces... /usr/bin/m4 |
43 |
> checking whether /usr/bin/m4 accepts --gnu... yes |
44 |
> checking how m4 supports trace files... --debugfile |
45 |
> checking for perl... /usr/bin/perl |
46 |
> checking whether /usr/bin/perl Fcntl::flock is implemented... yes |
47 |
> checking for emacs... no |
48 |
> checking for emacs... no |
49 |
> checking where .elc files should go... ${datadir}/emacs/site-lisp |
50 |
> checking for grep that handles long lines and -e... /bin/grep |
51 |
> checking for egrep... /bin/grep -E |
52 |
> checking for a sed that does not truncate output... /bin/sed |
53 |
> checking whether make is case sensitive... yes |
54 |
> configure: creating ./config.status |
55 |
> config.status: creating tests/Makefile |
56 |
> config.status: creating tests/atlocal |
57 |
> config.status: creating man/Makefile |
58 |
> config.status: creating lib/emacs/Makefile |
59 |
> config.status: creating Makefile |
60 |
> config.status: creating doc/Makefile |
61 |
> config.status: creating lib/Makefile |
62 |
> config.status: creating lib/Autom4te/Makefile |
63 |
> config.status: creating lib/autoscan/Makefile |
64 |
> config.status: creating lib/m4sugar/Makefile |
65 |
> config.status: creating lib/autoconf/Makefile |
66 |
> config.status: creating lib/autotest/Makefile |
67 |
> ////////////////////////////////// |
68 |
> |
69 |
> On Fri, Jan 7, 2011 at 2:40 PM, Simon <turner25@×××××.com> wrote: |
70 |
>> Ok, the fsck reported nothing wrong... |
71 |
>> I still got the same bug again... while doing `emerge -e @system`... |
72 |
>> It got stuck right after the ">>> Installing" line below... |
73 |
>> |
74 |
>> Dale, I just checked my python version and it was already 2.6, i set |
75 |
>> it to 2.6 again, just in case, and continued my emerge (the ctrl-z + |
76 |
>> %% worked at this point). |
77 |
>> |
78 |
>> I'll reply here again with the next issue... |
79 |
>> |
80 |
>> Thanks, |
81 |
>> Simon |
82 |
>> |
83 |
>> //////////////////////////////////////////////////////// |
84 |
>>>>> Emerging (35 of 151) sys-devel/binutils-config-1.9-r4 |
85 |
>> * Package: sys-devel/binutils-config-1.9-r4 |
86 |
>> * Repository: gentoo |
87 |
>> * Maintainer: toolchain@g.o |
88 |
>> * USE: elibc_glibc kernel_linux userland_GNU x86 |
89 |
>>>>> Unpacking source... |
90 |
>>>>> Source unpacked in /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/work |
91 |
>>>>> Compiling source in /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/work ... |
92 |
>>>>> Source compiled. |
93 |
>>>>> Test phase [not enabled]: sys-devel/binutils-config-1.9-r4 |
94 |
>> |
95 |
>>>>> Install binutils-config-1.9-r4 into /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/image/ category sys-devel |
96 |
>>>>> Completed installing binutils-config-1.9-r4 into /mnt/tmp/portage/sys-devel/binutils-config-1.9-r4/image/ |
97 |
>> |
98 |
>> ecompressdir: bzip2 -9 /usr/share/man |
99 |
>> |
100 |
>>>>> Installing (35 of 151) sys-devel/binutils-config-1.9-r4 |
101 |
>> \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ |
102 |
>> |
103 |
>> |
104 |
>> |
105 |
>> |
106 |
>> On Fri, Jan 7, 2011 at 1:22 PM, Dale <rdalek1967@×××××.com> wrote: |
107 |
>>> Simon wrote: |
108 |
>>>> |
109 |
>>>> Hi there, |
110 |
>>>> something went wrong during a previous update and now revdep-rebuild |
111 |
>>>> will kind-of freeze around 30%. When it freezes like that, the |
112 |
>>>> hosting company shows one of it's CPU core is used at 100% non-stop |
113 |
>>>> and the rest is idle. I have tried `emerge -e world` and with system, |
114 |
>>>> they all fail similarly. |
115 |
>>>> |
116 |
>>>> I managed to reconfigure it to have a working console and started |
117 |
>>>> the `emerge -e system` from the console. After a while it froze, but |
118 |
>>>> typed a ctrl-z to suspend the process, then %% to resume it and it |
119 |
>>>> "unlocked" it. It often hung like in between two phases of the emerge |
120 |
>>>> process (like after unpacking source, or just before doing the |
121 |
>>>> install, etc). I was able to resume the emerge like that a good dozen |
122 |
>>>> times until now, and now it's really locked, not responding at all... |
123 |
>>>> seems like all 4 cores are used at 100%. |
124 |
>>>> |
125 |
>>>> It hung while emerging perl and I've included the output on the |
126 |
>>>> console below so you can see exactly where it hung. I will now force |
127 |
>>>> a reboot on it and retry emerging just perl, I will reply to the list |
128 |
>>>> with my results of that. |
129 |
>>>> |
130 |
>>> |
131 |
>>> <<SNIP>> |
132 |
>>> |
133 |
>>> Have you enabled python3 by any chance? eselect python list should show 2.6 |
134 |
>>> as the active python. |
135 |
>>> |
136 |
>>> Just a thought. Someone else did this the other day and had troubles. |
137 |
>>> |
138 |
>>> Dale |
139 |
>>> |
140 |
>>> :-) :-) |
141 |
>>> |
142 |
>>> |
143 |
>> |
144 |
> |