Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
cancel
Showing results for 
Search instead for 
Did you mean: 

cmdvwagt

fiorenzo monteleone
Occasional Advisor

cmdvwagt

The process consume a lot of CPU, I don't find any suggestion. How can i resolv it?
8 REPLIES
Hoefnix
Honored Contributor

Re: cmdvwagt

Starting with command "top" should give you an idea which process (+pid) is consuming much CPU.

Regards,

Peter
G. Vrijhoeven
Honored Contributor

Re: cmdvwagt

Hi,

What you can do is take a look if you can find its PPID. This should give you some idea.
check:
# ps -eaf |grep cmdvwagt

Processes that start with cm can indicate it is a MC/SG process. do you have that running. Check /var/adm/syslog/syslog.log for errors and dmesg for hardware errorrs if so.
HTH,

Gideon
fiorenzo monteleone
Occasional Advisor

Re: cmdvwagt

Thanks,
I know the PID process but I want to know why this process consume CPU.
I don't find any documentation about it and I don't know how can i stop it and restart and his use.
Radim Jarosek
Regular Advisor

Re: cmdvwagt

Hi,

in addition, if you have HP GlancePlus/UX , you should have :), you can trace a process and find almost everything what you need to know.

To find out if you have installed Glance.

# swlist | grep -i glance
B3693AA C.03.70.00 HP GlancePlus/UX for s800 11i

HTH

Radim
Jakes Louw
Trusted Contributor

Re: cmdvwagt

This doesn't look like a Cluster Manager process.

Have you looked through /sbin/init.d or /etc/rc.log to see if there is any reference to what this agent belong to?
Trying is the first step to failure - Homer Simpson
Hoefnix
Honored Contributor

Re: cmdvwagt

Is the process(cmdvwagt) owned by root or is it a specific user that gives a qlue?

fiorenzo monteleone
Occasional Advisor

Re: cmdvwagt

I find in /sbin/init.d this:

SnmpCmdVw:# Start the SNMP commandview sdm subAgent (cmdvwagt).
SnmpCmdVw:# "" Start cmdvw subAgent (cmdvwagt daemon)
SnmpCmdVw:# "1" Start cmdvw subAgent (cmdvwagt daemon)
SnmpCmdVw:SUBAGENT="/usr/sbin/cmdvwagt"


Jakes Louw
Trusted Contributor

Re: cmdvwagt

Ah! So I think you need to execute:

/sbin/init.d/SnmpCmdVw stop

But the reason for the high CPU is probably because of the filtering theshold settings for CommandView (not that I know a thing about the product...)


Trying is the first step to failure - Homer Simpson