Troubleshooting troubleshooting procedures, Or /var, Cpu bound conditions – Siemens Unix V4.0 User Manual
Page 243: Unbalanced disk loads, Are they on the same hub, Are they using the same applications or printers, Are they on the same lmx.srv process, Are they members of the same advanced server group
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
Connectivity between nodes using TCP/IP may be available but if connectivity between
NetBIOS names is not working then Advanced Server will not work. All Advanced Server
communications are based on NetBIOS name sessions. Use the test tools provided with
your protocol software to verify NetBIOS level connectivity. If you find a problem, isolate it
according to the information provided with the NetBIOS protocol documentation.
Step 4: Verify UNIX System Functionality
If all of the network connectivity modules check out properly, the next item to verify is the
UNIX operating system on the computer hosting Advanced Server. The operating system
provides a variety of log files and system checks that can be performed to verify proper
operation. For information on these checks, see your UNIX system administrator documen-
tation.
Advanced Server is particularly sensitive to the following system problems:
●
Insufficient disk space in critical file systems such as
root
(
/
) or
/var
.
●
Insufficient system memory causing excessive swapping.
●
CPU bound conditions.
●
Unbalanced disk loads.
●
Improperly tuned kernel parameters such as maximum number of open files or
maximum number of locks.
Operating system problems usually will affect all or most client computers connected to the
server. Do not spend much time on this step if you are troubleshooting an individual client
problem.
Step 5: Isolating Problems on the Advanced Server
If you determine that all of the underlying software is functioning properly, then you should
check Advanced Server for problems. Problem isolation on the server often is dependent
on the type of problem reported by the user community.
If only a single user is experiencing a problem, then you can narrow your focus quickly to
the operations that this user is attempting to perform.
If a group of users is experiencing problems but many other users are not, then you should
look for a common thread among the users with problems. For example,
●
Are they on the same hub?
●
Are they using the same applications or printers?
●
Are they on the same
lmx.srv
process?
●
Are they members of the same Advanced Server group?