On 2020-03-05 19:12, François Patte wrote:
Bonjour,
I am wondering why selinux changes its policy. I did note update or
upgrade my system for a long time now, but selinux policy has changed!
I used to use dictd server on my computer and it worked fine up today: I
can't start the server for selinux block it (If I setenforce 0, I can
start the dictd server). Why? I don't know.
And, as usual, journalctl is unable to give me any clue:
using journalctl -u dictd answers:
mars 05 11:57:53 dipankar systemd[1]: Starting Dictd Dictionary Server
Daemon...
mars 05 11:57:53 dipankar systemd[1]: Started Dictd Dictionary Server
Daemon.
mars 05 11:57:53 dipankar systemd[1]: dictd.service: Main process
exited, code=exited, status=1/FAILURE
mars 05 11:57:53 dipankar systemd[1]: dictd.service: Failed with result
'exit-code'.
Thank you sir! "Failed with result 'exit-code'" What can I do with
this.
dictd.log file is also useless:
:I: 1701 starting dictd 1.12.1/rf on Linux 5.3.14-200.fc30.x86_64 Thu
Mar 5 11:21:46 2020
:I: Initializing 'MW'
:I: Opening indices
(dict_index_open) Cannot mmap index file "H=
(dict_index_open) dict_index_open: Permission denied
OK! What can I do with this?
The only way I found is to stop selinux!
Who can help?
When the server fails to start with selinux enabled what do you get with
ausearch -m AVC,USER_AVC -ts recent
--
The key to getting good answers is to ask good questions.