LANDesk UNIX Server Troubleshooting
WorldMark 4300 Server Management Product Manual
B-27
Error Constant Name
SM Error Code
SM_ERROR_SUCCESS
5114
SM_ERROR_DOES_NOT_EXIST
5115
WIN API error code constant names are used in the LANDesk software and redefined to the
following SM Error Codes for logging:
WIN Error Code Constant Name
Redefined to SM Error Code:
ERROR_ALREADY_EXISTS
SM_WARNING_EXISTS
ERROR_INVALID_HANDLE
SM_ERROR_INVALID_HAND
ERROR_IO_PENDING
SM_ERROR_IO_PENDING
ERROR_MORE_DATA
SM_ERROR_MORE_DATA
ERROR_SUCCESS
SM_ERROR_SUCCESS
Detecting ldsm Process Death or Failure on UNIX
Under normal operations the LANDesk Server consists of 30 plus ldsm processes. LANDesk on
Windows NT consists of services with multiple threads. On MP-RAS UNIX, version 3.01, kernel
threads were not available, so each agent thread on Windows NT was ported to a UNIX process.
In the
ps -ef
, the LANDesk process displays a command of /opt/ldsm/bin/ldsm plus the DMI
Proxy has one process with command /opt/ldsm/bin/smdmips. Depending on whether Server
Manager Module or Server Monitor Board is installed on your system, determines the number of
ldsm processes that should be running at all times on your system. The table below identifies the
typical number that should display from the command
ps -ef | grep
/opt/ldsm/bin/ldsm | grep -v grep wc -l
:
System Configuration
# ldsm process
running
Without SMM or SMB
31
With SMM
33
With SMB
35
If not all UNIX ldsm processes are running, examine the UNIX Server Manager log file
/var/ldsm/log/sm_log_mmddyy to determine the reason for the failure. The process id for each
ldsm agent created is logged in an INFO entry with E_Tag of 660300501 in the following
format:
mm/dd/yy hh:mm:ss:mm pid 660300501 mod.c agent_func INFO 0
sm_thread_or_fork new process created = agent_pid
Note the agent_pid and verify each is still running via
ps -p agent_pid
. Check for logs with
pid field equal to the agent_pid indicating a failure or termination of the process. Check for
process core files in SMDATAROOT location, /var/ldsm. If a reason for ldsm process failure
and corrective action cannot be determined, provide the process listing (
ps -ef | grep ldsm
output
), SM log file, and core files (if any) to development.
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...
