Httpd Could Not Open Error Log File /private/var/log/apache2/error_log
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of permission denied httpd could not open error log file this site About Us Learn more about Stack Overflow the company Business
Unable To Open Logs Httpd Start
Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ could not open configuration file etc httpd conf httpd conf permission denied Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody
Httpd Unable To Open Logs Centos
can answer The best answers are voted up and rise to the top I always get “No such file or directory: apache2: could not open error log file /etc/apache2/$ apache_log_dir /error.log” how cat I fix this up vote 4 down vote favorite 2 I am using Ubuntu Studio 12.04 and when I am trying to start apache2, I get this error message: No such file unable to open logs apache or directory: apache2: could not open error log file /etc/apache2/$ apache_log_dir /error.log This meas, I should have a path like this /etc/apache2/var/log/apache2/ but in envvars the log dir is defined as /var/log/apache2$SUFFIX not /etc/apache2/ How can I fix this. apache2 share|improve this question edited Feb 17 '13 at 9:00 Andrea Corbellini 8,96713254 asked Feb 17 '13 at 8:56 user132827 21112 could you please post the envvars file data through pastebin ? –Raja Feb 17 '13 at 9:15 pastebin.com/iHrtUMYq thats my envvars file on pastebin –user132827 Feb 17 '13 at 9:23 What does grep ErrorLog /etc/apache2/sites-enabled/* print? –Florian Diesch Feb 18 '13 at 1:01 I created the path /var/log/apache2 but every time I restart my Pc apapche2 is gone HELP PLEASE D: –user267331 Apr 10 '14 at 5:18 add a comment| 1 Answer 1 active oldest votes up vote 3 down vote Look at your vhosts-files in /etc/apache2/sites-available/
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers
Starting Httpd: No Listening Sockets Available, Shutting Down
or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault
Ah00014: Configuration Check Failed
is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: ah00015: unable to open logs Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Why can't apache create log files? up vote 1 down vote favorite I have a simple LAMP stack on CentOS setup. Apache http://askubuntu.com/questions/257237/i-always-get-no-such-file-or-directory-apache2-could-not-open-error-log-file is setup with vhosts and each developer has their web files inside their user folder. The directory structure is like so (for the user test): /home/test |_ apache |_ domain1.com |_ backups |_ conf |_ vhost.conf |_ logs |_ errors.log |_ images.log |_ web.log |_ private |_ public The vhost config is in the vhost.conf file. The log files in logs don't exist when the config is first setup, and this throws an error with apache when I run service httpd http://serverfault.com/questions/590012/why-cant-apache-create-log-files restart: (13)Permission denied: httpd: could not open error log file /home/test/apache/domain1.com/logs/error.log. Unable to open logs I tried running httpd -X as root and it created the log files (with root ownership/group). I thought it would be a case of making sure that the files are there, with group set as apache and writeable (so I don't have to make the whole directory belong to apache group and writeable), but this confuses me: [root@dev logs]# ls -al total 16 drwxr-xr-x. 2 test developers 4096 Apr 18 21:02 . drwxr-xr-x. 8 test developers 4096 Apr 18 20:25 .. -rw-r--r--. 1 test developers 1818 Apr 18 21:02 error.log -rw-r--r--. 1 test developers 14 Apr 18 20:25 .gitignore -rw-r--r--. 1 test developers 0 Apr 18 20:54 image.log [root@dev logs]# service httpd restart Stopping httpd: [ OK ] Starting httpd: [FAILED] [root@dev logs]# touch web.log [root@dev logs]# chown test:developers web.log [root@dev logs]# service httpd restart Stopping httpd: [FAILED] Starting httpd: [ OK ] I'm confused because apache runs as user apache and shouldn't have write access on the logs, should it? In fact, I can even do this: [root@dev logs]# rm -f ./*.log [root@dev logs]# touch {error.log,image.log,web.log} [root@dev logs]# ls -al total 12 drwxr-xr-x. 2 test developers 4096 Apr 18 21:10 . drwxr-xr-x. 8 test developers 4096 Apr 18 20:25 .. -rw-r--r--. 1 root root 0 Apr 18 21:10 error.log -rw-r--r--. 1 test developers 14 Apr 18 20:25 .gitignore -rw-r--r--. 1 root root 0 Apr 18 21:10 im
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu https://ubuntuforums.org/showthread.php?t=2037520 Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: http://forums.fedoraforum.org/showthread.php?t=230294 Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community unable to Ubuntu Official Flavours Support General Help [SOLVED] Apache: restart results in "can't open log file" error Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 2 of 2 Thread: Apache: restart results in "can't unable to open open log file" error Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode August 4th, 2012 #1 slipstream180 View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date May 2009 Beans 11 Apache: restart results in "can't open log file" error I was recently tweaking some log file configuration in my /etc/apache2/sites-enabled/my.file file. I also changed some things in my /etc/apache2/apache2.conf file. (Comment out ServerRoot line) Now when I attempt to restart apache I get: Code: (2)No such file or directory: apache2: could not open error log file /etc/apache2/{$APACHE_LOG_DIR}/error.log. Unable to open logs Action 'start' failed. I've tried everything, but can't figure out why apache is prepending /etc/apache2 to the log directory path. (The actual path is the standard /var/log/apache2 dir) Here's my /etc/apache2/envvars file: Code: # envvars - default environment variables for apache2ctl # this won't be correct after changing uid unset HOME # fo
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Servers & Networking service httpd restart not working FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 17th September 2009, 12:23 AM ruchita Offline Registered User Join Date: Sep 2009 Posts: 9 service httpd restart not working I'm getting the following error when i run service httpd restart: [root@localhost ruchita]# service httpd restart Stopping httpd: [FAILED] Starting httpd: (13)Permission denied: httpd: could not open error log file /etc/httpd/logs/error_log. Unable to open logs [FAILED] Also the SElinux shows the following alert: Summary: SELinux prevented httpd reading and writing access to http files. Detailed Description: SELinux prevented httpd reading and writing access to http files. Ordinarily httpd is allowed full access to all files labeled with http file context. This machine has a tightened security policy with the httpd_unified turned off, this requires explicit labeling of all files. If a file is a cgi script it needs to be labeled with httpd_TYPE_script_exec_t in order to be executed. If it is read-only content, it needs to be labeled httpd_TYPE_content_t, it is writable content. it needs to be labeled httpd_TYPE_script_rw_t or httpd_TYPE_script_ra_t. You can u