public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sven Vermeulen" <sven.vermeulen@siphos.be>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-docs:master commit in: xml/selinux/
Date: Sun, 11 Dec 2011 14:36:45 +0000 (UTC)	[thread overview]
Message-ID: <5a3923f95ddfe75d03cb2a363151a7f096b61bf1.SwifT@gentoo> (raw)

commit:     5a3923f95ddfe75d03cb2a363151a7f096b61bf1
Author:     Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
AuthorDate: Sun Dec 11 14:35:39 2011 +0000
Commit:     Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
CommitDate: Sun Dec 11 14:35:39 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-docs.git;a=commit;h=5a3923f9

Adding portage installation failure information

---
 xml/selinux/hb-using-troubleshoot.xml |   70 ++++++++++++++++++++++++++++++++-
 1 files changed, 68 insertions(+), 2 deletions(-)

diff --git a/xml/selinux/hb-using-troubleshoot.xml b/xml/selinux/hb-using-troubleshoot.xml
index 96df785..16fff0a 100644
--- a/xml/selinux/hb-using-troubleshoot.xml
+++ b/xml/selinux/hb-using-troubleshoot.xml
@@ -7,8 +7,8 @@
 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/hardened/selinux/hb-appendix-troubleshoot.xml,v 1.2 2011/04/25 20:12:59 zorry Exp $ -->
 
 <sections>
-<version>0</version>
-<date>2011-02-24</date>
+<version>1</version>
+<date>2011-12-11</date>
 
 <section>
 <title>Unable To Load SELinux Policy</title>
@@ -225,4 +225,70 @@ contexts</e> that you see in the output with the next table.
 </body>
 </subsection>
 </section>
+
+<section>
+<title>Unable to Emerge Anything (OSError: [Errno 22] Invalid argument)</title>
+<subsection>
+<title>Problem Description</title>
+<body>
+
+<p>
+When trying to install software with Portage, you get a huge python stacktrace
+and finally the error message <e>OSError: [Errno 22] Invalid argument</e>:
+</p>
+
+<pre caption="Stacktrace dump when portage fails to install software">
+Traceback (most recent call last):
+  File "/usr/bin/emerge", line 43, in &lt;module&gt;
+    retval = emerge_main()
+  File "/usr/lib64/portage/pym/_emerge/main.py", line 1906, in emerge_main
+    myopts, myaction, myfiles, spinner)
+  File "/usr/lib64/portage/pym/_emerge/actions.py", line 437, in action_build
+    retval = mergetask.merge()
+...
+  File "/usr/lib64/portage/pym/portage/package/ebuild/doebuild.py", line 104, in _doebuild_spawn
+    return spawn(cmd, settings, **kwargs)
+  File "/usr/lib64/portage/pym/portage/package/ebuild/doebuild.py", line 1255, in spawn
+    return spawn_func(mystring, env=mysettings.environ(), **keywords)
+  File "/usr/lib64/portage/pym/portage/_selinux.py", line 105, in wrapper_func
+    setexec(con)
+  File "/usr/lib64/portage/pym/portage/_selinux.py", line 79, in setexec
+    if selinux.setexeccon(ctx) &lt; 0: 
+OSError: [Errno 22] Invalid argument
+</pre>
+
+</body>
+</subsection>
+<subsection>
+<title>Wrong Context</title>
+<body>
+
+<p>
+The above error comes when you launch portage (through <c>emerge</c>) while you
+are not in <c>sysadm_t</c> context. You can verify this with <c>id -Z</c>:
+</p>
+
+<pre caption="Checking current context">
+~# <i>id -Z</i>
+system_u:system_r:local_login_t
+</pre>
+
+<p>
+As long as the context isn't <c>sysadm_t</c>, then Portage will break. This is
+because Portage wants to switch its execution context from <c>portage_t</c> to
+<c>portage_sandbox_t</c> but fails (it isn't in <c>portage_t</c> to begin with
+because the user who launched Portage isn't in <c>sysadm_t</c>).
+</p>
+
+<p>
+Please check <uri link="#doc_chap2">Unable to Log On</uri> above first. Also
+make sure that you can <c>dispatch-conf</c> or <c>etc-update</c> after
+installing SELinux so that <path>/etc/pam.d/system-login</path> is updated with
+the right <path>pam_selinux.so</path> calls.
+</p>
+
+</body>
+</subsection>
+</section>
+
 </sections>



             reply	other threads:[~2011-12-11 14:36 UTC|newest]

Thread overview: 95+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-11 14:36 Sven Vermeulen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-05-07 20:20 [gentoo-commits] proj/hardened-docs:master commit in: xml/selinux/ Sven Vermeulen
2012-05-07 20:07 Sven Vermeulen
2012-05-05 18:56 Sven Vermeulen
2012-04-29 14:22 Sven Vermeulen
2012-04-10 18:22 Sven Vermeulen
2012-04-10 18:22 Sven Vermeulen
2012-04-10 18:22 Sven Vermeulen
2012-04-05 16:24 Sven Vermeulen
2012-03-01 20:09 Sven Vermeulen
2012-01-29 12:42 Sven Vermeulen
2012-01-21 13:20 Sven Vermeulen
2011-12-17 10:52 Sven Vermeulen
2011-12-11 14:39 Sven Vermeulen
2011-12-10 14:00 Sven Vermeulen
2011-11-22 20:08 Sven Vermeulen
2011-11-11 19:59 Sven Vermeulen
2011-10-27 19:18 José María Alonso
2011-10-26 22:05 José María Alonso
2011-10-23 13:01 Sven Vermeulen
2011-10-19 12:55 Sven Vermeulen
2011-10-15 18:24 Sven Vermeulen
2011-10-15 17:43 Sven Vermeulen
2011-10-15 17:12 Sven Vermeulen
2011-10-15 15:54 Sven Vermeulen
2011-10-15 15:18 Sven Vermeulen
2011-10-15 13:04 Sven Vermeulen
2011-10-15 13:04 Sven Vermeulen
2011-09-30 17:36 Sven Vermeulen
2011-09-18 13:49 Sven Vermeulen
2011-09-11  9:51 Sven Vermeulen
2011-09-04 19:22 Sven Vermeulen
2011-08-16 16:58 José María Alonso
2011-08-12 21:00 Sven Vermeulen
2011-07-22 16:03 Sven Vermeulen
2011-07-21 19:11 Sven Vermeulen
2011-07-13 21:39 Sven Vermeulen
2011-07-09 18:56 Sven Vermeulen
2011-06-09 18:54 José María Alonso
2011-06-09 17:49 Sven Vermeulen
2011-06-09 17:40 Francisco Blas Izquierdo Riera
2011-06-09 17:24 Sven Vermeulen
2011-06-07 19:38 Sven Vermeulen
2011-06-07 19:26 Sven Vermeulen
2011-06-02 19:50 Sven Vermeulen
2011-06-02 11:57 Sven Vermeulen
2011-06-02 11:55 Sven Vermeulen
2011-06-02 11:03 Sven Vermeulen
2011-06-02 11:03 Sven Vermeulen
2011-05-31 20:22 Sven Vermeulen
2011-05-31 20:16 Sven Vermeulen
2011-05-31 20:16 Sven Vermeulen
2011-05-24 20:39 Sven Vermeulen
2011-05-24 19:56 Sven Vermeulen
2011-05-20 19:32 Sven Vermeulen
2011-05-14 12:51 Sven Vermeulen
2011-05-13 19:43 Sven Vermeulen
2011-05-03 20:47 Sven Vermeulen
2011-05-03 20:12 Sven Vermeulen
2011-04-22 21:43 Sven Vermeulen
2011-04-22 19:30 Sven Vermeulen
2011-04-22 19:28 Sven Vermeulen
2011-04-22 19:05 Sven Vermeulen
2011-04-22 19:05 Sven Vermeulen
2011-04-22 10:32 Sven Vermeulen
2011-04-22 10:32 Sven Vermeulen
2011-04-16  9:06 Sven Vermeulen
2011-04-15 19:10 Sven Vermeulen
2011-04-15 17:52 Sven Vermeulen
2011-04-15 17:52 Sven Vermeulen
2011-04-10  7:49 Sven Vermeulen
2011-04-01 17:45 Sven Vermeulen
2011-03-09 16:54 Sven Vermeulen
2011-03-02 20:48 Sven Vermeulen
2011-03-02 20:38 Sven Vermeulen
2011-03-02 20:38 Sven Vermeulen
2011-03-02 20:13 Sven Vermeulen
2011-03-02 20:13 Sven Vermeulen
2011-03-02 20:13 Sven Vermeulen
2011-03-02 15:53 Sven Vermeulen
2011-02-24 21:19 Sven Vermeulen
2011-02-20 13:26 Sven Vermeulen
2011-02-19 17:00 Francisco Blas Izquierdo Riera
2011-02-19  3:21 Francisco Blas Izquierdo Riera
2011-02-19  3:12 Francisco Blas Izquierdo Riera
2011-02-13 18:20 Sven Vermeulen
2011-02-12 23:44 Sven Vermeulen
2011-02-12 23:44 Sven Vermeulen
2011-02-12 20:50 Sven Vermeulen
2011-02-12 20:49 Sven Vermeulen
2011-02-12 20:47 Sven Vermeulen
2011-02-12 20:47 Sven Vermeulen
2011-02-12 20:47 Sven Vermeulen
2011-02-12 17:33 Sven Vermeulen
2011-02-06 19:53 Sven Vermeulen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5a3923f95ddfe75d03cb2a363151a7f096b61bf1.SwifT@gentoo \
    --to=sven.vermeulen@siphos.be \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox