On Tue, May 3, 2011 at 8:19 PM, Kevin O'Gorman <kogor...@gmail.com> wrote:
> On Mon, May 2, 2011 at 8:30 PM, Adam Carter <adamcart...@gmail.com> wrote: > >> >> >>>> Okay, there was already a thread about that, and my Python problem seems >>> solved. I still have no log entries. >>> >>> >> Ok, as root, try lsof | grep apache and see if there are any open log >> files. You may need to emerge lsof first if you dont already have it. >> >> IIRC apache fails to start if it cant write to the log directory - could >> be wrong on that tho. >> > > > So there should be an access_log, and there is, but it has not been touched > in a while: > treat apache2 # ls -l > > total 1584 > -rw-rw-rw- 1 apache apache 0 Feb 4 03:10 access_log > -rw-rw-rw- 1 apache apache 191438 Jun 15 2009 access_log.1.gz > -rw-rw-rw- 1 apache apache 111538 Dec 26 03:10 access_log-20101226.gz > -rw-rw-rw- 1 apache apache 15152 Jan 18 03:10 access_log-20110118.gz > -rw-rw-rw- 1 apache apache 179611 Jan 25 03:10 access_log-20110125.gz > -rw-rw-rw- 1 apache apache 16844 Feb 4 03:10 access_log-20110204.gz > -rw-rw-rw- 1 apache apache 234663 Jun 8 2009 access_log.2.gz > -rw-rw-rw- 1 apache apache 270349 Jun 1 2009 access_log.3.gz > -rw-rw-rw- 1 apache apache 277761 May 25 2009 access_log.4.gz > -rw-rw-rw- 1 apache apache 0 Feb 4 03:10 error_log > -rw-rw-rw- 1 apache apache 117611 Jun 15 2009 error_log.1.gz.out > -rw-rw-rw- 1 apache apache 33793 Dec 26 03:10 error_log-20101226.gz > -rw-rw-rw- 1 apache apache 3729 Jan 18 03:10 error_log-20110118.gz > -rw-rw-rw- 1 apache apache 34184 Jan 25 03:10 error_log-20110125.gz > -rw-rw-rw- 1 apache apache 4350 Feb 4 03:10 error_log-20110204.gz > -rw-rw-rw- 1 apache apache 5706 Jun 8 2009 error_log.2.gz > -rw-rw-rw- 1 apache apache 5628 Jun 1 2009 error_log.3.gz > -rw-rw-rw- 1 apache apache 6344 May 25 2009 error_log.4.gz > -rw-rw-rw- 1 apache apache 0 Feb 6 03:10 ssl_access_log > -rw-rw-rw- 1 apache apache 89 Dec 31 03:10 ssl_access_log-20101231.gz > -rw-rw-rw- 1 apache apache 137 Jan 22 03:10 ssl_access_log-20110122.gz > -rw-rw-rw- 1 apache apache 182 Jan 30 03:10 ssl_access_log-20110130.gz > -rw-rw-rw- 1 apache apache 89 Feb 6 03:10 ssl_access_log-20110206.gz > -rw-rw-rw- 1 apache apache 0 Feb 7 03:10 ssl_error_log > -rw-rw-rw- 1 apache apache 122 Dec 20 03:10 ssl_error_log-20101220.gz > -rw-rw-rw- 1 apache apache 122 Jan 18 03:10 ssl_error_log-20110118.gz > -rw-rw-rw- 1 apache apache 208 Jan 30 03:10 ssl_error_log-20110130.gz > -rw-rw-rw- 1 apache apache 203 Feb 7 03:10 ssl_error_log-20110207.gz > -rw-rw-rw- 1 apache apache 0 Feb 6 03:10 ssl_request_log > -rw-rw-rw- 1 apache apache 102 Dec 31 03:10 ssl_request_log-20101231.gz > -rw-rw-rw- 1 apache apache 158 Jan 22 03:10 ssl_request_log-20110122.gz > -rw-rw-rw- 1 apache apache 197 Jan 30 03:10 ssl_request_log-20110130.gz > -rw-rw-rw- 1 apache apache 103 Feb 6 03:10 ssl_request_log-20110206.gz > treat apache2 # > > -- > Kevin O'Gorman, PhD > > Well, 2.2.17 is indeed my server, but I decided to stop it and start it again. Current log files showed up. Problem solved, by brute force again, and without any epiphanies of understanding. Thanks for your help. -- Kevin O'Gorman, PhD
