saltstack / saltstack/salt

Env not set error while running Tomcat shutdown

Open
#56,567 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Confirmed severity-medium
Dominant language
Python
Stars
15.7k
Forks
5.6k
Avg merge
2d 44m
Merged PRs (30d)
80

Description

Description of Issue

Im getting CATALINE_HOME path not set error while executing the SLS for shutdown the tomcat server using the bat file on windows minion server.

The same is running fine while invoking the bat file manually from the server.

Setup

stop_apache_tomcat:
cmd.run:
- name: C:\apache-tomcat-8.5.47\bin\shutdown.bat

error:
ID: stop_apache_tomcat
Function: cmd.run
Name: C:\apache-tomcat-8.5.47\bin\shutdown.bat
Result: True
Comment: Command "C:\apache-tomcat-8.5.47\bin\shutdown.bat" run
Started: 14:47:56.945968
Duration: 220.023 ms
Changes:
----------
pid:
14708
retcode:
0
stderr:
stdout:
The CATALINA_HOME environment variable is not defined correctly
This environment variable is needed to run this program

Versions Report

Salt Version:
Salt: 2019.2.3

Dependency Versions:
cffi: 1.14.0
cherrypy: Not Installed
dateutil: Not Installed
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
ioflo: Not Installed
Jinja2: 2.8.1
libgit2: 0.99.0
libnacl: Not Installed
M2Crypto: 0.35.2
Mako: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.5.6
mysql-python: Not Installed
pycparser: 2.20
pycrypto: Not Installed
pycryptodome: Not Installed
pygit2: 1.1.1
Python: 3.6.8 (default, Jan 8 2020, 17:06:25)
python-gnupg: Not Installed
PyYAML: 3.12
PyZMQ: 15.3.0
RAET: Not Installed
smmap: Not Installed
timelib: Not Installed
Tornado: 4.4.2
ZMQ: 4.1.4

System Versions:
dist: redhat 7.7 Maipo
locale: UTF-8
machine: x86_64
release: 3.10.0-1062.12.1.el7.x86_64
system: Linux
version: Red Hat Enterprise Linux Server 7.7 Maipo

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named. Start by reproducing the SLS cmd.run invocation on a Windows minion and compare its environment with manually running shutdown.bat; completion would require identifying the environment discrepancy and documenting or testing the supported behavior.

Written by the indexing model from the issue text.

Assessment

Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.