2022/03/23 03:00:25.798313 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/23 03:00:25.798375 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/23 03:00:25.798471 logstash.go:90: INFO Max Retries set to: 3
2022/03/23 03:00:25.798553 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/23 03:00:25.798690 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-8mz8r
2022/03/23 03:00:25.798841 metrics.go:23: INFO Metrics logging every 30s
2022/03/23 03:00:25.798932 async.go:63: INFO Flush Interval set to: 1s
2022/03/23 03:00:25.798958 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/23 03:00:25.799569 beat.go:221: INFO filebeat start running.
2022/03/23 03:00:25.799666 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/23 03:00:25.807566 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/23 03:00:25.807667 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/23 03:00:25.807722 crawler.go:38: INFO Loading Prospectors: 1
2022/03/23 03:00:25.807784 registrar.go:236: INFO Starting Registrar
2022/03/23 03:00:25.807826 sync.go:41: INFO Start sending events to output
2022/03/23 03:00:25.807981 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/23 03:00:25.808001 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/23 03:00:25.808168 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/23 03:00:25.808195 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/23 03:00:45.810058 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/23 03:00:45.810207 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/23 03:00:45.810327 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/23 03:00:45.810445 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/23 03:00:45.810517 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/23 03:00:50.813606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:00:50.813646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:00:51.817885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:00:51.817937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:00:53.821218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:00:53.821259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:00:55.799467 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/23 03:00:57.828334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:00:57.828493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:05.831805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:05.831835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:21.836999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:21.837047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:25.799180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:01:53.840425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:53.840457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:01:55.799144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:02:25.799195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:02:53.844499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:02:53.844527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:02:55.799149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:03:25.799315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:03:53.848457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:03:53.848503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:03:55.799711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:04:25.799209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:04:53.853356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:04:53.853408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:04:55.799198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:05:25.799196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:05:50.820260 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/23 03:05:50.820320 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/23 03:05:50.820309 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/23 03:05:50.820280 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/23 03:05:53.856762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:05:53.856820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:05:55.799221 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/23 03:05:57.825778 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/23 03:06:25.799349 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/23 03:06:53.859811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:06:53.859850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:06:55.799188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:07:25.799183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:07:53.862915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:07:53.862968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:07:55.799199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:08:25.799103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:08:53.869388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:08:53.869431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:08:55.799281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:09:25.799106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:09:53.877396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:09:53.877438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:09:55.799219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:10:25.799296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:10:53.882271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:10:53.882307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:10:55.800939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:11:25.800986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:11:53.891266 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:11:53.891307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:11:55.799121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:12:25.799236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:12:53.899048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:12:53.899083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:12:55.799092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:13:25.799266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:13:53.902299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:13:53.902528 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:13:55.800956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:14:25.799076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:14:53.906040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:14:53.906169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:14:55.799638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:15:25.800818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:15:53.909506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:15:53.909553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:15:55.799118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:16:25.799160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:16:53.912271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:16:53.912303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:16:55.799140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:17:25.799233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:17:53.916196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:17:53.916232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:17:55.799127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:18:25.799140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:18:53.919784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:18:53.919840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:18:55.799211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:19:25.799202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:19:53.923271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:19:53.923304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:19:55.799163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:20:25.799094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:20:53.929569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:20:53.929613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:20:55.799245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:21:25.799269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:21:53.932750 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:21:53.932876 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:21:55.799191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:22:25.799260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:22:53.936245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:22:53.936298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:22:55.799211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:23:25.799235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:23:53.939516 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:23:53.939548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:23:55.799151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:24:25.799149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:24:53.943416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:24:53.943454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:24:55.799122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:25:25.799219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:25:53.946205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:25:53.946245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:25:55.799296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:26:25.799212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:26:53.949637 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:26:53.949669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:26:55.799153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:27:25.799192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:27:53.953143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:27:53.953179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:27:55.799184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:28:25.799467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:28:53.956525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:28:53.956553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:28:55.799097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:29:25.799380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:29:53.959582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:29:53.959618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:29:55.799209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:30:25.799145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:30:53.962548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:30:53.962595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:30:55.799183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:31:25.799268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:31:53.965484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:31:53.965518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:31:55.799130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:32:25.799170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:32:53.968737 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:32:53.968777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:32:55.799236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:33:25.799336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:33:53.973857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:33:53.973910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:33:55.799324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:34:25.799164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:34:53.978093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:34:53.978144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:34:55.799189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:35:25.799426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:35:53.984968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:35:53.985019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/23 03:35:55.799355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/23 03:36:25.800115 metrics.go:34: INFO No non-zero metrics in the last 30s