On 2020-03-06 05:43, François Patte wrote:
> Le 05/03/2020 à 21:52, Ed Greshko a écrit :
>> On 2020-03-06 01:15, François Patte wrote:
>>> Le 05/03/2020 à 14:16, Ed Greshko a écrit :
>>>> On 2020-03-05 21:02, François Patte wrote:
>>>>> Le 05/03/2020 à 13:53, Ed Greshko a écrit :
>>>>>> When the server fails to start with selinux enabled what do you get with
>>>>>>
>>>>>> ausearch -m AVC,USER_AVC -ts recent
>>>>>>
>>>>> [root@dipankar ~]# ausearch -m AVC,USER_AVC -ts recent
>>>> It is "odd" that you are getting so many but the one that is related to dictd is
>>>>
>>>>> ----
>>>>> time->Thu Mar 5 13:59:45 2020
>>>>> type=AVC msg=audit(1583413185.069:328): avc: denied { map } for
>>>>> pid=8869 comm="dictd"
>>>>> path="/opt/share/stardict/dic/stardict-xmlittre-2.4.2/xmlittre.index"
>>>>> dev="dm-4" ino=402 scontext=system_u:system_r:dictd_t:s0
>>>>> tcontext=unconfined_u:object_r:usr_t:s0 tclass=file permissive=0
>>>>> ----
>>>>>
>>>> sudo journalctl -t setroubleshoot --since="2020-03-05 13:59:4"
>>> journalctl -t setroubleshoot --since="2020-03-05 13:59:4"
>>> Journal file
>>> /var/log/journal/bd9a117e29a44dd4b335896e866a41d2/system@0005995d04fbac9f-d1196d9ceef66b92.journal~
>>> is truncated, ignoring file.
>>> -- Logs begin at Sun 2019-10-20 16:16:14 CEST, end at Thu 2020-03-05
>>> 17:59:01 CET. --
>>> mars 05 13:59:48 dipankar setroubleshoot[8876]: failed to get filesystem
>>> list from rpm
>>> mars 05 13:59:48 dipankar setroubleshoot[8876]: failed to retrieve rpm
>>> info for /opt/share/stardict/dic/stardict->
>>> mars 05 13:59:48 dipankar setroubleshoot[8876]: failed to retrieve rpm
>>> info for selinux-policy
>>> mars 05 13:59:48 dipankar setroubleshoot[8876]: failed to retrieve rpm
>>> info for selinux-policy
>>>
>>>
>>>> Should output a list of selinux errors around that time, Find the one associated with dictd and
>>>> run the
>>>>
>>>> sealert -l XXXXXXX
>>> Does XXXXXXX mean 8876?
>>>
>>> In that case, I get:
>>>
>>> Error
>>> query_alerts error (1003): id (8876) not found
>> No.
>>
>> You're not getting anything close to valid information from those command.
>>
>> Based on the errors returned by journalctl and the other AVC errors you've shown I think you should
>> do....
>>
>> fixfiles onboot
> This did not fix the problem!
But, now can you get valid information from journalctl?
Have a look at https://access.redhat.com/articles/2191331 for what you should expect from those
commands.
--
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
