New answers tagged selinux
The error message is not talking about crontab, but httpd (Apache). Start investigating by temporarily turning SELinux off: setenforce 0 (which will address most but not all of the blockage). The problem can usually be fixed using one of the SELinux settings via semanage (if Drupal's files are stored in some place that SELinux does not expect), or using ...
Googling around I found this RHEL error report. Now, I know pretty little about SELinux but I do remember seeing a SELinux relabel taking place after upgrading my OS distribution, my SELinux issues casually happened after a kernel upgrade and the error report suggested trying a forced autorelabel by creating an empty file on the system root directory called ...
SELinux in permissive mode is still running, but not enforcing the restrictions. You would be interested in testing it without SELinux. Either uninstall it, or at best configure it in disabled mode instead of permissive mode.
Bratchley was on the right track. Indeed 'semanage' can change (modify) already defined ports. Here's a way that worked for myself: [root@host ~]# semanage port -l |grep ssh ssh_port_t tcp 22 [root@host ~]# semanage port -m -t ssh_port_t -p tcp 23 [root@host ~]# semanage port -l |grep ssh ssh_port_t tcp ...
I am no friend of SELinux, so this is just a wild guess: Modify /etc/services so that 23/tcp has the same entry as 22/tcp?
I'm going to put my head above the parapet with this answer - after all, an answer is deletable! Apache processes it's modules in a not very well defined order. You can view the processing order by enabling the mod_info module. On a Fedora 22 installation, this came up with the following (extact): Post-Read Request: -10 mod_http2.c 00 ...
You need to enable module "rewrite" to get .hatccess working: a2enmod rewrite service httpd restart
I believe if you set /etc/selinux/config to disabled reboot. Then set it to enforcing and reboot, it will re-label if you've had trouble getting it to relabel otherwise. It's weird that restorecon didn't work though. If you want to reset things the hard way, the /home directory itself should be: system_u:object_r:home_root_t and each user home directory ...
Top 50 recent answers are included