LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
LinkBack Search this Thread
Old 09-06-2007, 06:44 PM   #1
sundialsvcs
Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 5,062

Rep: Reputation: 972Reputation: 972Reputation: 972Reputation: 972Reputation: 972Reputation: 972Reputation: 972Reputation: 972
Unhappy How to diagnose: Apache exit(1) with empty error_log


Okay, okay, "me bad," I know that I am doing something where I easily deserve to be getting strange and cryptic error-messages. What I have not figured out in this case is how to go about diagnosing ... the utter and complete lack of any messages at all!

I have built an Apache 1.3 server from-source, and apachectl checkconfig runs clean. But when I try apachectl start I get the message "httpd could not be started," and there is an error-log file, and that error-log is completely empty. (Yes, this error-log is known to be brand-new, newly-created... known to be the log-file, and known to be empty.)

gdb tells me that the httpd program has ended with return-code "1" and that it did so completely normally. No segfault, no core dump, and no messages anywhere.

How might one diagnose this problem? Remember, I do have the source and I do, basically, know what I am doing. I'm sure that it basically comes down to an exit(1); but with no preceding sprintf()s that would have written to the logfile.

I guess my first thought is... does Apache have some "really great tell-you-what-I'm-doing-now" logging that I might turn on, so that it can give me a chatty play-by-play leading up to the problem?

Remember: I'm doing a custom build, from scratch, in a "nice out-of-the-way place," just for testing. I can start up the 'standard' Apache server on the box at any time, so I'm not dead in any water.

Last edited by sundialsvcs; 09-06-2007 at 06:47 PM.
 
Old 09-07-2007, 08:08 AM   #2
bigrigdriver
LQ Addict
 
Registered: Jul 2002
Location: East Centra Illinois, USA
Distribution: Debian Squeeze
Posts: 5,698

Rep: Reputation: 287Reputation: 287Reputation: 287
According to this, you should check the Errorlog Directive. If your config shows the /path/to/errorlog, try changing it to point to syslog instead. It might provide more information.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
apache error_log always full Suinatsa Linux - Software 1 07-21-2006 03:44 AM
Apache error_log Sapient Linux - Software 1 12-31-2005 08:10 PM
a better php/apache error_log joe.biz Linux - Software 1 10-27-2005 06:17 PM
apache looks empty... ebasi Linux - Software 2 08-05-2004 12:11 AM
Apache error_log "file not found" question WorldBuilder Linux - Networking 4 11-26-2003 12:53 PM


All times are GMT -5. The time now is 05:37 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration