using fedora core 4 installed everything without a prob when i want start httpd i get this eror in my /var/log/http/error_log __begin past unable to start piped log program '/root/ispconfig/cronolog --symlink=/var/log/httpd/ispconfig_access_log /var/log/httpd/ispconfig_access_log_%Y_%m_%d': Permission denied Unable to open logs [root@vac httpd]# __end past looked at ther permissions at those files.. __begin past [root@vac httpd]# ls -al /root/ispconfig/cronolog -rwxr-xr-x 1 root root 55866 aug 5 17:58 /root/ispconfig/cronolog [root@vac httpd]# [root@vac httpd]# ls -al /var/log/httpd/ispconfig_access_log_%Y_%m_%d ls: /var/log/httpd/ispconfig_access_log_%Y_%m_%d: Onbekend bestand of map <dutch for unkown file> [root@vac httpd]# [root@vac httpd]# ls -al /var/log/httpd/ispconfig_access_log -rw-r--r-- 1 root root 0 aug 5 17:58 /var/log/httpd/ispconfig_access_log [root@vac httpd]# --endpast it seems to me the parameters %y %d %m are past to cornolog but if i do cronolog --help %y for example doesnt show.. Even from the ispconfig console under services i am not able to start the normal httpd https on port 81 runs perfect. anyone might have an idea of what is wrong? <or what i doin/did wrong ??>
The cronolog line in httpd.conf is correct and the cronolog binary has the correct permissions. Have you enabled somtehing like SE Linux or any apache directive that permits apache to start piped programs in the /root directory or that are not owned by the apache user?
you where correct the problem was SE linux i now have disabled the SELinux httpd deamon. don know if that is a proper or correct way to do. <SElinux is somehow new to me> so im open for any ideas to work around this problem and still enable the selinux httpd deamon. greetz TraXX
Maybe it helps to chown the cronolog binary to the httpd user or put the cronolog binary in the location where SE linux allows it to be exectuted (I'am not familar with SE linux so i dint know where it expects binarys).
If it helps anyone else (2 years on!) I've just discovered that there's more to disabling SELinux than just running system-config-securitylevel (that's assuming a Fedora variant). In one case that didn't, on it's own, disable SELinux. See this post for details! Thanks, Neil
