By type
2022/04/11 03:04:01.899365 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:01.899447 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/11 03:04:01.899624 logstash.go:90: INFO Max Retries set to: 3
2022/04/11 03:04:01.899755 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/11 03:04:01.899935 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-fzxqk
2022/04/11 03:04:01.900421 metrics.go:23: INFO Metrics logging every 30s
2022/04/11 03:04:01.900427 async.go:63: INFO Flush Interval set to: 1s
2022/04/11 03:04:01.900492 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/11 03:04:01.901263 beat.go:221: INFO filebeat start running.
2022/04/11 03:04:01.901425 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/11 03:04:01.909351 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/11 03:04:01.909441 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/11 03:04:01.909480 crawler.go:38: INFO Loading Prospectors: 1
2022/04/11 03:04:01.909689 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/11 03:04:01.909777 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/11 03:04:01.909799 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/11 03:04:01.909820 registrar.go:236: INFO Starting Registrar
2022/04/11 03:04:01.909863 sync.go:41: INFO Start sending events to output
2022/04/11 03:04:01.909913 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/11 03:04:21.914590 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/04/11 03:04:21.914717 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/04/11 03:04:21.914982 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/04/11 03:04:21.915070 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/04/11 03:04:21.915147 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/04/11 03:04:26.934125 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:26.934185 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:27.938720 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:27.938855 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:29.947070 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:29.947107 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:31.901589 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=76 registrar.writes=1
2022/04/11 03:04:33.953912 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:33.953975 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:41.966445 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:41.966478 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:57.986681 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:57.986723 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:01.900694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:05:30.006396 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:30.006510 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:31.900791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:06:01.900833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:06:30.022490 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:30.022534 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:31.900737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:07:01.900715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:07:30.041145 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:30.041193 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:31.900778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:08:01.900859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:08:30.056713 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:30.057030 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:31.900742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:09:01.900710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:09:26.936529 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/11 03:09:30.075366 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:30.075410 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:31.900823 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/04/11 03:10:01.900725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:10:30.092925 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:30.092957 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:31.900752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:11:01.900729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:11:30.110661 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:30.110805 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:31.900808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:12:01.900776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:12:30.128168 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:30.128237 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:31.900771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:13:01.900808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:13:30.145521 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:30.145559 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:31.900780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:14:01.900713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:14:30.161472 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:30.161608 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:31.900836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:15:01.900688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:15:30.180989 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:30.181034 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:31.901422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:16:01.900732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:16:30.197720 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:30.197769 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:31.900738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:17:01.900714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:17:30.213996 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:30.214048 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:31.900786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:18:01.900926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:18:30.231608 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:30.231659 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:31.900766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:19:01.900716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:19:30.249512 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:30.249567 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:31.900786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:20:01.900775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:20:30.267126 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:30.267253 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:31.900744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:21:01.900827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:21:30.284657 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:30.284699 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:31.900821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:22:01.900813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:22:30.305226 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:30.305265 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:31.900741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:23:01.900785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:23:30.325004 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:30.325041 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:31.900948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:24:01.900755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:24:30.342150 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:30.342184 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:31.900858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:25:01.900797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:25:30.360056 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:30.360232 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:31.900733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:26:01.900782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:26:30.378747 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:30.378801 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:31.900841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:27:01.900744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:27:30.396059 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:30.396097 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:31.900804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:28:01.900814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:28:30.414396 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:30.414434 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:31.900697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:29:01.900890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:29:30.431404 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:30.431435 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:31.900817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:30:01.900751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:30:30.450742 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:30.450828 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:31.900749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:31:01.900726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:31:30.466823 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:30.466857 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:31.900781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:32:01.900800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:32:30.483193 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:30.483247 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:31.900817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:33:01.900728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:33:30.500284 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:30.500323 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:31.900771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:34:01.900755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:34:30.517650 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:30.517701 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:31.900751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:35:01.900954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:35:30.536169 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:30.536274 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:31.900709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:36:01.900887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:36:30.554845 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:30.554879 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:31.900801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:37:01.900798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:37:30.571843 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:30.571881 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:31.900825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:38:01.900783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:38:30.590218 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:30.590252 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:31.900843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:39:01.900881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/11 03:39:30.607551 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:30.607592 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:31.900794 metrics.go:34: INFO No non-zero metrics in the last 30s