1 |
* then it is advised to look at the error above and take appropriate |
2 |
* action since the new SELinux policies are not loaded until the |
3 |
* command finished succesfully. |
4 |
* |
5 |
* To reload, run the following command from within /usr/share/selinux/strict: |
6 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
7 |
* or |
8 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
9 |
* depending on if you need the unconfined domain loaded as well or not. |
10 |
* SELinux module load failed. Trying full reload... |
11 |
* Failed to reload SELinux policies. |
12 |
* |
13 |
* If this is *not* the last SELinux module package being installed, |
14 |
* then you can safely ignore this as the reloads will be retried |
15 |
* with other, recent modules. |
16 |
* |
17 |
* If it is the last SELinux module package being installed however, |
18 |
* then it is advised to look at the error above and take appropriate |
19 |
* action since the new SELinux policies are not loaded until the |
20 |
* command finished succesfully. |
21 |
* |
22 |
* To reload, run the following command from within /usr/share/selinux/targeted: |
23 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
24 |
* or |
25 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
26 |
* depending on if you need the unconfined domain loaded as well or not. |
27 |
* Messages for package sec-policy/selinux-shutdown-2.20170805-r3: |
28 |
* SELinux module load failed. Trying full reload... |
29 |
* Failed to reload SELinux policies. |
30 |
* |
31 |
* If this is *not* the last SELinux module package being installed, |
32 |
* then you can safely ignore this as the reloads will be retried |
33 |
* with other, recent modules. |
34 |
* |
35 |
* If it is the last SELinux module package being installed however, |
36 |
* then it is advised to look at the error above and take appropriate |
37 |
* action since the new SELinux policies are not loaded until the |
38 |
* command finished succesfully. |
39 |
* |
40 |
* To reload, run the following command from within /usr/share/selinux/strict: |
41 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
42 |
* or |
43 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
44 |
* depending on if you need the unconfined domain loaded as well or not. |
45 |
* SELinux module load failed. Trying full reload... |
46 |
* Failed to reload SELinux policies. |
47 |
* |
48 |
* If this is *not* the last SELinux module package being installed, |
49 |
* then you can safely ignore this as the reloads will be retried |
50 |
* with other, recent modules. |
51 |
* |
52 |
* If it is the last SELinux module package being installed however, |
53 |
* then it is advised to look at the error above and take appropriate |
54 |
* action since the new SELinux policies are not loaded until the |
55 |
* command finished succesfully. |
56 |
* |
57 |
* To reload, run the following command from within /usr/share/selinux/targeted: |
58 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
59 |
* or |
60 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
61 |
* depending on if you need the unconfined domain loaded as well or not. |
62 |
* Messages for package sec-policy/selinux-mandb-2.20170805-r3: |
63 |
* SELinux module load failed. Trying full reload... |
64 |
* Failed to reload SELinux policies. |
65 |
* |
66 |
* If this is *not* the last SELinux module package being installed, |
67 |
* then you can safely ignore this as the reloads will be retried |
68 |
* with other, recent modules. |
69 |
* |
70 |
* If it is the last SELinux module package being installed however, |
71 |
* then it is advised to look at the error above and take appropriate |
72 |
* action since the new SELinux policies are not loaded until the |
73 |
* command finished succesfully. |
74 |
* |
75 |
* To reload, run the following command from within /usr/share/selinux/strict: |
76 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
77 |
* or |
78 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
79 |
* depending on if you need the unconfined domain loaded as well or not. |
80 |
* SELinux module load failed. Trying full reload... |
81 |
* Failed to reload SELinux policies. |
82 |
* |
83 |
* If this is *not* the last SELinux module package being installed, |
84 |
* then you can safely ignore this as the reloads will be retried |
85 |
* with other, recent modules. |
86 |
* |
87 |
* If it is the last SELinux module package being installed however, |
88 |
* then it is advised to look at the error above and take appropriate |
89 |
* action since the new SELinux policies are not loaded until the |
90 |
* command finished succesfully. |
91 |
* |
92 |
* To reload, run the following command from within /usr/share/selinux/targeted: |
93 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp) |
94 |
* or |
95 |
* semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp) |
96 |
* depending on if you need the unconfined domain loaded as well or not. |
97 |
* Messages for package sys-apps/busybox-1.28.0: |
98 |
* Could not locate user configfile, so we will save a default one |
99 |
* Your configuration for sys-apps/busybox-1.28.0 has been saved in |
100 |
* /etc/portage/savedconfig/sys-apps/busybox-1.28.0 for your editing pleasure. |
101 |
* You can edit these files by hand and remerge this package with |
102 |
* USE=savedconfig to customise the configuration. |
103 |
* You can rename this file/directory to one of the following for |
104 |
* its configuration to apply to multiple versions: |
105 |
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/ |
106 |
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}] |
107 |
* Messages for package sys-apps/sysvinit-2.88-r9: |
108 |
* The last/lastb/mesg/mountpoint/sulogin/utmpdump/wall tools have been moved to |
109 |
* sys-apps/util-linux. The pidof tool has been moved to sys-process/procps. |
110 |
* Messages for package sys-apps/man-db-2.7.6.1-r2: |
111 |
* Defaulting to USE=gdbm due to ambiguous berkdb/gdbm USE flag settings |
112 |
* Messages for package sys-apps/openrc-0.34.11: |
113 |
* Auto-adding 'termencoding' service to your boot runlevel |
114 |
* Auto-adding 'sysfs' service to your sysinit runlevel |
115 |
* Auto-adding 'loopback' service to your boot runlevel |
116 |
* Auto-adding 'binfmt' service to your boot runlevel |
117 |
* Auto-adding 'mtab' service to your boot runlevel |
118 |
* Messages for package net-misc/netifrc-0.5.1: |
119 |
* The network configuration scripts will use dhcp by |
120 |
* default to set up your interfaces. |
121 |
* If you need to set up something more complete, see |
122 |
* //usr/share/doc/netifrc-0.5.1/README |
123 |
* Messages for package sys-fs/eudev-3.2.5: |
124 |
* Unable to find kernel sources at /usr/src/linux |
125 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
126 |
* |
127 |
* For more information on eudev on Gentoo, writing udev rules, and |
128 |
* fixing known issues visit: https://wiki.gentoo.org/wiki/Eudev |
129 |
* Messages for package sys-fs/udev-init-scripts-32: |
130 |
* Adding udev to the sysinit runlevel |
131 |
* Adding udev-trigger to the sysinit runlevel |
132 |
* Messages for package dev-libs/glib-2.52.3: |
133 |
* Unable to find kernel sources at /usr/src/linux |
134 |
* Unable to calculate Linux Kernel version for build, attempting to use running version |
135 |
|
136 |
|
137 |
|
138 |
|
139 |
|
140 |
|
141 |
|
142 |
|
143 |
|
144 |
|
145 |
|
146 |
|
147 |
|
148 |
|
149 |
|
150 |
|
151 |
|
152 |
|
153 |
|
154 |
|
155 |
|
156 |
|
157 |
|
158 |
|
159 |
|
160 |
|
161 |
|
162 |
|
163 |
|
164 |
|
165 |
|
166 |
|
167 |
|
168 |
|
169 |
|
170 |
|
171 |
|
172 |
|
173 |
|
174 |
|
175 |
|
176 |
|
177 |
|
178 |
|
179 |
04 Feb 2018 00:16:02 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1 |
180 |
04 Feb 2018 00:16:02 UTC: ERROR : CatalystError: Stage build aborting due to error. |
181 |
04 Feb 2018 00:16:02 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 |
04 Feb 2018 00:16:02 UTC: NOTICE : Cleaning up... Running unbind() |
198 |
Command exited with non-zero status 2 |
199 |
2329.70user 647.37system 40:38.19elapsed 122%CPU (0avgtext+0avgdata 324840maxresident)k |
200 |
8inputs+10641240outputs (4major+288304923minor)pagefaults 0swaps |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /home/release/tmp/run/catalyst-auto.20180203T104446Z.1hFjV5/log/hardened_stage3-selinux.log |