• I’ve read the other half dozen or so threads with this same issue and I’m still stuck. Here’s what I’ve done so far:

    • Verified that there are recent entries in /home/wp/logs/php-errors.log
    • Used copy and paste to ensure that I don’t have any typos in the filename or path.
    • Checked file permissions. Owner and group are both wp. Permissions are 660.
    • Created a php file that reads the file contents and echos them out. Ran this file from the command line and it displayed the log file contents.

    Relevant portion of wp-config.php

    ini_set('log_errors', 'On');
    ini_set('error_log', '/home/wp/logs/php-errors.log');

    The WordPress directory is /var/www/html/

    I’m not well versed in the ways of Linux. Can anyone think of what I’m missing?

    Thanks,
    Evan

    • This topic was modified 5 years, 11 months ago by EvanGoss.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter EvanGoss

    (@evangoss)

    In case it is relevant, this is a multisite setup. Everything in my original message is based upon what I see in the Network Admin Dashboard.

    When I go to the dashboard of one of the sites, I see:

    Error Log Monitor setup

    To start logging errors you’ll need to make a few changes to the WordPress configuration.

    “Use Recommended Settings” button
    “Manual Configuration” button

    This is a site that I’ve inherited and I’m pretty new to WordPress. Is there something relevant that I need to configure for each site?

    • This reply was modified 5 years, 11 months ago by EvanGoss.
    Plugin Author Janis Elsts

    (@whiteshadow)

    Sorry for the very late response! If you’re still having this problem, here are a few things to check:

    • Are there any open_basedir restrictions in effect? That could prevent the plugin from accessing the file even if the file permissions are set correctly. You can find the open_basedir setting in phpinfo() output; some hosting providers might also have a way to view or change it in the server control panel.
    • Does the file path include any symbolic links? Normally, that shouldn’t be a problem by itself, but it could obscure other configuration issues like the open_basedir restrictions mentioned above.
    • Try temporarily changing file permissions to 664. Does that help? Usually it’s not necessary to make the log file world-readable, but it can be useful as a test. If it makes the plugin work, that suggests there’s something wrong with permissions – maybe PHP is running as the wrong user/group or something like that.
    Thread Starter EvanGoss

    (@evangoss)

    Thanks for getting back to me.

    open_basedir is empty.

    664 didn’t help.

    I guess I’ll have to throw it on someone else’s lap at my org unless anyone has other suggestions.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘The log file /home/wp/logs/php-errors.log does not exist or is inaccessible.’ is closed to new replies.