2022/03/15 02:59:46.942255 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/15 02:59:46.942315 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/15 02:59:46.942488 logstash.go:90: INFO Max Retries set to: 3
2022/03/15 02:59:46.942497 metrics.go:23: INFO Metrics logging every 30s
2022/03/15 02:59:46.942659 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/15 02:59:46.942859 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-k6pm9
2022/03/15 02:59:46.943142 async.go:63: INFO Flush Interval set to: 1s
2022/03/15 02:59:46.943166 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/15 02:59:46.943875 beat.go:221: INFO filebeat start running.
2022/03/15 02:59:46.944119 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/15 02:59:46.947854 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/15 02:59:46.948014 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/15 02:59:46.948116 crawler.go:38: INFO Loading Prospectors: 1
2022/03/15 02:59:46.948316 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/15 02:59:46.948335 sync.go:41: INFO Start sending events to output
2022/03/15 02:59:46.948150 registrar.go:236: INFO Starting Registrar
2022/03/15 02:59:46.948621 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/15 02:59:46.948869 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/15 02:59:46.949008 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/15 03:00:06.951851 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/15 03:00:06.955304 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/15 03:00:06.955405 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/15 03:00:06.955449 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/15 03:00:06.955614 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/15 03:00:11.978080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:11.978152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:12.982024 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:12.982064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:14.992416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:14.992459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:16.943012 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/03/15 03:00:18.999179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:18.999532 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:27.009885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:27.010005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:43.027832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:43.028222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:46.943664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:01:15.043951 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:01:15.043979 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:01:16.942881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:01:46.943896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:02:15.066648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:02:15.066958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:02:16.942933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:02:46.943041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:03:15.084744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:03:15.084787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:03:16.943101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:03:46.942862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:04:15.103336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:04:15.103394 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:04:16.942869 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:04:46.942872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:05:11.967739 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/15 03:05:15.125729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:05:15.125788 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:05:16.942864 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/15 03:05:46.943044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:06:15.144504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:06:15.144562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:06:16.943008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:06:46.943001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:07:15.163219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:07:15.163296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:07:16.942944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:07:46.943171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:08:15.181743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:08:15.181807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:08:16.942978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:08:46.942830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:09:15.199324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:09:15.199404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:09:16.942871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:09:46.942981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:10:15.217539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:10:15.217593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:10:16.943087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:10:46.942882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:11:15.236611 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:11:15.236675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:11:16.942870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:11:46.942798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:12:15.253561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:12:15.253594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:12:16.942883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:12:46.942862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:13:15.273005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:13:15.273070 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:13:16.943004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:13:46.942892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:14:15.291543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:14:15.291614 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:14:16.942863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:14:46.942922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:15:15.311080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:15:15.311129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:15:16.942825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:15:46.942874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:16:15.328315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:16:15.328358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:16:16.942922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:16:46.942916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:17:15.346757 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:17:15.346808 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:17:16.942889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:17:46.943195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:18:15.366573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:18:15.366626 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:18:16.942917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:18:46.942820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:19:15.391547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:19:15.391594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:19:16.942882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:19:46.943165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:20:15.409297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:20:15.409349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:20:16.942858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:20:46.942932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:21:15.427584 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:21:15.427635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:21:16.943078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:21:46.942933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:22:15.445547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:22:15.445602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:22:16.942954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:22:46.942826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:23:15.464836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:23:15.464918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:23:16.942929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:23:46.943674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:24:15.483204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:24:15.483243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:24:16.942960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:24:46.942803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:25:15.502306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:25:15.502435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:25:16.942924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:25:46.943131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:26:15.520852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:26:15.520900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:26:16.942847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:26:46.942949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:27:15.540311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:27:15.540376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:27:16.942978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:27:46.942911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:28:15.558365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:28:15.558406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:28:16.942893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:28:46.942878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:29:15.575299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:29:15.575340 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:29:16.942873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:29:46.942883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:30:15.592928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:30:15.592963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:30:16.942804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:30:46.943882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:31:15.612282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:31:15.612322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:31:16.942914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:31:46.942954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:32:15.632357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:32:15.632420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:32:16.943019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:32:46.942877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:33:15.654710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:33:15.654748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:33:16.942972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:33:46.942935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:34:15.673193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:34:15.673242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:34:16.942921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:34:46.942932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:35:15.691478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:35:15.691558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:35:16.942918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:35:46.942902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:36:15.716696 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:36:15.716877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:36:16.942957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:36:46.942916 metrics.go:34: INFO No non-zero metrics in the last 30s