The following notes may be helpful when troubleshooting system problems:
The alerts service writes to a log file named _ims54alertd.log in x:\Sybase\ImpactServer-5_4\bin\.bin at start up and shut down. If you have problems with the alerts service, examine the log file first. A common error is an invalid home directory specified during the service’s install or set up.
If the alert service fails to start and the log file is not created, the most common reason is that the required environment variables are not properly defined, which prevents alertdsrv from executing. This error may be caused because the script or binary cannot find shared libraries.
After a successful startup, alertdsrv creates alertd.xlog1 in the home directory specified during install or setup. The following shows typical log entries for a successful startup:
2005-06-14 15:18:03.807 Log limit = 1000000
2005-06-14 15:18:03.807 Log max roll depth = 2
2005-06-14 15:18:03.807 | ims54alertd | 2524 | 1124 | |
BEGIN_COPYRIGHT
Confidential property of Sybase, Inc.
Copyright 1987-2005.
Sybase, Inc. All rights reserved.
Unpublished rights reserved under U.S. copyright laws.
END_COPYRIGHT
BEGIN_DISCLAIMER
This software contains confidential and trade secret information of
Sybase, Inc. Use, duplication or disclosure of the software and
documentation by the U.S. Government is subject to restrictions set
forth in a license agreement between the Government and Sybase, Inc.
or other written agreement specifying the Government's rights to use
the software and any applicable FAR provisions, for example,
FAR 52.227-19.
Sybase, Inc. One Sybase Drive, Dublin, CA 94568, USA
END_DISCLAIMER
2005-06-14 15:18:03.807 | ims54alertd | 2524 | 1124 | | Alert handler
start
2005-06-14 15:18:03.807 | ims54alertd | 2524 | 1124 | | Create context:
OTI_Context
2005-06-14 15:18:03.807 | ims54alertd | 2524 | 1124 | | Create input
transport: AlertsIn
2005-06-14 15:18:03.817 | ims54alertd | 2524 | 1124 | | Create log
transport: AlertLog
2005-06-14 15:18:03.817 | ims54alertd | 2524 | 1124 | | Create error
transport: AlertError
2005-06-14 15:18:03.817 | ims54alertd | 2524 | 1124 | | Will poll
transport at rate: 3 s
2005-06-14 15:18:03.817 | ims54alertd | 2524 | 1124 | | Enter read/poll
loop...
2005-06-14 15:18:03.827 | ims54alertd | 2524 | 1124 | | Started Command
"myalert", in dir: ".", PID: 2460
2005-06-14 15:18:10.818 | ims54alertd | 2524 | 1124 | | Finished Command
"myalert", PID 2460, exit code: 0
2005-06-14 15:18:10.818 | ims54alertd | 2524 | 1124 | | Move Alert
message to log transport
A typical sequence for a successful read, the invocation of a script or binary, and log creation looks similar to this:
2005-06-14 15:18:03.827 | ims54alertd | 2524 | 1124 | | Started Command
"myalert", in dir: ".", PID: 2460
2005-06-14 15:18:10.818 | ims54alertd | 2524 | 1124 | | Finished Command
"myalert", PID 2460, exit code: 0
2005-06-14 15:18:10.818 | ims54alertd | 2524 | 1124 | | Move Alert
message to log transport
The following code shows typical log entries for a successful shutdown when alerts are running as a Windows service:
2005-06-14 15:18:10.818 | ims54alertdsvc | 2524 | 1124 | | Alert handler
exiting
If the script or binary blocks awaiting user input, such as for a pause or read command, the “Finished…” and “Move…” log lines are not present. To break the deadlock, use the Windows Task Manager to end the script or binary process. You should then see these log entries.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
