Expand my Community achievements bar.

AEM dispatcher not serving page from publisher

Avatar

Level 5

Hello everyone,

 

I am facing an issue where the AEM dispatcher is not serving the page from the publisher.

 

AEM setup is on-premise and non-prod. I had AEM 6.3.3.8 running with the dispatcher(4.2.x) on the Apache server, where the publisher and dispatcher are hosted on separate servers. 

I had performed an upgrade of AEM from 6.3.3.8 to 6.5.9 (Because, the application project is built using JAVA JDK8). Now, the dispatcher is also updated to 4.3.3 as per Adobe's documentation.

The existing dispatcher configurations were not touched, I have replaced the mod_dispatcher.so file and restarted the dispatcher(httpd service restarted).

When requesting a page via the dispatcher, I always get a 502 gateway timeout. When I switched to debug mode, I found the below logs in the dispatcher.log file -

[D] [pid 3968399] Found farm website-farm for <website_name>
[D] [pid 3968399] checking [/test-page.html]
[D] [pid 3968399] cachefile does not exist: /var/www/html/website/content/test-page.html
[D] [pid 3968399] try to create new cachefile: /var/www/html/website/content/test-page.html
[D] [pid 3968399] cache-action for [/test-page.html]: CREATE
[D] [pid 3968399] Creating new connection: <publisher_IP>:4503
[D] [pid 3968399] Connected to backend 0 (<publisher_IP>:4503)
[D] [pid 3968399] Adding request header: Content-Type
[D] [pid 3968399] Adding request header: User-Agent
[D] [pid 3968399] Adding request header: Host
[D] [pid 3968399] Adding request header: Via
[D] [pid 3968399] Adding request header: X-Forwarded-For
[D] [pid 3968399] Adding request header: Server-Agent
[W] [pid 3968399] ignoring unexpected character 
[W] [pid 3968399] ignoring unexpected character 
[W] [pid 3968399] ignoring unexpected character 
[W] [pid 3968399] ignoring unexpected character [Thu Nov 14 00:08:05 2024] [W] [pid 3968399] ignoring unexpected character 
[W] [pid 3968399] ignoring unexpected character 
[W] [pid 3968399] ignoring unexpected character P
[D] [pid 3968399] Unable to parse response: no more bytes available (remote peer closed connection), state = 1
[W] [pid 3968399] Failed parsing response: no more bytes available (remote peer closed connection).
[D] [pid 3968399] initializing retry, closing connection
[W] [pid 3968399] ignoring unexpected character 
[W] [pid 3968399] ignoring unexpected character 
[W] [pid 3968399] ignoring unexpected character 
[W] [pid 3968399] ignoring unexpected character [Thu Nov 14 00:08:05 2024] [W] [pid 3968399] ignoring unexpected character 
[W] [pid 3968399] ignoring unexpected character 
[W] [pid 3968399] ignoring unexpected character P
[D] [pid 3968399] Unable to parse response: no more bytes available (remote peer closed connection) (no more bytes available (remote peer closed connection)), state = 1
[W] [pid 3968399] Failed parsing response: no more bytes available (remote peer closed connection) (no more bytes available (remote peer closed connection)).
[D] [pid 3968399] No socket reuse: response body not fully consumed
[I] [pid 3968399] "GET /test-page.html" 502 miss [website-farm/0] 9ms

 

Also, when I performed the CURL command from the dispatcher - I noticed that when the URL contains HTTP protocol, I get an output as the letter "P" and when the URL contains HTTPS protocol, I get the output with the desired HTML.

 

Any pointers, where I should check further to solve the issue?

__PRESENT

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Reply

Avatar

Community Advisor

Hi, 

It sounds like there is a typo somewhere, can you check the redirects and make sure there is nothing that could be causing the issue? 



Esteban Bustamante