Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Systemd doesn't recognize Splunkd.service on upgrade #223

Closed
tjohnson-disney opened this issue Jan 13, 2023 · 0 comments · Fixed by #224
Closed

Systemd doesn't recognize Splunkd.service on upgrade #223

tjohnson-disney opened this issue Jan 13, 2023 · 0 comments · Fixed by #224

Comments

@tjohnson-disney
Copy link
Contributor

👻 Brief Description

We are using the cookbook to upgrade to 9.0.3. Upon trying to start Splunk after upgrade we are getting this error:

STDERR: Failed to start Splunkd.service: Unit Splunkd.service not found.
---- End output of ["/usr/bin/systemctl", "--system", "start", "Splunkd"] ----
Ran ["/usr/bin/systemctl", "--system", "start", "Splunkd"] returned 5
* Mixlib::ShellOut::ShellCommandFailed occurred in delayed notification: service[splunk] (chef-splunk::service line 103) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '5'
---- Begin output of ["/usr/bin/systemctl", "--system", "start", "Splunkd"] ----

🥞 Cookbook version

9.2.0

👩‍🍳 Chef-Infra Version

17.10.0

🎩 Platform details

RHEL8, cinc-client running on an AWS EC2

Steps To Reproduce

Steps to reproduce the behavior:

  1. Direct chef to upgrade from 8.2.4 to 9.0.3.
  2. Run cinc-client on a node
  3. cinc-client finishes in error. Error is fixed by running sudo systemctl daemon-reload and re-running cinc-client

🚓 Expected behavior

cinc-client is able to start Splunk successfully after upgrade

➕ Additional context

@ramereth ramereth linked a pull request Feb 2, 2023 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant