Sponsored Content
Top Forums Web Development How to log http 404 error to a separate log file? Post 302985554 by raghur77 on Friday 11th of November 2016 07:21:56 AM
Old 11-11-2016
Hammer & Screwdriver How to log http 404 error to a separate log file?

Apache Web Server:
how to log http 404 error to a separate log file and i do not want to log in access.log
please advice.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Need to log http requests

Hi folks, I am trying to build this GUI application that will perform some http requests to a specific server. Basically I will use curl to "pretend" that it is a browser a sending an http request from a form. My http knowledge is very low, and the site is tricky, but I think if I could... (3 Replies)
Discussion started by: fundidor
3 Replies

2. Web Development

HTTP 404 Error Fetches File from Another Server

Has any seen any PHP or other scripting code that will executive on a 404 "File Not Found' error and then fetch the requested file from a different server? (0 Replies)
Discussion started by: Neo
0 Replies

3. Shell Programming and Scripting

Capture all error message in Log file and send the Log file by email

Hi I have a requirement to write a script to capture all errors in a Logfile and send the file in email. If there is any error occurred the subject of email will be ERROR , If there are no error occurred the subject of email will be SUCCESS. So I created a Log file and put the Appropriate... (2 Replies)
Discussion started by: dgmm
2 Replies

4. Shell Programming and Scripting

Saving svn log in a separate directory

Hi Folks, I have a directory at /usr/local/aa and there is other directory where I have checkout the code through svn checkout command ( /opt/app/fgh) now I can apply svn log command here as shown below $ cd /opt/app/fgh svn checkout <url> svn log shows me the log on console . please... (3 Replies)
Discussion started by: punpun66
3 Replies

5. Shell Programming and Scripting

How to grep a log file for words listed in separate text file?

Hello, I want to grep a log ("server.log") for words in a separate file ("white-list.txt") and generate a separate log file containing each line that uses a word from the "white-list.txt" file. Putting that in bullet points: Search through "server.log" for lines that contain any word... (15 Replies)
Discussion started by: nbsparks
15 Replies

6. Solaris

Log error from cron job into log file

Hi Please would it be right to log the errors from a script running in cron in the following manner: /datax/vendor/dump.sh > /datax/vendor/err.log 2>&1 (16 Replies)
Discussion started by: fretagi
16 Replies

7. Red Hat

Cant update yum what so ever [Errno 14] HTTP Error 404 - Not Found

Hello!!! I am so frustrated I'm about to snap!!! I cant hear any sound in Firefox or re-install Chrome. Every time I try to do anything with YUM inside my terminal (like update or install) I keep getting this error:failure: repodata/repomd.xml from virtualbox: No more mirrors to try. I... (2 Replies)
Discussion started by: ApacheOmega
2 Replies

8. Red Hat

HTTP/1.1 404 Not Found error in Web Server

I am running 2 jboss instances with ports 8585 and 8686 in my web server. Now trying to get header using the command curl -s --connect-timeout 360 -m 360 --head http: // localhost:8686/ then i get the following error HTTP/1.1 404 Not Found Server: Apache-Coyote/1.1 Content-Length: 0... (1 Reply)
Discussion started by: hridan
1 Replies

9. Shell Programming and Scripting

awk script to find time difference between HTTP PUT and HTTP DELETE requests in access.log

Hi, I'm trying to write a script to determine the time gap between HTTP PUT and HTTP DELETE requests in the HTTP Servers access log. Normally client will do HTTP PUT to push content e.g. file_1.txt and 21 seconds later it will do HTTP DELETE, but sometimes the time varies causing some issues... (3 Replies)
Discussion started by: Juha
3 Replies

10. UNIX for Advanced & Expert Users

Spacewalk repodata/repomd.xml [Errno 14] HTTP Error 404 - Not Found

I Configured spacwalk 2.7 and synchronized the channels as the root FS was and the server was unresponsive through gui i deleted the cache in /var/cache/rhn & /var/cache/yum and ran yum clean all on the server as well as spacewalk client i could see the following error Loaded plugins: rhnplugin... (0 Replies)
Discussion started by: James0806
0 Replies
LOG(1)							User Contributed Perl Documentation						    LOG(1)

NAME
Apache::Log -- Perl API for Apache Logging Methods Synopsis #in startup.pl #------------- use Apache::Log; my $s = Apache->server; $s->log_error("server: log_error"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_ERR, 0, "log_serror logging at err level"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "debug print"); Apache::Server->log_error("routine warning"); Apache->warn("routine warning"); Apache::warn("routine warning"); Apache::Server->warn("routine warning"); #in a handler #------------ use Apache::Log; sub handler{ my $r = shift; $r->log_error("request: log_error"); $r->warn("whoah!"); my $rlog = $r->log; for my $level qw(emerg alert crit error warn notice info debug) { no strict 'refs'; $rlog->$level($package, "request: $level log level"); } # can use server methods as well my $s = $r->server; $s->log_error("server: log_error"); $r->log_rerror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "in debug"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_INFO, 0, "server info"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_ERR, APR::ENOTIME, "fatal error"); $s->warn('routine server warning'); } Description "Apache::Log" provides the Perl API for Apache logging methods. Constants The following constants (sorted from the most severe level to the least severe) are used in logging methods to specify the log level at which the message should be logged: o "Apache::LOG_EMERG" o "Apache::LOG_ALERT" o "Apache::LOG_CRIT" o "Apache::LOG_ERR" o "Apache::LOG_WARNING" o "Apache::LOG_NOTICE" o "Apache::LOG_INFO" o "Apache::LOG_DEBUG" For example if the current "LogLevel" is set to warning, only messages with log level of the level warning or higher (err, crit, elert and emerg) will be logged. Therefore this: $r->log_rerror(Apache::LOG_MARK, Apache::LOG_WARNING, APR::ENOTIME, "warning!"); will log the message, but this one won't: $r->log_rerror(Apache::LOG_MARK, Apache::LOG_INFO, APR::ENOTIME, "just an info"); It will be logged only if the server log level is set to info or debug. (either in the configuration file or using the "$s->loglevel()" method.) Other constants: o "Apache::LOG_LEVELMASK" used to mask off the level value, to make sure that the log level's value is within the proper bits range. e.g.: $loglevel &= LOG_LEVELMASK; o "Apache::LOG_TOCLIENT" used to give content handlers the option of including the error text in the "ErrorDocument" sent back to the client. When "Apache::LOG_TOCLIENT" is passed to "log_rerror()" the error message will be saved in the $r's notes table, keyed to the string "error-notes", if and only if the severity level of the message is "Apache::LOG_WARNING" or greater and there are no other "error-notes" entry already set in the request record's notes table. Once the "error-notes" entry is set, it is up to the error handler to determine whether this text should be sent back to the client. For example: $r->log_rerror(Apache::LOG_MARK, Apache::LOG_ERR|Apache::LOG_TOCLIENT, APR::ENOTIME, "request log_rerror"); now the log message can be retrieved via: $r->notes->get("error-notes"); Remember that client generated text streams sent back to the client MUST be escaped to prevent CSS attacks. o "Apache::LOG_STARTUP" is set only during the startup. Server Logging Methods "$s->log_error()" $s->log_error(@message); just logs the supplied message. For example: $s->log_error("running low on memory"); "$s->log_serror()" log_serror($file, $line, $level, $status, @message); where: * $file The file in which this function is called * $line The line number on which this function is called * $level The level of this error message * $status The status code from the previous command * @message The log message This function provides a fine control of when the message is logged, gives an access to built-in status codes. For example: $s->log_serror(Apache::LOG_MARK, Apache::LOG_ERR, 0, "log_serror logging at err level"); $s->log_serror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "debug print"); "$s->log()" my $slog = $s->log; returns a handle which can be used to log messages of different level. See the next entry. emerg(), alert(), crit(), error(), warn(), notice(), info(), debug() $s->log->emerg(@message); after getting the log handle with "$s->log", use these methods to control when messages should be logged. For example: my $slog = $s->log; $slog->debug("just ", "some debug info"); $slog->warn(@warnings); $slog->crit("dying"); Request Logging Methods "$r->log_error()" $r->log_error(@message); logs the supplied message (similar to "$s->log_error"). For example: $r->log_error("the request is about to end"); the same as "$s->log_error". "$r->log_rerror()" log_rerror($file, $line, $level, $status, @message); same as "$s->log_rerror". For example: $s->log_rerror(Apache::LOG_MARK, Apache::LOG_ERR, 0, "log_rerror logging at err level"); $s->log_rerror(Apache::LOG_MARK, Apache::LOG_DEBUG, APR::ENOTIME, "debug print"); "$r->log()" my $rlog = $r->log; Similar to "$s->log()" the emerg(), alert(), crit(), error(), warn(), notice(), info(), debug() methods Similar to the server's log functions with the same names. For example: $rlog->debug("just ", "some debug info"); $rlog->warn(@req_warnings); $rlog->crit("dying"); General Functions "Apache::LOG_MARK()" my($file, $line) = Apache::LOG_MARK(); Though looking like a constant, this is a function, which returns a list of two items: "(__FILE__, __LINE__)", i.e. the file and the line where the function was called from. Aliases "$s->warn()" $s->warn(@warnings); is the same as: $s->log_error(Apache::LOG_MARK, Apache::LOG_WARNING, 0, @warnings) For example: $s->warn('routine server warning'); "Apache->warn()" "Apache::warn()" Apache->warn(@warnings); perl v5.8.0 2002-08-14 LOG(1)
All times are GMT -4. The time now is 02:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy