1 |
File "/usr/lib/portage/pym/portage/__init__.py", line 215, in __call__ |
2 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
3 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/.ipc_lock' |
4 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
5 |
* is known to be triggered by things such as failed variable assignments |
6 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
7 |
* exiting, bash should have displayed an error message above. If bash did |
8 |
* not produce an error message above, it's possible that the ebuild has |
9 |
* called `exit` when it should have called `die` instead. This behavior |
10 |
* may also be triggered by a corrupt bash binary or a hardware problem |
11 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
12 |
* it appears to occur randomly, then it is likely to be triggered by a |
13 |
* hardware problem. If you suspect a hardware problem then you should try |
14 |
* some basic hardware diagnostics such as memtest. Please do not report |
15 |
* this as a bug unless it is consistently reproducible and you are sure |
16 |
* that your bash binary and hardware are functioning properly. |
17 |
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/environment: line 4699: pushd: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build: No such file or directory |
18 |
tar: Cowardly refusing to create an empty archive |
19 |
Try `tar --help' or `tar --usage' for more information. |
20 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/other: No space left on device |
21 |
* |
22 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/other: No space left on device |
23 |
* Please include /var/tmp/portage/sys-devel/gcc-4.5.3-r1/gcc-build-logs.tar.bz2 in your bug report |
24 |
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/other: No space left on device |
25 |
* |
26 |
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/environment: line 4704: popd: directory stack empty |
27 |
/usr/lib/portage/bin/misc-functions.sh: line 978: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/.die_hooks: No space left on device |
28 |
Traceback (most recent call last): |
29 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 276, in <module> |
30 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
31 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main |
32 |
return ebuild_ipc.communicate(args) |
33 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 63, in communicate |
34 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
35 |
File "/usr/lib/portage/pym/portage/locks.py", line 73, in lockfile |
36 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
37 |
File "/usr/lib/portage/pym/portage/__init__.py", line 215, in __call__ |
38 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
39 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/.ipc_lock' |
40 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
41 |
* behavior is known to be triggered by things such as failed variable |
42 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
43 |
* Normally, before exiting, bash should have displayed an error message |
44 |
* above. If bash did not produce an error message above, it's possible |
45 |
* that the ebuild has called `exit` when it should have called `die` |
46 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
47 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
48 |
* not reproducible or it appears to occur randomly, then it is likely to |
49 |
* be triggered by a hardware problem. If you suspect a hardware problem |
50 |
* then you should try some basic hardware diagnostics such as memtest. |
51 |
* Please do not report this as a bug unless it is consistently |
52 |
* reproducible and you are sure that your bash binary and hardware are |
53 |
* functioning properly. |
54 |
|
55 |
* Messages for package sys-apps/coreutils-8.7 merged to /tmp/stage1root/: |
56 |
* Make sure you run 'hash -r' in your active shells. |
57 |
* You should also re-source your shell settings for LS_COLORS |
58 |
* changes, such as: source /etc/profile |
59 |
|
60 |
|
61 |
* Messages for package sys-libs/timezone-data-2011n merged to /tmp/stage1root/: |
62 |
|
63 |
* You do not have TIMEZONE set in /tmp/stage1root/etc/timezone. |
64 |
* Setting /tmp/stage1root/etc/localtime to Factory. |
65 |
|
66 |
* Messages for package net-misc/wget-1.12-r3 merged to /tmp/stage1root/: |
67 |
* The /etc/wget/wgetrc file has been relocated to /etc/wgetrc |
68 |
|
69 |
|
70 |
* Messages for package sys-devel/gcc-4.5.3-r1 merged to /tmp/stage1root/: |
71 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
72 |
* is known to be triggered by things such as failed variable assignments |
73 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
74 |
* exiting, bash should have displayed an error message above. If bash did |
75 |
* not produce an error message above, it's possible that the ebuild has |
76 |
* called `exit` when it should have called `die` instead. This behavior |
77 |
* may also be triggered by a corrupt bash binary or a hardware problem |
78 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
79 |
* it appears to occur randomly, then it is likely to be triggered by a |
80 |
* hardware problem. If you suspect a hardware problem then you should try |
81 |
* some basic hardware diagnostics such as memtest. Please do not report |
82 |
* this as a bug unless it is consistently reproducible and you are sure |
83 |
* that your bash binary and hardware are functioning properly. |
84 |
|
85 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
86 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
87 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
88 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
89 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
90 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
91 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
92 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
93 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
94 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
95 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/var/tmp/ccache: not mounted |
96 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
97 |
|
98 |
!!! catalyst: run script failed. |
99 |
|
100 |
|
101 |
Traceback (most recent call last): |
102 |
File "modules/generic_stage_target.py", line 1207, in run_local |
103 |
"run script failed.",env=self.env) |
104 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 542, in cmd |
105 |
raise CatalystError,myexc |
106 |
CatalystError |
107 |
None |
108 |
|
109 |
!!! catalyst: Stage build aborting due to error. |
110 |
|
111 |
/proc is still mounted; performing auto-bind-umount... !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//var/tmp/ccache failed. |
112 |
!!! catalyst: Killing any pids still running in the chroot |
113 |
Checking for processes running in chroot and killing them. |
114 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
115 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/var/tmp/ccache: not mounted |
116 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
117 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
118 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/tmp/kerncache: not mounted |
119 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
120 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//var/tmp/ccache |
121 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//tmp/kerncache failed. |
122 |
!!! catalyst: Killing any pids still running in the chroot |
123 |
Checking for processes running in chroot and killing them. |
124 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
125 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/tmp/kerncache: not mounted |
126 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
127 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
128 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/tmp/stage1root/proc: not mounted |
129 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
130 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//tmp/kerncache |
131 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//tmp/stage1root/proc failed. |
132 |
!!! catalyst: Killing any pids still running in the chroot |
133 |
Checking for processes running in chroot and killing them. |
134 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
135 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/tmp/stage1root/proc: not mounted |
136 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
137 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
138 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/usr/portage: not mounted |
139 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
140 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//tmp/stage1root/proc |
141 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//usr/portage failed. |
142 |
!!! catalyst: Killing any pids still running in the chroot |
143 |
Checking for processes running in chroot and killing them. |
144 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
145 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/usr/portage: not mounted |
146 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
147 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
148 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/dev: not mounted |
149 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
150 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//usr/portage |
151 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//dev failed. |
152 |
!!! catalyst: Killing any pids still running in the chroot |
153 |
Checking for processes running in chroot and killing them. |
154 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
155 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/dev: not mounted |
156 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
157 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
158 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/proc: not mounted |
159 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
160 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//dev |
161 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//proc failed. |
162 |
!!! catalyst: Killing any pids still running in the chroot |
163 |
Checking for processes running in chroot and killing them. |
164 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
165 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110/proc: not mounted |
166 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
167 |
!!! catalyst: Couldn't umount bind mount: /var/tmp/catalyst/tmp/default/stage1-ia64-20120110//proc |
168 |
|
169 |
Traceback (most recent call last): |
170 |
File "modules/generic_stage_target.py", line 1263, in run |
171 |
apply(getattr(self,x)) |
172 |
File "modules/generic_stage_target.py", line 1212, in run_local |
173 |
raise CatalystError,"Stage build aborting due to error." |
174 |
CatalystError |
175 |
None |
176 |
|
177 |
!!! catalyst: Couldn't umount one or more bind-mounts; aborting for safety. |
178 |
|
179 |
|
180 |
Traceback (most recent call last): |
181 |
File "modules/generic_stage_target.py", line 609, in mount_safety_check |
182 |
self.unbind() |
183 |
File "modules/generic_stage_target.py", line 936, in unbind |
184 |
"Couldn't umount one or more bind-mounts; aborting for safety." |
185 |
CatalystError |
186 |
None |
187 |
|
188 |
!!! catalyst: Unable to auto-unbind /proc |
189 |
|
190 |
Traceback (most recent call last): |
191 |
File "/usr/lib/catalyst/catalyst", line 209, in build_target |
192 |
mytarget.run() |
193 |
File "modules/generic_stage_target.py", line 1265, in run |
194 |
self.mount_safety_check() |
195 |
File "modules/generic_stage_target.py", line 615, in mount_safety_check |
196 |
raise CatalystError, "Unable to auto-unbind "+x |
197 |
CatalystError |
198 |
!!! catalyst: Error encountered during run of target stage1 |
199 |
Catalyst aborting.... |
200 |
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-ia64-20120110/.catalyst_lock' |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.2430/log/stage1.log |