-
Notifications
You must be signed in to change notification settings - Fork 308
playbook fails to starts the grafana server #163
Comments
Which CentOS? |
Here is the CentOS version Operating System: CentOS Linux 7 (Core) Yes, as mentioned in my last comment if I just give homepath it works fine. |
But I want to use it as a service and not start as a command. |
This role doesn't configure systemd service for grafana as it is included in grafana rpm package. From what I see here the problem is in systemd service file. If you think that regardless fact stated above this somehow might be related to this role, please provide answers to following questions:
|
This is a fresh VM and just created from vsphere. I only think I have changed in the role "ansible-grafana" is changing the grafana password. Other than that, everthing else is the same. |
Hi Paul, |
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. |
Hi,
While I was running the playbook on my vsphere CentOS VM, I got the following error while starting the grafana server in the handler.
RUNNING HANDLER [grafana : restart grafana] *****************************************************************************************************************************************
fatal: [10.128.58.8]: FAILED! => {"changed": false, "msg": "Unable to start service grafana-server: Job for grafana-server.service failed because the control process exited with error code. See "systemctl status grafana-server.service" and "journalctl -xe" for details.\n"}
If I look into /var/log/messages then I see the following error
Aug 13 14:32:45 terraform-test systemd: Failed at step USER spawning /usr/sbin/grafana-server: No such process
Aug 13 14:32:45 terraform-test systemd: grafana-server.service: main process exited, code=exited, status=217/USER
Aug 13 14:32:45 terraform-test systemd: Failed to start Grafana instance.
Aug 13 14:32:45 terraform-test systemd: Unit grafana-server.service entered failed state.
Aug 13 14:32:45 terraform-test systemd: grafana-server.service failed.
Aug 13 14:32:45 terraform-test systemd: grafana-server.service holdoff time over, scheduling restart.
Aug 13 14:32:45 terraform-test systemd: Stopped Grafana instance.
Aug 13 14:32:45 terraform-test systemd: Starting Grafana instance...
Aug 13 14:32:45 terraform-test systemd: Failed at step USER spawning /usr/sbin/grafana-server: No such process
Aug 13 14:32:45 terraform-test systemd: grafana-server.service: main process exited, code=exited, status=217/USER
Aug 13 14:32:45 terraform-test systemd: Failed to start Grafana instance.
Aug 13 14:32:45 terraform-test systemd: Unit grafana-server.service entered failed state.
Aug 13 14:32:45 terraform-test systemd: grafana-server.service failed.
If I run "grafana-server" then I get the following error
"/usr/sbin/grafana-server
Grafana-server Init Failed: Could not find config defaults, make sure homepath command line parameter is set or working directory is homepath
If I provide a homepath then it works. So it looks like something is missing in the playbook.
Can you please help me with this ?
The text was updated successfully, but these errors were encountered: