RE: {bb} bb-prtdiag-4_3 not on the display server

["Dobbs, Steve-CONT (CR)" <Steve.Dobbs@cnet.navy.mil>]

I've got bb-prtdiag running on about 50 solaris 8/9 boxen, and here's some of the things that I've run into:

First, as a good diagnostic, log into the client having problems and run prtdiag manually.  There are some patch issues under solaris 8 & 9 that cause prtdiag to fail on a variety of platform/patch level configurations.  The only one I can think of off the top of my head is Solaris 9 on a V880 with patch 113574-08, but there are others, too.

Be aware that starting with Solaris 9, prtdiag is also in /usr/sbin, not just in /usr/platform/`uname -i`/sbin/.  Make sure that if you are using a mixed solaris 8/9 environment, that you have the $PRTDIAG_COMMAND defined correctly.

make sure that you are not accidentally running 2 copies of bigbrother on the client machine at the same time.  If so, what happens is that the second instance of bb-prtdiag deletes/overwrites the temp file used by the first instance of BB and hilarity ensues.  

Finally, on the client, become the bigbrother user, source the bbsys.local file, modify the bb-prtdiag script and set DEBUG=Y, and diagnose what's going on by running $PRTDIAG_COMMAND, bb-prtdiag, and other things referenced by the bb-prtdiag script.

-----Original Message-----
From: Trevor Holden [mailto:Trevor.Holden@justice.qld.gov.au]
Sent: Monday, May 31, 2004 1:40 AM
To: bb@bb4.com
Subject: {bb} bb-prtdiag-4_3 not on the display server


Hi

I searched the archives for information on this but couldn't find
anything.

Just setting up BB for the 1st time on a few hosts (well only on #2 so
far).

I have successfully got bb-prtdiag-4_3 to work on my display server
under Solaris 9 using bb version 1.9e, but not on a 2nd client. Perhaps
this isn't a problem specific to the prtdiag script, but it's the only
one I am having a problem with so far.

It always displays red, and the output from the red button is:

                ======================================
red Fri May 28 10:36:15 EST 2004  prtdiag reports some failures !!! 
 prtdiag reports some faults !!!  
<FONT SIZE=+2><b>Prtdiag Info</b><

 


Status unchanged in 17.75 hours
Status message received from 10.5.1.19 

                 ======================================

It seems the output after the '</b><' is missing as compared to the
output on the display server for its local client. The fact that the
text isn't interpreted as HTML isnt such a concern (it happens for other
tests, and there is probably a resolution in the archives, but I haven't
got round to that one yet).


Details:

To get bb onto a 2nd host, again running Solaris 9, the steps I took
were:
 Setup a bb user and home dir (same path as display server) on the 2nd
client
 Updated the ./etc/bb-hosts under the bb and bbc directories for the 2nd
client on the display server
 Copied across a tar file of the client dir on the Display Server
 Untarred it
 Added a link for bbc to it.
 Restarted  the bb client and server on the Display server
 Started bb on the 2nd client


My other tests (std tests, plus: meta_2_2.sh, bb-iostat-3_10, even one
of my own (it only did uptime, just to see what was required)) work.

The prtdiag test is referenced in bbc/etc/bb-bbexttab on the 2nd client
with:
localhost : : bb-prtdiag-4_3/bb-prtdiag.sh

Removing '$PRTFILE' from the line:
$RM $PRTFILE $YELLOWLINE $REDLINE

in 
./bbc/ext/bb-prtdiag-4_3/bb-prtdiag.sh

does result in the output of prtdiag -v being left in the bbc/tmp dir.

I don't see any problems listed in BBOUT.

Not sure what I am missing, any help appreciated.

Cheers
 Trevor


--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.