Anonymous_User Absent Member.
Absent Member.
190 views

lagmonitor: determine if the service is running or not...


Hi Guys,

Currently we wanted to monitor the health of access gateway and found
that this could be accomplished using lagmonitor script.
But, from the documentation it seems that it only has information about
how to start it and add to chkconfig in init process.

Could you Gurus help me understand what happens when I start lagmonitor,
as I am not able to find it, when I do a ps -eaf |grep lagmonitor....
Does this service start any other processes?
How should I determine if its up and running?
Or what should I expect when I start that service?

Any help?
Pointers...?

Dinesh


--
ddgaikwad
------------------------------------------------------------------------
ddgaikwad's Profile: https://forums.netiq.com/member.php?userid=5917
View this thread: https://forums.netiq.com/showthread.php?t=49821

0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: lagmonitor: determine if the service is running or not...

ddgaikwad wrote:

>
> Hi Guys,
>
> Currently we wanted to monitor the health of access gateway and found
> that this could be accomplished using lagmonitor script.
> But, from the documentation it seems that it only has information
> about how to start it and add to chkconfig in init process.
>
> Could you Gurus help me understand what happens when I start
> lagmonitor, as I am not able to find it, when I do a ps -eaf |grep
> lagmonitor.... Does this service start any other processes?
> How should I determine if its up and running?
> Or what should I expect when I start that service?
>
> Any help?
> Pointers...?
>
> Dines


If you are looking to upgrade to NAM 4 there's actually a SNMP option
to monitor the access gateway service?

The lagmonitor script starts two other scripts being laghealthcheck and
lagdiskusage. The laghealthcheck script parses the config.xml
(/var/novell/cfgdb/.current/config.xml) and looks for the soapbc proxy
(built in, can't be removed) and once it has found its details it will
try to connect to it on http://ip:port/aghealth (it tries first via
https and if that fails it tries via http). It'll try to connect a
number of times to this aghealth url and if it hits a threshhold it'll
restart the ics_dyn process.

The lagdiskusage script checks how much disk space is left on the root
partition. If it gets below 5GB it'll start reporting errors in the
/var/log/ics_dyn.log file.

Hopefully this helps.

--
Cheers,
Edward
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.