Daemon scopeux not running

[panks]

Hi,

I am new to HPUX environment and curious about knowing for what the scopeux is responsible. In my server I am observing the situation where server is not responding to any ssh or telnet connection but it is pingable. All the oracle jobs got killed in that case. The ex admin here has written a scripts by which it give me alert of Daemon scopeux not running in that situation. Can anyone tell me more about this daemon and its neccessity for system function.

[Analyst]

The daemon is related to HPOV.
It is OVPA Data Collector.To collect the data this should be running.

Plz check for the script and restart the OV agent.

[TTr · Accepted solution]

The scopeux daemon is part of glanceplusPAK and measureware packages. These packages are used to extract performance metrics from the kernel. The ex admin probably checks for it in one of the scripts. The scopeux daemonhas nothing to do with the ssh/telnet not responding or pracle jobs geting killed. Something else is wrong with your server, maybe a table in the kernel got full and no more processes can get started. You need to look further by observing the status of the server using glance.

[arun khatwani]

Its a performance process try out with the following command:
mwa start all

[LJenkins]

This daemon is related to the MWA agents that is responsible to monitored the applications
you can see the status with the following command
<<<<>>>>>
/opt/perf/bin/mwa status

<<<<>>>>>>>
/opt/perf/bin/mwa stop

<<<<<>>>>>>
/opt/perf/bin/mwa start

if that is no the correct path you can find this command and please use the flags to get information.

I hope this could help you

LCJC

[Johnson Punniyalingam]

Hi,

>>>Daemon scopeux not running in that situation. Can anyone tell me more about this daemon and its neccessity for system function.<<<

Trr:- has explained to about "scopeux"

now we need start investigate "why scopeux" wasn't running ..?

could be couple of reasons

In this case you should check from the logs any process couldn't register with "ttd"

most common reason "ttd" couldn't register with rpcbind because rpcbind wasn't running

SOLUTION:
***********
# ps -ef |grep rpc
root 725 1 0 Jul 28 ? 0:01 /usr/sbin/rpcbind
root 767 1 0 Jul 28 ? 0:00 /usr/sbin/rpc.lockd
root 761 1 0 Jul 28 ? 0:00 /usr/sbin/rpc.statd
root 1154 1 0 Jul 28 ? 12:05 /opt/dce/sbin/rpcd
root 1646 1 0 Jul 28 ? 0:00 /usr/sbin/rpc.mountd
root 4568 3369 1 18:00:43 ttyp2 0:00 grep rpc
# kill -9 725 1154 (.....to permanently kill the Process ID for "rpcbind" and "rpcd" daemons)
# /sbin/rc2.d/S590Rpcd start (.....to restart the "rpcd" daemon)
# /usr/sbin/rpcbind (.....to restart the "rpcbind" daemon)
# ps -ef |grep rpc (.....both daemons should be showing the current time)
# mwa stop
# ttd -k
# cat /dev/null >logtran
# cat /dev/null >logappl
# cat /dev/null >logdev
# cat /dev/null >logglob
# cat /dev/null >logindx
# cat /dev/null >logproc
# mwa start
# mwa status (.....wait for few minutes before checking the status)


Thanks,
Johnson