• Resolved notanonymous

    (@notanonymous)


    I’m using Azure’s Linux web app hosting for a site using the latest version of the Wordfence plugin (7.1.12). I’m getting sporadic errors that php can’t read/write to some of the config files. Examples:

    [17-Sep-2018 22:34:06 UTC] Unable to open /home/site/wwwroot/wp-content/wflogs/config-transient.php for reading and writing.
    [17-Sep-2018 22:34:06 UTC] Unable to open /home/site/wwwroot/wp-content/wflogs/config-transient.php for reading and writing.
    [17-Sep-2018 22:34:21 UTC] Unable to open /home/site/wwwroot/wp-content/wflogs/config-synced.php for reading and writing.

    But its able to read/write to them some times, just inconsistently. Has anyone run into this issue running either Azure’s linux hosting or other docker container environment. I’m working with Azure support as well, but thought I’d check here too.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi @notanonymous

    On some servers, we have seen that certain scripts might delete “wflogs” directory thinking of it as a potential threat (false positive), as a result the folder will be regenerated again, it might be that when it’s regenerated it will be owned by a different user than the user your web server is running on?

    I suggest manually deleting this folder and recheck the generated copy to make sure it’s owned by the server user that has read/write permissions.

    Thanks.

    Hi @notanonymous,
    Since we haven’t heard from you for a while I’m going to go ahead and resolve this thread. You are welcome to create a new one at any time!

    Thread Starter notanonymous

    (@notanonymous)

    Thanks. To follow up in case anyone else comes across this, it seems to be an issue with our hosting environment. It’s running in a container with a virtual file system and I think it’s just not able to keep up with the read/write requests so things get locked. Engineers are investigating.

    That’s very helpful thanks for sharing @notanonymous!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Config File Locking’ is closed to new replies.