| 1 |
* If this is *not* the last SELinux module package being installed, |
| 2 |
* then you can safely ignore this as the reloads will be retried |
| 3 |
* with other, recent modules. |
| 4 |
* |
| 5 |
* If it is the last SELinux module package being installed however, |
| 6 |
* then it is advised to look at the error above and take appropriate |
| 7 |
* action since the new SELinux policies are not loaded until the |
| 8 |
* command finished succesfully. |
| 9 |
* |
| 10 |
* To reload, run the following command from within /usr/share/selinux/targeted: |
| 11 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
| 12 |
* or |
| 13 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
| 14 |
* depending on if you need the unconfined domain loaded as well or not. |
| 15 |
|
| 16 |
* Messages for package sec-policy/selinux-mandb-2.20170805-r3: |
| 17 |
|
| 18 |
* SELinux module load failed. Trying full reload... |
| 19 |
* Failed to reload SELinux policies. |
| 20 |
* |
| 21 |
* If this is *not* the last SELinux module package being installed, |
| 22 |
* then you can safely ignore this as the reloads will be retried |
| 23 |
* with other, recent modules. |
| 24 |
* |
| 25 |
* If it is the last SELinux module package being installed however, |
| 26 |
* then it is advised to look at the error above and take appropriate |
| 27 |
* action since the new SELinux policies are not loaded until the |
| 28 |
* command finished succesfully. |
| 29 |
* |
| 30 |
* To reload, run the following command from within /usr/share/selinux/strict: |
| 31 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
| 32 |
* or |
| 33 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
| 34 |
* depending on if you need the unconfined domain loaded as well or not. |
| 35 |
* SELinux module load failed. Trying full reload... |
| 36 |
* Failed to reload SELinux policies. |
| 37 |
* |
| 38 |
* If this is *not* the last SELinux module package being installed, |
| 39 |
* then you can safely ignore this as the reloads will be retried |
| 40 |
* with other, recent modules. |
| 41 |
* |
| 42 |
* If it is the last SELinux module package being installed however, |
| 43 |
* then it is advised to look at the error above and take appropriate |
| 44 |
* action since the new SELinux policies are not loaded until the |
| 45 |
* command finished succesfully. |
| 46 |
* |
| 47 |
* To reload, run the following command from within /usr/share/selinux/targeted: |
| 48 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
| 49 |
* or |
| 50 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
| 51 |
* depending on if you need the unconfined domain loaded as well or not. |
| 52 |
|
| 53 |
* Messages for package sec-policy/selinux-openrc-2.20170805-r3: |
| 54 |
|
| 55 |
* SELinux module load failed. Trying full reload... |
| 56 |
* Failed to reload SELinux policies. |
| 57 |
* |
| 58 |
* If this is *not* the last SELinux module package being installed, |
| 59 |
* then you can safely ignore this as the reloads will be retried |
| 60 |
* with other, recent modules. |
| 61 |
* |
| 62 |
* If it is the last SELinux module package being installed however, |
| 63 |
* then it is advised to look at the error above and take appropriate |
| 64 |
* action since the new SELinux policies are not loaded until the |
| 65 |
* command finished succesfully. |
| 66 |
* |
| 67 |
* To reload, run the following command from within /usr/share/selinux/strict: |
| 68 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
| 69 |
* or |
| 70 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
| 71 |
* depending on if you need the unconfined domain loaded as well or not. |
| 72 |
* SELinux module load failed. Trying full reload... |
| 73 |
* Failed to reload SELinux policies. |
| 74 |
* |
| 75 |
* If this is *not* the last SELinux module package being installed, |
| 76 |
* then you can safely ignore this as the reloads will be retried |
| 77 |
* with other, recent modules. |
| 78 |
* |
| 79 |
* If it is the last SELinux module package being installed however, |
| 80 |
* then it is advised to look at the error above and take appropriate |
| 81 |
* action since the new SELinux policies are not loaded until the |
| 82 |
* command finished succesfully. |
| 83 |
* |
| 84 |
* To reload, run the following command from within /usr/share/selinux/targeted: |
| 85 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
| 86 |
* or |
| 87 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
| 88 |
* depending on if you need the unconfined domain loaded as well or not. |
| 89 |
|
| 90 |
* Messages for package sec-policy/selinux-shutdown-2.20170805-r3: |
| 91 |
|
| 92 |
* SELinux module load failed. Trying full reload... |
| 93 |
* Failed to reload SELinux policies. |
| 94 |
* |
| 95 |
* If this is *not* the last SELinux module package being installed, |
| 96 |
* then you can safely ignore this as the reloads will be retried |
| 97 |
* with other, recent modules. |
| 98 |
* |
| 99 |
* If it is the last SELinux module package being installed however, |
| 100 |
* then it is advised to look at the error above and take appropriate |
| 101 |
* action since the new SELinux policies are not loaded until the |
| 102 |
* command finished succesfully. |
| 103 |
* |
| 104 |
* To reload, run the following command from within /usr/share/selinux/strict: |
| 105 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
| 106 |
* or |
| 107 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
| 108 |
* depending on if you need the unconfined domain loaded as well or not. |
| 109 |
* SELinux module load failed. Trying full reload... |
| 110 |
* Failed to reload SELinux policies. |
| 111 |
* |
| 112 |
* If this is *not* the last SELinux module package being installed, |
| 113 |
* then you can safely ignore this as the reloads will be retried |
| 114 |
* with other, recent modules. |
| 115 |
* |
| 116 |
* If it is the last SELinux module package being installed however, |
| 117 |
* then it is advised to look at the error above and take appropriate |
| 118 |
* action since the new SELinux policies are not loaded until the |
| 119 |
* command finished succesfully. |
| 120 |
* |
| 121 |
* To reload, run the following command from within /usr/share/selinux/targeted: |
| 122 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
| 123 |
* or |
| 124 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
| 125 |
* depending on if you need the unconfined domain loaded as well or not. |
| 126 |
|
| 127 |
* Messages for package sys-apps/sysvinit-2.88-r9: |
| 128 |
|
| 129 |
* The last/lastb/mesg/mountpoint/sulogin/utmpdump/wall tools have been moved to |
| 130 |
* sys-apps/util-linux. The pidof tool has been moved to sys-process/procps. |
| 131 |
|
| 132 |
* Messages for package sys-libs/glibc-2.25-r9: |
| 133 |
|
| 134 |
* Defaulting /etc/host.conf:multi to on |
| 135 |
* Generating all locales; edit /etc/locale.gen to save time/space |
| 136 |
|
| 137 |
* Messages for package sys-apps/util-linux-2.30.2: |
| 138 |
|
| 139 |
* The mesg/wall/write tools have been disabled due to USE=-tty-helpers. |
| 140 |
* The agetty util now clears the terminal by default. You |
| 141 |
* might want to add --noclear to your /etc/inittab lines. |
| 142 |
|
| 143 |
* Messages for package sys-apps/man-db-2.7.6.1-r2: |
| 144 |
|
| 145 |
* Defaulting to USE=gdbm due to ambiguous berkdb/gdbm USE flag settings |
| 146 |
|
| 147 |
* Messages for package sys-apps/openrc-0.34.11: |
| 148 |
|
| 149 |
* Auto-adding 'termencoding' service to your boot runlevel |
| 150 |
* Auto-adding 'sysfs' service to your sysinit runlevel |
| 151 |
* Auto-adding 'loopback' service to your boot runlevel |
| 152 |
* Auto-adding 'binfmt' service to your boot runlevel |
| 153 |
* Auto-adding 'mtab' service to your boot runlevel |
| 154 |
|
| 155 |
* Messages for package net-misc/netifrc-0.5.1: |
| 156 |
|
| 157 |
* The network configuration scripts will use dhcp by |
| 158 |
* default to set up your interfaces. |
| 159 |
* If you need to set up something more complete, see |
| 160 |
* //usr/share/doc/netifrc-0.5.1/README |
| 161 |
|
| 162 |
* Messages for package sys-fs/eudev-3.1.5: |
| 163 |
|
| 164 |
* Unable to find kernel sources at /usr/src/linux |
| 165 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
| 166 |
* |
| 167 |
* For more information on eudev on Gentoo, writing udev rules, and |
| 168 |
* fixing known issues visit: https://wiki.gentoo.org/wiki/Eudev |
| 169 |
|
| 170 |
* Messages for package sys-fs/udev-init-scripts-32: |
| 171 |
|
| 172 |
* Adding udev to the sysinit runlevel |
| 173 |
* Adding udev-trigger to the sysinit runlevel |
| 174 |
|
| 175 |
* Messages for package dev-libs/glib-2.50.3-r1: |
| 176 |
|
| 177 |
* Unable to find kernel sources at /usr/src/linux |
| 178 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
| 179 |
15 Jan 2018 20:04:18 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1 |
| 180 |
15 Jan 2018 20:04:18 UTC: ERROR : CatalystError: Stage build aborting due to error. |
| 181 |
15 Jan 2018 20:04:18 UTC: ERROR : Exception running action sequence run_local |
| 182 |
Traceback (most recent call last): |
| 183 |
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1354, in run_local |
| 184 |
env=self.env) |
| 185 |
File "/usr/lib64/python3.5/site-packages/catalyst/support.py", line 54, in cmd |
| 186 |
print_traceback=False) |
| 187 |
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1 |
| 188 |
|
| 189 |
During handling of the above exception, another exception occurred: |
| 190 |
|
| 191 |
Traceback (most recent call last): |
| 192 |
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1454, in run |
| 193 |
getattr(self, x)() |
| 194 |
File "/usr/lib64/python3.5/site-packages/catalyst/base/stagebase.py", line 1363, in run_local |
| 195 |
print_traceback=False) |
| 196 |
catalyst.support.CatalystError: Stage build aborting due to error. |
| 197 |
15 Jan 2018 20:04:18 UTC: NOTICE : Cleaning up... Running unbind() |
| 198 |
Command exited with non-zero status 2 |
| 199 |
2101.80user 502.29system 35:43.26elapsed 121%CPU (0avgtext+0avgdata 325088maxresident)k |
| 200 |
2960inputs+10590704outputs (4major+284534765minor)pagefaults 0swaps |
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
Full build log at /home/release/tmp/run/catalyst-auto.20180115T030001Z.RaCxij/log/hardened_stage3-selinux.log |
Archives