


We're using AEM cloud and running into the following dispatcher error: Unable to create parent directory /mnt/var/www/html/content. Since its on cloud I'm not sure how to resolve since we don't have access to adjust any permissions.
Views
Replies
Sign in to like this content
Total Likes
Can you share a bit more context? Does the deployment break because of this?
The deployment doesn't break. We turned up the logging in the staging environment and saw this
Found farm ****_farm for staging.****.com
checking [/us/en/tests/****/subscribe.html]
cachefile does not exist: /mnt/var/www/html/content/****/us/en/tests/****/subscribe.html
try to create new cachefile: /mnt/var/www/html/content/****/us/en/tests/****/subscribe.html
cache-action for [/us/en/tests/****/subscribe.html]: CREATE
Connected to backend 0 (localhost:8080)
Sending request body to remote server
Request body sent to remote server
Unable to create parent directory /mnt/var/www/html/content/****/us/en/tests/****: Permission denied
response.status = 200
this means that the unix user used by the Apache httpd cannot create files/directories below there. Not really specific to AEM or the dispatcher. Adjust the permissions below /mnt/var/www/html so that the user used by httpd (in many distributions it is called "httpd") can write there.
This makes sense for an on prem dispatcher. Not sure how I can adjust permissions on cloud.
Sorry, I did not see the hint to CS 🙂 Can you create a support ticket for it and send me its ID in private here in the forums?
Thanks!
Do you have a fix for this issue.
Views
Replies
Sign in to like this content
Total Likes