2022/03/28 03:05:32.271885 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/28 03:05:32.271972 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/28 03:05:32.272137 logstash.go:90: INFO Max Retries set to: 3
2022/03/28 03:05:32.272212 metrics.go:23: INFO Metrics logging every 30s
2022/03/28 03:05:32.272222 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/28 03:05:32.272492 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-6wwps
2022/03/28 03:05:32.272887 async.go:63: INFO Flush Interval set to: 1s
2022/03/28 03:05:32.272906 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/28 03:05:32.273921 beat.go:221: INFO filebeat start running.
2022/03/28 03:05:32.274048 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/28 03:05:32.279983 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/28 03:05:32.280053 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/28 03:05:32.280127 crawler.go:38: INFO Loading Prospectors: 1
2022/03/28 03:05:32.280199 registrar.go:236: INFO Starting Registrar
2022/03/28 03:05:32.280225 sync.go:41: INFO Start sending events to output
2022/03/28 03:05:32.280375 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/28 03:05:32.280640 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/28 03:05:32.280729 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/28 03:05:32.280771 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/28 03:05:52.284428 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/28 03:05:52.285302 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/28 03:05:52.285653 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/28 03:05:52.285837 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/28 03:05:52.286287 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/28 03:05:52.330292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:52.330368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:53.340628 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:53.340670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:55.346470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:55.346530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:59.363682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:05:59.363721 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:06:02.273562 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=63 registrar.writes=1
2022/03/28 03:06:07.374359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:06:07.374396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:06:23.396497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:06:23.396549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:06:32.272620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:06:55.415873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:06:55.415988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:07:02.272516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:07:32.272575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:07:55.434318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:07:55.434366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:08:02.272619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:08:32.272572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:08:55.455572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:08:55.455677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:09:02.272749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:09:32.272618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:09:55.472406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:09:55.472442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:10:02.272600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:10:32.272852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:10:55.488342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:10:55.488379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:10:57.309962 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/28 03:11:02.272556 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/28 03:11:32.272556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:11:55.507838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:11:55.507893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:12:02.272612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:12:32.272622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:12:55.526571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:12:55.526623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:13:02.273184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:13:32.273402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:13:55.546617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:13:55.546670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:14:02.272541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:14:32.272550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:14:55.566757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:14:55.566797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:15:02.272717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:15:32.272621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:15:55.586736 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:15:55.587095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:16:02.272508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:16:32.272515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:16:55.605507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:16:55.605719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:17:02.272568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:17:32.272642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:17:55.623779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:17:55.623854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:18:02.273164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:18:32.272632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:18:55.641709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:18:55.641753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:19:02.273426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:19:32.272539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:19:55.659036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:19:55.659134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:20:02.272586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:20:32.272537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:20:55.677341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:20:55.677382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:21:02.272469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:21:32.273347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:21:55.701027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:21:55.701106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:22:02.276170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:22:32.272566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:22:55.719535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:22:55.719921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:23:02.272573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:23:32.272978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:23:55.740534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:23:55.740575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:24:02.272432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:24:32.272956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:24:55.758386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:24:55.758434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:25:02.272692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:25:32.272724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:25:55.774923 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:25:55.774961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:26:02.272564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:26:32.272579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:26:55.791999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:26:55.792038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:27:02.272524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:27:32.272532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:27:55.809641 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:27:55.809677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:28:02.272942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:28:32.272515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:28:55.829982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:28:55.830022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:29:02.272586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:29:32.272540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:29:55.851346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:29:55.851388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:30:02.272535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:30:32.272566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:30:55.872809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:30:55.872854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:31:02.272583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:31:32.272511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:31:55.889471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:31:55.889512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:32:02.273460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:32:32.272686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:32:55.907876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:32:55.907931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:33:02.272664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:33:32.272686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:33:55.925083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:33:55.925118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:34:02.272582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:34:32.272542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:34:55.944215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:34:55.944272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:35:02.272577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:35:32.272593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:35:55.962951 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:35:55.963014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:36:02.272597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:36:32.272585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:36:55.984173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:36:55.984476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:37:02.272587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:37:32.272828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:37:56.002881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:37:56.002935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:38:02.277814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:38:32.272580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:38:56.023440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:38:56.023488 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:39:02.272554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:39:32.272587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:39:56.044151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:39:56.044221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:40:02.272562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:40:32.272629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:40:56.061330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:40:56.061378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:41:02.272556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:41:32.272543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:41:56.079713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:41:56.079779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:42:02.272536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:42:32.272888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:42:56.098447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:42:56.098500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:43:02.272577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:43:32.272553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/28 03:43:56.116780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/28 03:43:56.116821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host