Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Dispatcher Issue

Avatar

Level 1

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

1 Accepted Solution

Avatar

Correct answer by
Level 10

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 ?

View solution in original post

6 Replies

Avatar

Level 1

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. 

Avatar

Correct answer by
Level 10

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 ?

Avatar

Former Community Member

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

Avatar

Level 10

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

What is the URL you are trying to access

Avatar

Former Community Member

I'm trying to access an another URL like: 

/content/geometrixx-outdoors/en.html