{"id":1434,"date":"2015-05-05T08:07:37","date_gmt":"2015-05-05T07:07:37","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=1434"},"modified":"2015-05-05T08:07:37","modified_gmt":"2015-05-05T07:07:37","slug":"arm-rogue-selinux-fixed","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=1434","title":{"rendered":"ARM – Rogue SELinux Fixed..?"},"content":{"rendered":"

I updated the CuBox-i4-Pro (Fedora 22) to Kernel 4.1-rc2<\/strong>, but the (re)boot process was very<\/span> sluggish, with several key commands failing:<\/p>\n

.....<\/strong><\/span>\r\nsystemd[1]: Unit dbus.service entered failed state<\/strong><\/span>\r\n.....<\/strong><\/span>\r\n[FAILED] Failed to start Login Service.<\/strong><\/span>\r\n.....<\/strong><\/span>\r\n[FAILED] Failed to start Modem Manager.<\/strong><\/span>\r\n.....<\/strong><\/span>\r\n[FAILED] Failed to start Avahi mDNS\/DNS-SD Stack.<\/strong><\/span>\r\n.....<\/strong><\/span>\r\n[FAILED] Failed to start Network Manager.<\/strong><\/span><\/pre>\n
The boot process eventually completed, but there was no networking, and various systemctl<\/strong><\/em> commands failed:<\/p>\n
Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)<\/span><\/strong><\/pre>\n
dbus-daemon<\/strong><\/em> was not running at all, and attempts to start it manually failed..<\/p>\n
My first suspicion was that 4.1-rc2 was the culprit, but reverting to known\/good<\/em> 4.1-rc1 and 4.0.0 resulted in the same problems..<\/p>\n
I then tried (re)installing dbus, systemd, etc, but with no change..<\/p>\n
I then checked SELinux – which I always have configured as ‘disabled’ – but it appeared to be active, despite this..:<\/p>\n
# <\/strong>sestatus<\/span>\r\nSELinux status: enabled<\/strong><\/span>\r\nSELinuxfs mount: \/sys\/fs\/selinux<\/strong><\/span>\r\nSELinux root directory: \/etc\/selinux<\/strong><\/span>\r\nLoaded policy name: targeted<\/strong><\/span>\r\nCurrent mode: permissive<\/strong><\/span>\r\nMode from config file: disabled<\/strong><\/span>\r\nPolicy MLS status: disabled<\/strong><\/span>\r\nPolicy deny_unknown status: denied<\/strong><\/span>\r\nMax kernel policy version: 29<\/strong><\/span>\r\n# <\/strong>getenforce<\/span>\r\nPermissive<\/strong><\/span><\/pre>\n
Attempts to disable SELinux manually did nothing, and so I decided to ‘remove’ SELinux by de-selecting it in the kernel config, and re-compiling\/installing the kernel.<\/p>\n
After this, everything worked OK!<\/p>\n
I have other ARM systems with similar configurations, where SELinux is behaving correctly (staying ‘disabled’!) and I have another Fedora 22 system (X86_64) with the same software versions where everything also works OK, so have no explanation as to the real cause of this – apart from some possible SELinux persistent aberration on this single system..<\/p>\n
But… at least I have an acceptable – if somewhat drastic – fix..<\/p>\n
Robert Gadsdon.\u00a0\u00a0 May 05, 2015.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
I updated the CuBox-i4-Pro (Fedora 22) to Kernel 4.1-rc2, but the (re)boot process was very sluggish, with several key commands failing: ….. systemd[1]: Unit dbus.service entered failed state ….. [FAILED] Failed to start Login Service. ….. [FAILED] Failed to start Modem Manager. ….. [FAILED] Failed to start Avahi mDNS\/DNS-SD Stack. ….. [FAILED] Failed to start Network Manager. …<\/span> Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[5,6,862,10,11,14,16,19,20],"tags":[1093,863,1095,1096,161,1091,1092,1175,1094],"class_list":["post-1434","post","type-post","status-publish","format-standard","hentry","category-compilation","category-crash-and-burn","category-cubox","category-fedora","category-hacks","category-kernel","category-linux-arm","category-opinion","category-performance-2","tag-active-despite-disable","tag-cubox-i4-pro","tag-dbus-fail","tag-disable-selinux-in-kernel-config","tag-fix","tag-kernel-4-1-rc2","tag-selinux","tag-success","tag-systemctl-failing"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1434","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1434"}],"version-history":[{"count":1,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1434\/revisions"}],"predecessor-version":[{"id":1435,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1434\/revisions\/1435"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1434"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1434"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1434"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}