Access log is erratic with my scripts

After seeing logs mentioned above, I remembered this.

I do not see my scripts appearing properly in access log

I have an older script that never shows an access into the log (only errors)
I have a new script with same name but a few differences in two
different virtual hosts.

After a stop start, one script shows posts the other does not show anything.
The older script, nothing.

--
A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects.
-- Robert Heinlein

Re: Access log is erratic with my scripts

On Tue, Apr 27, 2010 at 1:07 PM, Chris Bennett
wrote:
> I do not see my scripts appearing properly in access log

That probably means your scripts are crashing before they finish. You
could use mod_log_forensic to find out more.

- Perrin

Re: Access log is erratic with my scripts

On 04/27/10 13:28, Perrin Harkins wrote:
> On Tue, Apr 27, 2010 at 1:07 PM, Chris Bennett
> wrote:
>> I do not see my scripts appearing properly in access log
>
> That probably means your scripts are crashing before they finish. You
> could use mod_log_forensic to find out more.
>
> - Perrin
>
This was a helpful suggestion, but it is not available on the default
apache with OpenBSD. I will look into how this works, anyway.

I just realized the problem, since I was running a similiar script with
one host non-SSL and the other SSL. The fact of access is only recorded
in SSl logs, not access logs. I did not realize this before.
This has security implications in that I should be monitoring SSL logs
also. I have read plenty of security "stuff" but I don't remeber ever
seeing that that needs to be done.

Thanks

Re: Access log is erratic with my scripts

On Tue, Apr 27, 2010 at 3:48 PM, Chris Bennett
wrote:
> I just realized the problem, since I was running a similiar script with one
> host non-SSL and the other SSL. The fact of access is only recorded in SSl
> logs, not access logs.

I don't think that's true. My access logs show both SSL and non-SSL
requests. Maybe you've configured yours to log to a different file
for certain virtual hosts.

- Perrin

Re: Access log is erratic with my scripts

Perrin Harkins wrote:
> On Tue, Apr 27, 2010 at 1:07 PM, Chris Bennett
> wrote:
>> I do not see my scripts appearing properly in access log
>
> That probably means your scripts are crashing before they finish. You
> could use mod_log_forensic to find out more.
>
Maybe something also useful to point out : if you are using Apache 2.x +
mod_perl 2.x and VirtualHost's, then most perl error messages will
appear in the error log of the VirtualHost "running" the script/handler
(*)(as one would expect), but some do appear in the "main" server's
error log. I never could figure out what determines the choice really.

"Invalid/Incomplete headers from script" (or something similar) is one
of those. Warnings about concatenating an undef value with a string
also, as I recall.



(*) I guess canonically, I should have said : the error log file
configured for the VirtualHost whose configuration was selected to
process the request for which the script/handler runs.
But that was quite a mouthful.

Re: Access log is erratic with my scripts

On 04/27/10 12:07, Chris Bennett wrote:
> After seeing logs mentioned above, I remembered this.
>
> I do not see my scripts appearing properly in access log
>
> I have an older script that never shows an access into the log (only
> errors)
> I have a new script with same name but a few differences in two
> different virtual hosts.
>
> After a stop start, one script shows posts the other does not show
> anything.
> The older script, nothing.
>

I have to admit, I have had many small problems with the SSL section of
conf. I did not realize that I had to add error and transfer log
sections to SSL area also. I was getting errors in error log before, so
this problem didn't jump to the top of my head.

This was always the problem

I think I need to go ahead and break into files for each virtual host to
avoid these little errors. I have also had other similar errors before,
which went away after adding the new section to ssl also.

a quick diff will pop these errors out quickly.