grafana/packaging/rpm/systemd/grafana-server.service

[Unit]
Description=Grafana instance
Documentation=http://docs.grafana.org
Wants=network-online.target
After=network-online.target
After=postgresql.service mariadb.service mysql.service

[Service]
EnvironmentFile=/etc/sysconfig/grafana-server
User=grafana
Group=grafana
Type=notify
Restart=on-failure
WorkingDirectory=/usr/share/grafana
RuntimeDirectory=grafana
RuntimeDirectoryMode=0750
ExecStart=/usr/sbin/grafana-server                                                  \
                            --config=${CONF_FILE}                                   \
                            --pidfile=${PID_FILE_DIR}/grafana-server.pid            \
                            cfg:default.paths.logs=${LOG_DIR}                       \
                            cfg:default.paths.data=${DATA_DIR}                      \
                            cfg:default.paths.plugins=${PLUGINS_DIR}                \
                            cfg:default.paths.provisioning=${PROVISIONING_CFG_DIR}  

LimitNOFILE=10000
TimeoutStopSec=20

[Install]
WantedBy=multi-user.target
Rpm working again, systemd working on centos 7 2015-04-10 16:20:01 +02:00			`[Unit]`
Update systemd unit's description to be more understandable Signed-off-by: Christopher Meng <i@cicku.me> 2016-09-06 16:29:15 +02:00			`Description=Grafana instance`
Rpm working again, systemd working on centos 7 2015-04-10 16:20:01 +02:00			`Documentation=http://docs.grafana.org`
			`Wants=network-online.target`
			`After=network-online.target`
Add an After= DB ordering relation to systemd .service (#7903) In systemd `After=` merely codes an ordering relation and does not start other units. Grafana needs to specify that it wants to start up _after_ either of the supported DB services have started, _if they start_. Enabling the database services, however, is out of scope for Grafana. 2017-03-22 16:49:35 +01:00			`After=postgresql.service mariadb.service mysql.service`
Rpm working again, systemd working on centos 7 2015-04-10 16:20:01 +02:00
			`[Service]`
			`EnvironmentFile=/etc/sysconfig/grafana-server`
			`User=grafana`
			`Group=grafana`
Use systemd notification where applicable With this change in place, the grafana service will signal readiness to serve by writing "READY=1" to the path specified through the NOTIFY_SOCKET environment variable. If this environment variable is not present or empty, no notification will happen. This notification is the standard systemd mechanism for indicating a service is ready to serve. For Grafana this may be a couple of seconds from startup due to database migrations. This change also adjusts the Grafana systemd service definition to make use of this feature. 2017-11-28 18:16:38 +01:00			`Type=notify`
feat(packaging): added Restart=on-failure to systemd service spec file 2016-01-13 13:57:22 +01:00			`Restart=on-failure`
Rpm working again, systemd working on centos 7 2015-04-10 16:20:01 +02:00			`WorkingDirectory=/usr/share/grafana`
packaging: changed how pid directory is created for systemd systems, #9133 2017-09-04 16:40:42 +02:00			`RuntimeDirectory=grafana`
			`RuntimeDirectoryMode=0750`
dashboards as cfg: move dash/ds config files to /provisioning/* 2017-12-07 15:14:57 +01:00			`ExecStart=/usr/sbin/grafana-server \`
			`--config=${CONF_FILE} \`
			`--pidfile=${PID_FILE_DIR}/grafana-server.pid \`
			`cfg:default.paths.logs=${LOG_DIR} \`
			`cfg:default.paths.data=${DATA_DIR} \`
			`cfg:default.paths.plugins=${PLUGINS_DIR} \`
			`cfg:default.paths.provisioning=${PROVISIONING_CFG_DIR}`
dashboards as cfg: include cfg files in dist packages 2017-12-05 15:44:10 +01:00
Rpm working again, systemd working on centos 7 2015-04-10 16:20:01 +02:00			`LimitNOFILE=10000`
			`TimeoutStopSec=20`

			`[Install]`
			`WantedBy=multi-user.target`