Return of the M.710xxxx file

[Terry Barkoulas_1]

Hi, back in mid Aug-Sept I started thread regarding a growing file in the /etc/opt/resmon/persistence directory that begins M.710... (don't remember full name). I was pointed to an errant UPS configuration and once I removed the old UPS from SAM, the file stopped being created. Now it seems after a subsequent re-boot of the server, the file has reared its ugly head again and I don't know how to stop it this time. I checked to see if a UPS entry was made in SAM and checked to see if the UPS_MOND daemon was running and none of the above was happening. Is there something else I should be checking? I have not installed the latest diagnostics patch which was also was recommended (mea culpa). Any thoughts? Thanks.

Terry

[RAC_1]

If you do a fuser -u "file_name" it will tell you which process is using/accessing it. From then on, may be we can make some sense.

Anil

[Terry Barkoulas_1]

Hi Anil, I tried the command and it does not return anything for that file M.710574890

[RAC_1]

lsof "file_name"

Anil

[Robert-Jan Goossens]

Hi Terry,

This is the link to your previous question.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=672217

Best regards,
Robert-Jan

[Terry Barkoulas_1]

Robert-Jan, I went through the last I created and have performed the following;
- Checked for DM_UPS daemon, it wasn't running but I did remove the PowerWare software that was monitoring the UPS
- Removed the ups_mond entry in the inittab file
- Renamed the ups_conf file
Unfortunately after trying all of the above, the file is still growing. How do I stop/restart the Online Diags (next thing to try?)
In the interim, I have create a CRON job to remove the file on an hourly basis, since I don't know what else I can do at this point.

[RAC_1]

/sbin/init.d/diagnostic stop and
/sbin/init.d/diagnostic start

did you do lsof "file"

Anil

[Robert-Jan Goossens]

Hi Terry,

Try this,

# /etc/opt/resmon/lbin/monconfig

choose "(D)elete a monitoring request"

choose "7) Send events generated by monitors
/system/events/ups"

choose the kill option, answer Y
choose E to enable again.

check your conf with the C option.
(C)heck detailed monitoring status

Regards,
Robert-Jan

[Terry Barkoulas_1]

Robert-Jan, I tried the command sequence you stated, and there are a few monitoring jobs related to the UPS;
) Send events generated by monitors
/system/events/ups
with severity >= INFORMATION to TEXTLOG /var/opt/resmon/log/event.log
with client configuration file:
/var/stm/config/tools/monitor/default_dm_ups.clcfg
8) Send events generated by monitors
/system/events/ups
with severity >= MAJOR WARNING to SYSLOG
with client configuration file:
/var/stm/config/tools/monitor/default_dm_ups.clcfg
9) Send events generated by monitors
/system/events/ups
with severity >= MAJOR WARNING to EMAIL root
with client configuration file:
/var/stm/config/tools/monitor/default_dm_ups.clcfg

Do I need to remove all of these or just the one indicated in No.7 Please advise. Thanks.

Terry

[Robert-Jan Goossens]

Hi Terry,

If you don't use the ups I would remove all three.

Best regards,
Robert-Jan

[Terry Barkoulas_1]

The problem here is this all started when we replaced the existing UPS and are now using a new HP UPS and it was being monitored by the HP recommended software Powerware Lansafe which I have removed thinking it was adding to the problem. I guess I can remove these monitors and totally rely on the Powermonitor daemon that is installed with the Lansafe software, or is this not recommended? Thanks again for all your help