| 1 |
On Tue, May 3, 2011 at 8:19 PM, Kevin O'Gorman <kogorman@×××××.com> wrote: |
| 2 |
|
| 3 |
> On Mon, May 2, 2011 at 8:30 PM, Adam Carter <adamcarter3@×××××.com> wrote: |
| 4 |
> |
| 5 |
>> |
| 6 |
>> |
| 7 |
>>>> Okay, there was already a thread about that, and my Python problem seems |
| 8 |
>>> solved. I still have no log entries. |
| 9 |
>>> |
| 10 |
>>> |
| 11 |
>> Ok, as root, try lsof | grep apache and see if there are any open log |
| 12 |
>> files. You may need to emerge lsof first if you dont already have it. |
| 13 |
>> |
| 14 |
>> IIRC apache fails to start if it cant write to the log directory - could |
| 15 |
>> be wrong on that tho. |
| 16 |
>> |
| 17 |
> |
| 18 |
> |
| 19 |
> So there should be an access_log, and there is, but it has not been touched |
| 20 |
> in a while: |
| 21 |
> treat apache2 # ls -l |
| 22 |
> |
| 23 |
> total 1584 |
| 24 |
> -rw-rw-rw- 1 apache apache 0 Feb 4 03:10 access_log |
| 25 |
> -rw-rw-rw- 1 apache apache 191438 Jun 15 2009 access_log.1.gz |
| 26 |
> -rw-rw-rw- 1 apache apache 111538 Dec 26 03:10 access_log-20101226.gz |
| 27 |
> -rw-rw-rw- 1 apache apache 15152 Jan 18 03:10 access_log-20110118.gz |
| 28 |
> -rw-rw-rw- 1 apache apache 179611 Jan 25 03:10 access_log-20110125.gz |
| 29 |
> -rw-rw-rw- 1 apache apache 16844 Feb 4 03:10 access_log-20110204.gz |
| 30 |
> -rw-rw-rw- 1 apache apache 234663 Jun 8 2009 access_log.2.gz |
| 31 |
> -rw-rw-rw- 1 apache apache 270349 Jun 1 2009 access_log.3.gz |
| 32 |
> -rw-rw-rw- 1 apache apache 277761 May 25 2009 access_log.4.gz |
| 33 |
> -rw-rw-rw- 1 apache apache 0 Feb 4 03:10 error_log |
| 34 |
> -rw-rw-rw- 1 apache apache 117611 Jun 15 2009 error_log.1.gz.out |
| 35 |
> -rw-rw-rw- 1 apache apache 33793 Dec 26 03:10 error_log-20101226.gz |
| 36 |
> -rw-rw-rw- 1 apache apache 3729 Jan 18 03:10 error_log-20110118.gz |
| 37 |
> -rw-rw-rw- 1 apache apache 34184 Jan 25 03:10 error_log-20110125.gz |
| 38 |
> -rw-rw-rw- 1 apache apache 4350 Feb 4 03:10 error_log-20110204.gz |
| 39 |
> -rw-rw-rw- 1 apache apache 5706 Jun 8 2009 error_log.2.gz |
| 40 |
> -rw-rw-rw- 1 apache apache 5628 Jun 1 2009 error_log.3.gz |
| 41 |
> -rw-rw-rw- 1 apache apache 6344 May 25 2009 error_log.4.gz |
| 42 |
> -rw-rw-rw- 1 apache apache 0 Feb 6 03:10 ssl_access_log |
| 43 |
> -rw-rw-rw- 1 apache apache 89 Dec 31 03:10 ssl_access_log-20101231.gz |
| 44 |
> -rw-rw-rw- 1 apache apache 137 Jan 22 03:10 ssl_access_log-20110122.gz |
| 45 |
> -rw-rw-rw- 1 apache apache 182 Jan 30 03:10 ssl_access_log-20110130.gz |
| 46 |
> -rw-rw-rw- 1 apache apache 89 Feb 6 03:10 ssl_access_log-20110206.gz |
| 47 |
> -rw-rw-rw- 1 apache apache 0 Feb 7 03:10 ssl_error_log |
| 48 |
> -rw-rw-rw- 1 apache apache 122 Dec 20 03:10 ssl_error_log-20101220.gz |
| 49 |
> -rw-rw-rw- 1 apache apache 122 Jan 18 03:10 ssl_error_log-20110118.gz |
| 50 |
> -rw-rw-rw- 1 apache apache 208 Jan 30 03:10 ssl_error_log-20110130.gz |
| 51 |
> -rw-rw-rw- 1 apache apache 203 Feb 7 03:10 ssl_error_log-20110207.gz |
| 52 |
> -rw-rw-rw- 1 apache apache 0 Feb 6 03:10 ssl_request_log |
| 53 |
> -rw-rw-rw- 1 apache apache 102 Dec 31 03:10 ssl_request_log-20101231.gz |
| 54 |
> -rw-rw-rw- 1 apache apache 158 Jan 22 03:10 ssl_request_log-20110122.gz |
| 55 |
> -rw-rw-rw- 1 apache apache 197 Jan 30 03:10 ssl_request_log-20110130.gz |
| 56 |
> -rw-rw-rw- 1 apache apache 103 Feb 6 03:10 ssl_request_log-20110206.gz |
| 57 |
> treat apache2 # |
| 58 |
> |
| 59 |
> -- |
| 60 |
> Kevin O'Gorman, PhD |
| 61 |
> |
| 62 |
> |
| 63 |
Well, 2.2.17 is indeed my server, but I decided to stop it and start it |
| 64 |
again. Current log files showed up. |
| 65 |
Problem solved, by brute force again, and without any epiphanies of |
| 66 |
understanding. |
| 67 |
|
| 68 |
Thanks for your help. |
| 69 |
|
| 70 |
|
| 71 |
-- |
| 72 |
Kevin O'Gorman, PhD |
Archives