By type
2022/03/13 03:04:15.623264 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/13 03:04:15.623412 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/13 03:04:15.623453 metrics.go:23: INFO Metrics logging every 30s
2022/03/13 03:04:15.623619 logstash.go:90: INFO Max Retries set to: 3
2022/03/13 03:04:15.623750 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/13 03:04:15.625459 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-kn7fv
2022/03/13 03:04:15.625903 async.go:63: INFO Flush Interval set to: 1s
2022/03/13 03:04:15.625944 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/13 03:04:15.626841 beat.go:221: INFO filebeat start running.
2022/03/13 03:04:15.627037 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/13 03:04:15.634802 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/13 03:04:15.634940 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/13 03:04:15.635078 crawler.go:38: INFO Loading Prospectors: 1
2022/03/13 03:04:15.635216 sync.go:41: INFO Start sending events to output
2022/03/13 03:04:15.635254 registrar.go:236: INFO Starting Registrar
2022/03/13 03:04:15.635561 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/13 03:04:15.635664 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/13 03:04:15.636111 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/13 03:04:15.636262 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/13 03:04:35.641599 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/13 03:04:35.643379 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/13 03:04:35.643544 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/13 03:04:35.643576 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/13 03:04:35.643559 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/13 03:04:40.670848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:40.670901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:41.679044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:41.679089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:43.690332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:43.690366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:45.623933 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/13 03:04:47.698129 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:47.698164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:55.705340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:04:55.705407 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:11.732371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:11.732433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:15.623970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:05:43.750821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:43.750858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:05:45.624166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:06:15.623807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:06:43.770727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:06:43.770790 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:06:45.623890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:07:15.623881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:07:43.789774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:07:43.789804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:07:45.623803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:08:15.623806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:08:43.815491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:08:43.815535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:08:45.623788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:09:15.623819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:09:40.665688 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:09:43.833588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:09:43.833645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:09:45.623776 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/13 03:10:15.623768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:10:43.852543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:10:43.852593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:10:45.623775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:11:15.623923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:11:43.871910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:11:43.871987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:11:45.625529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:12:15.623831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:12:43.889644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:12:43.889694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:12:45.623785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:13:15.623805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:13:43.908575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:13:43.908615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:13:45.623731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:14:15.623818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:14:43.926187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:14:43.926224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:14:45.624016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:15:15.624208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:15:43.945013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:15:43.945149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:15:45.623842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:16:15.623798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:16:43.963949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:16:43.964003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:16:45.623748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:17:15.623793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:17:43.983836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:17:43.983890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:17:45.623801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:18:15.623775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:18:44.010180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:18:44.010226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:18:45.623870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:19:15.626345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:19:44.030226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:19:44.030269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:19:45.625687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:15.623777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:44.050410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:20:44.050467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:20:45.623832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:15.623844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:44.066150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:21:44.066190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:21:45.623763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:15.623765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:44.084037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:22:44.084085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:22:45.623855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:15.623840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:44.102261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:23:44.102309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:23:45.623814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:24:15.623771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:24:44.121659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:24:44.121697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:24:45.623733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:15.623770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:44.142239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:25:44.142278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:25:45.623797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:15.623826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:44.163071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:26:44.163124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:26:45.623817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:15.623802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:44.180782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:27:44.181203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:27:45.623743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:15.623773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:44.199682 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:28:44.199718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:28:45.623743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:15.623730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:44.216873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:29:44.216910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:29:45.623742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:15.623750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:44.235478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:30:44.235521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:30:45.623852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:15.623778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:44.257040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:31:44.257084 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:31:45.623841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:15.623784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:44.275333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:32:44.275376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:32:45.623788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:15.623785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:44.293261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:33:44.293297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:33:45.623796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:15.623777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:44.311159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:34:44.311205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:34:45.623854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:15.623856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:44.331178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:35:44.331221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:35:45.623783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:15.623738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:44.348741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:36:44.348779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:36:45.623766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:15.623826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:44.367086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:37:44.367139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:37:45.623759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:15.623791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:44.384365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:38:44.384520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:38:45.623970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:15.623832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:44.402322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:39:44.402369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:39:45.623848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:15.623729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:44.421605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:40:44.421649 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:40:45.623746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:15.623707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:44.438725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:41:44.438871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:41:45.627453 metrics.go:34: INFO No non-zero metrics in the last 30s