HP NonStop Time Synchronization User’s Guide Abstract HP NonStop™ Time Synchronization (TimeSync) synchronizes time between HP NonStop servers, Microsoft Windows™ systems, and Linux systems. It can act as both an NTP/SNTP client and server to receive time from external NTP time sources and to provide time to NTP clients. This document describes how to install, configure, and use NonStop Time Synchronization. Product Version V01 Supported Release Version Updates (RVUs) This manual supports G06.
Document History Part Number Product Version Published 544583-001 V01 – 1.0 July 2007 544583-002 V01 – 1.1 June 2009 544583-003 V01 – 1.
Table of Contents HP NonStop Time Synchronization User’s Guide ....................................................................... 1 Abstract ................................................................................................................................................................... 1 Product Version ....................................................................................................................................................
.3.1 Process Options ................................................................................................................................... 29 4.3.2 Server Options ...................................................................................................................................... 32 4.3.3 Client Options ....................................................................................................................................... 34 4.3.4 Logging Options...............
What’s New in This Manual New and Changed Information TimeSync 1.3 Added the LocalAddress option on page 30. Added the AlwaysSendRefTS option on page 32. Added the RetryInterval option on page 36. Added the RetryLimit option on page 37. Updated the SET command options on page 57.
About This Manual Audience The intended audience for this document is system managers or administrators responsible for maintaining HP NonStop Servers, Windows workstations and/or Linux systems. Related Documents None Manual Organization Section Description Overview Overview and architecture of the HP NonStop TimeSync product. TimeSync Quick Start Outline of key TimeSync installation and configuration steps.
This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 25. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters Lowercase italic letters indicate variable items that you supply.
A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address { } Braces A group of items enclosed in braces is a list from which you are required to choose one item.
Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "[" repetition-constant-list "]" Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma.
!i,o In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i,o !i:i In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
Backup Up. lowercase italic letters Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
% Percent Sign A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: %005400 %B101111 %H2F P=%p-register E=%e-register Notation for Management Programming Interfaces This list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual.
1. Overview 1.1. Introduction to NonStop TimeSync NonStop TimeSync synchronizes time across multiple NonStop, Linux, and Windows systems. It has the ability to act as a synchronization client, a synchronization server, or both simultaneously. In client mode, TimeSync obtains reference times from one or more configured time sources, and adjusts the local system time accordingly. Supported time sources include any system running TimeSync in server mode anywhere in your network, or any NTP/SNTP server.
General Features Allows any supported system to act as a Time Synchronization Server. Allows any supported system to operate as a Time Synchronization Client. Supports both Guardian and OSS environments on NonStop servers. Runs as a service on Microsoft Windows and as a daemon on Linux. Integrates with native event management services on each platform to enable logging of critical events (EMS on NonStop, syslog on Linux, and the Windows event log on Windows).
TimeSync and Daylight Savings Time (DST) Transitions TimeSync tracks all system times and calculates all time differences using Coordinated Universal Time (UTC)/Greenwich Mean Time (GMT). UTC/GMT time is the “base time” off of which all other times are calculated. In addition, UTC/GMT time is not affected by Daylight Savings Time transitions. When a DST transition occurs, UTC/GMT time does not change; instead everyone’s “difference” from UTC/GMT times changes.
Thu Jul 12 18:06:52 UTC 2007 On Linux, you can also use the date and date –u commands as described above: /tmp > date Thu Jul 12 12:08:48 CDT 2007 /tmp > date -u Thu Jul 12 17:08:50 UTC 2007 On Windows, double-click the clock in the system tray to check time settings. Once you have determined how your local clock is set up, you can configure TimeSync accordingly. Again, see Process Options for more information on setting up the GMTOffset value for your system if necessary.
To eliminate potential issues with the system clock being set backward, TimeSync can instead be configured to “drift” backward changes in slowly as well. In this case, TimeSync never alters the system clock to an earlier time. Instead, it works by slowing down how quickly time moves forward on the system, essentially waiting for the reference source to “catch up” before resuming normal timekeeping. This does not, however, mean that time stops on the local system.
Because all TimeSync features are available on all supported platforms, you have a great deal of flexibility in how you choose to configure TimeSync within your network. Any platform/system can act as a server, and any platform/system can act as a client. Thus it’s really up to you to decide which configuration makes the most sense for your particular environment. For example, Figure 1-1 shows one way that TimeSync can be configured to manage time across systems: Figure 1-1.
2. TimeSync Quick Start This section is intended to provide a brief overview of the steps required to install and run TimeSync on your system(s). It does not replace the other material contained in this manual. Please read the other sections thoroughly before deploying TimeSync in your environment. In general, you will need to follow the steps below in order to get TimeSync up and running: 1. Install TimeSync on your system(s).
9. Save all configuration changes and exit the text editor. 10. If you will be running TimeSync with client mode enabled, disable the time synchronization capabilities of any other software running on the system (e.g. ASAP or NSX on NonStop, NTP client on Linux, NTP client on Windows). 11. Start TimeSync as described in Running TimeSync. 12. Monitor TimeSync activity using a system log viewer (e.g. EMSA or WebViewpoint on NonStop, Windows Event Viewer on Windows, or Syslog Viewer on Linux). 13.
3. Installing NonStop TimeSync This section covers the procedures for installing TimeSync on NonStop, Linux and Windows systems. 3.1 Installing TimeSync on a NonStop Server TimeSync is packaged on a CD as an independent product. To install TimeSync on a NonStop server, proceed as follows using the product CD: 1. Run the IPSetup program to begin installation, and follow the on-screen prompts to copy the TimeSync files to the NonStop system. 2.
-> add process $ZZKRN.#TimeSync, cpu 1, name $TIME, program $SYSTEM.SYSTEM.TIMESYNC, hometerm $ZHOME, autorestart 5, startmode APPLICATION & & & & & & 4. If you plan to run the OSS version of TimeSync, copy the OSSPAX file from the product subvolume to an OSS directory, adding a .pax extension, and use the pax utility to extract the file contents. For example, from an OSS shell prompt, do the following (assuming you used IPSetup to place the TimeSync files in $DSMSCM.
flexibility in terms of how the product is installed. For customers who prefer to more closely control the installation process, the TimeSync for Linux CD also contains a tar archive of the product files. You can extract the contents of this and then install the product as you wish. To install TimeSync using the RPM-based installer, proceed as follows: 1. Place the CD into the CD drive on the Linux system. 2.
8. In order for the TimeCom CI to communicate with TimeSync, loop-back support (address 127.0.0.1) must be enabled on the system. To install TimeSync using the tar archive file, proceed as follows: 1. Place the CD into the CD drive on the Linux system. 2. Mount the CD if your system is not configured to do so automatically, for example: [root tmp]# mount /mnt/cdrom 3.
Note that in the above, the name of the file in the /etc/init.d folder must match the name supplied following the /sbin/chkconfig –-add command (in this case, both are “timesync”). In addition, if you choose to start TimeSync at system boot time, be sure that the RunAsService flag in the timesync.conf file is set to True. See Process Options below for more information. 8.
TimeSync.exe TimeSync process object file TimeSync User’s Guide.pdf TimeSync manual (this document) in PDF format 3. Edit the TimeSync configuration file, TimeSync.conf, and create a custom configuration for the system as described in Configuring TimeSync. 4. If you will be running TimeSync with client mode enabled (i.e. TimeSync will be updating the local system time), you should disable the built-in Windows NTP client to avoid potential erratic changes to system time. 5.
4. Configuring TimeSync TimeSync configuration settings are stored by default in the timesync.conf file (Windows, Linux, and OSS) or the TSCONF file (Guardian) located in the TimeSync program directory. TimeSync loads this configuration information immediately at startup. To control TimeSync behavior, you can either alter the settings in this file before starting the process, or else change settings dynamically using the TimeCom CI. 4.
a particular functional area. Sections are denoted by a section name contained in square brackets: for example, [Process]. The configuration file can contain any or all of these sections: [Process] The [Process] section contains settings related to general TimeSync process attributes. [Server] The [Server] section contains settings related to TimeSync running as a time source server (i.e. supplying time to remote systems).
4.3 Configuration Options The timesync.conf/TSCONF file can contain any or all of the options described below. If the configuration file does not specify a given option, TimeSync uses the default value defined for that option. Descriptions for each option follow. 4.3.1 Process Options Process configuration options are contained in the Process section of the configuration file. These options specify general run-time parameters for TimeSync.
because TimeSync performs all clock operations using GMT/UTC time. Instead, the GMTOffset value should only be used if you have explicitly set your system clock to something other than true GMT/UTC time. Value Range: -2147483648 to 2147483647 Default Value: 0 Example: GMTOffset = -3600 LocalAddress The IP address/interface on the local system which the TimeSync process will use to communicate with remote systems. If this value is not set, TimeSync will use any local address.
TimeSync uses to communicate with other systems. TimeSync must use a port on the local system at all times in order to be able to send requests to time sources (if client mode is enabled), receive requests from clients (if server mode is enabled), and receive commands from the TimeCom CI. However, when TimeSync is running with client mode enabled, it also must know the IP address/host name and port number of each defined time source.
the RunAsService value will be set to True in the default configuration file). If the TimeSync process will be started manually from a command prompt, then this value can be set to either True or False. If set to True, TimeSync will close the terminal when it starts up, change its default directory, and take other actions to try to ensure that it keeps running even in if there are system problems. If this value is set to False, TimeSync will run as a standard user process.
both as a client and server simultaneously), reference timestamps are always included in responses to NTP clients, and the AlwaysSendRefTS flag has no effect. In this case, the reference timestamp will be the time at which the TimeSync system last synced its clock to an external source. If no sync has been performed yet, then the reference timestamp value will be 0.
4.3.3 Client Options Client configuration options are contained in the Client section of the configuration file. These options control how TimeSync behaves when running as a time source client. ClientMode True | False Flag controlling whether the TimeSync process should behave as a time source client and obtain time information from remote systems. If True, the TimeSync process will run as a time source client, obtain time information from the defined time source, and set the local system time accordingly.
Value Range: -1 through 2147483647 Default Value: -1 (all backward changes should be drifted in) Example: DriftBackwardThreshold = 1000 DriftForward True | False Flag controlling whether operations involved in setting the system time “forward” (i.e. to a later time) take place immediately or are done incrementally in a fashion that prevents abrupt time change on the system. If True, TimeSync drifts forward time changes in slowly. If False, TimeSync simply sets the system time to the new time value.
Default Value: 300000 (5 minutes) Example: MaxReplyDeviation = 250000 MaxReplyWindow The amount of time, in milliseconds, for which the TimeSync process will wait for a response from a time source. If a response is received outside of this window, it will be discarded by the TimeSync process.
requests in cases where an error occurs. Note that the RetryInterval value takes precedence over the UpdateInterval or SyncAt list in situations where TimeSync encountered an error when attempting to send a sync request. Thus if the configured UpdateInterval value or next sync time in the SyncAt list would call for a sync request to be sent sooner than the configured RetryInterval, TimeSync will still use the RetryInterval value if it is retrying a previous sync attempt.
amount of potential disruption to the system. Value Range: True or False Default Value: False Example: ReportOnly = True SyncAt [, , …] Specifies the list of times each day at which TimeSync sends synchronization requests to the defined time source(s) in order to update the local system time. The list of SyncAt times is only utilized if client mode is enabled; if client mode is disabled, the SyncAt list is ignored.
the configuration file, otherwise TimeSync will not be able to synchronize the local system time. Value Range: { | }[:], where is a legal dotted-decimal IP address, is a legal TCP/IP host name, and is a valid TCP/IP port number. If is not given, the default NTP/SNTP port number of 123 is used.
file. These options control TimeSync’s built-in logging mechanism. Note that these options affect TimeSync’s logging facility only, and do not in any way relate to messages logged to the system log. The TimeSync log file itself can be either a basic text file or an HTML text file, depending upon the HTMLFormat option described below. You can use any text or HTML file viewer to examine the log.
If True, logging is enabled for the TimeSync process. If False, logging is disabled, and no messages are generated. Note, however, that messages are still written to the system’s event logging subsystem. Value Range: True or False Default Value: False Example: Enabled = True FileName The name of the TimeSync log file. If logging is enabled, log records are written to this file, in either HTML or text format.
messages to be logged. The default value of 3 should be used under normal circumstances. Value Range: 1 through 4 Default Value: 3 (All error and warning messages are logged.) Example: Level = 4 Suppress True | False If True, duplicate messages logged in succession are suppressed and counted, and a summary message is written to the log file indicating how many times the message occurred. If False, no suppression is performed and all log messages are written directly to the log file.
The name of the TimeSync trace output file. If tracing is enabled, trace data is written to this file in either HTML or text format. All trace data is captured in memory in order to reduce the impact of tracing on the TimeSync process. Trace data is written to the trace output file only when tracing is stopped or when the TimeSync process shuts down. If you change this value, be sure to fully qualify the file name if RunAsService is set to True.
0x00000004 Warnings 0x00000008 Informational messages 0x00000010 Data received via interprocess communication 0x00000020 Data sent via interprocess communication 0x00000040 Insertion of queue items 0x00000080 Removal of queue items 0x00000100 Creation of objects (Do not enable unless instructed to do so by HP support. It could significantly affect the performance of the TimeSync process.) 0x00000200 Destruction of objects (Do not enable unless instructed to do so by HP support.
0x02000000 Data sent via UDP 0x04000000 Data received via TCP 0x08000000 Data sent via TCP 0x10000000 Data received via NTP 0x20000000 Data sent via NTP Value Range: 0x00000000 – 0x0FFFFFFF Default Value: 0x00000003 (critical and noncritical errors) Example: Mask = 0x0F80003F RecordLimit Defines the maximum number of trace records to capture, where 0 = no limit. Once this limit is reached, no further trace records are captured unless Wrap is True.
5. Running TimeSync This section describes how to run TimeSync on all supported platforms – Guardian, OSS, Linux, and Windows. Because there are generally multiple mechanisms for starting TimeSync on any given system, it is important to understand how each mechanism works - and how it impacts the TimeSync configuration - before you run TimeSync the first time. 5.
5.2 Starting TimeSync on OSS You can start TimeSync on OSS simply by executing timesync from a shell prompt, or by using the run command. In neither case are changes or specific settings required in the configuration file. If you want to start TimeSync directly from a shell prompt, HP recommends you launch it as a background process. If TimeSync will run with client mode enabled, it must be started with SUPER group authority in order to update the local system time.
order to update the local system time. For example, to start the TimeSync service manually, the commands would be: [root tmp]# cd /etc/init.d [root tmp]# ./timesync start If TimeSync will be run as a Linux service/daemon, you must set the RunAsService value in the TimeSync configuration file (timesync.conf) to True.
1. Click on the Start button 2. Choose Administrative Tools 3. Choose Services 4. In the Services browser window that opens, right click on “TimeSync for Windows” and choose “Start” If TimeSync will be run as a Windows service, you must set the RunAsService value in the TimeSync configuration file (timesync.conf) to True. If you did not install TimeSync as a Windows service, then you can run it as you would any other Windows application.
6. The TimeSync Command Interface The TimeSync product provides a command interpreter (CI) that can communicate with the local version of TimeSync as well as remote versions of TimeSync. The TimeSync CI (TimeCom) provides both command-line and interactive interfaces to execute commands against the TimeSync server process.
- the DNS host name of the new time source. - the port number of the new time source. Examples timecom > add TimeSources 16.32.101.10:123 timecom –add TimeSources 17.34.45.56:19095 6.2 CONF Command The CONF command instructs the TimeSync server to load the specified configuration file. The CONF command can only be issued against the local TimeSync server. The command can be issued as a command-line parameter or can be entered interactively at a TimeCom prompt.
the prior command using subcommands, as described below. After you enter the subcommands you want, press the RETURN key. Your edited command and a new editing template then appear. If you want to make more corrections to the edited command, you can enter more subcommands in the editing template and then press RETURN. If the edited command is correct, you can re-execute it by pressing RETURN without entering any subcommands.
is any text that does not begin with R, I, or D (or r, i, or d). Characters in replace characters immediately above them on a one-for-one basis. For example, a D in replaces the character displayed above it instead of deleting it. is any text that does not begin with R, I, or D (or r, i, or d). Characters in are inserted into the prior command immediately in front of the character displayed by the I or i.
Examples timecom >info System Local system:123 (127.0.0.1) -- TimeSync Settings -- Version : 1.3.203, 03 March 2010, 18:00 Program File Name : C:\Program Files\HP\TimeSync\TimeSync.exe Process ID : 1948 Configuration File : C:\Program Files\HP\TimeSync\timesync.
RunAsService : True LogEnabled : False LogFileName : C:\Program Files\HP\TimeSync\timesynclog.txt LogLevel : 3 LogClearOnOpen : False LogDeleteOnClose : False LogHTMLFormat : False LogSuppress : True TraceEnabled : False TraceFileName : C:\Program Files\HP\TimeSync\timesynctrace.txt TraceHTMLFormat : False TraceMask : 0x00000003 TraceRecordLimit : 1000 TraceWrap : False 6.5 REMOVE Command The REMOVE command removes one or more TimeSources from the TimeSync configuration.
timecom > remove TimeSources 16.32.101.10:123 timecom –remove TimeSources 17.34.45.56:19095 6.6 SAVE Command The SAVE command saves current TimeSync option settings to the TimeSync configuration file on the specified system. SAVE is redundant if AutoSave is set to True in the TimeSync configuration file. The command can be issued as a command-line parameter or can be entered interactively at a TimeCom prompt. The SAVE command can only be issued against the local TimeSync server.
SERVERCONF [] - is the name of the configuration file to load. If is not provided, TimeCom will load the default configuration file from the default location. Examples timecom > serverconf /etc/timeSync/myconf.conf timecom –serverconf $USERS.DATA.TIMECNF timecom –serverconf $USERS.DATA.TIMECNF; –add TimeSources 12.13.134.234 6.8 SET Command The SET command alters configuration settings online for the TimeSync process.
AlwaysSendRefTS True | False ClientMode True | False DriftBackward True | False DriftBackwardThreshold DriftForward True | False DriftForwardThreshold MaxReplyDeviation MaxReplyWindow MultiSource True | False RetryInterval RetryLimit ReportOnly True | False SyncAt [, , …] TimeSources | [:] [, | , …] UpdateInterval LogCl
TraceWrap True | False TraceHTMLFormat True | False Examples timecom > set LogEnabled False timecom –set LogEnabled False 6.9 SHOW Command The SHOW command outputs current configuration settings from the TimeCom CI. SHOW Examples Timecom > show TimeCom Settings: Target System 192.168.1.107:123 (Local system) Local Address 192.168.1.107 timecom –show TimeCom Settings: Target System 16.102.111.12:123 (Local system) Local Address 127.0.0.1 Transport $ZTC04 6.
command. The command can be issued as a command-line parameter or can be entered interactively at a TimeCom prompt. STATUS [SYSTEM ] - is the IP address or DNS name and optional port number of the server from which information is to be retrieved. For example, system 11.12.13.14, system 11.12.13.14:1234, system dns.host.name, or system dns.host.name:1234. If is not supplied, the local system will be used.
ClientMode must be enabled in order to initiate a sync operation. If TimeSync is configured to sync at a specified interval via the UpdateInterval value, the next normally scheduled sync time will be adjusted to occur at UpdateInterval seconds after the SYNCNOW operation was completed. If TimeSync is configured to sync at specific times via the SYNCAT list, subsequent sync operations will continue to occur as scheduled; the SYNCNOW operation will not affect those scheduled sync times.
will be used. Note: If SYSTEM is entered without specifying any parameters the TimeCom CI will resume communication with the local copy of the TimeSync server. Examples timecom > system 16.102.111.12 timecom SYSTEM 11.12.13.
7. Appendix A: TimeSync Event Messages This appendix provides details about the event messages generated by TimeSync and logged to the system event log. The same message numbers and descriptions apply to all supported platforms unless otherwise stated. 7.1 General TimeSync Messages 1000 1000: TimeSync encountered an error during command line processing; process will exit TimeSync encountered an error while processing command line arguments and will exit. This error only occurs during startup. Cause.
1002: TimeSync version started TimeSync started successfully. version is the version of TimeSync; for example, 1.0.126. Cause. TimeSync was started on the system. Effect. TimeSync begins processing. Recovery. Not applicable. 1003 1003: TimeSync could not initiate operations; shutting down TimeSync could not initiate operations with the communication layer, and is shutting down as a result. This error only occurs during startup. Cause.
1005 1005: TimeSync shutting down TimeSync is shutting down normally. Cause. The operator or system initiated a shutdown of the TimeSync process. Effect. TimeSync shuts down. Recovery. Not applicable. 1006 1006: Error initializing application socket: description TimeSync could not initialize an application socket. description is the description of the error condition encountered. Cause. TimeSync could not obtain a socket from the communication infrastructure. Effect. TimeSync shuts down. Recovery.
be sure that all network infrastructure is up and running (network device drivers, TCP/IP processes/daemons, etc.). If the problem still persists, contact HP support. 1008 1008: Could not send TimeSync request; no time sources defined TimeSync could not send a request to obtain a reference time because no time sources were defined. This error can only occur if Client mode is enabled. Cause. Client mode was enabled but no time sources were defined in the TimeSync configuration file. Effect.
1010: Could not obtain time source data while processing TimeSync response; action could not be completed TimeSync received a response from a time source, but cannot locate that time source in the list of defined sources. Cause. The time source was removed from the TimeSync configuration after a request was sent to the time source, but before a response was received. Effect. The response is discarded and the update or report operation is canceled. Recovery.
Effect. The response is discarded and the update or report operation is canceled. Recovery. Not necessary; TimeSync will automatically retry the update using the next configured time source. 1013 1013: Could not proceed with operation due to time source error; time source source, error info: description TimeSync could not adjust the local system clock or complete a report operation because the response received from the configured time source was invalid.
Recovery. Define one or more time sources in the TimeSync configuration file and restart the TimeSync process, or else specify one or more time sources interactively via the TIMECOM ADD TIMESOURCES or SET TIMESOURCES command.
is the amount by which the clock needs to be updated. A negative value indicates that the local system clock is too fast and needs to slow down or move backward; a positive value indicates that the local system clock is too slow and needs to speed up or move forward. Cause. A TimeSync update was performed. Effect. The local system clock is updated if ReportOnly mode is disabled, otherwise the time difference is logged but no action is taken. Recovery. Not applicable.
1019 1019: TimeSync license will expire in number days, please email license.manager@hp.com to renew the license The TimeSync license for the local system will expire in the number of days shown. number is the number of days remaining before the license expires. Cause. TimeSync is running with a license that will expire in 30 days or less. Effect. TimeSync starts and executes normally. Recovery. Obtain an updated license from HP by emailing license.manager@hp.
7.2 Windows-specific Messages This section describes messages that are logged on Windows systems only. These messages will not be logged on any other platform. 2000 2000: TimeSync shutting down due to error TimeSync is shutting down due to an error encountered during Windows service initialization. Cause. TimeSync could not interact with some portion of the Windows services infrastructure. Effect. TimeSync does not start. Recovery.
TimeSync could not register its control handler with the Windows services infrastructure. errnum is the Windows service error that occurred. Cause. There was an error communicating with the Windows services infrastructure while trying to register the TimeSync service control handler. Effect. TimeSync does not start. Recovery. Check the system log and/or TimeSync log for additional messages detailing the specific cause of the error, and ensure that TimeSync is running with Administrator permissions.
Recovery. Verify that TimeSync is running with Administrator permissions and that security policy on the system is not set up to prevent time adjustments by the TimeSync process. 2005 2005: Error trying to get system time adjustment parameters; error number was errnum TimeSync could not obtain Windows system clock adjustment information. errnum is the Windows system error that occurred. Cause. TimeSync encountered a problem trying to get details on current Windows clock adjustment settings.
2007 2007: Error trying to get privilege info to adjust system time; error number was errnum TimeSync could not obtain Windows privilege information in preparation for updating the local system time. errnum is the Windows system error that occurred. Cause. TimeSync encountered a problem trying to get privilege data while preparing to update the local system clock. In most cases, this is a security-related issue. Effect. TimeSync does not adjust the local system time. Recovery.
2009: Error trying to set system time adjustment parameters; error number was errnum TimeSync could not adjust the local system time. errnum is the Windows system error that occurred. Cause. TimeSync encountered a problem trying to adjust the local system time. In most cases, this is a security-related issue. Effect. TimeSync does not adjust the local system time. Recovery.
7.3 Linux-specific Messages This section describes messages that are logged on Linux systems only. These messages will not be logged on any other platform. 3000 3000: Error trying to adjust system clock; error number was errnum TimeSync could not adjust the local system time. errnum is the Linux system error that occurred. Cause. TimeSync encountered a problem trying to adjust the local system time. In most cases, this is a security-related issue. Effect. TimeSync does not adjust the local system time.
is the Linux system error that occurred. Cause. TimeSync could not set the local system time. In most cases, this is a securityrelated issue. Effect. TimeSync does not set the local system time. Recovery. Verify that TimeSync is running with root permissions and that security policy on the system is not set up to prevent time adjustments by the TimeSync process.
7.4 OSS-specific Messages This section describes messages that are logged only on NonStop systems running the OSS version of TimeSync. These messages will not be logged on any other platform. 4000 4000: Error obtaining system time; could not proceed with time update TimeSync could not obtain the local system time while preparing to update the time. Cause. TimeSync could not retrieve the current local system time while preparing to perform a clock update. In most cases, this is a security-related issue.
7.5 Guardian-specific Messages This section describes messages that are logged only on NonStop systems running the Guardian version of TimeSync. These messages will not be logged on any other platform. 5000 5000: Error obtaining system time; could not proceed with time update TimeSync could not obtain the local system time while preparing to update the time. Cause. TimeSync could not retrieve the current local system time while preparing to perform a clock update.
Cause. A transport process name was supplied in the TimeSync configuration file or via a SET TRANSPORT command, but that process does not exist on the local system. Effect. TimeSync cannot access the network, and therefore cannot operate in either client or server mode. Recovery. Supply a valid transport process name.
