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

3magnus’s picture

3magnus commented

By 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:

  • Custom Search enabled. Don't forget to set permissions.
  • The image was resized to fit within the maximum allowed dimensions of 85x85 pixels.
  • The configuration options have been saved.
  • The configuration options have been saved.

Error message

  • No active batch.

and I'm on the homepage, not logged in and with no user account set.

japerry’s picture

japerry
Location KOMK
commented

I 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).

devin carlson’s picture

devin carlson commented
Status: Active » Fixed

As 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.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

3magnus’s picture

3magnus commented

Just wanna say thank you for the help.

alberthendriks2’s picture

alberthendriks2 commented

If 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.

sea7kenp’s picture

sea7kenp commented

I 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

aquilessina’s picture

aquilessina commented

I 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.

Liquidwebdhultin’s picture

Liquidwebdhultin commented
Issue summary: View changes

Hello,

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.

hairidine’s picture

hairidine commented

Varnish 4.1 Error 503 Backend fetch failed #15