|When you start JobServer, the Job does not inherit the environment variables of your user profile.|
|Product||Talend Data Integration|
After starting JobServer using the start_rs.sh script file, the output of the environment from a terminal matches with the output of the environment generated by the Job. This was also crosschecked with the /proc/PID/environ file used by JobServer.
|Problem root cause||Different sets of environment variables were noticed when JobServer was started using the systemd option.|
|Solution or Workaround||
For the environment variables to work correctly when JobServer is started using systemctl, you have to use either an Environment or an EnvironmentFile directive.
[Unit] Requires=coreos-metadata.service After=coreos-metadata.service [Service] EnvironmentFile=/run/metadata/coreos
[Service] # Client Env Vars Environment=ETCD_CA_FILE=/path/to/CA.pem
More information, see Using environment variables in systemd units
|JIRA ticket number|