Apache Cgi Error Logs
Contents |
Module Identifier:cgi_module Source File:mod_cgi.c Summary Any file that apache error logs ubuntu has the handler cgi-script will be treated as a CGI
Apache Error Logs Cpanel
script, and run by the server, with its output being returned to the client. apache error logs centos Files acquire this handler either by having a name containing an extension defined by the AddHandler directive, or by being in a href="../mod/mod_alias.html#scriptalias">ScriptAliasWhere Are Apache Error Logs Located
Configuring Apache to permit CGI Writing a CGI program But it's still not working! What's going on behind the scenes? CGI modules/libraries
Linux Apache Error Log
For more information See alsoComments Introduction Related ModulesRelated Directivesmod_aliasmod_cgimod_cgid href="../mod/mod_mime.html#addhandler">AddHandlerApache Cgi Python
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us http://stackoverflow.com/questions/2165022/how-can-i-troubleshoot-my-perl-cgi-script Learn more about Stack Overflow the company Business Learn more about hiring developers http://search.cpan.org/~jmoore/CGI-Log-1.00/Log.pm or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How can I troubleshoot my Perl CGI error log script? up vote 85 down vote favorite 55 I have a Perl script that isn't working and I don't know how to start narrowing down the problem. What can I do? Note: I'm adding the question because I really want to add my very lengthy answer to Stackoverflow. I keep externally linking to it in other answers and it deserves to be here. Don't be shy about apache error log editing my answer if you have something to add. perl cgi share|improve this question edited Jan 29 '10 at 20:53 community wiki 2 revsbrian d foy 2 @Evan - this claim is incorrect - it is simply a matter of rep. I think this should have remained without CW, but I'm glad the OP has some decent answers. –Marc Gravell♦ Feb 4 '10 at 5:33 @Marc, at the time the question was not CW, so we couldn't edit it, now that the OP, and the person with the answer (which he disclaimed in the question) has marked both as CW I can edit it. –Evan Carroll Feb 4 '10 at 16:17 5 @Evan - my point is simply that even as non-CW it still is editable - if you have enough karma; 100 for CW, 2k otherwise. So now you have 2060 you should be able to edit non-CW posts. –Marc Gravell♦ Feb 4 '10 at 16:39 Ah, I didn't know the magic point was at 2000 exp –Evan Carroll Feb 4 '10 at 17:41 1 @Evan, the magic points are listed in the tooltips in the right-hand column here: stackoverflow.com/privileges &ndash
POD View/Report Bugs Module Version: 1.00 Source NAME SYNOPSIS DESCRIPTION Types and Formats of Messages TIPS/TRICKS BUGS AUTHOR SEE ALSO NAME CGI::Log - Perl extension for centralized logging of debug, error, status and success messages from scripts or other modules. SYNOPSIS use CGI::Log; Log->debug("user: $user"); ## add messages Log->status("Welcome $user."); Log->error("I'm sorry $user, but you do not have access to that area."); @msg = Log->get_debug(); ## get messages @msg = Log->get_error(); @msg = Log->get_error("UI"); @msg = Log->get_status(); Log->is_error; ## test for messages Log->is_status; Log->is_success; Log->debug_off; ## causes print() and debug() to be skipped Log->print(); ## outputs debug and error logs in HTML Log->clear; ## clear all entries (current pid) Log->_report; ## reports the sizes of the arrays (lengths) Log->ui_no_error(); ## turns off inclusion of $! in user error messages DESCRIPTION This module acts as a central repository for debug, status and error messages. It instantiates itself automatically (if it needs to) so you can access the Log object functions from anywhere in you code including other modules/objects with a simple consistent syntax. It was written for CGI and mod_perl programming, but it could easily be used in any perl script where there is a need for centralized logging. (The only function which is CGI specific is print() since it outputs the debug and error logs with HTML formatting.) It was originally written to just hold debugging information, but it has been extended to hold information that you might want to return to the user (i.e. the user-interface). It is designed to be very painless to use. Add the following to any script or module where you want to log messages: use CGI::Log; The CGI::Log:: namespace has been aliased to Log:: in order to save a bit of typing when adding debugging messages. So, to add a debug message, enter: Log->debug("