2.4.1 Resetting the date/time of a manager or agent to a past date/time
When you change the date/time of a manager or agent, do not return it to a past date/time, as a rule. On a host where JP1/IM is running, resetting the system clock of the operating system to a past date/time affects the database significantly, which requires JP1/IM to be re-installed or the database to be set up again.
Even when you are correcting a system clock that is too fast or slow, setting the system time back may disrupt the order in which the execution results of automated actions are displayed, or it may cause a problem in the way the monitoring tree status change date/time is displayed. Such problems occur when resetting the system time causes inconsistencies in the data managed by JP1/IM - Manager and JP1/Base. JP1/IM - View is not affected.
Furthermore, if the system time is set back, events may not be correctly searched when you search for events by specifying the arrival time.
If you intentionally set the system date/time forward to a future date/time for testing purposes, and you then need to return the system date/time to the original settings, use the procedure below.
- Important
-
If you are using a method to set the server's system date/time that does not reset it to a past date/time, such as a method using a Network Time Protocol (NTP) server, you can change the date/time without following the procedure described below. In this case, there is no need to stop JP1/Base.
- Organization of this subsection
(1) Resetting the manager's date/time back to the original date/time
-
Stop JP1/IM - Manager.
-
If the IM database is being used, stop the IM database.
-
Stop JP1/Base.
-
Reset the system to an earlier time.
-
When the system reaches the original time, start JP1/IM - Manager.
For example, if the system was reset from 02:00 to 01:00 in step 2, start JP1/IM - Manager when the system reaches 02:00.
However, if the IM database is being used, perform the following steps to start JP1/IM - Manager in step 4.
1. JP1/Base
2. IM database
3. JP1/IM - Manager
- Important
-
If you inadvertently start a service before the system time has reached the original time before the reset (that is, before 02-00 in step 5), the integrated monitoring database might become corrupted. If such corruption occurs, you need to rebuild the system.
Before resetting the time, back up the configuration information and database so that they can be recovered after the system is rebuilt.
The files that can be recovered are those that were backed up at a system time that was before the system time at the time of recovery. If the system time during the backup was not prior to the system time at the time of recovery, recover the files after the system time is past the backup time.
Alternatively, you can use the method described below to reset the system date and time. However, note that if you use this method, the information shown in step 5 and the event and host information in the IM database must be deleted.
Steps 3 and 6 are required only if you are using the IM database. To reset the date/time back to the original date/time:
-
Stop JP1/IM - Manager.
-
Stop JP1/Base.
-
Perform unsetup for the IM database.
For Windows, you need to start the JP1/IM2 - Manager DB Server service beforehand.
If the integrated monitoring database and IM Configuration Management database have been set up, you must remove both of those setups.
-
Reset the system date/time to the current date/time.
-
Delete the action information file, action hosts file, event database, and command execution log file.
The tables below show where the files to delete are stored.
- In Windows:
-
Table 2‒1: Files to delete (Windows) File name
Storage location
Action information file
Console-path\log\action\actinf.log
shared-folder\jp1cons\log\action\actinf.log
Action hosts file
Console-path\log\action\acttxt{1|2}.log
shared-folder\jp1cons\log\action\acttxt{1|2}.log
Command execution log file
All files under Base-path\log\COMMAND\
All files under shared-folder\jp1base\log\COMMAND\
Event database
IMEvent*.* files under Base-path\sys\event\servers\default\#
IMEvent*.* files under shared-folder\jp1base\event\ #
#: If a different path was specified in the event server index (index) file, the files under the specified path need to be deleted.
- In UNIX:
-
Table 2‒2: Files to delete (UNIX) File name
Storage location
Action information file
/var/opt/jp1cons/log/action/actinf.log
shared-directory/jp1cons/log/action/actinf.log
Action hosts file
/var/opt/jp1cons/log/action/acttxt{1|2}.log
shared-directory/jp1cons/log/action/acttxt{1|2}.log
Command execution log file
All files under /var/opt/jp1base/log/COMMAND/
All files under shared-directory/jp1base/log/COMMAND/
Event database
IMEvent*.* files under /var/opt/jp1base/sys/event/servers/default/ #
IMEvent*.* files under shared-directory/jp1base/event/ #
#: If a different path was specified in the event server index (index) file, the files under the specified path need to be deleted.
-
Set up the IM database.
-
Start JP1/Base.
-
Start JP1/IM - Manager.
This completes resetting of the system data/time of the manager. If you are using Central Scope, perform the following tasks.
-
From JP1/IM - View, log in to JP1/IM - Manager (Central Scope).
-
From the Monitoring Tree window, choose the highest-order monitoring group and set its state to the initial state.
Resetting all monitored nodes to their initial states eliminates inconsistencies in the data managed by Central Scope.
(2) Resetting the agent's date/time to the original date/time
When you reset the agent's date/time to the original date/time, you must modify the settings for JP1/Base on the applicable host. For details such as the relevant procedure, see the explanation on necessary tasks when the system date and time is changed in the chapter about changing settings during operation of JP1/Base in the JP1/Base User's Guide.