Details
Assignee
UnassignedUnassignedReporter
Ubence QuevedoUbence QuevedoHB Grooming Date
Apr 18, 2023HB Backlog Status
Refined BacklogComponents
Fix versions
Affects versions
Priority
Low
Details
Details
Assignee
Unassigned
UnassignedReporter
Ubence Quevedo
Ubence QuevedoHB Grooming Date
Apr 18, 2023
HB Backlog Status
Refined Backlog
Components
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created April 18, 2023 at 7:57 PM
Updated June 6, 2023 at 4:10 PM
In the beginning of the initialization script for Sentinel, it still contains legacy lsb info.
This causes problems in newer versions of RHEL based OSes since the
systemd-sysv-install
script is not installed by default and is a compatibility program to be able to interact with the legacy init service system which causes the enabling of the service to fail.I propose changing the following in the
/opt/sentinel/bin/sentinel
script:#!/bin/sh - # # chkconfig: 345 99 01 # description: Starts and stops the OpenNMS Sentinel distributed client # processname: java # ### BEGIN INIT INFO # Provides: sentinel # Required-Start: $network $remote_fs # Required-Stop: $network $remote_fs # Should-Start: $local_fs # Should-Stop: $local_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: OpenNMS Sentinel # Description: OpenNMS Sentinel in a Karaf Container ### END INIT INFO NAME="sentinel" DESC="Sentinel"
to the below which is similar to what is in the
$OPENNMS_HOME/bin/opennms
script that is already systemd native:#!/usr/bin/env bash NAME="sentinel" DESC="Sentinel"
Or whatever changes need to occur to make this script systemd native.