PHP问题：error_log()无法写入日志文件

Hey there! Let's troubleshoot why your error_log() isn't writing debug info to a file for your PHP login system—this is a super common snag, so we'll work through it step by step.

1. Double-check your file path & permissions first #

This is the #1 culprit for this issue:

• Use absolute paths instead of relative ones: Relative paths (like debug.log) can be tricky because PHP uses the server's working directory, not your script's directory. Use __DIR__ to reference your script's folder, e.g.:

  error_log("Login debug: User attempted login", 3, __DIR__ . '/login_debug.log');
  

• Verify write permissions: The web server user (usually www-data on Linux, IUSR on Windows) needs write access to the file or its parent directory. You can:
  • Create the log file manually first and set permissions with chmod 664 login_debug.log (Linux)
  • Use get_current_user() in a test script to see which user PHP is running as, then adjust permissions accordingly.

2. Confirm PHP ini settings are configured correctly #

error_log() relies on a few critical ini settings—let's make sure they're enabled:

• Check these values (you can use phpinfo() or ini_get() in your script):
  • log_errors: Must be set to On (this enables logging entirely)
  • error_log: If you're not specifying a custom file, this tells PHP where to write default logs (e.g., /var/log/apache2/error.log on Linux)
  • display_errors: This controls on-page error display, but doesn't affect file logging—don't confuse it with log_errors
• You can temporarily override settings in your script if needed (though permanent changes in php.ini are better):

  ini_set('log_errors', 1);
  

3. Make sure your error_log() call uses the right parameters #

The second parameter dictates where the log goes—don't mix this up:

• Use 3 as the second argument to write to a custom file. A full example:

  $debug_msg = "Login attempt: Username = " . $_POST['username'] . " | Timestamp = " . date('Y-m-d H:i:s');
  // Write to custom log file
  error_log($debug_msg, 3, __DIR__ . '/login_debug.log');
  

• If you omit the second parameter (use 0, the default), logs will go to the system's default error log (not your custom file).

4. Test with a minimal script to rule out code conflicts #

Sometimes other parts of your login system (like output buffering, error suppression, or redirects) can interfere. Create a standalone test script:

<?php
$test_msg = "Test log entry at " . date('Y-m-d H:i:s');
$log_path = __DIR__ . '/test_log.log';

// Try writing the log
$success = error_log($test_msg, 3, $log_path);

if ($success) {
    echo "Log written! Check: " . $log_path;
} else {
    echo "Failed to write log. Check permissions and path.";
}
?>

Run this script directly—if it works, the issue is in your login system code; if not, it's a server/config problem.

5. Check for server environment restrictions #

• On shared hosting, some providers block custom log file paths. Try using the default system log instead (omit the custom path):

  error_log("Login debug: This will go to system default log");
  

  Then check your host's error log tool (e.g., cPanel's "Error Logs" section).
• For local dev environments (XAMPP/WAMP), check the default logs first—sometimes PHP falls back to these even if you specify a custom path.

内容的提问来源于stack exchange，提问作者Albert Capp