| 1 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 296, in ebuild_ipc_main |
| 2 |
return ebuild_ipc.communicate(args) |
| 3 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 71, in communicate |
| 4 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
| 5 |
File "/usr/lib/portage/pym/portage/locks.py", line 103, in lockfile |
| 6 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
| 7 |
File "/usr/lib/portage/pym/portage/__init__.py", line 230, in __call__ |
| 8 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
| 9 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/.ipc_lock' |
| 10 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
| 11 |
* is known to be triggered by things such as failed variable assignments |
| 12 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
| 13 |
* exiting, bash should have displayed an error message above. If bash did |
| 14 |
* not produce an error message above, it's possible that the ebuild has |
| 15 |
* called `exit` when it should have called `die` instead. This behavior |
| 16 |
* may also be triggered by a corrupt bash binary or a hardware problem |
| 17 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
| 18 |
* it appears to occur randomly, then it is likely to be triggered by a |
| 19 |
* hardware problem. If you suspect a hardware problem then you should try |
| 20 |
* some basic hardware diagnostics such as memtest. Please do not report |
| 21 |
* this as a bug unless it is consistently reproducible and you are sure |
| 22 |
* that your bash binary and hardware are functioning properly. |
| 23 |
/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/environment: line 4624: pushd: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build: No such file or directory |
| 24 |
tar: Cowardly refusing to create an empty archive |
| 25 |
Try `tar --help' or `tar --usage' for more information. |
| 26 |
/usr/lib/portage/bin/isolated-functions.sh: line 277: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/logging/other: No space left on device |
| 27 |
* |
| 28 |
/usr/lib/portage/bin/isolated-functions.sh: line 277: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/logging/other: No space left on device |
| 29 |
* Please include /var/tmp/portage/sys-devel/gcc-4.5.3-r2/gcc-build-logs.tar.bz2 in your bug report |
| 30 |
/usr/lib/portage/bin/isolated-functions.sh: line 277: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/logging/other: No space left on device |
| 31 |
* |
| 32 |
/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/environment: line 4629: popd: directory stack empty |
| 33 |
/usr/lib/portage/bin/misc-functions.sh: line 1231: /var/tmp/portage/sys-devel/gcc-4.5.3-r2/.die_hooks: No space left on device |
| 34 |
Traceback (most recent call last): |
| 35 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 299, in <module> |
| 36 |
sys.exit(ebuild_ipc_main(sys.argv[1:])) |
| 37 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 296, in ebuild_ipc_main |
| 38 |
return ebuild_ipc.communicate(args) |
| 39 |
File "/usr/lib/portage/bin/ebuild-ipc.py", line 71, in communicate |
| 40 |
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
| 41 |
File "/usr/lib/portage/pym/portage/locks.py", line 103, in lockfile |
| 42 |
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
| 43 |
File "/usr/lib/portage/pym/portage/__init__.py", line 230, in __call__ |
| 44 |
rval = self._func(*wrapped_args, **wrapped_kwargs) |
| 45 |
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/.ipc_lock' |
| 46 |
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
| 47 |
* behavior is known to be triggered by things such as failed variable |
| 48 |
* assignments (bug #190128) or bad substitution errors (bug #200313). |
| 49 |
* Normally, before exiting, bash should have displayed an error message |
| 50 |
* above. If bash did not produce an error message above, it's possible |
| 51 |
* that the ebuild has called `exit` when it should have called `die` |
| 52 |
* instead. This behavior may also be triggered by a corrupt bash binary or |
| 53 |
* a hardware problem such as memory or cpu malfunction. If the problem is |
| 54 |
* not reproducible or it appears to occur randomly, then it is likely to |
| 55 |
* be triggered by a hardware problem. If you suspect a hardware problem |
| 56 |
* then you should try some basic hardware diagnostics such as memtest. |
| 57 |
* Please do not report this as a bug unless it is consistently |
| 58 |
* reproducible and you are sure that your bash binary and hardware are |
| 59 |
* functioning properly. |
| 60 |
|
| 61 |
* Messages for package sys-libs/timezone-data-2012f 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 sys-apps/coreutils-8.16 merged to /tmp/stage1root/: |
| 67 |
|
| 68 |
* Make sure you run 'hash -r' in your active shells. |
| 69 |
* You should also re-source your shell settings for LS_COLORS |
| 70 |
* changes, such as: source /etc/profile |
| 71 |
|
| 72 |
* Messages for package sys-apps/util-linux-2.21.2 merged to /tmp/stage1root/: |
| 73 |
|
| 74 |
* The agetty util now clears the terminal by default. You |
| 75 |
* might want to add --noclear to your /etc/inittab lines. |
| 76 |
|
| 77 |
* Messages for package sys-libs/glibc-2.15-r3 merged to /tmp/stage1root/: |
| 78 |
|
| 79 |
* Defaulting /etc/host.conf:multi to on |
| 80 |
|
| 81 |
* Messages for package sys-devel/gcc-4.5.3-r2 merged to /tmp/stage1root/: |
| 82 |
|
| 83 |
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
| 84 |
* is known to be triggered by things such as failed variable assignments |
| 85 |
* (bug #190128) or bad substitution errors (bug #200313). Normally, before |
| 86 |
* exiting, bash should have displayed an error message above. If bash did |
| 87 |
* not produce an error message above, it's possible that the ebuild has |
| 88 |
* called `exit` when it should have called `die` instead. This behavior |
| 89 |
* may also be triggered by a corrupt bash binary or a hardware problem |
| 90 |
* such as memory or cpu malfunction. If the problem is not reproducible or |
| 91 |
* it appears to occur randomly, then it is likely to be triggered by a |
| 92 |
* hardware problem. If you suspect a hardware problem then you should try |
| 93 |
* some basic hardware diagnostics such as memtest. Please do not report |
| 94 |
* this as a bug unless it is consistently reproducible and you are sure |
| 95 |
* that your bash binary and hardware are functioning properly. |
| 96 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
| 97 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
| 98 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
| 99 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
| 100 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
| 101 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
| 102 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
| 103 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
| 104 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
| 105 |
umount: /var/tmp/catalyst/tmp/default/stage1-ia64-20121106/tmp/kerncache: not mounted |
| 106 |
cannot open /etc/mtab.tmp (No space left on device) - mtab not updated |
| 107 |
|
| 108 |
!!! catalyst: run script failed. |
| 109 |
|
| 110 |
|
| 111 |
Traceback (most recent call last): |
| 112 |
File "modules/generic_stage_target.py", line 1199, in run_local |
| 113 |
"run script failed.",env=self.env) |
| 114 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 542, in cmd |
| 115 |
raise CatalystError,myexc |
| 116 |
CatalystError |
| 117 |
None |
| 118 |
|
| 119 |
!!! catalyst: Stage build aborting due to error. |
| 120 |
|
| 121 |
/proc is still mounted; performing auto-bind-umount... !!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20121106//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-20121106/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-20121106/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-20121106//tmp/kerncache |
| 131 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20121106//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-20121106/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-20121106/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-20121106//tmp/stage1root/proc |
| 141 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20121106//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-20121106/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-20121106/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-20121106//usr/portage |
| 151 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20121106//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-20121106/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-20121106/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-20121106//dev |
| 161 |
!!! catalyst: First attempt to unmount: /var/tmp/catalyst/tmp/default/stage1-ia64-20121106//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-20121106/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-20121106//proc |
| 168 |
|
| 169 |
Traceback (most recent call last): |
| 170 |
File "modules/generic_stage_target.py", line 1259, in run |
| 171 |
apply(getattr(self,x)) |
| 172 |
File "modules/generic_stage_target.py", line 1204, 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 614, in mount_safety_check |
| 182 |
self.unbind() |
| 183 |
File "modules/generic_stage_target.py", line 940, 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 208, in build_target |
| 192 |
mytarget.run() |
| 193 |
File "modules/generic_stage_target.py", line 1261, in run |
| 194 |
self.mount_safety_check() |
| 195 |
File "modules/generic_stage_target.py", line 620, 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-20121106/.catalyst_lock' |
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
Full build log at /catalyst-auto.6180/log/stage1.log |
Archives