Sample Header Ad - 728x90

Can't enable grafana on boot in Fedora because systemd-sysv-install missing

5 votes
1 answer
9292 views
Fairly stock standard Fedora 30 install: $ uname -a Linux 5.1.16-300.fc30.x86_64 #1 SMP Wed Jul 3 15:06:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/fedora-release Fedora release 30 (Thirty) I have installed grafana using standard instructions, ie. add grafana rpm repo and then sudo dnf install grafana. I can manually start and use grafana without issue using sudo systemctl start grafana-server. I cannot, however, get it to start on boot. Here's what happens when I use the commonly recommended method: $ sudo systemctl enable grafana-server Synchronizing state of grafana-server.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable grafana-server Failed to execute /usr/lib/systemd/systemd-sysv-install: No such file or directory systemd-sysv-install is indeed missing: $ ls /usr/lib/systemd/ boot systemd-bless-boot systemd-journald systemd-rfkill systemd-user-sessions catalog systemd-bootchart systemd-localed systemd-shutdown systemd-vconsole-setup libsystemd-shared-241.so systemd-boot-check-no-failures systemd-logind systemd-sleep systemd-veritysetup network systemd-cgroups-agent systemd-makefs systemd-socket-proxyd systemd-volatile-root ntp-units.d systemd-coredump systemd-modules-load systemd-sulogin-shell system-generators portable systemd-cryptsetup systemd-networkd systemd-sysctl system-preset purge-nobody-user systemd-dissect systemd-networkd-wait-online systemd-timedated system-shutdown resolv.conf systemd-export systemd-portabled systemd-timesyncd system-sleep system systemd-fsck systemd-quotacheck systemd-time-wait-sync user systemd systemd-growfs systemd-random-seed systemd-udevd user-environment-generators systemd-ac-power systemd-hibernate-resume systemd-remount-fs systemd-update-done user-generators systemd-backlight systemd-hostnamed systemd-reply-password systemd-update-utmp user-preset systemd-binfmt systemd-initctl systemd-resolved systemd-user-runtime-dir Apparently systemd-sysv-install is supposed to be a symlink to chkconfig on Fedora. So is it Fedora, grafana or systemd's responsibility to decide which tool is responsible for installing the boot script for non-native services? And therefore who is responsible for providing the missing link? I see [anaconda](https://bugzilla.redhat.com/show_bug.cgi?id=1369794) had the same drama with the network service.
Asked by Heath Raftery (1652 rep)
Aug 8, 2019, 12:48 AM
Last activity: Aug 8, 2019, 12:51 AM