topic Re: /opt/pred/bin/psaction MEMSCAN(160A) (160B) errors in Operating System - HP-UX

/opt/pred/bin/psaction MEMSCAN(160A) (160B) errors

Joe Profaizer — Fri, 01 Jun 2001 12:32:08 GMT

I'm currently getting these errors on all my HP servers every night. I've loaded the March '01 Support CD and also applied PHSS_24044. This all started after loading the PHSS patch. Should I remove the patch?
I have C.11.00.17 HP Predictive suppport product loaded.

Please consult.

Re: /opt/pred/bin/psaction MEMSCAN(160A) (160B) errors

Bill McNAMARA_1 — Fri, 01 Jun 2001 12:50:37 GMT

From the patch description there doesn't appear to be any critical fixes in that patch..

http://europe-support2.external.hp.com/wpsl/bin/doc.pl/screen=wpslDisplayPatch/sid=adb07ae5119b4d8ffb?PATCH_PATH=/hp-ux_patches/s700_800/11.X/PHSS_24044&HW=s800&OS=11.00

However, it is probably a good idea to upgrade your diagnostic to the 25 version as the patch is a patch for that version
Patch Description: s700_800 11.00 Support Tool Manager A.25.00 Patch

Here's the link to the free download.

http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=B6191AAE

or

http://software.hp.com/SUPPORT_PLUS/

Later,
Bill

Re: /opt/pred/bin/psaction MEMSCAN(160A) (160B) errors

Joe Profaizer — Fri, 01 Jun 2001 12:56:00 GMT

I have STM A.25.10 already loaded. Is there a newer version. This was installed w/ my March '01 Support Plus I believe.

Re: /opt/pred/bin/psaction MEMSCAN(160A) (160B) errors

Bill McNAMARA_1 — Fri, 01 Jun 2001 13:00:10 GMT

theres a patch
see
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xca9dee3e323bd5118fef0090279cd0f9,00.html

Later,
Bill

Re: /opt/pred/bin/psaction MEMSCAN(160A) (160B) errors

CHRIS_ANORUO — Fri, 01 Jun 2001 13:16:47 GMT

Remove the patch and check if there is any dependencies or wait for HP to pass on info on this.

Re: /opt/pred/bin/psaction MEMSCAN(160A) (160B) errors

Bill McNAMARA_1 — Fri, 01 Jun 2001 13:20:48 GMT

there are no dependancies on the patch.
It does seem like a bug too.
Check the symptom description on the patch claiming to fix it.

Later,
Bill