[Top] [All Lists]

Re: [nv-l] ovelmd daemon

To: nv-l@lists.tivoli.com
Subject: Re: [nv-l] ovelmd daemon
From: "James Shanks" <jshanks@us.ibm.com>
Date: Tue, 19 Mar 2002 12:25:05 -0500
I don't know what the problem with Events History application is, but you 
are barking up the wrong tree with trying to start ovelmd, I'll bet.
You are making a lot of assumptions here that I don't think are warranted. 
 So let's start over.

Do ovstatus.  Do you see an ems_log_agent?  Then he is registered.  That 
is the name that is used for ovelmd.  Since the days of HP, ovelmd has 
been called the "ems_log_agent" and the guy who feeds him, ovesmd, the 
"ems_sieve_agent".   Are these guys running?   If not you start them with 
either a general ovstart or a specific "ovstart ems_log_agent" or "ovstart 
ems_sieve_agent".   Kill your command-lie one first

I don't know why your ovaddjob failed.  You did not mention what directory 
you were in when you did it, nor what operands you used, but if you not in 
/usr/OV/lrf then you must give the full path to the  lrf file, as in 
"ovaddobj /usr/OV/lrf/ovelmd.lrf" .  If you are cd'd to /usr/OV/lrf, then 
you can just give the short file name.
But this should not be necessary.  This daemon come pre-registered.  If he 
is missing then someone deliberately removed him.   If you do have to add 
him back, and it still fails, even though you have use the correct syntax, 
then most likely you changed either the hostname or the IP address of the 
NetView box after installation and did not run reset_ci.  If that's true, 
you can do it now, but it will take down all the daemons when it s run. 
Not having done the reset_ci may also be why no events show up in the 
ovevent.log.  The ems_sieve_agent, ovesmd, feeds the log agent, ovelmd, 
but he has to be fed by pmd, who won't send anything if he doesn't know 
what box he is on. 

 Also, by default, ovelmd logs to /usr/OV/log/ovevent.log.  There is no 
need to specify any parameters on the daemon at all.  The defaults are 
correct for all installations.  The only reason to change them is for a 
special case.

And I am not surprised that /usr/OV/bin/ovelmd -f /usr/OV/log/ovevent.log 
did not work from the command line.  ovelmd can only log what ovesmd gives 
him.  And he can only log what pmd gives him.

So give all this some thought and try again.  Sorry it has to be so 

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group

"Dejan Mijailovic" <dejanm@webhosting.com>
03/19/2002 12:10 PM

        To:     <nv-l@lists.tivoli.com>
        Subject:        [nv-l] ovelmd daemon


Hi there.

I am running NetView 7.1 on Solaris 7 and I can't use "Monitor -> Events 
Event History.." application,....nor doing it
from command line using /usr/OV/bin/nvela. Application just "hangs" there,
window comes up but no events are shown...Application just "hangs"
I have noticed the OVELMD is running  and "ls" shows it is running
/usr/OV/bin/ovelmd.... no options.
I have noticed that ovelmd is not registrated with ovspmd and there for
"ovstart/ovstop can't be used"
If I try to run /usr/OV/bin/ovaddobj I get this message:

"ld.so.1: /usr/OV/bin/ovaddobj: fatal: libucb.so.1: openfailed: No such 
or directory

If I try running this from command line:  /usr/OV/bin/ovelmd -f
/usr/OV/log/ovevent.log,..again, just hangs there.

Any Idea?


Dejan Mijailovic
InQuent Technologies inc.
e-mail: dejan.mijailovic@inquent.com

To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web