LANDesk UNIX Server Troubleshooting
B-28
Troubleshooting
LANDesk Problem Documentation
The following documentation should be provided to development to facilitate diagnosis of a
problem depending on the suspected area of the problem. This section also provides an overview
of the data files used by the LANDesk server during its operations.
LANDesk Server package VERSION and PSTAMP obtained from pkginfo -l ldsm.
UNIX user System Log -- /var/adm/usererr/error.mm-dd
servermon and ldsm agent process log error conditions in NCR standard log format. This file
may exist in a non-standard location depending on your UNIX system syslog configuration.
Server Manager Log File -- /var/ldsm/log/sm_log_mmddyy
Contains informational and error conditions from the ldsm agent process in Server Manager
specific format.
CPIO of SMDATAROOT tree -- In general the ldsm data files are stored in /var/ldsm and its
sub-directories, so a cpio and compress of the entire /var/ldsm tree could be useful. If the area
causing a problem can be determined, the following documentation can be selectively provided
to development as needed.
History File(s) -- /var/ldsm/hist/HIST*.HST
Contains history data (currently or previously) collected.
Memory Map(s) -- /var/ldsm/shm/*
Provide all maps or the map(s) for the particular agent in trouble. For general problems the
following two maps are also useful:
–
Message System problems – sm_map_MSGSYS
–
UNIX Port semaphore/handle problems – sm_map_PORT_SHM0
Registry Data -- /var/ldsm/reg/*
/var/ldsm/reg/SmmProxy -- The SMM Proxy stores data into files in this directory for the active
event configuration.
Server Manager Configurable/Tunables -- /var/ldsm/sm_config and /var/ldsm/shm/sm_tunes
These files define configuration tunables that can be set to adjust the size of memory mappings
used for semaphores, handles, and Message System structures. The sm_config file defines the
user configuration. Comments indicate the tunables which can be adjusted by name, default
value, minimum value, and maximum value. This file normally would not need to be changed
after package installation and should already contain appropriate values for operation of the
standard ldsm agents plus NCR add-on agents. The sm_tunes file is the configuration values for
the tunables which are currently in use. This file should NEVER be altered manually.
AMS Binding database -- /var/ldsm/AMS2DB
Stores the AMS alert action configuration (i.e., actions to be taken on a particular alert type;
where an alert instance should be delivered).
Optionally also the backup AMS Data Base file -- /var/ldsm/AMS2DB.bk
The backup file is created at AMS startup prior to compacting the AMS data base free space.
Password File -- /opt/ldsm/bouncer.dat
Process Stack Trace or Dump – If an ldsm process is not responding (e.g., hung), a process
stack trace or process dump could be provided.
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...