![background image](http://html1.mh-extra.com/html/ncr/worldmark-4300/worldmark-4300_product-manual_3744381074.webp)
Diagnostics
B-8
Troubleshooting
process is running using
ps -ef | grep ldsm
and start LanDesk if needed, using
/etc/init.d/ldsm start
.
•
For the UNIX ldsm server, if some ldsm processes are running, check the UNIX Server
Manager log file, /var/ldsm/log/sm_log_mmddyy, to see if only some of the ldsm agent
processes have died. If so, stop and restart the ldsm using
/etc/init.d/ldsm
{stop|start}
. Check process core files in the SMDATAROOT location, /var/ldsm.
•
Verify the UNIX server accepts broadcast or multicast IP messages. The default option for
discovery is “Send a broadcast message”. Try multicast by selecting “Use IP Multicast for
Discovery” option in the Configure > Communications > Networks dialog and retry the
auto-discovery. If neither is accepted by your servers network configuration, configure the
server manually using the Configure > Communications > Addresses dialog.
Services Troubleshooting Procedure
•
Same as above.
•
If not all UNIX dsm 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 gent_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.
Auto-discovery Never Returns
Possible Causes
•
Communications TimeOut and/or Retry options are set too high
User Troubleshooting Procedure
•
Verify that network services for IP or IPX are running on the LANDesk console.
•
Try a smaller TimeOut and/or Retry option in the Configuration > Communications dialog.
Services Troubleshooting Procedure
•
Same as above
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...