Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nv\-l\]\s+polling\s+daemon\s+problems\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nv\-l\]\s+polling\s+daemon\s+problems\s*$/: 4 ]

Total 4 documents matching your query.

1. [nv-l] polling daemon problems (score: 1): Author: jason.ctr.alburger AT faa DOT gov; Date: Fri, 11 Jun 2004 10:01:04 -0400; RH 7.2, NV 7.1.3 + FixPack 2 Hello all, I'm polling a handful of MIBs on different boxes with custom built polling daemons. I've custom built topology icons under some nodes to represent these MIBs a; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-06/msg00111.html (11,756 bytes)
2. Re: [nv-l] polling daemon problems (score: 1): Author: James Shanks <jshanks AT us.ibm DOT com>; Date: Fri, 11 Jun 2004 10:51:46 -0400; Sounds like you have an xxmap problem, since he would be the one updating the GUI for nvotChangeVertexStatus( ). He works in tandem with gtmd. gtmd gets the call, updated the database, and xxmap shou; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-06/msg00113.html (14,101 bytes)
3. Re: [nv-l] polling daemon problems (score: 1): Author: jason.ctr.alburger AT faa DOT gov; Date: Fri, 11 Jun 2004 11:24:41 -0400; I don't see any recent cores for xxmap or gtmd. I'll keep an eye on it, though. Any ideas on the "synchronizing" or the ovspmd core? Is it possible they're not related to my polling daemon problems?; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-06/msg00114.html (16,248 bytes)
4. Re: [nv-l] polling daemon problems (score: 1): Author: James Shanks <jshanks AT us.ibm DOT com>; Date: Fri, 11 Jun 2004 12:33:39 -0400; Well the constant synchronizing most probably means that ipmap or xxmap is continually dying and then restarting because something in the database is messed up. And ovspmd is the daemon who controls; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-06/msg00116.html (26,207 bytes)

Current List: 1 - 4
Page: [1]