
Diagnostics
B-12
Troubleshooting
Services Troubleshooting Procedure
•
Same as above
•
Examine the UNIX Server Manager Log file, to find the process id for the Historian process
which are used to process History graph requests. An example log below shows the log
entries of interest, extracted from a typical LANDesk startup log, with process id of interest
marked with superscipt numbers. Note, the process created id for the functions Historian
(marked
3
), MsgSys HIST (marked
6
; preceeds MsgSysRegister log for HIST marked
7
), and
HISTMsgReceive (marked
8
). Verify that these ldsm process are still running. Check the log
for any error entries indicating problems with these processes, problems processing
messages, or termination of these processes.
•
If History graphs are no longer recording data values (or History files are no longer
growing), verify that the Poller process id are still running. Identify these process ids by the
process-created log entries for the functions of NTPollerMain (marked
1
), POLLMsgReceive
(marked
2
), and MsgSys for POLL (marked
4
; preceeds MsgSysRegister log for POLL
marked
5
). Check for other logs indicating problems with these process ids in the pid field
(follows time).
09/27/96 08:14:21:980 4238 660300501 phstartup.c NTPollerMain INFO 0
sm_thread_or_fork new process created = 4263
1
09/27/96 08:14:22:90 4265 660300501 poller.c POLLMsgReceive INFO 0
sm_thread_or_fork new process created = 4267
2
09/27/96 08:14:22:90 4263 660300501 phstartup.c Historian INFO 0
sm_thread_or_fork new process created = 4268
3
09/27/96 08:14:22:180 4267 660300501 msgsys.c MsgSysThread INFO 0
sm_thread_or_fork new process created = 4273
4
09/27/96 08:14:22:190 4267 661100002 msgsys.c MsgSysRegister INFO 0
MsgSysThread created for moduleName POLL
5
09/27/96 08:14:22:290 4268 660300501 msgsys.c MsgSysThread INFO 0
sm_thread_or_fork new process created = 4275
6
09/27/96 08:14:22:300 4268 661100002 msgsys.c MsgSysRegister INFO 0
MsgSysThread created for moduleName HIST
7
09/27/96 08:14:22:300 4268 660300501 historian.c HISTMsgReceive INFO 0
sm_thread_or_fork new process created = 4276
8
SMB Parameters Do Not Display In-band
Possible Causes
•
DMI Service Layer is not running
•
SMB Agent has timed out and been de-registered from the DMI Service Layer
Summary of Contents for WorldMark 4300
Page 1: ...BD20 1398 B000 12 97 WorldMark 4300 Server Management Product Manual Release 2 0...
Page 6: ...Contents iv Table of Contents...
Page 10: ...Preface viii Preface...
Page 14: ...Monitored Controlled Attributes 1 4 Overview...
Page 50: ...Working With Event Actions 2 36 User Interface...
Page 66: ...Chassis Events A 10 SMB Event Code Tables...
Page 96: ...LANDesk UNIX Server Troubleshooting B 30 Troubleshooting...
Page 100: ...Index Index 4 WorldMark 4300 Server Management Product Manual...