Well, ipmap is restarted automatically every time it dies, whether intentionally
or not, which is why you see this error message over and over again.  And if you
want someone to look at the core, then you will have to open a problem to
Support.  But that is not your real problem.

But the error message would seem to indicate that that ovtopmd is not running.
Is this true?  Do    ovstatus  | more
and find out.  If ovtopmd or other daemons have died, then your ipmap problem is
just a symptom of that and not the cause.  Look in your ovstatus output for the
last message from the daemons which are down.   If you have problems with
starting or keeping the daemons up, then there is no point in opening the map.
It won't be correct.

If you are having trouble with ovtopmd, then I would first make certain that
your ovwdb cache size is good -- about 20% larger than the number of objects you
have (ovobjprint -S  will tell you that) because ovtopmd will go down if he has
trouble talking to ovwdb or to trapd.  And if you can get ovtopmd restarted, I
would try doing and ovmapcount -a
followed by an ovtopofix -A  (if you have only one map) or ovtopofix -a (if you
have multiple maps --  ovwls will list them).   And then I would format the
nettl logs (netfmt -f nettl.LOG00 > formatted.LOG00   and do the same for LOG01)
and look for errors in there.  There will probably be messages about lost
interfaces and objects that you should try to clean up.  Again, call Support if
you need help.

As far as netmon being unable communicate with snmpd, you should investigate
that also.  Is snmpd running?  Try stopping and restarting him and see if netmon
will run after that.  Some operating systems have an snmpd which periodically
goes out to lunch and stops responding even though it is technically still up.

PS:  Next time you ask for help on the list, it would be good to tell us all
what version of NetView and what level of operating system you are running, and
how long you have been running NetView before the problem occurred.

Good luck.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Mamadou <mamadou AT CESAR.ORG DOT BR> on 11/04/99 10:32:00 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  ipmap died on signal: SIGSEGV (11) (see
      /var/opt/OV/log/ipmap_err.log)




Hi List,

I have a problem when I try to open my map

The map and event categories window are opened but I receive the

following repeted message on my console:

ipmap died on signal: SIGSEGV (11) (see /var/opt/OV/log/ipmap_err.log)

and sometimes later:

Fatal IPMap error: Cannot connect to database and a window message error

Fatal object database error: Connection to databas lost

looking on the netmon.trace I have the following message

-----------------------------------------------------------

Thu Nov 4 10:16:34 GMT 1999

Cannot communicate with SNMP daemon via loopback address (127.0.0.1); it is

either not running or has been configured with a community name different

from that configured into OpenView for this system. If a community name has

been configured into the SNMP daemon, that community name must be configured

via xnmsnmpconf or ovsnmpconf for address 127.0.0.1 as well as for the

hostname or IP address of this system. It is also possible that the

MIB-II sub-agent is not running or responding to the master agent.

-------------------------------------------------------------------------
----

my snmpd.conf looks like OK.

Does anyone have an idea on how to fix this problem

Regards, Mamadou