DocumentationExperience Cloud KCS

Unable to edit dispatcher configuration files in Adobe Experience Manager

Last update: August 18, 2026

In Adobe Experience Manager (AEM), users with SSH access to a stage dispatcher server might be unable to modify dispatcher and server configuration files because they do not have sufficient permissions. Administrative tasks that require sudo or root access fail even though SSH authentication succeeds. To fix this issue, verify the current permissions, check for file locks, and obtain the required access through the approved process.

Description description

Environment

Adobe Experience Manager (AEM) (all versions)

Issue/Symptoms

A user with SSH access to the stage dispatcher server is unable to perform administrative tasks such as editing dispatcher configuration files due to lack of sudo/root permissions. Attempts to use sudo prompt for a password that is not available to the user, who authenticates via SSH public key.

Symptoms include:

  • Read-only access to configuration files in directories such as /etc/httpd/conf.d/available_vhosts/, /etc/httpd/conf.d/rewrites/, /etc/httpd/conf.dispatcher.d/filters/, and /mnt/var/www/html/

  • Inability to modify or save changes to these files

  • When attempting to edit a file with sudo vim, the following prompt appears: [ sudo] password for <user>:

  • When opening a file with vi, the following message may appear if the file is already open by another user:

    code language-none 
    E325: ATTENTION
Found a swap file by the name ".<filename>.swp"
owned by: <another user>
file name: /etc/httpd/conf.d/rewrites/<filename>
process ID: <pid>
Swap file ".<filename>.swp" already exists!
[ O] pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:

Resolution resolution

  1. Verify Current Permissions

    • Run sudo -l to check whether the user has any sudo privileges.
    • Attempt to edit the required file without sudo using vi <filename>.

  2. If you see an E325 warning about a swap file, confirm whether another user has the file open. If so, coordinate to close the file or choose an appropriate recovery option.

  3. Request Elevated Access via Approved Process

    • If direct sudo/root access is not available, contact the system administrator or follow the organization’s standard change management process to request temporary or permanent write access to the required directories.
    • Provide justification for the access, including the specific directories and activities needed (e.g., dispatcher configuration updates, log analysis).

  4. If elevated access cannot be granted, submit a request to the appropriate operations or support team to perform the required configuration changes on your behalf.

recommendation-more-help
experience-cloud-kcs-help-kbarticles