Changes between Version 7 and Version 8 of Sun-Local Computing

Timestamp:

04/03/06 16:23:31 (20 years ago)

Author:

cdelarcuz

Comment:

--

Sun-Local Computing

@@ -327 +327 @@
 To use SSL, you'll need to select that option in your email program.
 
-Refer to [http://www.astro.columbia.edu/~crussell/computing/notes/netscape_email_ssl.note
-SSL email setup details] for Netscape 6.2 .
-
-
+Refer to [http://www.astro.columbia.edu/~crussell/computing/notes/netscape_email_ssl.note SSL-notes] for Netscape 6.2 setup details.
+
+= Pool & Backup = 
+
+== Permanent Sun host Data Directory Space ==
+
+
+        If you need disk space on the Sun hosts, send mail to crussell@astro .
+        Note that ONLY /home directories are backedup on the Sun hosts. 
+
+
+
+== Backup Info ==
+
+        4mm tape media is available in 1008 or in 1328 so that students can
+        backup data directories. 
+
+== Backing up Directories ==
+
+        Notes for backing up directories can be found [http://www.astro.columbia.edu/~crussell/computing/notes/backup.note here].
+
+= Rebooting Sun Hosts =
+
+== EMERGENCY SUN HOST REBOOT/POWER OFF ==
+
+
+If no one with root password access (crussell, caleb, jules or arlin) is
+available and you have determined (see below) that a reboot is
+necessary, you can reboot as follows:
+
+
+1. If host has a front panel 'button' (ie. all SunBlades and all Ultras
+                                           except for Ultra-1's)
+   then to reboot safely:
+
+   Push and let go quickly the lit button on the front panel.  The
+   screen will go black.  About a minute or two later, the screen will
+   light up, a message about syncing the disks will be displayed and
+   then the cpu box will be powered off.
+
+   After a moment, check that the light in or near the front panel
+   button is off.  Then push and let go quickly the button.  The host
+   will boot back up.
+        
+        NOTE: Host lakme in Room 1325 has a hardware problem and this
+              does not work on that host.
+        NOTE: If the 'safe' reboot doesn't work, the last resort is 
+              to hold in the 'button' about 4 seconds or more until the
+              cpu box powers off (light is out).  If that fails, then
+              unplug the cpu box.
+
+   *See below for errors that occur when the 'safe' reboot isn't possible.*
+
+        
+2. If host has no front panel 'button' (ie. Ultra-1     attila, isolde, lucia
+                                            SPARCtation-10      odyssey
+                                            SPARCstation-5      doncarlo )
+   then to reboot safely:
+
+   Hold down 'Stop' key and the 'a' key.  This will display the okay prompt:
+                OK>
+   In order to sync the disks (this does NOT work on other hosts),
+        type:
+                OK> sync
+   After many messages (ie: syncing disks, dumping, ...) the screen
+   will go black.  When the screen turns white, the host has started
+   to reboot.
+
+   If you need to power off the host, then instead, as soon as the
+   screen turns white for the reboot, do a 2nd 'Stop-A'.  Then at the
+   prompt, type
+                OK> power-off
+   to power off the cpu box.
+
+        NOTE: If the 'safe' reboot doesn't work, the last resort is 
+              use the switch by the plug to power off the cpu box.
+
+   *See below for errors that occur when the 'safe' reboot isn't possible.*
+
+                    ............................
+
+== IS A REBOOT NECESSARY? ==
+
+Most Sun hosts act as data disk servers, some also as home directory
+servers and others as mail, print, web, and software servers.
+
+As the Sun systems are interdependent, they are ideally always up and
+running with all disks mounted.  Rebooting should be a last resort.
+
+Below are guidelines on how to avoid a reboot/poweroff of a Sun host.
+See guidelines for doing a 'safe' reboot/poweroff above.
+
+How to avoid a reboot:
+
+1. Keep a 'console' window open.  All system error messages are
+   displayed in the console window.  (In CDE's menu, select HOSTS -->
+   Terminal Console )
+
+2. Check the messages in the console window.  If they include:
+        ... server SOME_HOST not responding ...
+   then your host is likely just waiting on another host that is
+   temporarily unavailable.  Wait for the remote host to be 
+   back up.  You should only reboot as a last resort and only if you
+   can work without that remote host. 
+
+   If the console messages include:
+        ... server SOME_HOST_X not responding ...
+        ... server SOME_HOST_Y not responding ...
+        ... server SOME_HOST_Z not responding ...
+   then there is likely a network problem and rebooting will not help.
+   Get in touch with the system manager.
+
+3. If your console session is hung or frozen and there are no 
+        ... server SOME_HOST not responding ...  
+    messages, then try to kill the session from another host:
+                > ssh -l your_username  your_hostname
+                > psallw | grep ksh
+USER PID  %CPU PRI NI S %MEM  VSZ   SZ  ELAPSED    TIME TT      COMMAND   
+YOU  9561  0.0  59 20 S  0.1 1952  244  1-02:32:54 0:00 ?  /bin/ksh \
+                                                        /usr/dt/bin/Xsession
+                > kill  9561            (PID# for your Xsession 'ksh' process)
+
+
+                    .................................
+
+== LIKELY ERRORS AFTER 'UNSAFE' REBOOT/POWEROFF ==
+
+   These occur when the 'safe' reboot/poweroff described above was
+   not possible.
+
+        Disk .../dev/dsk/c0t0d0s0... not OKAY
+
+                ...Run fsck...
+
+   Before the indicated disk(s) can be mounted, the root account must run
+   'fsck' on that disk.  If no one is available to use the root
+   account, the disk and, possibly the host, will remain off line.
+
+        
+        
+                
+