Operating System - HP-UX
1834769 Members
2927 Online
110070 Solutions
New Discussion

Re: /etc/opt/resmon/persistence files caused root to 100%

 
Adam Noble
Super Advisor

/etc/opt/resmon/persistence files caused root to 100%

All,

We had a problem this morning whereby we had to re-boot our system due to root being 100%. Could not even get on via console or scp, ftp etc. Anyway this should have been captured by ITO however template was not working.

More importantly does anyone know what the p.* files are in the above directory as we seem to get thousands of them. It also seems strange that the monitoring logs should be going into a filesystem mounted on /. I also note on my 11.00 systems (this one is 11i v1) there only appear to be m.* files. There also appears to be no housekeeping. How can I manage these files??? I had over 100MB of files!!!
10 REPLIES 10
Arunvijai_4
Honored Contributor

Re: /etc/opt/resmon/persistence files caused root to 100%

These files are related to STM and EMS products. If you dont require them, you can safely delete.

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Adam Noble
Super Advisor

Re: /etc/opt/resmon/persistence files caused root to 100%

I appreciate I can delete them, however what benefit do they actually provide. In otherwords if they are of no value can I prevent them from being generated?
Robert-Jan Goossens
Honored Contributor

Re: /etc/opt/resmon/persistence files caused root to 100%

Adam,

Could you post your ems version(s)

# swlist -l product | grep -i ems

Regards,
Robert-Jan
Arunvijai_4
Honored Contributor

Re: /etc/opt/resmon/persistence files caused root to 100%

Those products are for monitoring and system health checkup utilities. If you suppose log a call with HP, support personnel may ask you to provide information from these files/products.

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Adam Noble
Super Advisor

Re: /etc/opt/resmon/persistence files caused root to 100%

EMS-Config A.04.00.02 EMS Config
EMS-Core A.04.00.02 EMS Core Product
EMS-KRMonitor A.11.11.04 EMS Kernel Resource Monitor
EMS-MIBMonitor A.04.00.02 EMS MIB Resource Monitor Product
Adam Noble
Super Advisor

Re: /etc/opt/resmon/persistence files caused root to 100%

Thanks for that it seems to me very strange that we should be getting so many of these p.* files on the system, and also poor design in the fact they fill up /, surely its not designed for logging such as this? I also note on my 11.00 systems there are no such files only m.* files and I do not have this problem.
Arunvijai_4
Honored Contributor

Re: /etc/opt/resmon/persistence files caused root to 100%

Yes, EMS and STM are not installed by default in 11.0 systems where as in 11.11 it is default.

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Adam Noble
Super Advisor

Re: /etc/opt/resmon/persistence files caused root to 100%

To be honest it doesn't seem to add up. I have a number of 11i systems some are generating the p.* files and some are not. All of our server 11.00 and 11i have ems installed and all 11.00 servers are not generating the files. I am going to raise a call with HP for clarification.
Arunvijai_4
Honored Contributor

Re: /etc/opt/resmon/persistence files caused root to 100%

For more information,
http://docs.hp.com/en/B5735-90001/index.html
[Using EMS HA Monitors]

http://docs.hp.com/en/J6374-90018/ch04s04.html
[HP Support Tools Manager (STM)]

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Andrew Merritt_2
Honored Contributor

Re: /etc/opt/resmon/persistence files caused root to 100%

Hi Adam,
What version of OnlineDiags are you running on the affected system?

There have been some problems in the past where a defect would lead to a lot of p.* files being created, but those should all be fixed in the latest version of OnlineDiags. The files are temporary files used by the online diags for information about configured devices; they should, from memory, only exist for a short while, so their continued and prolific existance indicates a problem.

Have you removed a UPS from the system recently? I think that was one possible trigger for this being seen.

Andrew