Apachectl Error Log
Contents |
a front end to the Apache HyperText Transfer Protocol (HTTP) server. It is designed to help the apache access log location administrator control the functioning of the Apache httpd daemon. The apache access log format apachectl script can operate in two modes. First, it can act as a simple front-end to the httpd command that simply sets any necessary environment variables and then invokes httpd, passing through any command line arguments. Second, apachectl can act as a SysV init script,
Apache Log Level
taking simple one-word arguments like start, restart, and stop, and translating them into appropriate signals to httpd. If your Apache installation uses non-standard paths, you will need to edit the apachectl script to set the appropriate paths to the httpd binary. You can also specify any necessary httpd command line arguments. See the comments in apache log rotation the script for details. The apachectl script returns a 0 exit value on success, and >0 if an error occurs. For more details, view the comments in the script. Synopsis Options See alsoStarting ApacheStopping ApacheConfiguration FilesPlatform DocshttpdComments Synopsis When acting in pass-through mode, apachectl can take all the arguments available for the httpd binary. apachectl [ httpd-argument ] When acting in SysV init mode, apachectl takes simple, one-word commands, defined below. apachectl command Options Only the SysV init-style options are defined here. Other arguments are defined on the httpd manual page. start Start the Apache httpd daemon. Gives an error if it is already running. This is equivalent to apachectl -k start. stop Stops the Apache httpd daemon. This is equivalent to apachectl -k stop. restart Restarts the Apache httpd daemon. If the daemon is not running, it is started. This command automatically checks the configuration files as in configtest before initiating the restart to make sure the daemon doesn't die. This is equivalent to a
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 apache error log format Business Learn more about hiring developers or posting ads with us Ask Different Questions
Apache Log Example
Tags Users Badges Unanswered Ask Question _ Ask Different is a question and answer site for power users of Apple hardware and software.
Apache Access Log Analyzer
Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Where is the httpd error https://httpd.apache.org/docs/2.4/programs/apachectl.html log file on Lion? up vote 24 down vote favorite 3 I'm running a local web (development) server on my mac with apache installed. I'm sure it depends on my apache config but basically I just want to run tail -f /var/log/httpd-error.log in a terminal so I can see the error and warnings that occur during the development of my websites. So my question is where or how do I find where this log file http://apple.stackexchange.com/questions/40713/where-is-the-httpd-error-log-file-on-lion is placed since it is not placed in /var/log/ lion osx apache share|improve this question edited Feb 20 '12 at 14:58 bmike♦ 115k38202438 asked Feb 17 '12 at 11:18 FLY 1,62751531 add a comment| 5 Answers 5 active oldest votes up vote 45 down vote accepted As morth pointed out, for the default Mac OS X Apache installation these are located in: /var/log/apache2/error_log. The location can be changed in the httpd config using the ErrorLog directive, even for individual virtual hosts. Also note that if you installed another Apache besides the built-in one (like through MacPorts, or MAMP), this probably is different for you too. In that case you should have a look at the httpd.conf or equivalent for your installation. tip: If you have Growl installed, also have a look at this 'growltail' script. I think it's great to get notified of errors while developing, without having the need to switch back to the Terminal all the time. share|improve this answer edited Jan 25 '13 at 15:57 FLY 1,62751531 answered Feb 17 '12 at 11:52 Gerry 11.1k33565 2 Doesn't lion use apache2 and not apache in /var/log to contain the web server logs? Also, the Console app in /Applications/Utilities is the "Cocoa" log viewer, but it's not as handy as tail for most developers other than to explore the conten
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 http://serverfault.com/questions/150249/best-way-to-troubleshoot-apache-not-starting site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault 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: Anybody can ask a question Anybody can error log answer The best answers are voted up and rise to the top Best way to troubleshoot apache not starting? up vote 4 down vote favorite 3 We have recently gotten a backup server to mirror all our data onto in case the primary server goes down. I've gotten all the sites data updated through rsync, and all the apache config and databases updated. Both machines apache access log are on Ubuntu 9 (9.04 on the primary, 9.10 on the backup). So everything seems synced up for the most part at this point (still need to figure out user syncing), and I try to start Apache. I get * Starting web server apache2 [fail] Nothing else indicating what the problem could be. I know I don't have enough info to expect a solution from you guys, so I'd just like to know where I can go from here to further investigate this issue. Would there be any error logs for this? Thanks! apache-2.2 troubleshooting share|improve this question asked Jun 10 '10 at 21:22 Lowgain 147115 so far, I have found logs saying "No such file or directory: mod_fcgid" - this is a good start –Lowgain Jun 10 '10 at 21:25 add a comment| 3 Answers 3 active oldest votes up vote 7 down vote accepted In some specific cases, a log entry will not be written to disk -- this can occur if logs don't exist, for example, or Apache simply cannot write to the log files due to permissions issues, etc. In such cases, the best way to d