Dispatcher Issue | Community
Skip to main content
October 16, 2015
Solved

Dispatcher Issue

  • October 16, 2015
  • 6 replies
  • 1406 views

Hi,

We are facing a weird issue with the HTTPD server having dispatcher in it.

The publisher works fine with the default content through the domain configured in HTTPD/dispatcher, but when we activate some content from author or just simply install any package on publisher we start getting the following issue:

"Service Unavailable: Back-end server is at capacity"

The bundle/app are working fine, the issue comes when we add content to publisher either by activation or packages.

Please advise.

Regards,

Shishir

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Lokesh_Shivalingaiah

Hi Shishir,

What is your deployment arch ?? Usually we see this error when there is a load balancer and when its health checker receives 'Page Not found' or if there are any configuration issue with the virtual host

can you check your dispatcher logs for any error stack ?

6 replies

October 16, 2015

For all those who will be visiting this forum for similar issue. 

The culprit was the health checker (/opt/eagle/eagle/chech.sh) which is expecting the 404 pages to have string “ApacheSling” in the response body. As in our case this was not present and ELB is throwing the dispatcher out from the load balancer nodes list. Just to inform that we are using Adobe Manage Server where this script was available. 

Lokesh_Shivalingaiah
Lokesh_ShivalingaiahAccepted solution
Level 10
October 16, 2015

Hi Shishir,

What is your deployment arch ?? Usually we see this error when there is a load balancer and when its health checker receives 'Page Not found' or if there are any configuration issue with the virtual host

can you check your dispatcher logs for any error stack ?

October 16, 2015

Hi bsloki,

Thanks for your quick response, here is the app stack that we are using:

1. AEM 6.0 SP2

2. Dispatcher:dispatcher-apache2.2-4.1.9.so

3. OS - Red Hat Enterprise Linux Server release 6.5

In dispatcher log we see the following lines:

--------

Found farm publishfarm for localhost
checking [/content/cqms_nonexistent_page.html]
cachefile does not exist: /mnt/var/www/html/content/cqms_nonexistent_page.html
try to create new cachefile: /mnt/var/www/html/content/cqms_nonexistent_page.html
cache-action for [/content/cqms_nonexistent_page.html]: CREATE
Creating new socket: x.x.x.x:4503
Connected to backend 0 (x.x.x.x:4503)
Adding request header: user-agent
Adding request header: accept
Adding request header: host
Adding request header: Via
Adding request header: X-Forwarded-For
Adding request header: Server-Agent
response.status = 404
response.headers[Date] = "Tue, 26 May 2015 11:58:39 GMT"
response.headers[Set-Cookie] = "JSESSIONID=k0p08rzmv18m7c3xgoggnz31;Path=/"
response.headers[Expires] = "Thu, 01 Jan 1970 00:00:00 GMT"
response.headers[Content-Type] = "text/html;charset=UTF-8"
"GET /content/cqms_nonexistent_page.html" 404 17399 43ms

 

---------

Please advise

October 16, 2015

While browsing through web I got this link on NPE.

https://github.com/Adobe-Consulting-Services/acs-aem-commons/commit/b7de92afd4b2bd12ffc69c644d6c8e99c82be03d 

Please suggest if this is related to this.

Lokesh_Shivalingaiah
Level 10
October 16, 2015

Its showing that 'cqms_nonexistent_page.html' page is not available !

What is the URL you are trying to access

October 16, 2015

I'm trying to access an another URL like: 

/content/geometrixx-outdoors/en.html