01ba660fe7
This commit e80a5e3cb3 introduced an issue,
it wrongly passes an empty string to scylla-jmx cmdline, which causes
scylla-jmx script stuck. The cmdline real executes is:
# scylla-jmx -l /usr/lib/scylla/jmx ""
Wrapped quotation marks of env variable can't be parsed away if we use
${SCYLLA_PARAMS} in ExecStart cmdline, but $SCYLLA_PARAMS works.
Another problem is the variable can't be re-used insider env file,
reference: [1]. Let's split the parameters to multiple env variables,
and combine them in ExecStart cmdline.
[1] https://unix.stackexchange.com/questions/358998/systemd-environmentfile-re-using-variables-how
Fixes scylladb/scylla#2935
Signed-off-by: Amos Kong <amos@scylladb.com>
Message-Id: <c983103c08a3f901037fd282a14df5bb7f85dddd.1510494507.git.amos@scylladb.com>
30 lines
580 B
Plaintext
30 lines
580 B
Plaintext
# scylla home dir
|
|
SCYLLA_HOME=/var/lib/scylla
|
|
|
|
# scylla config dir
|
|
SCYLLA_CONF=/etc/scylla
|
|
|
|
# The jmx port to open
|
|
# SCYLLA_JMX_PORT="-jp 7199"
|
|
|
|
# The API port to connect to
|
|
#SCYLLA_API_PORT="-p 10000"
|
|
|
|
# API address to connect to
|
|
#SCYLLA_API_ADDR="-a localhost"
|
|
|
|
# use alternate jmx address
|
|
#SCYLLA_JMX_ADDR="-ja localhost"
|
|
|
|
# A configuration file to use
|
|
#SCYLLA_JMX_FILE="-cf /etc/scylla.d/scylla-user.cfg"
|
|
|
|
# The location of the jmx proxy jar file
|
|
SCYLLA_JMX_LOCAL="-l /usr/lib/scylla/jmx"
|
|
|
|
# allow to run remotely
|
|
#SCYLLA_JMX_REMOTE="-r"
|
|
|
|
# allow debug
|
|
#SCYLLA_JMX_DEBUG="-d"
|