UNIX for Advanced & Expert Users

Dear All....Help required

prtdiag -v command shows no output on my V440 server.

Following is the details:

root@sdp16b>prtdiag -v
root@sdp16b>

root@sdp16b>uname -a
SunOS sdp16b 5.9 Generic_122300-31 sun4u sparc SUNW,Sun-Fire-V440

root@sdp16b>echo $path
/usr/sbin /usr/bin /usr/sbin /usr/dt/bin /usr/sfw/bin /usr/openwin/bin /opt/EABfds/bin /opt/EABcsutls/bin /opt/TimesTen/bin /opt/EABcss7ut/bin /opt/EABss7009/bin

root@sdp16b>/usr/sbin/prtdiag -v
root@sdp16b>

OS is solaris 9

Have you tried:

Code:

/usr/platform/`arch -k`/sbin/prtdiag -v

Which is how one ran prtdiag on Solaris 8 and below?

Sorry Mate still does not work....

root@sdp16b>/usr/platform/`arch -k`/sbin/prtdiag -v
root@sdp16b>

I've read that prtdiag does not work on all platforms.

Was it working previously...

Have you recently applied any patches ?

Is picl correctly installed:

Code:

# pkginfo -l | grep picl
PKGINST: SUNWpiclr
PKGINST: SUNWpiclu
DESC: PICL Daemon, Libraries, prtpicl client and plug-in modules
PKGINST: SUNWpiclx

If so a bounce of picld may resolve issue.

Otherwise you may need to pkgrm/pkgadd picld p again to get a clean set up...

HTH

@Tytalus

I think its picl installed properly.

root@sdp16a>pkginfo -l | grep picl
PKGINST: SUNWpiclr
PKGINST: SUNWpiclu
DESC: PICL Daemon, Libraries, prtpicl client and plug-in modules
PKGINST: SUNWpiclx

It was working previously... then I upgraded the machine and installed some new patches. I did the same to the other machine in the cluster and every thing is Ok over there and the prtdiag command runs there error free.

---------- Post updated at 03:41 PM ---------- Previous update was at 03:39 PM ----------

@Tytalus

Sorry I gave you the output of the A node the troubled nodes output is:

root@sdp16b>pkginfo -l | grep picl
PKGINST: SUNWpiclr
PKGINST: SUNWpiclu
DESC: PICL Daemon, Libraries, prtpicl client and plug-in modules
PKGINST: SUNWpiclx

ok- so try a stop/ start of picl. It's the usual cause for prtdiag (and sunmc) issues.

You could also try a truss on your prtdiag and see what's happening.

often you'll see it's spinning on a door call - so you can then track that back. It's often picl - hence the restart.

another route if the picl stop/start doesn't work is to dive into the console and do a resetsc