Skip to main content
Announcements
Qlik Connect 2025: 3 days of full immersion in data, analytics, and AI. May 13-15 | Orlando, FL: Learn More

Jobs do not inherit the environment variables of the user profile starting JobServer

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
TalendSolutionExpert
Contributor II
Contributor II

Jobs do not inherit the environment variables of the user profile starting JobServer

Last Update:

Feb 9, 2024 1:22:49 PM

Updated By:

Jamie_Gregory

Created date:

Apr 1, 2021 6:13:25 AM

Talend Version 6.4.1

Summary

When you start JobServer, the Job does not inherit the environment variables of your user profile.
Additional Versions 
ProductTalend Data Integration
ComponentJobServer
Problem Description

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 causeDifferent 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.

 

Solution 1

[Unit]
Requires=coreos-metadata.service
After=coreos-metadata.service

[Service]
EnvironmentFile=/run/metadata/coreos

Solution 2

[Service]
# Client Env Vars
Environment=ETCD_CA_FILE=/path/to/CA.pem

 

More information, see Using environment variables in systemd units

 

JIRA ticket number 
Version history
Last update:
‎2024-02-09 01:22 PM
Updated by: