topic Re: cmdvwagt in Disk Enclosures

cmdvwagt

fiorenzo monteleone — Thu, 22 Jan 2004 05:52:29 GMT

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

Re: cmdvwagt

Hoefnix — Thu, 22 Jan 2004 05:58:16 GMT

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

Regards,

Peter

Re: cmdvwagt

G. Vrijhoeven — Thu, 22 Jan 2004 06:04:18 GMT

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

Re: cmdvwagt

fiorenzo monteleone — Thu, 22 Jan 2004 06:06:37 GMT

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.

Re: cmdvwagt

Radim Jarosek — Thu, 22 Jan 2004 06:11:16 GMT

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

Re: cmdvwagt

Jakes Louw — Thu, 22 Jan 2004 06:14:58 GMT

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?

Re: cmdvwagt

Hoefnix — Thu, 22 Jan 2004 06:20:19 GMT

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

Re: cmdvwagt

fiorenzo monteleone — Thu, 22 Jan 2004 06:31:18 GMT

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"

Re: cmdvwagt

Jakes Louw — Thu, 22 Jan 2004 06:39:36 GMT

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...)