Results

          2022/04/19 10:39:39.979212 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/04/19 10:39:39.979277 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/19 10:39:39.979406 metrics.go:23: INFO Metrics logging every 30s
2022/04/19 10:39:39.979611 logstash.go:90: INFO Max Retries set to: 3
2022/04/19 10:39:39.979713 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/19 10:39:39.979910 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-bt9th
2022/04/19 10:39:39.980312 async.go:63: INFO Flush Interval set to: 1s
2022/04/19 10:39:39.980341 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/19 10:39:39.981219 beat.go:221: INFO filebeat start running.
2022/04/19 10:39:39.981358 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/19 10:39:39.987728 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/19 10:39:39.987807 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/19 10:39:39.987845 crawler.go:38: INFO Loading Prospectors: 1
2022/04/19 10:39:39.988062 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/19 10:39:39.988179 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/19 10:39:39.988201 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/19 10:39:39.988213 registrar.go:236: INFO Starting Registrar
2022/04/19 10:39:39.988250 sync.go:41: INFO Start sending events to output
2022/04/19 10:39:39.988299 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/19 10:39:39.989137 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/19 10:39:39.989279 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/19 10:39:39.989499 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/19 10:39:39.989517 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/19 10:39:39.989613 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/19 10:39:45.014008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:39:45.014289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:39:46.020151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:39:46.020185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:39:48.025119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:39:48.025163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:39:52.032881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:39:52.033057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:40:00.042070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:40:00.042104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:40:09.987343 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=356 registrar.writes=1
2022/04/19 10:40:16.064743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:40:16.064799 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:40:39.979958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:40:48.089267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:40:48.089317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:41:09.979870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:41:39.979757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:41:48.107866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:41:48.107919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:42:09.979763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:42:39.979759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:42:48.125908 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:42:48.125975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:43:09.983297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:43:39.979734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:43:48.145329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:43:48.145389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:44:09.979846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:44:39.979792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:44:45.013841 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/19 10:44:45.013898 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/19 10:44:45.013841 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/19 10:44:45.013878 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/19 10:44:45.017868 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/19 10:44:48.164877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:44:48.164922 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:45:09.979767 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=5 filebeat.harvester.open_files=-5 filebeat.harvester.running=-5
2022/04/19 10:45:39.979729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:45:48.189359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:45:48.189398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:46:09.979839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:46:39.979719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:46:48.214735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:46:48.214782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:47:09.979785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:47:39.980734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:47:48.243943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:47:48.244011 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:48:09.979787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:48:39.979776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:48:48.261994 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:48:48.262035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:49:09.984293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:49:39.979813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:49:48.281111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:49:48.281143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:50:09.979814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:50:39.979906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:50:48.301025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:50:48.301075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:51:09.979897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:51:39.979715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:51:48.323102 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:51:48.323146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:52:09.979835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:52:39.979758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:52:48.348814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:52:48.348901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:53:09.979859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:53:39.982155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:53:48.371771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:53:48.371816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:54:09.979803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:54:39.979727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:54:48.390247 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:54:48.390285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:55:09.979726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:55:39.979704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:55:48.410513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:55:48.410554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:56:09.979711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:56:39.979739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:56:48.432488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:56:48.432531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:57:09.979735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:57:39.979668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:57:48.450813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:57:48.450852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:58:09.979842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:58:39.979802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:58:48.469458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:58:48.469501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:59:09.979921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:59:39.979849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 10:59:48.490239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 10:59:48.490285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:00:09.979760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:00:39.979809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:00:48.509307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:00:48.509351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:01:09.979750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:01:39.979737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:01:48.529615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:01:48.529668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:02:09.979749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:02:39.979772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:02:48.549632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:02:48.549786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:03:09.979765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:03:39.979827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:03:48.571687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:03:48.571725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:04:09.979841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:04:39.979759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:04:48.595179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:04:48.595222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:05:09.979692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:05:39.979841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:05:48.616067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:05:48.616103 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:06:09.979757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:06:39.979845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:06:48.637233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:06:48.637269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:07:09.980820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:07:39.979935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:07:48.659945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:07:48.659983 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:08:09.980057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:08:39.979730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:08:48.679426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:08:48.679472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:09:09.979710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:09:39.979750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:09:48.700443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:09:48.700498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:10:09.991219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:10:39.979743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:10:48.722956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:10:48.723018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:11:09.979684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:11:39.979690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:11:48.742819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:11:48.742900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:12:09.979706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:12:39.979726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:12:48.761995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:12:48.762030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:13:09.979754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:13:39.979748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:13:48.780333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:13:48.780458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:14:09.979686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:14:39.979719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:14:48.802089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:14:48.802129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:15:09.979773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:15:39.979766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/19 11:15:48.822092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:15:48.822127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/19 11:16:09.979854 metrics.go:34: INFO No non-zero metrics in the last 30s