Troubleshooting
Troubleshooting Procedures
Product Manual
U7613-J-Z815-6-76
©
S
ie
m
ens
Ni
x
d
o
rf
I
n
fo
rm
a
ti
o
ns
s
y
s
te
m
e A
G
19
95
P
fad
:
D
:\
O
761
3e
6\
u76
13
e.
k
1
1
Are There Messages in the Error Logs?
Always check the error logs used by the server. You can view the system, security, and
application logs from a client computer using Event Viewer or at the system console using
the elfread command. You also can view the logs in the PRINTLOG share area if there is
a printing-related problem. For problems related to server startup, you can check the
lmxstart.log
located in the
/var/opt/lanman/logs
directory.
If there are entries in any of these logs, save them for future reference. Never discard or
overwrite error messages since they may indicate the cause of the problem. These logs
may have to be supplied to support personnel at a later date.
The following message is particularly indicative of a server problem:
An Advanced Server for UNIX systems process with pid <no> unexpectedly
terminated.
This message indicates that a server process has encountered an unexpected error.
Depending on how your server is configured, there may be a core file located on your
system.
If the value of the CoreOk keyword is set to 1 (yes) in the Advanced Server Registry, then
a core file is located somewhere on the system. The CoreOk value is in the following key:
SYSTEM\CurrentControlSet\Services\AdvancedServer\ProcessParameters
Go to the
root
directory, and execute the following command to search the file system for
core files:
find . -name "core*" -print
Save any files that you may find. If the coreok parameter is set to no, then core files will not
be created. You may want to set the coreok keyword to yes in order to capture core files
which are useful for debugging purposes.
