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

Prometheus autostart after installing #3463

Closed
neuroxdnb opened this Issue Nov 13, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@neuroxdnb
Copy link

neuroxdnb commented Nov 13, 2017

Usual behavior of packages containing services upon installation is to register the service being installed and start it. However this is not true for prometheus packages.
RPM POSTIN spec does not contain systemctl enable prometheus.service.

What did you do?
yum install prometheus
What did you expect to see?
systemctl enable prometheus.service
What did you see instead? Under which circumstances?
none
Environment
CentOS Linux release 7.4.1708 (Core)

  • System information:
    Linux 3.10.0-514.16.1.el7.x86_64 x86_64
  • Prometheus version:
    prometheus, version 1.8.2 (branch: HEAD, revision: 5211b96)
    build user: root@1412e937e4ad
    build date: 20171104-16:09:14
    go version: go1.9.2
  • Alertmanager version:
    alertmanager, version 0.10.0 (branch: HEAD, revision: 133c888ef3644b47a52acbaeffb09f4cc637df1b)
    build user: root@01302b7cd08a
    build date: 20171109-15:34:53
    go version: go1.9.2
  • Prometheus configuration file:
    not applicable
  • Alertmanager configuration file:
    not applicable
  • Logs:
    not applicable
@grobie

This comment has been minimized.

Copy link
Member

grobie commented Nov 13, 2017

@neuroxdnb

This comment has been minimized.

Copy link
Author

neuroxdnb commented Nov 13, 2017

Thank you!

@neuroxdnb neuroxdnb closed this Nov 13, 2017

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.