Welcome, Guest. Please login or register.

Author Topic: Normal Poll fails, but Inventory Poll is successful  (Read 85 times)

healy@bnl.gov

  • Newbie
  • *
  • Posts: 13
  • Get with the SCRIPTING or get out.
    • View Profile
Normal Poll fails, but Inventory Poll is successful
« on: January 02, 2018, 11:09:52 PM »
 The reason for this post:  for some ODD reason, the inventory run (second crontab below) is successful for several devices that, for some reason, FAIL TO UPDATE during the normal 2-hr cycle (first crontab below).  Obviously, the arguments are VERY different, but still - this makes no sense to me.  So i'm wondering if anyone has seen this or can tell me the cause based on the arguments I used in the two crontab entries.  Device status shows "Discovery Outdated" and "last" is: 1:11 1-Jan-18 (as per inventory cron).  The host name, mac or IP of at least one of these does NOT show up in the logfile nedi.lastrun at all after the run is complete, much less with any error.

Here is my crontab entry for our normal every-two-hours polling of the network:

  #-  Almost every 2 hrs (not 24)
  0 2,4,6,8,10,12,14,16,18,20,22 * * * /var/nedi/nedi.pl -p > /var/nedi/log/nedi.lastrun 2>&1


The "inventory run" crontab is given below.
#-  run inventory poll at 1.11am on Monday morning ea week
11 1 * * 1 /var/nedi/nedi.pl -Aall -SAFGgadobewituvjp -Yam > /var/nedi/log/nedi_Y.lastrun 2>&1




ascii

  • Jr. Member
  • **
  • Posts: 73
    • View Profile
Re: Normal Poll fails, but Inventory Poll is successful
« Reply #1 on: January 04, 2018, 10:50:26 AM »
it might be a neighbour problem.
-p discovers the next neighbours
-A all discovers every device in the database

check if the missing devices have a neighbour