Hello!

So I just had a pretty crazy problem overnight that I want to find a way to mitigate. Hopefully someone can lead me into a good direction.

I received this error:
[pid 22257] (13)Permission denied: [client 127.0.0.1:51345] AH00529: /var/www/html/mysite.com/sites/default/files/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable and that '/var/www/html/mysite.com/sites/default/files/' is executable

Which renders Drupal useless after received. The only way to fix was to disable, then re-enable s3fs module and it fixed the page loading issue (not something I want to repeat).

So what I am wondering, should this module have any way of say after failure resort to using the local file system. Then possibly setting up a cron run to update the local file system with S3's data.

Basically the .htaccess file was on the local server as well. But this issue still came up.

Thank you,
-Jesse

Comments

dobe created an issue. See original summary.

coredumperror’s picture

coredumperror CreditAttribution: coredumperror commented

So wait, what actually happened here? Under what situation did you experience this error? Do you know what code was trying to inspect the .htaccess file?

The only reason I can imagine that s3fs could be involved in this at all would be if you have public:// takeover enabled. But I've used that for ages on my own machine, as have many others, and I've never seen this error nor had it reported before. So my best guess is that there's a poorly-behaved third party module on your site that's triggering this, possibly by hooking into a low-level Drupal process, expecting public://.htaccess to exist, and when it doesn't (because you have public:// slaved to your S3 bucket), it freaks out.

Other than that, I don't have a clue what could have gone wrong, or how s3fs could have been involved.

dobe’s picture

dobe CreditAttribution: dobe as a volunteer commented

I have no idea what was trying to call the .htaccess file. I am using public:// and private:// on s3.

So my best guess is that there's a poorly-behaved third party module on your site that's triggering this

Very possible.

dobe’s picture

dobe CreditAttribution: dobe as a volunteer commented
Status: Active » Closed (works as designed)

So it seems that this likely doesn't cause the site to do down. It happens because the file drupal is looking for doesn't exist in S3.