Error 503 Backend fetch failed Backend fetch failed

shaun 2018-02-15 22:32:50 UTC #1

Keywords: Magento - Amazon Web Services - Technical issue - Other
bnsupport ID: 47c05810-26c0-4e4d-2630-03c5f765720d
Description:
Hello,

I launched a new AMI with Bitnami. When I went into my admin I received this error message at the top --> One or more integrations have been reset because of a change to their xml configs.

After researching I found that it is related to this --> Since Magento 2.2 they provide a new default integration. By activating it you can link you shop to your Facebook Page and sync your Shop to the Shop on the Facebook page.

It was recommended to get rid of this error message I could just disable this social media Facebook module --> by this page https://github.com/magento/magento2/issues/12095

Someone asked -->

Hello,

I have the same issue, starting when I upgraded 2.1.9 to 2.2.0. We're not using Magento Social at the moment and would like to keep the integration off for the moment. Is there any way of removing it, or at least the error message?

And what was recommended --> switch it off you can disable the Magento Social module from your Web Setup Wizard.

I proceeded to Web Setup Wizard and disabled the Magento Social module after that my website stopped showing and I get this error message now-->

Error 503 Backend fetch failed
Backend fetch failed

Guru Meditation:
XID: 98334

Varnish cache server

I dont know what to do it fix this error and get my website back?

I saw this article --> http://devdocs.magento.com/guides/v2.0/config-guide/varnish/tshoot-varnish-503.html

But I cant find the file http_resp_hdr_len, I looked in /opt/bitnami/varnish/. by following this thread https://community.bitnami.com/t/location-of-varnish-startup-defaults-file/42052/2

I really can't find a solution to just show my website again, please can you assist?

silvio 2018-02-16 12:19:44 UTC #2

Hi @shaun,

That is a known issue and we are currently working on fixing it. We expect to release a new revision of Magento probably next week with that annoying behavior fixed. Sorry for the inconveniences.

Meanwhile you can check this thread, and try @eduard solution:

cd /opt/bitnami/apps/magento/htdocs
php bin/magento cache:enable
php bin/magento cache:clean
rm -rf var/cache/*
sudo /opt/bitnami/ctlscript.sh restart varnish

Hope it helps.

Best regards,
Silvio Fernández

shaun 2018-02-18 18:49:34 UTC #3

Hi Silvio,

Thank you for this solution it worked.

I am lucky this is a development site, today my CPU spiked for no reason. I decided I would terminate this instance and wait for the updated stack as there have been many bad reviews about this version, please see --> https://bitnami.com/stack/magento users have complained about it being unstable. I also hesitate to upgrade my existing Magento 2.18 stack.

Problem with my existing Magento stack because when I tried to update my application from Admin previously my website went down, luckily I created an image of it before. I would like to bypass this by upgrading the whole stack but only when this is confirmed stable?

Could you possibly let me know when you expect the updated stable Magento stack as I would also like to deploy a new instance and start developing a new website soon if possible?

Many thanks.

silvio 2018-02-19 14:41:55 UTC #4

Hi @shaun,

We are actively working on this issue but, unfortunately, I cannot provide you with an ETA. In order to get notified when the new Magento revision was published, you can go to https://bitnami.com/stack/magento and click on the "Follow" button just to the right of the Magento name/logo.

Best regards,
Silvio Fernández

shaun 2018-02-23 05:46:16 UTC #5

Hello,

So I went ahead and waited for the Magento Stack update.

I deployed it yesterday and just so many issues. Firstly I couldnt copy theme files to APP folder because incorrect user, I had to change permissions for Bitnami.

Then I after uploading my theme files and running this command php bin/magento setup:upgrade my site breaks and I get this error now -->

Error 503 Backend fetch failed
Backend fetch failed

Guru Meditation:
XID: 7

Varnish cache server

I honestly wish Bitnami wasn't so full of bigs and could just work, it is so frustrating, why is it that you have so many issues with your Bitnami Stack and so many bad reviews?

I really want to be positive but how do I wait for bug fixes only to find the updated stack is worse?

Please guys, can someone possibly help here?

silvio 2018-02-23 16:04:43 UTC #6

Hi @shaun,

The new changes that avoid that issues include from versions 2.2.2-4 on. Which version are you using? Please take into account that usually there are some days between the publication of the new version in bitnami.com and into the Cloud Marketplaces.

Please also take into account that you need to use the command bin/magento-cli not PHP bin/Magento. This is in order to enable you to use the Magento and composer commands. If not you can find how to recover your system and get more info here and here

Hope it helps.

Best regards,
Silvio Fernández

shaun 2018-02-24 13:52:26 UTC #7

Hi Silvio,

I deployed it from Bitnami console, I am aware that from Bitnami console it takes awhile for the application to move to Cloud MArketplaces. I used this link --> https://bitnami.com/stack/magento

Why is this Magento Stack a complete disaster?

Firstly I couldn't even copy files to my server, I had to change owners with this command --> sudo chown -R bitnami: /opt/bitnami/apps

I uploaded my theme files and run these commands -->

cd /opt/bitnami
sudo ./use_magento

cd /opt/bitnami/apps/magento/htdocs/
bin/magento-cli setup:upgrade

My site is completely broken now and I get this error:

Error 503 Backend fetch failed

Backend fetch failed
Guru Meditation:

XID: 24

Varnish cache server

This MAgento Stack is a complete headache, nobody can provide me support to get up and running. I waited week for the new release thinking it will resolve some bugs only to find it is worse and I cant even upload my theme to show.

I just wish Bitnami can get these Magento Stack working

There has been an error processing your request Exception printing is disabled by default for security reasons. Error

silvio 2018-02-26 10:34:56 UTC #8

Hi @shaun,

I am sorry to hear that. I will try to help you.

In the latest revision of Bitnami Magento Stack, we move from the two users approach, where folders and files belong to bitnami:daemon; to the one user approach, where folders and files belong to daemon:daemon. Consequently, after upload a new theme or any other file you need to change the ownership of it. You can perform it executing:

sudo chown -R daemon:daemon /opt/bitnami/apps/Magento/htdocs/

Then restart the servers using this command:

sudo /opt/bitnami/ctlscript restart

Your system must work fine now. You can find more help in this section.

Best regards,
Silvio Fernández

system 2018-03-12 10:34:56 UTC #9

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!