Gentoo Archives: gentoo-releng-autobuilds

From: catalyst@×××××××××××××××××.org
To: releng@g.o, gentoo-releng-autobuilds@l.g.o
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst fatal build error - hardened/stage3-selinux.spec
Date: Fri, 12 Jan 2018 06:48:26
Message-Id: 20180112064803.72E412036E@nightheron.gentoo.org
1 *
2 * To reload, run the following command from within /usr/share/selinux/targeted:
3 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp)
4 * or
5 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp)
6 * depending on if you need the unconfined domain loaded as well or not.
7 * Messages for package sec-policy/selinux-mandb-2.20170805-r3:
8 * SELinux module load failed. Trying full reload...
9 * Failed to reload SELinux policies.
10 *
11 * If this is *not* the last SELinux module package being installed,
12 * then you can safely ignore this as the reloads will be retried
13 * with other, recent modules.
14 *
15 * If it is the last SELinux module package being installed however,
16 * then it is advised to look at the error above and take appropriate
17 * action since the new SELinux policies are not loaded until the
18 * command finished succesfully.
19 *
20 * To reload, run the following command from within /usr/share/selinux/strict:
21 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp)
22 * or
23 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp)
24 * depending on if you need the unconfined domain loaded as well or not.
25 * SELinux module load failed. Trying full reload...
26 * Failed to reload SELinux policies.
27 *
28 * If this is *not* the last SELinux module package being installed,
29 * then you can safely ignore this as the reloads will be retried
30 * with other, recent modules.
31 *
32 * If it is the last SELinux module package being installed however,
33 * then it is advised to look at the error above and take appropriate
34 * action since the new SELinux policies are not loaded until the
35 * command finished succesfully.
36 *
37 * To reload, run the following command from within /usr/share/selinux/targeted:
38 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp)
39 * or
40 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp)
41 * depending on if you need the unconfined domain loaded as well or not.
42 * Messages for package sec-policy/selinux-openrc-2.20170805-r3:
43 * SELinux module load failed. Trying full reload...
44 * Failed to reload SELinux policies.
45 *
46 * If this is *not* the last SELinux module package being installed,
47 * then you can safely ignore this as the reloads will be retried
48 * with other, recent modules.
49 *
50 * If it is the last SELinux module package being installed however,
51 * then it is advised to look at the error above and take appropriate
52 * action since the new SELinux policies are not loaded until the
53 * command finished succesfully.
54 *
55 * To reload, run the following command from within /usr/share/selinux/strict:
56 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp)
57 * or
58 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp)
59 * depending on if you need the unconfined domain loaded as well or not.
60 * SELinux module load failed. Trying full reload...
61 * Failed to reload SELinux policies.
62 *
63 * If this is *not* the last SELinux module package being installed,
64 * then you can safely ignore this as the reloads will be retried
65 * with other, recent modules.
66 *
67 * If it is the last SELinux module package being installed however,
68 * then it is advised to look at the error above and take appropriate
69 * action since the new SELinux policies are not loaded until the
70 * command finished succesfully.
71 *
72 * To reload, run the following command from within /usr/share/selinux/targeted:
73 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp)
74 * or
75 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp)
76 * depending on if you need the unconfined domain loaded as well or not.
77 * Messages for package sec-policy/selinux-shutdown-2.20170805-r3:
78 * SELinux module load failed. Trying full reload...
79 * Failed to reload SELinux policies.
80 *
81 * If this is *not* the last SELinux module package being installed,
82 * then you can safely ignore this as the reloads will be retried
83 * with other, recent modules.
84 *
85 * If it is the last SELinux module package being installed however,
86 * then it is advised to look at the error above and take appropriate
87 * action since the new SELinux policies are not loaded until the
88 * command finished succesfully.
89 *
90 * To reload, run the following command from within /usr/share/selinux/strict:
91 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp)
92 * or
93 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp)
94 * depending on if you need the unconfined domain loaded as well or not.
95 * SELinux module load failed. Trying full reload...
96 * Failed to reload SELinux policies.
97 *
98 * If this is *not* the last SELinux module package being installed,
99 * then you can safely ignore this as the reloads will be retried
100 * with other, recent modules.
101 *
102 * If it is the last SELinux module package being installed however,
103 * then it is advised to look at the error above and take appropriate
104 * action since the new SELinux policies are not loaded until the
105 * command finished succesfully.
106 *
107 * To reload, run the following command from within /usr/share/selinux/targeted:
108 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp)
109 * or
110 * semodule -i base.pp -i $(ls *.pp | grep -v base.pp | grep -v unconfined.pp)
111 * depending on if you need the unconfined domain loaded as well or not.
112 * Messages for package sys-apps/sysvinit-2.88-r9:
113 * The last/lastb/mesg/mountpoint/sulogin/utmpdump/wall tools have been moved to
114 * sys-apps/util-linux. The pidof tool has been moved to sys-process/procps.
115 * Messages for package sys-apps/util-linux-2.30.2:
116 * The mesg/wall/write tools have been disabled due to USE=-tty-helpers.
117 * The agetty util now clears the terminal by default. You
118 * might want to add --noclear to your /etc/inittab lines.
119 * Messages for package sys-apps/man-db-2.7.6.1-r2:
120 * Defaulting to USE=gdbm due to ambiguous berkdb/gdbm USE flag settings
121 * Messages for package sys-apps/openrc-0.34.11:
122 * Auto-adding 'termencoding' service to your boot runlevel
123 * Auto-adding 'sysfs' service to your sysinit runlevel
124 * Auto-adding 'loopback' service to your boot runlevel
125 * Auto-adding 'binfmt' service to your boot runlevel
126 * Auto-adding 'mtab' service to your boot runlevel
127 * Messages for package net-misc/netifrc-0.5.1:
128 * The network configuration scripts will use dhcp by
129 * default to set up your interfaces.
130 * If you need to set up something more complete, see
131 * //usr/share/doc/netifrc-0.5.1/README
132 * Messages for package sys-fs/eudev-3.1.5:
133 *
134 * For more information on eudev on Gentoo, writing udev rules, and
135 * fixing known issues visit: https://wiki.gentoo.org/wiki/Eudev
136 * Messages for package sys-fs/udev-init-scripts-32:
137 * Adding udev to the sysinit runlevel
138 * Adding udev-trigger to the sysinit runlevel
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 12 Jan 2018 06:48:03 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage3/stage3-controller.sh', 'run']) exited 1
180 12 Jan 2018 06:48:03 UTC: ERROR : CatalystError: Stage build aborting due to error.
181 12 Jan 2018 06:48:03 UTC: ERROR : Exception running action sequence run_local
182 Traceback (most recent call last):
183 File "/usr/lib64/python3.4/site-packages/catalyst/base/stagebase.py", line 1354, in run_local
184 env=self.env)
185 File "/usr/lib64/python3.4/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.4/site-packages/catalyst/base/stagebase.py", line 1454, in run
193 getattr(self, x)()
194 File "/usr/lib64/python3.4/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 12 Jan 2018 06:48:03 UTC: NOTICE : Cleaning up... Running unbind()
198 Command exited with non-zero status 2
199 1163.02user 324.56system 20:16.66elapsed 122%CPU (0avgtext+0avgdata 445424maxresident)k
200 30256inputs+4955264outputs (4major+49384437minor)pagefaults 0swaps
201
202
203
204 Full build log at /release/tmp/run/catalyst-auto.20180111T214502Z.iwsrm6/log/hardened_stage3-selinux.log