By type
2022/03/12 03:00:35.165705 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/12 03:00:35.165748 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/12 03:00:35.165816 logstash.go:90: INFO Max Retries set to: 3
2022/03/12 03:00:35.165838 metrics.go:23: INFO Metrics logging every 30s
2022/03/12 03:00:35.165872 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/12 03:00:35.166009 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-q84kt
2022/03/12 03:00:35.166203 async.go:63: INFO Flush Interval set to: 1s
2022/03/12 03:00:35.166219 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/12 03:00:35.166758 beat.go:221: INFO filebeat start running.
2022/03/12 03:00:35.166853 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/12 03:00:35.172543 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/12 03:00:35.172642 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/12 03:00:35.172701 crawler.go:38: INFO Loading Prospectors: 1
2022/03/12 03:00:35.172710 registrar.go:236: INFO Starting Registrar
2022/03/12 03:00:35.172765 sync.go:41: INFO Start sending events to output
2022/03/12 03:00:35.172905 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/12 03:00:35.172951 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/12 03:00:35.173053 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/12 03:00:35.173075 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/12 03:00:55.175788 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/12 03:00:55.175943 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/12 03:00:55.176186 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/12 03:00:55.176278 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/12 03:00:55.176344 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/12 03:01:00.192625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:00.192673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:01.197612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:01.197719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:03.202591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:03.202731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:05.166731 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/12 03:01:07.209059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:07.209093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:15.215563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:15.215608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:31.237510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:31.237566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:35.166324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:02:03.255909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:02:03.255958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:02:05.166241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:02:35.166044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:03:03.274768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:03:03.274951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:03:05.166183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:03:35.166090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:04:03.291896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:04:03.291942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:04:05.166141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:04:35.166695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:05:03.311518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:05:03.311556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:05:05.178826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:05:35.166323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:06:00.188660 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/12 03:06:03.328836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:06:03.328894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:06:05.166177 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/12 03:06:35.166174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:07:03.347259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:07:03.347294 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:07:05.166373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:07:35.166316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:08:03.365390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:08:03.365441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:08:05.166239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:08:35.166200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:09:03.381259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:09:03.381297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:09:05.174202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:09:35.166128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:10:03.400371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:10:03.400408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:10:05.166103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:10:35.166327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:11:03.420301 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:11:03.420343 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:11:05.166158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:11:35.166185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:12:03.439679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:12:03.439720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:12:05.166112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:12:35.169713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:13:03.456972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:13:03.457010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:13:05.166203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:13:35.166158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:14:03.484324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:14:03.484387 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:14:05.166175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:14:35.166206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:15:03.502942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:15:03.502999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:15:05.166231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:15:35.166158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:16:03.522435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:16:03.522672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:16:05.166889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:16:35.166208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:17:03.541752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:17:03.541795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:17:05.166122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:17:35.166242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:18:03.560510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:18:03.560559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:18:05.166132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:18:35.168165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:19:03.579305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:19:03.579369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:19:05.166163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:19:35.166762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:20:03.597700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:20:03.597745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:20:05.166158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:20:35.172911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:21:03.619683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:21:03.619734 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:21:05.166182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:21:35.166083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:22:03.639040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:22:03.639090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:22:05.166170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:22:35.166809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:23:03.657415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:23:03.657651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:23:05.166146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:23:35.166098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:24:03.677026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:24:03.677219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:24:05.166431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:24:35.166061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:25:03.697924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:25:03.697981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:25:05.166236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:25:35.166146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:26:03.716030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:26:03.716097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:26:05.166165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:26:35.166189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:27:03.733778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:27:03.733872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:27:05.166222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:27:35.166335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:28:03.750647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:28:03.750688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:28:05.166177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:28:35.166124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:29:03.769320 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:29:03.769486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:29:05.166180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:29:35.166154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:30:03.789116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:30:03.789158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:30:05.166297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:30:35.166099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:31:03.810477 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:31:03.810574 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:31:05.168508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:31:35.166226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:32:03.830205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:32:03.830262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:32:05.166180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:32:35.166564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:33:03.848409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:33:03.848447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:33:05.166155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:33:35.166126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:34:03.865782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:34:03.865819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:34:05.166189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:34:35.166143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:35:03.884571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:35:03.884620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:35:05.166155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:35:35.166155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:36:03.903811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:36:03.903868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:36:05.166133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:36:35.166134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:37:03.923080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:37:03.923149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:37:05.166147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:37:35.166293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:38:03.941383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:38:03.941568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:38:05.166218 metrics.go:34: INFO No non-zero metrics in the last 30s