*sapconf* now detects the NTP configuration properly
Previously, the *sapconf* utility did not check whether the host system was configured to use the Network Time Protocol (NTP). As a consequence, even when NTP was configured, *sapconf* displayed the following error:
3: NTP Service should be configured and started
With this update, *sapconf* properly checks for the NTP configuration, and the described problem no longer occurs.
Description of problem:
sapconf only check whether chronyd is running or not. It does not check whether the host system is configured to use ntp.
[root@test ~]# ntpstat
synchronised to NTP server (X.X.X.X) at stratum 2
time correct to within 8108 ms
polling server every 64 s
[root@test ~]# service ntpd status
Redirecting to /bin/systemctl status ntpd.service
ntpd.service - Network Time Service
Loaded: loaded (/usr/lib/systemd/system/ntpd.service; disabled)
Active: active (running) since Fri 2015-06-05 13:04:09 IST; 52s ago
Process: 20921 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS (code=exited, status=0/SUCCESS)
Main PID: 20922 (ntpd)
└─20922 /usr/sbin/ntpd -u ntp:ntp -g
Whenever I run sapconf script, sapconf throws the following message
"3: NTP Service should be configured and started"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure NTP using ntp.conf/ntp package
2. run sapconf script
Sapconf prints the message that NTP is not running
sapconf should also honor ntp configuration made via the ntp package
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.