404 error due to ownership changing overnight

davej 2019-01-16 07:56:34 UTC #1

IMPORTANT, please fill the questions

We assume you are using Bitnami to deploy your application.

Which version of the application are you using?:
Please choose how you got the application: Installer (Windows, Linux, macOS), cloud image (AWS, GCE, Azure, ...) or VM (VMDK, VBOX):
Have you installed any plugin or modified any configuration file?:
Describe here your question/suggestion/issue (expected and actual results):
Steps to reproduce the issue (if relevant):
Copy the apache log (if relevant):
```
PASTE HERE
```

davej 2019-01-16 08:11:09 UTC #2

I have installed Magento 2.30 on a VMware box and every thing works ok until every night at midnight the site gives a 404 error which I noticed and changed the ownership to fix and then again at 1am it gives a 404 error again.

I have established that the problem is the ownership is changing as I can fix the site by issuing the following command from the htdocs directory ;

sudo chown -R daemon:daemon

I have checked the cron job and it is eaxctly the same as a working site so can only assume it is something to do with the sticky bit on the folders.

Not sure what to do now.

This is the Apache error

[Wed Jan 16 03:44:42.337310 2019] [proxy_fcgi:error] [pid 1924:tid 139828884657920] (70008)Partial results are valid but processing is incomplete: [client 127.0.0.1:49626] AH01075: Error dispatching request to :81: (reading input brigade)

Thanks

jdrios 2019-01-16 11:10:17 UTC #3

Hi @davej

We have a Support Tool that will gather relevant information for us to debug the issue. Could you please download and execute it on the machine where the stack is running by following the steps described in the guide below?

How to Run the Bitnami Support Tool

Please note that you need to paste the code outputted by the tool in your reply.

Also, could you run the this tool again at the time that the permissions are wrong and before you execute the chown command? That way we can compare both.

Was my answer helpful? Click on

davej 2019-01-16 11:21:17 UTC #4

Hi Jdrios,
The support ticket is a5ef1f51-1bd8-6ead-f072-a39d70cd6308

I should also say though that I have followed the Magento docs and performed the following to see if it fixes the issue.

cd /opt/bitnami/apps/magento/htdocs && sudo find var generated vendor pub/static pub/media app/etc -type f -exec chmod g+w {} + && sudo find var generated vendor pub/static pub/media app/etc -type d -exec chmod g+ws {} + && sudo chown -R :bitnami . && sudo chmod u+x bin/magento-cli

If it fails again tonight I will run the tool again.

Thanks

davej 2019-01-17 07:33:55 UTC #5

Unfortunately it would seem that the problem still exists and the previous action did not work.
Here is the new support ticket.

62b802cd-d37a-b2f7-5690-1278b97e53fb

Thanks

jdrios 2019-01-17 10:29:40 UTC #6

Hi @davej

I am unable to identify the ownership changing in the second support ticket. Could you list the permissions in the htdocs folder while magento is running properly and while magento turns inoperable?

# ie, replace `status` by `running` or `inoperable` to store the permissions in different files
ls -la /opt/bitnami/apps/magento/htdocs > permissions.status

Afterward, share the content of both files here.

Was my answer helpful? Click on

davej 2019-01-17 13:05:32 UTC #7

It seems that another users of magento are having the same problem and may not be just a Bitnami problem. https://community.magento.com/t5/Magento-2-x-Technical-Issues/Whoops-our-bad-error-on-main-store-page-every-day/td-p/116724
"The Whoops our bad" is the 404 page I mentioned.

I will need to check that it is definately the ownership and not the flushing cache after that fixes the problem.

I will take a snapshot of the VMware host so that I can do more tests without haing to wait for midnight.

Thanks

davej 2019-01-18 09:37:03 UTC #8

The site as usual was down again this morning but it seems a flush of the cache was all that is needed to fix the issue.
Sorry for the red herring over ownership.

I still dont know why there would be a problem with the cache.

Thanks

jdrios 2019-01-18 10:49:18 UTC #9

Hi @davej

Actually, it is really weird. Do you need further help from Bitnami? Otherwise, I will mark your post from the Magento community as solution.

Was my answer helpful? Click on

davej 2019-01-18 11:18:03 UTC #10

Hi @jdrios
I think at this stage the Magento community post is the only answere so yes.
Thanks for your help.

system 2019-02-01 11:18:07 UTC #11

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!