Results

          2022/04/11 03:04:24.589222 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/04/11 03:04:24.589324 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/11 03:04:24.589396 metrics.go:23: INFO Metrics logging every 30s
2022/04/11 03:04:24.589539 logstash.go:90: INFO Max Retries set to: 3
2022/04/11 03:04:24.589666 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/11 03:04:24.589823 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-2457t
2022/04/11 03:04:24.590168 async.go:63: INFO Flush Interval set to: 1s
2022/04/11 03:04:24.590206 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/11 03:04:24.590854 beat.go:221: INFO filebeat start running.
2022/04/11 03:04:24.591004 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/11 03:04:24.604739 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/11 03:04:24.605458 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/11 03:04:24.605526 crawler.go:38: INFO Loading Prospectors: 1
2022/04/11 03:04:24.605664 registrar.go:236: INFO Starting Registrar
2022/04/11 03:04:24.605830 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/11 03:04:24.605670 sync.go:41: INFO Start sending events to output
2022/04/11 03:04:24.606405 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/11 03:04:24.606530 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/11 03:04:24.606610 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/11 03:04:44.611179 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/11 03:04:44.612020 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/11 03:04:44.614676 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/11 03:04:44.615210 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/11 03:04:44.615474 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/11 03:04:44.648587 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:44.648639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:45.656267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:45.656675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:47.663511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:47.663562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:51.670996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:51.671029 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:54.589875 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=64 registrar.writes=1
2022/04/11 03:04:59.677871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:04:59.677923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:05:15.696875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:05:15.696926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:05:24.590808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:05:47.716068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:05:47.716113 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:05:54.589683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:06:24.589765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:06:47.742665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:06:47.743082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:06:54.589790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:07:24.589787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:07:47.769600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:07:47.769638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:07:54.590271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:08:24.589773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:08:47.788640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:08:47.788676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:08:54.589799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:09:24.589737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:09:47.808147 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:09:47.808181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:09:49.629690 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/11 03:09:49.629816 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/11 03:09:49.629853 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/11 03:09:49.629917 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/11 03:09:54.589756 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/04/11 03:10:04.633896 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/11 03:10:24.589787 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/04/11 03:10:47.827815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:10:47.827877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:10:54.589717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:11:24.589688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:11:47.847507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:11:47.847668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:11:54.589712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:12:24.589789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:12:47.880262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:12:47.880306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:12:54.589754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:13:24.589778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:13:47.898586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:13:47.898736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:13:54.589802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:14:24.592588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:14:47.918789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:14:47.918846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:14:54.589660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:15:24.589640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:15:47.936827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:15:47.936961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:15:54.589809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:16:24.589933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:16:47.955542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:16:47.955601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:16:54.589758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:17:24.589754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:17:47.973027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:17:47.973076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:17:54.589730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:18:24.589768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:18:47.989853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:18:47.989886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:18:54.589765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:19:24.589730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:19:48.007577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:19:48.007617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:19:54.589685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:20:24.589662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:20:48.024855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:20:48.024886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:20:54.589746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:21:24.589646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:21:48.046576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:21:48.046619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:21:54.589705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:22:24.589600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:22:48.065765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:22:48.065830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:22:54.589700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:23:24.589721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:23:48.083509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:23:48.083566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:23:54.589657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:24:24.589628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:24:48.102846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:24:48.102886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:24:54.589706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:25:24.589698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:25:48.119577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:25:48.119628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:25:54.589670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:26:24.589718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:26:48.139351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:26:48.139388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:26:54.589764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:27:24.589720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:27:48.158888 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:27:48.158932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:27:54.589634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:28:24.589640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:28:48.176209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:28:48.176264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:28:54.589753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:29:24.589714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:29:48.194900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:29:48.194941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:29:54.589695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:30:24.589661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:30:48.212640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:30:48.212695 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:30:54.589707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:31:24.589673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:31:48.229786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:31:48.229840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:31:54.589766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:32:24.589944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:32:48.248543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:32:48.248603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:32:54.589806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:33:24.589641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:33:48.265796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:33:48.265967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:33:54.589689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:34:24.589669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:34:48.284761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:34:48.284803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:34:54.589635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:35:24.589827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:35:48.302776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:35:48.302811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:35:54.589749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:36:24.589720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:36:48.321324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:36:48.321361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:36:54.589693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:37:24.589762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:37:48.339083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:37:48.339124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:37:54.589680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:38:24.589687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:38:48.356529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:38:48.356575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:38:54.589732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:39:24.589753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:39:48.375516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:39:48.375581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/11 03:39:54.589789 metrics.go:34: INFO No non-zero metrics in the last 30s