Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Unable to setup and run Dispatcher on Linux VM based on Azure Cloud


Level 1

Hi All,


We are facing an issue while trying to setup Dispatcher on Linux VM based on Azure Cloud. Added the environment details below for reference.

Seems like its unable to recognise the environment variables in httpd file under /etc/sysconfig. Does anyone have any idea what could be wrong?



Environment Details:

AEM - 6.5.5

Standard D2 v3 (2 vcpus)
memory - 16GB
space - 512GB
Local Firewalled  , Azure NSG
Azure NIC
RedHat Ent - 8.2 x64
6 Replies


Employee Advisor

Unfortunately this question does not provide information which are necessary to better understand what is going wrong. I understand that you assume that environment variables defined in /etc/sysconfig are not reflected in the dispatcher config.


Which documentation are you following? What are the environment variables you find not getting reflected in the dispatcher?



Level 1

There are environment level variables related to author and publisher that we define in httpd file under sysconfig such as AUTHOR_IP, AUTHOR_PORT, AUTHOR_DEFAULT_HOSTNAME, AUTHOR_DOCROOT, PUBLISH_IP, PUBLISH_PORT, PUBLISH_DEFAULT_HOSTNAME and PUBLISH_DOCROOT which we use throughout in our config files such as vhost etc. 


I am following the way its been setup in AMS servers. Its just this time that its not working on the VM based Linux environment. We've tried changing permissions, stopping firewall but its unable to parse them and throw error whenever we validate the dispatcher syntax to reflect the changes.


Level 1

Would you mind rephrasing your question? Not sure if I get this right.



Employee Advisor

If these "environment level variables" are defined in a different file, they need to get added to the httpd proces. Either directly as environment variables (which is then set as part of the start scripts), or these definitions are included into the apache configuration (because they are in a classical "key=value" format, which can be parsed by a lot of systems).


That means, at some parts of the httpd, either in the start script or somewhere in the documentation there is a reference to this definition file /etc/sysconfig. 


Community Advisor

@anuraggoswami3 Please try to include the /etc/sysconfig path in your httpd configuration (httpd.conf) or Update your environment variables under /etc/httpd/conf.d/variable/ (custom or global file) and include file path in your vhost file or httpd.conf file..


Like : Include conf.d/variables/custom.vars