Error log empty

(PHP 4, PHP 5, PHP 7, PHP 8)

(PHP 4, PHP 5, PHP 7, PHP 8)

error_log — Send an error message to the defined error handling routines

Description

error_log(
    string $message,
    int $message_type = 0,
    ?string $destination = null,
    ?string $additional_headers = null
): bool

Parameters

message

The error message that should be logged.

message_type

Says where the error should go. The possible message types are as
follows:

error_log() log types

0 message is sent to PHP’s system logger, using
the Operating System’s system logging mechanism or a file, depending
on what the error_log
configuration directive is set to. This is the default option.
1 message is sent by email to the address in
the destination parameter. This is the only
message type where the fourth parameter,
additional_headers is used.
2 No longer an option.
3 message is appended to the file
destination. A newline is not automatically
added to the end of the message string.
4 message is sent directly to the SAPI logging
handler.
destination

The destination. Its meaning depends on the
message_type parameter as described above.

additional_headers

The extra headers. It’s used when the message_type
parameter is set to 1.
This message type uses the same internal function as
mail() does.

Return Values

Returns true on success or false on failure.
If message_type is zero, this function always returns true,
regardless of whether the error could be logged or not.

Changelog

Version Description
8.0.0 destination and
additional_headers are now nullable.

Examples

Example #1 error_log() examples


<?php
// Send notification through the server log if we can not
// connect to the database.
if (!Ora_Logon($username, $password)) {
error_log("Oracle database not available!", 0);
}// Notify administrator by email if we run out of FOO
if (!($foo = allocate_new_foo())) {
error_log("Big trouble, we're all out of FOOs!", 1,
"operator@example.com");
}// another way to call error_log():
error_log("You messed up!", 3, "/var/tmp/my-errors.log");
?>

Notes

Warning

error_log() is not binary safe. message will be truncated by null character.

Tip

message should not contain null character. Note that message may be sent to file, mail, syslog, etc. Use appropriate conversion/escape function, base64_encode(), rawurlencode() or addslashes() before calling error_log().

kevindougans at gmail dot com

12 years ago


Advice to novices: This function works great along with "tail" which is a unix command to watch a log file live. There are versions of Tail for Windows too, like Tail for Win32 or Kiwi Log Viewer.

Using both error_log() and tail to view the php_error.log you can debug code without having to worry so much about printing debug messages to the screen and who they might be seen by.

Further Note: This works even better when you have two monitors setup. One for your browser and IDE and the other for viewing the log files update live as you go.


Sion

4 years ago


DO NOT try to output TOO LARGE texts in the error_log();

if you try to output massive amounts of texts it will either cut of the text at about 8ooo characters (for reasonable massive strings, < 32 K characters) or (for insanely massive strings, about 1.6 million characters) totally crash without even throwing an error or anything (I even put it in a try/catch without getting any result from the catch).

I had this problem when I tried to debug a response from a wp_remote_get(); all of my error_log() worked as they should, except for ONE of them... (-_-)
After about a day of debugging I finally found out why & that's why I type this.

Apparently the response contained a body with over 1.6 million chars (or bytes? (whatever strlen() returns)).

If you have a string of unknown length, use this:
$start_index = 0;
$end_index = 8000;
error_log( substr( $output_text , $start_index , $end_index ) );


frank at booksku dot com

16 years ago


Beware!  If multiple scripts share the same log file, but run as different users, whichever script logs an error first owns the file, and calls to error_log() run as a different user will fail *silently*!

Nothing more frustrating than trying to figure out why all your error_log calls aren't actually writing, than to find it was due to a *silent* permission denied error!


i dot buttinoni at intandtel dot com

14 years ago


Be carefull. Unexpected PHP dies when 2GByte of file log reached (on systems having upper file size limit).
A work aorund is rotate logs :)

php at kennel17 dot NOSPAM dot co dot uk

17 years ago


It appears that the system log = stderr if you are running PHP from the command line, and that often stderr = stdout.  This means that if you are using a custom error to both display the error and log it to syslog, then a command-line user will see the same error reported twice.

Anonymous

19 years ago


when using error_log to send email, not all elements of an extra_headers string are handled the same way.  "From: " and "Reply-To: " header values will replace the default header values. "Subject: " header values won't: they are *added* to the mail header but don't replace the default, leading to mail messages with two Subject fields.

<?php

error_log

("sometext", 1, "zigzag@my.domain",
  "Subject: FoonFrom: Rizzlas@my.domainn");?>

---------------%<-----------------------
To: zigzag@my.domain
Envelope-to: zigzag@my.domain
Date: Fri, 28 Mar 2003 13:29:02 -0500
From: Rizzlas@my.domain
Subject: PHP error_log message
Subject: Foo
Delivery-date: Fri, 28 Mar 2003 13:29:03 -0500

sometext
---------------%<---------------------

quoth the docs: "This message type uses the same internal function as mail() does." 

mail() will also fail to set a Subject field based on extra_header data - instead it takes a seperate argument to specify a "Subject: " string.

php v.4.2.3, SunOS 5.8


russ at russtanner dot com

3 years ago


You can easily filter messages sent to error_log() using "tail" and "grep" on *nix systems. This makes monitoring debug messages easy to see during development.

Be sure to "tag" your error message with a unique string so you can filter it using "grep":

In your code:

error_log("DevSys1 - FirstName: $FirstName - LastName: $Lastname");

On your command line:

tail -f /var/log/httpd/error_log | grep DevSys1

In this example, we pipe apache log output to grep (STDIN) which filters it for you only showing messages that contain "DevSys1".

The "-f" option means "follow" which streams all new log entries to your terminal or to any piped command that follows, in this case "grep".


Matthew Swift

3 years ago


Relative paths are accepted as the destination of message_type 3, but beware that the root directory is determined by the context of the call to error_log(), which can change, so that one instance of error_log () in your code can lead to the creation of multiple log files in different locations.

In a WordPress context, the root directory will be the site's root in many cases, but it will be /wp-admin/ for AJAX calls, and a plugin's directory in other cases. If you want all your output to go to one file, use an absolute path.


paul dot chubb at abs dot gov dot au

14 years ago


When logging to apache on windows, both error_log and also trigger_error result in an apache status of error on the front of the message. This is bad if all you want to do is log information. However you can simply log to stderr however you will have to do all message assembly:

LogToApache($Message) {
        $stderr = fopen('php://stderr', 'w');
        fwrite($stderr,$Message);
        fclose($stderr);
}


SJL

15 years ago


"It appears that the system log = stderr if you are running PHP from the command line"

Actually, it seems that PHP logs to stderr if it can't write to the log file. Command line PHP falls back to stderr because the log file is (usually) only writable by the webserver.


stepheneliotdewey at GmailDotCom

15 years ago


Note that since typical email is unencrypted, sending data about your errors over email using this function could be considered a security risk. How much of a risk it is depends on how much and what type of information you are sending, but the mere act of sending an email when something happens (even if it cannot be read) could itself imply to a sophisticated hacker observing your site over time that they have managed to cause an error.

Of course, security through obscurity is the weakest kind of security, as most open source supporters will agree. This is just something that you should keep in mind.

And of course, whatever you do, make sure that such emails don't contain sensitive user data.


p dot lhonorey at nospam-laposte dot net

16 years ago


Hi !

Another trick to post "HTML" mail body. Just add "Content-Type: text/html; charset=ISO-8859-1" into extra_header string. Of course you can set charset according to your country or Env or content.

EG: Error_log("<html><h2>stuff</h2></html>",1,"eat@joe.com","subject  :lunchnContent-Type: text/html; charset=ISO-8859-1");

Enjoy !


eguvenc at gmail dot com

14 years ago


<?php

//Multiline error log class

// ersin güvenç 2008 eguvenc@gmail.com

//For break use "n" instead 'n'
Class log {

  //

  const USER_ERROR_DIR = '/home/site/error_log/Site_User_errors.log';

  const GENERAL_ERROR_DIR = '/home/site/error_log/Site_General_errors.log';
/*

   User Errors...

  */

    public function user($msg,$username)

    {

    $date = date('d.m.Y h:i:s');

    $log = $msg."   |  Date:  ".$date."  |  User:  ".$username."n";

    error_log($log, 3, self::USER_ERROR_DIR);

    }

    /*

   General Errors...

  */

    public function general($msg)

    {

    $date = date('d.m.Y h:i:s');

    $log = $msg."   |  Date:  ".$date."n";

    error_log($msg."   |  Tarih:  ".$date, 3, self::GENERAL_ERROR_DIR);

    }

}

$log = new log();

$log->user($msg,$username); //use for user errors

//$log->general($msg); //use for general errors

?>

franz at fholzinger dot com

17 years ago


In the case of missing your entries in the error_log file:
When you use error_log in a script that does not produce any output, which means that you cannot see anything during the execution of the script, and when you wonder why there are no error_log entries produced in your error_log file, the reasons can be:
- you did not configure error_log output in php.ini
- the script has a syntax error and did therefore not execute

daniel dot fukuda at gmail dot com

13 years ago


If you have a problem with log file permission *silently*
it's best to leave error_log directive unset so errors will be written in your Apache log file for current VirtualHost.

Anonymous

2 years ago


Depending on the error, you may also want to add an error 500 header, and a message for the user:

$message =  'Description of the error.';
error_log($message);
header($_SERVER['SERVER_PROTOCOL'] . ' 500 Internal Server Error', true, 500);
exit($message);


Robert Chapin

4 years ago


When error_log() unexpectedly uses stdout, you should check if the php.ini value for error_log is empty in your CLI environment.  Something as simple as this might restore expected behavior:

<?php ini_set('error_log', 'error_log'); ?>


kazezb at nospam dot carleton dot edu

17 years ago


It appears that error_log() only logs the first line of multi-line log messages. To log a multi-line message, either log each line individually or write the message to another file.

Anonymous

13 years ago


After scouring the internet for getting event logging to
work in syslog on Windows 2003, I found the following
from this post and was able to successfully get Windows
Event Viewer to log PHP errors/notices:

http://forums.iis.net/p/1159662/1912015.aspx#1913338

   1. Copy the PHP 5 binaries to "C:php".
   2. Right-click My Computer and select Properties to bring
up the Computer Properties dialog. Switch to the Advanced
tab and click Environment Variables. Find the system
environment variable PATH, edit it and add ";C:php"
(without the quotes) to the end.
   3. Make sure that the configuration file "php.ini" resides
in the directory "C:php" and contains the correct path
settings.
   4. DELETE any old "php.ini" files from "C:WINDOWS"
and other directories.
   5. Open REGEDIT, navigate to the key
"HKLMSOFTWAREPHP" and DELETE the string value
"IniFilePath" from there. It is outdated and no longer
necessary!
   6. Modify NTFS security permissions of the directory
"C:php" to give Read and Execute permissions to (1) the
IIS Guest Account and (2) the group IIS_WPG.
   7. Modify NTFS security permissions of the directories
"C:phpsession" and "C:phpupload" to give additional
Modify permissions to (1) the IIS Guest Account and (2)
the group IIS_WPG.
   8. Navigate to the registry key
"HKLMSYSTEMCurrentControlSetServicesEventlog
Application" and edit the value "CustomSD" there. Find
the substring "(D;;0xf0007;;;BG)" which Denies access to
the application event log for Builtin Guest accounts (like
the IIS Web User account) and replace this substring with
"(A;;0x3;;;BG)" which allows read and write access. Please
pay attention to leave the rest of the security string intact.
Damaging this value can have dangerous effects!
   9. Create or update the registry key
"HKLMSYSTEMCurrentControlSetServicesEventlogApplication
PHP-5.2.0" (adapt the last to your version part
if necessary) with the following values:

          * "EventMessageFile" (REG_EXPAND_SZ) = "C:phpphp5ts.dll"

          * "TypesSupported" (REG_DWORD) = 7


Источник

While analyzing a connection problem between a client and a MariaDB 10.2 server, the so-called «error log» needed to be checked for warnings and errors. However the file (/var/log/mysql/error.log) did not contain any logged events.

Checking configuration and permissions

First thing to verify is the MySQL/MariaDB config whether or not the error_log was actually enabled. On this machine, running MariaDB 10.2 on Ubuntu 18.04 (Bionic), the config files seemed in order:

ck@mariadb:~$ cat /etc/mysql/conf.d/mariadb.cnf | grep error
# log errors
log_error=/var/log/mysql/error.log

But the running config needs to be verified as well. This can be done by checking the global variables:

root@mariadb:~# mysql
Welcome to the MariaDB monitor.  Commands end with ; or g.
Your MariaDB connection id is 308342315
Server version: 10.2.28-MariaDB-1:10.2.28+maria~bionic-log mariadb.org binary distribution

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type ‘help;’ or ‘h’ for help. Type ‘c’ to clear the current input statement.

MariaDB [(none)]> show global variables where variable_name like ‘%error%’;
+———————+—————————+
| Variable_name      | Value                    |
+———————+—————————+
| log_error          | /var/log/mysql/error.log |
| max_connect_errors | 100                      |
| max_error_count    | 64                       |
| slave_skip_errors  | OFF                      |
+———————+—————————+
4 rows in set (0.00 sec)

Same here: The log_error variable is set to a path — which means error logging is enabled.

Another potential reason of failure could be that the file does not exist, or that the permissions are wrong. The MySQL/MariaDB process, running usually under the user «mysql», needs to be able to write into this file:

root@mariadb:/var/log/mysql# ls -la
total 6717652
-rw-r—— 1 mysql adm         0 Oct 20 00:08 error.log
-rw-r—— 1 mysql adm         0 Oct 19 00:07 error.log.1
-rw-r—— 1 mysql adm   5037450 Apr 10  2020 error.log.8.gz
-rw-rw—- 1 mysql adm 105161366 Oct 18 11:58 mariadb-bin.007219
-rw-rw—- 1 mysql adm 105400817 Oct 18 13:26 mariadb-bin.007220
[…]

Inside the directory /var/log/mysql/ the files are listed. The error.log file clearly exists, and with the correct permissions; the mysql user is owner and can therefore read and write this file. However the size is 0 — meaning the file is empty and nothing was logged.

The fact that the MariaDB process is able to successfully write the binary logs (which are enabled on this machine, too) in the same path, shows that there is definitely no permission problem.

Syslog redirection in place!

It turns out that with the MariaDB package, an additional config file was installed, redirecting the error log to syslog under the [mysqld_safe] config section:

admck@mariadb:~$ cat /etc/mysql/conf.d/mysqld_safe_syslog.cnf
[mysqld_safe]
skip_log_error
syslog

This config file was installed by the mariadb-server package:

admck@mariadb:~$ dpkg -S /etc/mysql/conf.d/mysqld_safe_syslog.cnf
mariadb-server-10.2: /etc/mysql/conf.d/mysqld_safe_syslog.cnf

As Ubuntu starts MySQL/MariaDB with mysqld_safe (which can be seen in the process list), these config options are read and applied during the start of MariaDB. They cause the following behaviour:

  • skip_log_error: If log_error was set in a config file, this parameter causes MySQL/MariaDB to ignore the log_error variable — therefore switching off the error logging
  • syslog: This parameter tells MySQL/MariaDB to log to syslog instead of a dedicated file

It’s important to note that log_error and syslog cannot co-exist! Otherwise a warning will be issued and log_error takes precedence.

Once these two config options were commented/disabled and MariaDB restarted, the /var/log/mysql/error.log now started to log warnings and errors:

admck@mariadb:~$ ls -la /var/log/mysql/error.log
-rw-r—— 1 mysql adm 953061 Oct 20 17:14 /var/log/mysql/error.log

Add a comment

Show form to leave a comment

Comments (newest first)

No comments yet.

Источник
  • Home
  • Forum
  • The Ubuntu Forum Community
  • Ubuntu Specialised Support
  • Ubuntu Servers, Cloud and Juju
  • Server Platforms
  • Apache2 empty error.log

  1. Apache2 empty error.log

    OK. I decided to start new topic for this question.

    Well. What i have:

    Code:

    lsb_release -a
No LSB modules are available.
Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.1 LTS
Release:    14.04
Codename:    trusty

    Code:

     apache2 -v
Server version: Apache/2.4.7 (Ubuntu)
Server built:   Jul 22 2014 14:36:38

    All are fresh installed. Apache is without any modification so i have only default virtual host with default settings and log files.

    cat /etc/apache2/sites-available/000-default.conf

    Code:

    <VirtualHost *:80>
    # The ServerName directive sets the request scheme, hostname and port that
    # the server uses to identify itself. This is used when creating
    # redirection URLs. In the context of virtual hosts, the ServerName
    # specifies what hostname must appear in the request's Host: header to
    # match this virtual host. For the default virtual host (this file) this
    # value is not decisive as it is used as a last resort host regardless.
    # However, you must set it for any further virtual host explicitly.
    #ServerName www.example.com

    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html

    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the loglevel for particular
    # modules, e.g.
    #LogLevel info ssl:warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    # For most configuration files from conf-available/, which are
    # enabled or disabled at a global level, it is possible to
    # include a line for only one particular virtual host. For example the
    # following line enables the CGI configuration for this host only
    # after it has been globally disabled with "a2disconf".
    #Include conf-available/serve-cgi-bin.conf
</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

    The problem is that in my error.log I see only server restart messages. Like:

    Code:

    cat ./error.log
[Mon Jan 26 23:36:25.010217 2015] [mpm_event:notice] [pid 1611:tid 139708328335232] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
[Mon Jan 26 23:36:25.010365 2015] [core:notice] [pid 1611:tid 139708328335232] AH00094: Command line: '/usr/sbin/apache2'

    In the same time in access.log a see all GET requests to my server: normal requests, bad requests, spammers e.t.c.

    Code:

    cat ./access.log 
93.185.181.155 - - [26/Jan/2015:23:36:31 +0300] "GET /favicon.ico HTTP/1.0" 404 516 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"
93.185.181.155 - - [26/Jan/2015:23:36:34 +0300] "GET / HTTP/1.0" 200 11820 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"
93.185.181.155 - - [26/Jan/2015:23:36:34 +0300] "GET /icons/ubuntu-logo.png HTTP/1.0" 200 3688 "http://school371.ru/" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"
93.185.181.155 - - [26/Jan/2015:23:36:54 +0300] "GET /skfnsjkfbb/ HTTP/1.0" 404 502 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"
93.185.181.155 - - [26/Jan/2015:23:37:13 +0300] "GET /favicon.ico HTTP/1.0" 404 516 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"
93.185.181.155 - - [26/Jan/2015:23:37:26 +0300] "GET /favicon.ico HTTP/1.0" 404 516 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"
93.185.181.155 - - [26/Jan/2015:23:37:37 +0300] "GET /favicon.ico HTTP/1.0" 404 516 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"
93.185.181.155 - - [26/Jan/2015:23:37:39 +0300] "GET /favicon.ico HTTP/1.0" 404 515 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"

    I tried to add «LogLevel» setting to my virtual host, but this didnt helped me.

    So my question is — where is working error.log or why I doesn’t see any errors in it?

  2. Re: Apache2 empty error.log

    A 404 response code is not an «error» to Apache, so it is listed in access.log. «Errors» consist of problems loading the program, errors thrown by modules like PHP, or operating system errors like attempting to access a non-existent directory.

  3. Re: Apache2 empty error.log

    Quote Originally Posted by SeijiSensei
    View Post

    A 404 response code is not an «error» to Apache, so it is listed in access.log. «Errors» consist of problems loading the program, errors thrown by modules like PHP, or operating system errors like attempting to access a non-existent directory.

    That seems to be a difference between a 12.04 server and a 14.04 server. A 12.04 server does log such 404 errors in the error.log file, but yes (and I am surprised) the same is not true on a 14.04 server.

    Any follow-up information on your issue would be appreciated. Please have the courtesy to report back.

  4. Re: Apache2 empty error.log

    Exactly! But im affraid that this is difference not U. servers, but Apache servers.

    Apache2 v. 2.2.2

    access.log

    Code:

    95.167.186.8 - - [27/Jan/2015:10:37:08 +0300] "GET / HTTP/1.0" 200 479 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"
95.167.186.8 - - [27/Jan/2015:10:37:24 +0300] "GET /kjgndkjfgnkdjn HTTP/1.0" 404 436 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"
95.167.186.8 - - [27/Jan/2015:10:37:34 +0300] "GET /kjgndkjfgnkdjn.php HTTP/1.0" 404 440 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"

    error.log

    Code:

    [Tue Jan 27 10:37:24 2015] [error] [client 95.167.186.8] File does not exist: /var/www/cms/www/kjgndkjfgnkdjn
[Tue Jan 27 10:37:34 2015] [error] [client 95.167.186.8] script '/var/www/cms/www/kjgndkjfgnkdjn.php' not found or unable to stat

    Apache2 2.4.7

    access.log

    Code:

    95.167.186.13 - - [27/Jan/2015:10:41:56 +0300] "GET / HTTP/1.0" 200 11820 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"
95.167.186.13 - - [27/Jan/2015:10:42:01 +0300] "GET /dfgdfgdfg HTTP/1.0" 404 500 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"
95.167.186.13 - - [27/Jan/2015:10:42:06 +0300] "GET /dfgdfgdfg.php HTTP/1.0" 404 503 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0"

    error.log

    Code:

    [Mon Jan 26 23:36:25.010217 2015] [mpm_event:notice] [pid 1611:tid 139708328335232] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
[Mon Jan 26 23:36:25.010365 2015] [core:notice] [pid 1611:tid 139708328335232] AH00094: Command line: '/usr/sbin/apache2'

    In both cases there are same 3 requests: normal, request non-existing folder and non-existing file. So why 404 ERRORS aren’t errors anymore for apache?! And is there any way I can turn it back to «normal» work?

  5. Re: Apache2 empty error.log

    Quote Originally Posted by CrewDK
    View Post

    In both cases there are same 3 requests: normal, request non-existing folder and non-existing file. So why 404 ERRORS aren’t errors anymore for apache?! And is there any way I can turn it back to «normal» work?

    Well, it seems that the log level for the «File does not exist» error has moved from the «error» level to the «info» level. And so those entries can be turned on again by increasing either the overall log level or the specific log level in /etc/apache2/apcahe2.conf. The example below is specific:

    Code:

    #
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn core:info

    and gives this:

    Code:

    [Tue Jan 27 08:16:15.815255 2015] [mpm_prefork:notice] [pid 9239] AH00169: caught SIGTERM, shutting down
[Tue Jan 27 08:16:16.927209 2015] [mpm_prefork:notice] [pid 9563] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.5 OpenSSL/1.0.1f configured -- resuming normal operations
[Tue Jan 27 08:16:16.927259 2015] [core:notice] [pid 9563] AH00094: Command line: '/usr/sbin/apache2'
[Tue Jan 27 08:16:31.613340 2015] [core:info] [pid 9567] [client 192.168.111.101:53055] AH00128: File does not exist: /var/www/html/djgheht.html

    I do not know what other stuff, that perhaps I don’t want, will be spewed to the log.

    Myself, I am going back to the default settings.

    Any follow-up information on your issue would be appreciated. Please have the courtesy to report back.

Bookmarks

Bookmarks


Posting Permissions

Источник

Понравилась статья? Поделить с друзьями:
  • Error log apache2 debian
  • Error log apache где находится
  • Error log apache linux
  • Error loco translate failed to start up
  • Error locking project file