-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/31/2013 06:04 PM, Ranjan Maitra wrote:
On Thu, 31 Jan 2013 23:45:07 +0100 Reindl Harald
<h.reindl(a)thelounge.net>
wrote:
>
>
> Am 31.01.2013 22:04, schrieb Ranjan Maitra:
>> Jan 31 15:01:35 localhost systemd[1]: Failed to start firewalld -
>> dynamic firewall daemon. Jan 31 15:01:35 localhost systemd [1]: Unit
>> firewalld.service entered failed state Jan 31 15:01:36 localhost
>> setroubleshoot: SELinux is preventing /usr/bin/python2.7 from getattr
>> access on the file /run/firewalld.pid. For complete SELinux messages.
>> run sealert -l 6da93ecc-b84a-4d14-bc3f-0f8d06af82a2 Jan 31 15:01:37
>> localhost setroubleshoot: SELinux is preventing /usr/bin/python2.7 from
>> write access on the file firewalld.pid. For complete SELinux messages.
>> run sealert -l d6eea039-e995-4e5e-a6f3-57048fc05bae Jan 31 15:01:37
>> localhost setroubleshoot: SELinux is preventing /usr/bin/python2.7 from
>> unlink access on the file firewalld.pid. For complete SELinux messages.
>> run sealert -l 689b4650-7ccb-4ca7-a2db-2ec6c5f18b6f
>>
>> Not sure what to do with all this
>
> write a bugreport why this new shiny thing is broken by SElinux and
> realize that such things are the reason why i said "reboot blidnly" is a
> terrible idea
Bug report against firewalld?
> AND START IPATBLES AGAIN BEVAUSE YOU ARE WIDE OPEN NOW
Thanks, started it.
Ranjan
It is actually a file descriptor leak in firewalld. So not something to worry
about. But open a bug report about this specific case. I believe there are
existing bug reports on it, but we should look at this case. You should add me
as a CC on the bug.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlELti0ACgkQrlYvE4MpobPdEwCeNd2+XFyr6M38Kxd+eCCmmm9v
CoMAnRmxCHcc+EaPu/SHPIcQ6Z0fo7SR
=5jlq
-----END PGP SIGNATURE-----