Results

          2022/03/26 03:01:51.891986 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/03/26 03:01:51.892037 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/26 03:01:51.892194 logstash.go:90: INFO Max Retries set to: 3
2022/03/26 03:01:51.892302 metrics.go:23: INFO Metrics logging every 30s
2022/03/26 03:01:51.892326 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/26 03:01:51.892953 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-bs7hv
2022/03/26 03:01:51.893204 async.go:63: INFO Flush Interval set to: 1s
2022/03/26 03:01:51.893228 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/26 03:01:51.893936 beat.go:221: INFO filebeat start running.
2022/03/26 03:01:51.894030 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/26 03:01:51.901104 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/26 03:01:51.901205 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/26 03:01:51.901258 crawler.go:38: INFO Loading Prospectors: 1
2022/03/26 03:01:51.901487 registrar.go:236: INFO Starting Registrar
2022/03/26 03:01:51.901541 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/26 03:01:51.901559 sync.go:41: INFO Start sending events to output
2022/03/26 03:01:51.901651 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/26 03:01:51.901678 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/26 03:01:51.901732 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/26 03:02:11.905881 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/26 03:02:11.906089 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/26 03:02:11.906259 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/26 03:02:11.906336 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/26 03:02:11.906454 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/26 03:02:16.913077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:16.913107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:17.916489 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:17.916533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:19.920554 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:19.920587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:21.892861 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/03/26 03:02:23.927174 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:23.927216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:31.940474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:31.940516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:47.948967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:47.949003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:02:51.892825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:03:19.952685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:03:19.952729 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:03:21.892659 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:03:51.892764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:04:19.957694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:04:19.957749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:04:21.892832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:04:51.893074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:05:19.961744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:05:19.961812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:05:21.892709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:05:51.893074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:06:19.965022 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:06:19.965060 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:06:21.892719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:06:51.892685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:07:16.916432 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:07:16.916435 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:07:16.916454 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:07:16.916628 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:07:19.968796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:07:19.969055 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:07:21.892732 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/03/26 03:07:25.924578 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/26 03:07:51.892722 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/03/26 03:08:19.972298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:08:19.972335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:08:21.892766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:08:51.895354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:09:19.976189 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:09:19.976245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:09:21.892907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:09:51.892725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:10:19.979195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:10:19.979239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:10:21.892711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:10:51.892771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:11:19.985244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:11:19.985285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:11:21.892654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:11:51.892640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:12:19.991305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:12:19.991338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:12:21.892772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:12:51.893111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:13:19.999235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:13:19.999283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:13:21.893026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:13:51.892773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:14:20.004498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:14:20.004536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:14:21.892687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:14:51.892718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:15:20.010783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:15:20.010829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:15:21.892696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:15:51.892690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:20.018103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:16:20.018149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:16:21.893359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:16:51.892716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:20.032973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:17:20.033190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:17:21.892696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:17:51.892751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:20.041552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:18:20.041592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:18:21.892670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:18:51.892664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:20.048617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:19:20.048653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:19:21.892831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:19:51.892681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:20:20.055744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:20:20.055777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:20:21.892778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:20:51.892677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:20.062885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:21:20.063167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:21:21.892739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:21:51.892783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:20.068906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:22:20.068955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:22:21.892781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:22:51.892749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:20.076121 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:23:20.076169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:23:21.892733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:23:51.892757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:20.081645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:24:20.081692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:24:21.893018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:24:51.892710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:20.087449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:25:20.087490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:25:21.892674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:25:51.893238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:20.093883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:26:20.093923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:26:21.892704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:26:51.892657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:20.100384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:27:20.100426 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:27:21.892938 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:27:51.892775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:20.110184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:28:20.110232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:28:21.892691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:28:51.892963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:20.116389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:29:20.116428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:29:21.892756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:29:51.892674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:20.122171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:30:20.122219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:30:21.892678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:30:51.892733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:20.129164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:31:20.129207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:31:21.892708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:31:51.892702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:20.135834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:32:20.135879 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:32:21.892774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:32:51.892671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:20.142270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:33:20.142341 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:33:21.892747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:33:51.892662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:20.151095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:34:20.151126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:34:21.892690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:34:51.892714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:20.159423 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:35:20.159470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:35:21.892687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:35:51.892736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:20.166474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:36:20.166513 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:36:21.892842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:36:51.892691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:20.173467 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:37:20.173827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/26 03:37:21.892711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/26 03:37:51.892710 metrics.go:34: INFO No non-zero metrics in the last 30s