[mapserver-users] MapServer Errors in APACHE logs.

[Basques, Bob (CI-StPaul)]

Andy, 

I was just looking at it . . .  :c)

I think we can implement something through Apache to get at what I'm looking for.  I basically need to periodically check application access errors from time to time, and the process is rather tedious to do based on the CGI request alone, once it's even retrieved from the accessing client app.  Having the results showing up in a separated container is the end goal.

We are already applying some Apache magic to all our requests, I'll shoot this by the Web admin and see what extra filtering we can apply and try and figure out how much overhead something like this tracking might add onto the request process.

Thanks

Bobb



-----Original Message-----
From: Andy Colson [mailto:andy at squeakycode.net] 
Sent: Tuesday, April 29, 2014 3:15 PM
To: Basques, Bob (CI-StPaul); mapserver-users at lists.osgeo.org
Subject: Re: [mapserver-users] MapServer Errors in APACHE logs.

On 4/29/2014 1:55 PM, Basques, Bob (CI-StPaul) wrote:
> All,
>
> Has anyone done any work with capturing MapServer errors in APACHE?
> Specifically I want to be able to tell the difference between a 
> MapServer mis-config (textual error page) and a successful image
> response.   The idea is to somehow log those textual message responses
> in an automated way through Apache.
>
> I'm pretty sure I could make my own custom logfile for MapServer (CGI) 
> calls, but not so sure about textual response vs raster response 
> filters, at least from the APACHE point of view . . ..  Is a MapServer 
> Text based error page considered for inclusion in the Apache error log or??
>
> Thanks.
>
> Bobb
>


Have you checked your apache error log?  I'm running perl as fastcgi, and I get things like:

mod_fcgid: stderr:  maps.pl: msWMSLoadGetMapParams(): WMS server error. 
Invalid layer(s) given in the LAYERS parameter. A layer might be disabled for this request. Check wms/ows_enable_request settings.

The text vs raster response is only for sending errors to the browser, it wont affect whats written to the error log.

I think writing a thing to watch the error log is your best bet.  You could "simulate" some errors and see how it shows up in the error log.

-Andy