By type
2022/03/09 03:06:18.706069 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/09 03:06:18.706172 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/09 03:06:18.706203 metrics.go:23: INFO Metrics logging every 30s
2022/03/09 03:06:18.706346 logstash.go:90: INFO Max Retries set to: 3
2022/03/09 03:06:18.706505 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/09 03:06:18.706711 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-w7rvv
2022/03/09 03:06:18.707061 async.go:63: INFO Flush Interval set to: 1s
2022/03/09 03:06:18.707178 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/09 03:06:18.707968 beat.go:221: INFO filebeat start running.
2022/03/09 03:06:18.708145 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/09 03:06:18.712935 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/09 03:06:18.713066 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/09 03:06:18.713128 crawler.go:38: INFO Loading Prospectors: 1
2022/03/09 03:06:18.713477 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/09 03:06:18.713659 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/09 03:06:18.713695 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/09 03:06:18.713727 registrar.go:236: INFO Starting Registrar
2022/03/09 03:06:18.713782 sync.go:41: INFO Start sending events to output
2022/03/09 03:06:18.713857 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/09 03:06:38.719682 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/09 03:06:38.719852 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/09 03:06:38.720279 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/09 03:06:38.720382 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/09 03:06:38.720500 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/09 03:06:43.755485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:43.755522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:44.759459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:44.759498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:46.765291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:46.765327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:48.706640 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=70 registrar.writes=1
2022/03/09 03:06:50.773738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:50.773777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:58.781480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:06:58.781535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:14.804351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:14.804419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:18.706741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:07:46.833818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:46.833891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:07:48.706684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:08:18.706747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:08:46.854126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:08:46.854195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:08:48.706531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:09:18.706747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:09:46.871265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:09:46.871317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:09:48.706695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:10:18.706734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:10:46.891300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:10:46.891372 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:10:48.706715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:11:18.706616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:11:43.744815 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/09 03:11:46.925265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:11:46.925338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:11:48.706682 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/09 03:12:18.706646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:12:46.951205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:12:46.951251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:12:48.706764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:13:18.706602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:13:46.971578 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:13:46.971642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:13:48.706638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:14:18.706606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:14:46.995013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:14:46.995073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:14:48.706614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:15:18.706601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:15:47.014198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:15:47.014242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:15:48.706638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:16:18.706574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:16:47.049981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:16:47.050036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:16:48.706704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:17:18.706629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:17:47.069364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:17:47.069440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:17:48.706639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:18:18.706620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:18:47.087995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:18:47.088052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:18:48.706528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:19:18.706649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:19:47.110100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:19:47.110167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:19:48.706535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:20:18.713157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:20:47.162313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:20:47.162362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:20:48.706574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:21:18.706719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:21:47.190559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:21:47.190615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:21:48.706976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:22:18.706650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:22:47.215216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:22:47.215293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:22:48.706632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:23:18.706745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:23:47.235682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:23:47.236008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:23:48.706721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:24:18.706681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:24:47.261576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:24:47.261655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:24:48.706690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:25:18.706595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:25:47.286304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:25:47.286369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:25:48.706709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:26:18.706599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:26:47.305523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:26:47.305616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:26:48.706602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:27:18.706579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:27:47.343479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:27:47.343530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:27:48.706651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:28:18.706704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:28:47.375368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:28:47.375445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:28:48.706772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:29:18.707028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:29:47.394876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:29:47.394933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:29:48.706585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:30:18.706828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:30:47.415368 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:30:47.415434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:30:48.706640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:31:18.706684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:31:47.439448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:31:47.439520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:31:48.706776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:32:18.706635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:32:47.463854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:32:47.463905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:32:48.706654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:33:18.706809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:33:47.492395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:33:47.492461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:33:48.706591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:34:18.706661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:34:47.512721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:34:47.512775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:34:48.706691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:35:18.706588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:35:47.560689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:35:47.560753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:35:48.706632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:36:18.706642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:36:47.583375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:36:47.583443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:36:48.706572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:37:18.706618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:37:47.624067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:37:47.624150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:37:48.706964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:38:18.706768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:38:47.645518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:38:47.645573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:38:48.706586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:39:18.706670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:39:47.664200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:39:47.664260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:39:48.706579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:40:18.706635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:40:47.683456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:40:47.683537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:40:48.706676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:41:18.706673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:41:47.703248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:41:47.703329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:41:48.706522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:42:18.706623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:42:47.725093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:42:47.725139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:42:48.706584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:43:18.706681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:43:47.753435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:43:47.753502 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 03:43:48.706734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 03:44:18.706796 metrics.go:34: INFO No non-zero metrics in the last 30s