Bug #12987
closed
installing on 2.4 fails with error 'semanage boolean -m --on pulp_manage_puppet returned 1'
Description
[DEBUG 2016-01-04 21:11:19 main] Executing 'semanage boolean -m --on pulp_manage_puppet'
[ WARN 2016-01-04 21:11:41 main] /Stage[main]/Pulp::Config/Exec[selinux_pulp_manage_puppet]/returns: SELinux: Could not load policy file /etc/selinux/targeted/policy/policy.24: Inval
id argument
[ WARN 2016-01-04 21:11:41 main] /Stage[main]/Pulp::Config/Exec[selinux_pulp_manage_puppet]/returns: /sbin/load_policy: Can't load policy: Invalid argument
[ WARN 2016-01-04 21:11:41 main] /Stage[main]/Pulp::Config/Exec[selinux_pulp_manage_puppet]/returns: libsemanage.semanage_reload_policy: load_policy returned error code 2.
[ WARN 2016-01-04 21:11:41 main] /Stage[main]/Pulp::Config/Exec[selinux_pulp_manage_puppet]/returns: /usr/sbin/semanage: Could not commit semanage transaction
[ERROR 2016-01-04 21:11:42 main] semanage boolean -m --on pulp_manage_puppet returned 1 instead of one of [0]
Updated by Justin Sherrill almost 9 years ago
visible in /var/log/messages:
kernel: load_policy: page allocation failure. order:4, mode:0xd0 kernel: Pid: 28393, comm: load_policy Not tainted 2.6.32-358.el6.x86_64 #1 kernel: Call Trace: kernel: [<ffffffff8112c127>] ? __alloc_pages_nodemask+0x757/0x8d0 kernel: [<ffffffff811669d2>] ? kmem_getpages+0x62/0x170 kernel: [<ffffffff811675ea>] ? fallback_alloc+0x1ba/0x270 kernel: [<ffffffff8116703f>] ? cache_grow+0x2cf/0x320 kernel: [<ffffffff81167369>] ? ____cache_alloc_node+0x99/0x160 kernel: [<ffffffff81236507>] ? policydb_read+0x8a7/0x1080 kernel: [<ffffffff81168139>] ? __kmalloc+0x189/0x220 kernel: [<ffffffff81236507>] ? policydb_read+0x8a7/0x1080 kernel: [<ffffffff8123a021>] ? security_load_policy+0x141/0x410 kernel: [<ffffffff8114431a>] ? handle_mm_fault+0x23a/0x310 kernel: [<ffffffff8104757c>] ? __do_page_fault+0x1ec/0x480 kernel: [<ffffffff81150459>] ? vmap_page_range_noflush+0x279/0x370 kernel: [<ffffffff81151ff0>] ? __vmalloc_area_node+0x100/0x190 kernel: [<ffffffff8151311e>] ? do_page_fault+0x3e/0xa0 kernel: [<ffffffff815104d5>] ? page_fault+0x25/0x30 kernel: [<ffffffff8122dbcb>] ? sel_write_load+0xdb/0x710 kernel: [<ffffffff81228c1b>] ? selinux_file_permission+0xfb/0x150 kernel: [<ffffffff8121baf6>] ? security_file_permission+0x16/0x20 kernel: [<ffffffff81180f98>] ? vfs_write+0xb8/0x1a0 kernel: [<ffffffff81181891>] ? sys_write+0x51/0x90 kernel: [<ffffffff810dc565>] ? __audit_syscall_exit+0x265/0x290 kernel: [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b kernel: Mem-Info: kernel: Node 0 DMA per-cpu: kernel: CPU 0: hi: 0, btch: 1 usd: 0 kernel: CPU 1: hi: 0, btch: 1 usd: 0 kernel: Node 0 DMA32 per-cpu: kernel: CPU 0: hi: 186, btch: 31 usd: 0 kernel: CPU 1: hi: 186, btch: 31 usd: 170
Updated by Justin Sherrill almost 9 years ago
- Status changed from New to Rejected
After a morning of poking and debugging, increasing the memory to 4.5 GB seemed to make the install go through without error.
If you are hitting this you can simply run: "semanage boolean -m --on pulp_manage_puppet && katello-installer" and the problem should be resolved.
Its possible a reboot onto a newer kernel would fix this, as this was observed on centos 6.7 running a 6.4 kernel (as that is what our vagrant box is)