Filter
Top Products
38 Sun Blade 2500 Getting Started Guide • December 2004
Hung application.
Application won’t
respond.
Procedure 1: Using the Host Workstation
1. From the CDE toolbar, select Tools→Process.
2. In the Process Manager window, select Find Process.
3. Select the process that is hung. The name of the application or process is in the
Command column.
4. From the Process Manager menu, select Process→Kill Process.
Note: You may be able to log in from another workstation and use these same GUI
tools to save and close, or kill applications.
Procedure 2: Using a Terminal Window From Your Own Workstation
1. To determine the ID number of the hung process, type: ps -ef | grep process
name
Note: First kill the last application you used when the system hung and, if necessary,
kill the next most recent applications that you used.
2. To stop the process, type: kill -9 process ID
Procedure 3: Using Remote Login or Telnet
1. From another workstation, use a terminal window and type either:
rlogin hostname
or type: telnet hostname
2. Type your login ID and password.
3. From the terminal window, type: ps -ef | grep process name
4. Start killing processes. Type the name of the last application you were using when
the system froze.
Type: kill -9 process ID
After killing the processes for the last-used application, look at your system to see if
it is usable. If not, continue to kill processes until the system is usable or until you
can shut it down and restart it.
Caution: Be sure to log off from the remote system. Another user might be able to
access your system if you do not exit the terminal window.
5. On the second workstation, type exit and close the terminal window.
During the boot
procedure, the system
displays a network
error message.
Use this procedure if the system displays these error messages:
Warning: timed out waiting for NIS to come up
:Timeout waiting for ARP/RARP packet
1. From a remote system, ping the system with this command: ping hostname
2. Verify with your system administrator that the network is operational.
3. Is the Ethernet cable connected between the workstation and the wall outlet or
router?
4. Try connecting another Ethernet cable. Does the new cable work?
5. If cable changes do not help, bring the system to the ok prompt and verify the
OpenBoot PROM settings. Most systems should be set to diag-switch? = false
and boot-device set to disk net. For more information on OpenBoot PROM
settings, see the Sun Blade 2500 Service, Diagnostics, and Troubleshooting Manual, 817-
5117, or contact a Sun Service Support Center.
TABLE 4-1 Troubleshooting Procedures (Continued)
Symptom Troubleshooting