HP BL480c HP ProLiant Servers Troubleshooting Guide - Page 61
Appl a, tion software problems - ibm proliant
UPC - 882780759664
View all HP BL480c manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 61 highlights
o Novell NetWare-Repair traditional volumes with VREPAIR. On NetWare 5.X systems, repair NSS volumes with the NSS menu command, and on NetWare 6 systems, repair NSS volumes using the NSS/PoolVerify command followed by the NSS/PoolRebuild command, if necessary. Refer to the NetWare documentation for more information. o Caldera UnixWare and SCO OpenServer from Caldera-Emergency boot diskette. Refer to the Caldera UnixWare or SCO OpenServer from Caldera documentation for more information. o Sun Solaris-Device Configuration Assistant boot diskette. Refer to the Solaris documentation for more information. o IBM OS/2-Power up the server from the startup diskettes. Refer to the OS/2 documentation for more information. o Linux-Refer to the operating system documentation for information. Linux operating systems For troubleshooting information specific to Linux operating systems, refer to the Linux for ProLiant website (http://h18000.www1.hp.com/products/servers/linux). Application software problems Software locks up Action: 1. Check the application log and operating system log for entries indicating why the software failed. 2. Check for incompatibility with other software on the server. 3. Check the support website of the software vendor for known problems. 4. Review log files for changes made to the server which may have caused the problem. 5. Scan the server for viruses with an updated virus scan utility. Errors occur after a software setting is changed Action: Check the system logs to determine what changes were made, and then change settings to the original configuration. Errors occur after the system software is changed Action: Change settings to the original configuration. If more than one setting was changed, change the settings one at a time to isolate the cause of the problem. Errors occur after an application is installed Action: • Check the application log and operating system log for entries indicating why the software failed. • Check system settings to determine if they are the cause of the error. You may need to obtain the settings from the server setup utility and manually set the software switches. Refer to the application documentation, the vendor website, or both. Software problems 61
-
1
-
2
-
3
-
4
-
5
-
6
-
7
-
8
-
9
-
10
-
11
-
12
-
13
-
14
-
15
-
16
-
17
-
18
-
19
-
20
-
21
-
22
-
23
-
24
-
25
-
26
-
27
-
28
-
29
-
30
-
31
-
32
-
33
-
34
-
35
-
36
-
37
-
38
-
39
-
40
-
41
-
42
-
43
-
44
-
45
-
46
-
47
-
48
-
49
-
50
-
51
-
52
-
53
-
54
-
55
-
56
-
57
-
58
-
59
-
60
-
61
-
62
-
63
-
64
-
65
-
66
-
67
-
68
-
69
-
70
-
71
-
72
-
73
-
74
-
75
-
76
-
77
-
78
-
79
-
80
-
81
-
82
-
83
-
84
-
85
-
86
-
87
-
88
-
89
-
90
-
91
-
92
-
93
-
94
-
95
-
96
-
97
-
98
-
99
-
100
-
101
-
102
-
103
-
104
-
105
-
106
-
107
-
108
-
109
-
110
-
111
-
112
-
113
-
114
-
115
-
116
-
117
-
118
-
119
-
120
-
121
-
122
-
123
-
124
-
125
-
126
-
127
-
128
-
129
-
130
-
131
-
132
-
133
-
134
-
135
-
136
-
137
-
138
-
139
-
140
-
141
-
142
-
143
-
144
-
145
-
146
-
147
-
148
-
149
-
150
-
151
-
152
-
153
-
154
-
155
-
156
-
157
-
158
-
159
-
160
-
161
-
162
-
163
-
164
-
165
-
166
-
167
-
168
-
169
-
170
-
171
-
172
-
173
-
174
-
175
-
176
-
177
-
178
-
179
-
180
-
181
-
182
-
183
-
184
-
185
-
186
-
187
-
188