Can't disable st2timersengine
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
SUMMARY
I followed the documentation(https://docs.stackstorm.com/reference/ha.html#blueprint-box) to install a highly available st2,
I can't disable st2timersengine after I add:
[timer]
enable = False
STACKSTORM VERSION
st2 3.8.0, on Python 3.6.9
OS, environment, install method
Ubuntu 18.04.6, install by apt.
Steps to reproduce the problem
add the configuration, and then restart st2:
root@prod-stackstorm-03:/etc/apt/sources.list.d# tail -n 10 /etc/st2/st2.conf
...
db_name = st2
username = stackstorm
password = XXXX
compressors = zstd
[coordination]
url = redis://:Redis_XXXXX@10.XX.XX.XXX:6379
[timer]
enable = False
root@prod-stackstorm-03:/etc/st2# st2ctl restart
Failed to stop st2chatops.service: Unit st2chatops.service not loaded.
Failed to start st2chatops.service: Unit st2chatops.service not found.
##### st2 components status #####
st2actionrunner PID: 102513
st2actionrunner PID: 102515
st2actionrunner PID: 102517
st2actionrunner PID: 102519
st2actionrunner PID: 102521
st2actionrunner PID: 102523
st2actionrunner PID: 102525
st2actionrunner PID: 102527
st2actionrunner PID: 102529
st2actionrunner PID: 102531
st2api PID: 102539
st2stream PID: 102549
st2auth PID: 102559
st2garbagecollector PID: 102562
st2notifier PID: 102565
st2rulesengine PID: 102569
st2sensorcontainer PID: 102572
st2chatops is not running.
st2timersengine PID: 102577
st2workflowengine PID: 102580
st2scheduler PID: 102583
Expected Results
I expect st2timersengine is not running.
Actual Results
Now I have duplicate rule evaluations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the HA blueprint documentation and the [timer] section in /etc/st2/st2.conf, then trace how st2ctl restart starts st2timersengine. Verify whether the enable setting is read by the service and check the reported component status. Done means st2timersengine is not running after restart and duplicate rule evaluations no longer occur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100