Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1386180 - /etc/selinux/targeted/contexts/files/file_contexts.bin: line 1 error due to: Non-ASCII characters found
Summary: /etc/selinux/targeted/contexts/files/file_contexts.bin: line 1 error due to:...
Keywords:
Status: CLOSED DUPLICATE of bug 1502009
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 27
Hardware: s390x
OS: Linux
high
high
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1499883 (view as bug list)
Depends On:
Blocks: ZedoraTracker PPCTracker F25s390x
TreeView+ depends on / blocked
 
Reported: 2016-10-18 10:57 UTC by Jan Stodola
Modified: 2017-10-19 12:28 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-19 12:28:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
strace udevadm --help (22.06 KB, text/plain)
2016-10-18 10:58 UTC, Jan Stodola 		no flags Details
/var/log/anaconda/program.log for f26 ppc64 (BE) (87.58 KB, text/plain)
2017-04-10 12:31 UTC, Michel Normand 		no flags Details
View All

Description Jan Stodola 2016-10-18 10:57:33 UTC 
Description of problem:
During installation on s390x as well as on installed system, I can see the following error messages in journalctl:

Oct 18 05:02:30 localhost.localdomain systemd-sysusers[631]: /etc/selinux/targeted/contexts/files/file_contexts.bin:  line 1 error due to: Non-ASCII characters found
Oct 18 05:02:30 localhost.localdomain systemd-sysusers[631]: /etc/selinux/targeted/contexts/files/file_contexts.homedirs.bin:  line 1 error due to: Non-ASCII characters found
Oct 18 05:02:30 localhost.localdomain systemd-sysusers[631]: /etc/selinux/targeted/contexts/files/file_contexts.local.bin:  line 1 error due to: Non-ASCII characters found

It's easy to reproduce on installed system:

[root@rtt7 ~]# restorecon /root/anaconda-ks.cfg 
/etc/selinux/targeted/contexts/files/file_contexts.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.homedirs.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.local.bin:  line 1 error due to: Non-ASCII characters found
[root@rtt7 ~]# rpm -qf /etc/selinux/targeted/contexts/files/file_contexts.bin
selinux-policy-targeted-3.13.1-219.fc25.noarch
[root@rtt7 ~]#

[root@rtt7 ~]# udevadm --help
/etc/selinux/targeted/contexts/files/file_contexts.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.homedirs.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.local.bin:  line 1 error due to: Non-ASCII characters found
udevadm [--help] [--version] [--debug] COMMAND [COMMAND OPTIONS]
...


I tried the same on x86_64, but I cannot reproduce it there.

Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.13.1-219.fc25.noarch
policycoreutils-2.5-17.fc25
libselinux-2.5-12.fc25

How reproducible:
always on s390x

Steps to Reproduce:
1. install f25 on s390x and see journalctl

Actual results:
errors in journalctl:
/etc/selinux/targeted/contexts/files/file_contexts.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.homedirs.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.local.bin:  line 1 error due to: Non-ASCII characters found

Expected results:
no error messages
Comment 1 Jan Stodola 2016-10-18 10:58:53 UTC 
Created attachment 1211659 [details]
strace udevadm --help
Comment 2 Dan Horák 2016-10-21 13:26:37 UTC 
just saw it when update F-25 ppc64 machine - isn't a big endian related issue?

...
/etc/selinux/targeted/contexts/files/file_contexts.local.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.local.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.local.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.local.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.local.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.local.bin:  line 1 error due to: Non-ASCII characters found
/etc/selinux/targeted/contexts/files/file_contexts.local.bin:  line 1 error due to: Non-ASCII characters found
/var/tmp/rpm-tmp.z7vEzH: line 5: syntax error near unexpected token `else'
/var/tmp/rpm-tmp.z7vEzH: line 5: `	else'
warning: unknown(texlive-5:2016-7.20160520.fc25.ppc64) scriptlet failed, exit status 2
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/dnf/yum/rpmtrans.py", line 427, in callback
    self._scriptError(bytes, total, h)
  File "/usr/lib/python3.5/site-packages/dnf/yum/rpmtrans.py", line 557, in _scriptError
    pkg, _, _ = self._extract_cbkey(h)
  File "/usr/lib/python3.5/site-packages/dnf/yum/rpmtrans.py", line 229, in _extract_cbkey
    return self._extract_str_cbkey(cbkey)
  File "/usr/lib/python3.5/site-packages/dnf/yum/rpmtrans.py", line 237, in _extract_str_cbkey
    assert(isinstance(name, basestring))
AssertionError
FATAL ERROR: python callback ??? failed, aborting!
Comment 3 Dan Horák 2016-10-21 13:29:33 UTC 
from dnf history

    Upgraded libselinux-2.5-11.fc25.ppc64                                           @fedora
    Upgrade             2.5-12.fc25.ppc64                                           (unknown)
    Upgraded libselinux-devel-2.5-11.fc25.ppc64                                     @fedora
    Upgrade                   2.5-12.fc25.ppc64                                     (unknown)
    Upgraded libselinux-python-2.5-11.fc25.ppc64                                    @fedora
    Upgrade                    2.5-12.fc25.ppc64                                    (unknown)
    Upgraded libselinux-python3-2.5-11.fc25.ppc64                                   @fedora
    Upgrade                     2.5-12.fc25.ppc64                                   (unknown)
    Upgraded libselinux-utils-2.5-11.fc25.ppc64                                     @fedora
    Upgrade                   2.5-12.fc25.ppc64                                     (unknown)
    Upgraded libsemanage-2.5-7.fc25.ppc64                                           @fedora
    Upgrade              2.5-8.fc25.ppc64                                           (unknown)
    Upgrade  libsepol-2.5-10.fc25.ppc64                                             (unknown)
    Upgraded libsepol-2.5-9.fc25.ppc64                                              @fedora
    Upgrade  libsepol-devel-2.5-10.fc25.ppc64                                       (unknown)
    Upgraded libsepol-devel-2.5-9.fc25.ppc64                                        @fedora
    Upgraded selinux-policy-3.13.1-214.fc25.noarch                                  @fedora
    Upgrade                 3.13.1-219.fc25.noarch                                  (unknown)
    Upgraded selinux-policy-targeted-3.13.1-214.fc25.noarch                         @fedora
    Upgrade                          3.13.1-219.fc25.noarch                         (unknown)
Comment 4 Dan Horák 2016-10-21 13:32:36 UTC 
Also I suspect this bug to cause a failed load of selinux policy during boot (probably after a kernel update when a new initrd got created) and causing an unbootable system (workaround with selinux=0).
Comment 5 Vit Mojzis 2016-10-21 14:17:36 UTC 
selinux-policy-targeted contains following binary files created in little endian environment:
/targeted/contexts/files/file_contexts.bin
/targeted/contexts/files/file_contexts.homedirs.bin
/targeted/contexts/files/file_contexts.local.bin
These files should be recompiled during installation (which sometimes fails). The following commands should fix the issue:

# sefcontext_compile -o /targeted/contexts/files/file_contexts.bin /targeted/contexts/files/file_contexts

# sefcontext_compile -o /targeted/contexts/files/file_contexts.homedirs.bin /targeted/contexts/files/file_contexts.homedirs

# sefcontext_compile -o /targeted/contexts/files/file_contexts.local.bin /targeted/contexts/files/file_contexts.local
Comment 6 Dan Horák 2016-10-26 09:08:14 UTC 
So is it a transient issue that was caused by a policy update and not a general issue?
Comment 7 Vit Mojzis 2016-10-26 10:13:47 UTC 
Yes, we are still determining the exact cause of the installation procedure failure, but the issue should not occur without policy update (local policy changes should not trigger it). Furthermore, the issue was observed only on a few s390x machines with the majority unaffected.
Comment 8 Dan Horák 2016-10-26 10:19:35 UTC 
For the record we had it also on a F-25 ppc64 machine.
Comment 9 Daniel Moerner 2017-01-27 20:13:37 UTC 
I ran into this issue today twice while trying to install a Fedora 25 ppc64 instance in QEMU on an x86_64 Fedora 25 host, both during installation and after boot of the newly installed systems. Running the first two commands in Comment #5 fixed the problem for me after boot. (The first install failed with a "Pane is dead" error after creating the swap in Anaconda; switching from LVM to standard partitioning fixed this problem for me on the second try. I am not sure if this issue is related.)

I was able to reproduce it using the following virt-install command:

virt-install --name=fedora-25-ppc64 --arch=ppc64 --machine=pseries --cpu=POWER8 --vcpus=1 --os-type=linux --os-variant=fedora22 --ram=3072 --nographics --serial=pty --disk size=8,bus=scsi --controller scsi,model=virtio-scsi --location=https://dl.fedoraproject.org/pub/fedora-secondary/releases/25/Everything/ppc64/os/
Comment 10 Michel Normand 2017-04-10 12:31:31 UTC 
Created attachment 1270485 [details]
/var/log/anaconda/program.log for f26 ppc64 (BE)

Same error message while install ppc64 f26
as reported by attached log.
Comment 11 ruben.lledo.calatayud 2017-04-16 14:49:48 UTC 
Same problem when I try the following:

sudo semanage fcontext -a -t samba_share_t /home/ruben/Imágenes

Error message:
/var/lib/selinux/final/targeted/contexts/files/file_contexts.local:  line 5 error due to: Non-ASCII characters found
/var/lib/selinux/final/targeted/contexts/files/file_contexts.local:  line 5 error due to: Non-ASCII characters found
/var/lib/selinux/final/targeted/contexts/files/file_contexts: Invalid argument
libsemanage.semanage_validate_and_compile_fcontexts: setfiles returned error code 1.
OSError: [Errno 0] Error
Comment 12 R P Herrold 2017-10-05 14:14:33 UTC 
seen in F27 per:

Date: Thu, 5 Oct 2017 09:09:22
To: devel.org
Subject: f-dev] Re: Odd message when escalating priveledge with sudo - F27 -
    LXQt -  QTerminal ( Apologies if wrong list )
Comment 13 Petr Lautrbach 2017-10-07 11:56:23 UTC 
Jan Zarsky did an investigation related to the performance of SELinux userspace with and without .bin files [1].

It looks like we don't need to ship .bin files at all.

Regular users should not be affected by this change as these files are created on every policy rebuild.


[1] https://janzarskyblog.wordpress.com/2017/09/06/why-we-dont-need-to-ship-file_contexts-bin-with-selinux-policy/
Comment 14 Petr Lautrbach 2017-10-09 14:33:44 UTC 
*** Bug 1499883 has been marked as a duplicate of this bug. ***
Comment 15 Lukas Vrabec 2017-10-19 12:28:28 UTC 

*** This bug has been marked as a duplicate of bug 1502009 ***
Note You need to log in before you can comment on or make changes to this bug.