Any way, the problem for now is solved.
--Ron
The problem turned out to be that there seems to be an selinux
configuration issue on my machine and I didn't notice that the
setroubleshoot service die (I did suspect that there might be an selinux
issue but I was expecting there to be log messages.)
