Dispatcher not caching any file | Community
Skip to main content
Riju-Mahna
Riju-Mahna
Level 2
July 24, 2017
Solved

Dispatcher not caching any file

  • July 24, 2017
  • 2 replies
  • 3079 views

My website is not caching any file in the dispatcher, even though all permissions seem to be OK.

I cleared the bare docroot folder: /opt/aem/dispatcher/docroot/ to be on the safe side, but no affect.

The dispatcher and Error logs look like below. Not sure why the 'permission denied' error is there in disp logs. The 'docroot' folder is owned by 'apache' user with 0755 access.

Dispatcher log

[Mon Jul 24 10:43:41 2017] [D] [pid 20837] cachefile does not exist: /my/file/path/file.jpg

[Mon Jul 24 10:43:41 2017] [D] [pid 20837] try to create new cachefile: /my/file/path/file.jpg

[Mon Jul 24 10:43:41 2017] [D] [pid 20837] cache-action for [/my/file/path/file.jpg]: CREATE

[Mon Jul 24 10:43:41 2017] [D] [pid 20837] Reusing socket: <Publish-IP>:4503

[Mon Jul 24 10:43:41 2017] [D] [pid 20837] Connected to backend rend01 (<Publish-IP>:4503)

[Mon Jul 24 10:43:41 2017] [E] [pid 20837] Unable to create parent directory /opt/aem/dispatcher/docroot/my/file/path: Permission denied

[Mon Jul 24 10:43:41 2017] [D] [pid 20837] response.status = 200

Error log

[Mon Jul 24 10:46:47.028012 2017] [core:info] [pid 20841] [client <dispatcher-IP>] AH00129: Attempt to serve directory: /opt/aem/dispatcher/docroot/

[Mon Jul 24 10:46:47.028027 2017] [headers:debug] [pid 20841] mod_headers.c(848): AH01503: headers: ap_headers_error_filter()

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 Diego_Fontan

Please check within httpd.conf the user which apache is running (default is 'apache').  

Then you should restart apache service to take you change.

In addition, you can run this command to ensure everything goes correctly: sudo chown -R "nameOfUser" (It's a good practices(security) CHANGE all default user/pass)

2 replies

smacdonald2008
smacdonald2008
Level 10
July 24, 2017

We have a Dispatcher session tomorrow - i recommend that you attend this session and ask this question to the presenters -- Scott's Digital Community: Ask the AEM Community Experts for July 2017

It sounds like a config mistake somewhere.

    Diego_Fontan
    Diego_FontanAccepted solution
    Level 4
    July 24, 2017

    Please check within httpd.conf the user which apache is running (default is 'apache').  

    Then you should restart apache service to take you change.

    In addition, you can run this command to ensure everything goes correctly: sudo chown -R "nameOfUser" (It's a good practices(security) CHANGE all default user/pass)

    Terms & ConditionsAccessibility statement

    Loading footer...