[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]

Question - HP Superdome

Rich Holland holland@guidancetech.com
Wed, 13 Aug 2003 05:33:07 -0700 (PDT)


Someone posted a request a couple weeks ago about using the conserver in
an HP Superdome environment; I passed the question on to a friend who
does this and here's his response:

>       PROBLEM
> 
> While trying to connect to the *GSP* on the IP address, *gsp*
> is give the following error:
> 
>      *Force to *spy* *mode* by user admin*
> 
> What is causing this, and how can it be corrected?
> 
>       CONFIGURATION
> 
> HPUX-OS 11.x
> Superdome 32-way
> 
>       RESOLUTION
> 
> In this case, it was necessary to kill the shell process
> (pid) in order to start a new getty.  The procedure to do 
> this follows.
> 
> 1) Check if there is a getty running on the console:
> 
>    hostname:/home/root/.secure/etc#ps -ef | grep console
>     root *18489* 1  0  Sep 16 console 0:00 -sh
>     root 21620 18058  0 18:29:07 pts/4     0:00 grep console
> 
>    hostname:/home/root/.secure/etc#ps -ef | grep getty
>     root 21642 18058  0 18:29:18 pts/4     0:00 grep getty
> 
> ===> no getty running on console
> 
> 2) Try to start with init q
> 
> ==> If still no getty, go to step 3
> 
> 3) Kill the shell that was running on console:
> 
>    hostname:/home/root/.secure/etc#kill -9 *18489* (use the
> pid of the -sh above)
> 
> 4) Check for a getty again:
> 
>    hostname:/home/root/.secure/etc#ps -ef | grep getty
>     root 21687     1  0 18:29:41 console   0:00 
> /usr/sbin/getty console console
>     root 21707 18058  0 18:29:47 pts/4     0:00 grep getty
> 
> 5) *You should now be able to login on console via gsp.*
> 
> *BACKGROUND:*
> 
> If the hung shell process has filled up the audit log, you
> may also have to copy these 2 files to another directory and 
> create new, empty files.  The problem would be manifested 
> after using a Ctrl B and receiving this message:
> 
> "..file system of audit has 0%  left you must specify a
> backup file now and attempt to switch to backup file failed".
> 
> Use the command:  ll  /home/root/.secure/etc
> to check the file sizes of audfile1 and audfile2, then after
> copying them to a backup directory, recreate new files with 
> the commands:
> 
> # cat /dev/null > /home/root/.secure/etc/audfile1
> # cat /dev/null > /home/root/.secure/etc/audfile2

Hope this helps!
-- 
Rich Holland        (913) 645-1950        SAP Technical Consultant
print unpack("u","92G5S\=\"!A;F]T:&5R(\'!E<FP\@:&%C:V5R\"\@\`\`");