411377 – SELinux Handbook: how to recover from corrupted module store

Bug 411377 - SELinux Handbook: how to recover from corrupted module store

Summary: SELinux Handbook: how to recover from corrupted module store

Status:	RESOLVED FIXED

Alias:	None

Product:	Documentation
Classification:	Unclassified
Component:	Project-specific documentation (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Sven Vermeulen (RETIRED)

URL:	http://www.gentoo.org/proj/en/hardene...
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-04-09 18:15 UTC by Paweł Hajdan, Jr. (RETIRED)
Modified:	2012-04-10 20:20 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Paweł Hajdan, Jr. (RETIRED) gentoo-dev

2012-04-09 18:15:44 UTC

I recently experienced failure during "semodule -i" that brought down X and forced me to hard-reboot the system. After that further policy operations resulted in the following error:

libsemanage.semanage_load_module: Error while reading from module file /etc/selinux/targeted/modules/tmp/base.pp. (No such file or directory)

I managed to find https://bugzilla.redhat.com/show_bug.cgi?id=518094 and based on this here are my successful recover steps on Gentoo (I think it would be worth it to add them to the Troubleshooting section of the Handbook):

setenforce 0
mv /etc/selinux/targeted /etc/selinux/targeted.old
FEATURES="-selinux" emerge -1av $(eix -I --only-names sec-policy/)
restorecon -R /etc/selinux

Comment 1 Sven Vermeulen (RETIRED) gentoo-dev

2012-04-10 20:20:26 UTC

Fixed in CVS