Results

          2022/03/15 02:59:51.133192 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/15 02:59:51.133273 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/15 02:59:51.133401 logstash.go:90: INFO Max Retries set to: 3
2022/03/15 02:59:51.133492 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/15 02:59:51.133512 metrics.go:23: INFO Metrics logging every 30s
2022/03/15 02:59:51.133661 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-89z4g
2022/03/15 02:59:51.133946 async.go:63: INFO Flush Interval set to: 1s
2022/03/15 02:59:51.133968 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/15 02:59:51.136623 beat.go:221: INFO filebeat start running.
2022/03/15 02:59:51.136777 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/15 02:59:51.140410 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/15 02:59:51.140482 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/15 02:59:51.140524 crawler.go:38: INFO Loading Prospectors: 1
2022/03/15 02:59:51.140696 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/15 02:59:51.140799 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/15 02:59:51.140813 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/15 02:59:51.140823 registrar.go:236: INFO Starting Registrar
2022/03/15 02:59:51.140843 sync.go:41: INFO Start sending events to output
2022/03/15 02:59:51.140874 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/15 03:00:11.143644 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/15 03:00:11.144398 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/15 03:00:11.144819 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/15 03:00:11.145189 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/15 03:00:11.146509 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/15 03:00:11.167027 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:11.167085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:12.172662 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:12.172703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:14.177393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:14.177443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:18.188394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:18.188547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:21.137240 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=43 registrar.writes=1
2022/03/15 03:00:26.195480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:26.195656 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:42.214248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:42.214297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:00:51.137209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:01:14.243648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:01:14.243700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:01:21.137325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:01:51.133958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:02:14.263957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:02:14.264007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:02:21.137209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:02:51.133900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:03:14.284816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:03:14.284898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:03:21.137467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:03:51.137049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:04:14.304983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:04:14.305245 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:04:21.137354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:04:51.134511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:05:14.325043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:05:14.325096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:05:16.165863 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/15 03:05:16.165916 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/15 03:05:16.165863 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/15 03:05:16.165901 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/15 03:05:21.134049 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/15 03:05:26.166228 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/15 03:05:51.137248 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/15 03:06:14.346401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:06:14.346440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:06:21.136587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:06:51.137261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:07:14.364585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:07:14.364651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:07:21.137280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:07:51.133834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:08:14.385544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:08:14.385591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:08:21.136850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:08:51.137370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:09:14.403395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:09:14.403510 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:09:21.134232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:09:51.137309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:10:14.421552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:10:14.421602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:10:21.141153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:10:51.134406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:11:14.443878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:11:14.444368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:11:21.134747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:11:51.137267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:12:14.464159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:12:14.464220 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:12:21.135563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:12:51.137157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:13:14.488765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:13:14.488812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:13:21.137663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:13:51.134374 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:14:14.513748 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:14:14.513802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:14:21.137230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:14:51.133865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:15:14.531630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:15:14.531665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:15:21.134070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:15:51.137171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:16:14.548803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:16:14.548847 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:16:21.133900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:16:51.133931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:17:14.568098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:17:14.568142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:17:21.134013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:17:51.133898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:18:14.586598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:18:14.586657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:18:21.134056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:18:51.137231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:19:14.610152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:19:14.610210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:19:21.133894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:19:51.133905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:20:14.631139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:20:14.631194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:20:21.133892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:20:51.133848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:21:14.651377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:21:14.651420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:21:21.133947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:21:51.134154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:22:14.670798 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:22:14.670890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:22:21.133909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:22:51.138008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:23:14.690181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:23:14.690223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:23:21.137133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:23:51.134439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:24:14.708528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:24:14.708585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:24:21.137355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:24:51.133827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:25:14.726839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:25:14.726887 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:25:21.134011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:25:51.137234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:26:14.747815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:26:14.747877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:26:21.134074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:26:51.133851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:27:14.767623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:27:14.767677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:27:21.133872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:27:51.137218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:28:14.786987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:28:14.787026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:28:21.133846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:28:51.133849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:29:14.807264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:29:14.807322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:29:21.133865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:29:51.133897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:30:14.826652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:30:14.826703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:30:21.133995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:30:51.134407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:31:14.845415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:31:14.845479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:31:21.133914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:31:51.134059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:32:14.870983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:32:14.871026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:32:21.133920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:32:51.135487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:33:14.893623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:33:14.893708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:33:21.134015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:33:51.134136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:34:14.913165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:34:14.913208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:34:21.140901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:34:51.134769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:35:14.933233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:35:14.933553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:35:21.137274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:35:51.133868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:36:14.953359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:36:14.953402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 03:36:21.134134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 03:36:51.137440 metrics.go:34: INFO No non-zero metrics in the last 30s