Running NAV 3.7.0 on Debian 5-64-bit, about 700 switches and routers
currently in NAV.
There has been a lot of weird stuff (trouble) happening with Cricket
after going from the latest in the 3.5-series up to 3.7, some things got
better from 3.6 to 3.7, but not all is perfect. Not complaining, just a
summary from my point of view over the last months of releases.
About a week ago my Cricket graphs just stopped and after some debugging
I found the Cricket-cronjob run as navcron dies after a while and leaves
a lock-file, cleaning it up and doing some optimizing (separating switch
and router interfaces, and system values into separate cronjobs) I found
the cronjobs still dies and leaves lock-files. First of all; anyone
else seeing the Cricket collector dying? (In my case just about on
Second; Anyone have a good tip on how to tune Cricket to run a sensible
number of jobs to get thru it all in a sensible amount of time?
Currently, if the largest job (switch interfaces) don't die after only a
few minutes it usually runs for 25-30 minutes.
NAV in my environment isn't really a production system, but my
pet-project provides more accurate and sensible information than any
system we have in production so I'll hang on to it as long as I can.
Any input appreciated!