Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
In 3 attempts to install Commons 7.x-3.0-rc1 on a shared server host (using both PostgreSQL and MySQL bases) I've got the same error. On my test server it worked all right.
So, if you guys could help me, what the following error is about? What feature is missing?
Error 503 Service Unavailable
Service Unavailable
Guru Meditation:XID: 1521634984
Varnish cache server
Thanks in advance.
Comments
Comment #1
3magnus CreditAttribution: 3magnus commentedBy the way, the breaking point is in the end of modules installation, in this URL:
http://www.mysite.com/install.php?profile=commons&locale=en&op=start&id=1
Trying to reaload the page I get theese messages:
and I'm on the homepage, not logged in and with no user account set.
Comment #2
japerryI would not install this directly on a server that is currently running varnish, it can cause weird things to happen. Instead, I'd suggest that you start on a local or development box not behind memcache and varnish, set up the site as you see fit, and migrate the code and database over (or simply turn on varnish/memcache at that time if you have access).
Comment #3
Devin Carlson CreditAttribution: Devin Carlson commentedAs japerry mentioned, it's recommended to only enable varnish/memcache after you've already setup your site. You might also want to try the latest stable or -dev releases of Commons to see if they improve things.
Please feel free to reopen this issue if you are still having issues.
Comment #5
3magnus CreditAttribution: 3magnus commentedJust wanna say thank you for the help.
Comment #6
alberthendriks2 CreditAttribution: alberthendriks2 commentedIf you came here through google -like me-, I also had this error due to changing nginx.conf (server_names_hash_bucket_size 128; ) and then reloading nginx.
After I restarted nginx (rather than reloading), it was fixed.
Comment #7
sea7kenp CreditAttribution: sea7kenp commentedI am here, because I found these error messages on someone else's site, and wanted something intelligent to tell the Webmaster.
I'm a troubleshooter, so I may install a test version of this package (the reason I followed through to register myself).
Is there a page on your documentation I should go to, first, to understand this better? (Obviously, I could search for references to nginx, but would like to speed up my understanding).
Thank you and best regards,
Kenneth W Parker, Carrboro, NC
Comment #8
aquilessina CreditAttribution: aquilessina commentedI had "Error 503" when transferring the site to the hosting server.
It seems that the problem refers to mistakenly configure the port.
I corrected the problem changing the DB Config in settings.php to 'port' =>''; and everything worked properly.
Comment #9
Liquidwebdhultin CreditAttribution: Liquidwebdhultin as a volunteer commentedHello,
I have solved this issue. After watching the varnish log file you can see this issue when the Drupal cache is hit.
16 FetchError c Junk after gzip data
The issue was not .htaccess enabled gzip compression but he Drupal gzip compression.
To solve this issue I have done these steps.
Open settings.php and add these lines
$conf['css_gzip_compression'] = FALSE;
$conf['js_gzip_compression'] = FALSE;
$conf['page_compression'] = FALSE;
Then login to domain.com/admin and Flush all caches. After doing this and logging out the site is no longer having any issues and is working as expected.
Hopefully this works for you.
Comment #11
hairidine CreditAttribution: hairidine as a volunteer and commentedVarnish 4.1 Error 503 Backend fetch failed #15