Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Issue 1: When restoring an HP-UX 11i v3 system where the line 'export NTPDATE_SERVER=' in /etc/rc.config.d/netdaemons has more than 128 characters (such as when multiple ntpdate servers are specified) the restored system fails to start, showing a syntax error similar to the following: /sbin/rc[102]: syntax error at line 88 : '"' unmatched errors. The following example shows the relevant line in /sbin/rc: 101 if [ -f /etc/rc.config ]; then 102 . /etc/rc.config 103 Subsequent start-up scripts may display errors similar to the following: /sbin/rc1.d/S090hpvmguest[286]: /usr/bin/getconf: not found /sbin/rc1.d/S090hpvmguest[286]: /usr/bin/grep: not found ... The errors are due to a corrupted 'NTPDATE_SERVER=' entry restored in /etc/rc.config.d/netdaemons that split into two lines, causing the '"' unmatched errors. First-line >export NTPDATE_SERVER="wwww-wwww-wwww-www1.xxxxxxx.yyyyy wwww-wwww -wwww-www2.xxxxxxx.yyyyy wwww-wwww-wwww-www3.xxxxxxx.yyyyy wwww- Second-line>wwww-wwww-www4.xxxxxxx.yyyyy wwww-wwww-wwww-www5.xxxxxxx.yyyyy" Issue 2: When restoring an HP-UX 11i v3 system where the line 'export NTPDATE_SERVER=' in /etc/rc.config.d/netdaemons has multiple ntpdate servers configured, the restored systems /etc/ntp.conf effectively retains only one single 'server' entry (corresponding to the last ntpdate server listed under 'NTPDATE_SERVER'). Other 'server' entries in the original /etc/ntp.conf are silently lost therefore, the restored system will effectively have one (not multiple) ntp server configured.
Any HPE Integrity system running HP-UX 11i v3 and any version of Ignite/UX.
To resolve this issue, update to Ignite-UX version C.7.28.2, bundled in HP-UX 11i v3 May 2024 OEUR and downloadable from HPE Software Center. With Ignite-UX C.7.28.2, in determining the ntpdate server for the restored system, it detects whether the line ‘export NTPDATE_SERVER=' in /etc/rc.config.d/netdaemons has exceeded the 128-character limit and ignores the rest after the limit, thus addressing Issue #1. In restoring /etc/ntp.conf, all existing ‘server’ entries will be retained, addressing Issue #2. If the ntpdate server determined does not already have a corresponding ‘server’ entry in /etc/ntp.conf, such entry will be added by Ignite/UX during restore. With Ignite-UX C.7.28.2: • When the line ‘export NTPDATE_SERVER=' in /etc/rc.config.d/netdaemons exceeds 128 characters, the entire export statement, up to the end quote (“), will be retained in the restored system. This addresses Issue 1. • In restoring /etc/ntp.conf, all existing ‘server’ entries will be retained, addressing Issue 2. In addition, if there is no ‘server’ entry in /etc/ntp.conf corresponding to the ntpdate server configured for the restored system, such entry will be added by Ignite/UX. The workarounds below still serve to mitigate the impact of the two issues before upgrading Ignite-UX to C.7.28.2 (or later). Workaround for Issue 1 and Issue 2: As a workaround, follow the following procedure to avoid the above two issues in future Ignite-UX archives: Before taking archive via make_tape_recovery or make_net_recovery, save a copy of /etc/rc.config.d/netdaemons and /etc/ntp.conf by typing the following commands: # cp /etc/rc.config.d/netdaemons /tmp/netdaemons.save # cp /etc/ntp.conf /tmp/ntp.conf.save Stop the NTP service by typing the following command: # /sbin/init.d/xntpd stop Edit /etc/rc.config.d/netdaemons and locate the line containing "export NTPDATE_SERVER=". Either remove this line entirely or retain only one name server in its definition and save the file. Create the Ignite recovery archive with the updated /etc/rc.config.d/netdaemons. If the system needs to be recovered using the archive created above, re-instate the configuration and/or customization by restoring the saved copy of /etc/rc.config.d/netdaemons and /etc/ntp.conf. In cases where a system needs to be restored using impacted Ignite-UX archives, use the following workaround to mitigate the impact of the issue. Workaround for Issue 1: To work around the start-up failure, perform the following: Reboot the restored system to single-user mode, edit /etc/rc.config.d/netdaemons after saving a copy by typing the following commands: HPUX> hpux -is # mount /usr # mount /var # export TERM=xterm # cp /etc/rc.config.d/netdaemons /var/tmp/netdaemons.save # vi /etc/rc.config.d/netdaemons In 'vi', locate the line 'export NTPDATE_SERVER='. Either remove this line entirely, or retain only one NTP server in its definition and save the file. After saving the above changes to /etc/rc.config.d/netdaemons, the restored system should boot to init level 3. Reinstate the "export NTPDATE_SERVER=" line using the saved copy if needed. Reboot the system to ensure the system boots as expected and NTPDATE_SERVER is properly configured. In cases where the restored system has one (not multiple) ntp server configured, use the following workaround to mitigate the impact of the issue. Workaround for Issue 2: To mitigate the impact of the lost ntp server entries in /etc/ntp.conf and any customizations associated with the server entries, manually review /etc/ntp.conf and add back the lost entries. Note that some applications highly depend on server and client having synchronized system time using common NTP server(s) in the site. As such, it is very important to add back any lost ntp server entries to restore the NTP redundancy originally configured. Document Version Release Date Details 2 07/09/2024 Updated the Resolution with the permanent fix, Ignite-UX version C.7.28.2 1 07/20/2020 Original document release