...
| Code Block |
|---|
[nmis@demo var]$ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
+cachens2.onqnet 13.64.159.31 3 u 426 1024 377 4.845 -0.126 0.458
+ec2-13-54-31-22 54.252.165.245 3 u 352 1024 377 18.036 1.540 1.008
-node01.au.verbn 192.12.19.20 2 u 514 1024 377 18.966 -16.530 1.176
*ntp3.syrahost.c 218.100.43.70 2 u 422 1024 377 63.642 -1.172 0.852
[nmis@demo var]$ date -u
2017. 02. 16. (?) 22:33:31 UTC |
Compare the system UTC time with actual UTC time. A site such as https://time.is/UTC will show current UTC time.
...
| Code Block |
|---|
[root@opmantek ~]# /usr/local/nmis8/bin/nmis.pl node=asgard debug=9 type=update > nodeUpdate.txt -or- [root@opmantek ~]# /usr/local/nmis8/bin/nmis.pl node=asgard debug=9 type=update | tee nodeUpdate.txt ################### [root@opmantek ~]# /usr/local/nmis8/bin/nmis.pl node=asgard debug=9 type=collect > nodeCollect.txt -or- [root@opmantek ~]# /usr/local/nmis8/bin/nmis.pl node=asgard debug=9 type=collect | tee nodeCollect.txt |
Email alerts
Contacts.nmis must have the correct DutyTime format.
...
- input/output: These fields should be the SNMP index number of the input or output interfaces.
- first/last: This is a timestamp that the router assigns. It's important that the router time is in sync with opFlow time. opFlow uses this time to calculate statisitcs. For example, if the router time is an hour earlier than the server time, opFlow will not display the data until the server time catches up with the router time.
omkd Troubleshooting
...
- .
...
OMK General
Node synchronization with NMIS
...
- Backup the suspect configuration file
- Copy the default configuration file from omk/install into omk/conf
- Restart the associated daemons and test
MongoDB
In-memory Sort Operations
If the following repetitive error is observed in /usr/local/omk/log/opEvents.log it may be related to a MongoDB resource issue.
| Code Block |
|---|
[Sat Nov 3 20:47:51 2018] [error] supervisor[4683] worker process 5424 exited with code 255
[Sat Nov 3 20:47:51 2018] [info] worker process terminated after only 1s, delaying restart for 32s |
Look for a corresponding error in mongod.log
| Code Block |
|---|
2018-11-03T20:47:51.596+0000 E QUERY [conn507] Plan executor error during find command: FAILURE, stats: { stage: "SORT", nRetu
rned: 0, executionTimeMillisEstimate: 550, works: 459671, advanced: 0, needTime: 459670, needYield: 0, saveState: 3592, restoreSt
ate: 3592, isEOF: 0, invalidates: 0, sortPattern: { time: -1 }, memUsage: 33554492, memLimit: 33554432, inputStage: { stage: "SOR
T_KEY_GENERATOR", nReturned: 0, executionTimeMillisEstimate: 380, works: 459670, advanced: 0, needTime: 2, needYield: 0, saveStat
e: 3592, restoreState: 3592, isEOF: 0, invalidates: 0, inputStage: { stage: "COLLSCAN", filter: { $and: [] }, nReturned: 459668,
executionTimeMillisEstimate: 90, works: 459669, advanced: 459668, needTime: 1, needYield: 0, saveState: 3592, restoreState: 3592,
isEOF: 0, invalidates: 0, direction: "forward", docsExamined: 459668 } } } |
...