By type
2022/04/15 03:05:41.244291 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/15 03:05:41.244395 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/15 03:05:41.244464 metrics.go:23: INFO Metrics logging every 30s
2022/04/15 03:05:41.244571 logstash.go:90: INFO Max Retries set to: 3
2022/04/15 03:05:41.244762 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/15 03:05:41.245007 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-fksdq
2022/04/15 03:05:41.245514 async.go:63: INFO Flush Interval set to: 1s
2022/04/15 03:05:41.245552 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/15 03:05:41.246829 beat.go:221: INFO filebeat start running.
2022/04/15 03:05:41.246906 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/15 03:05:41.250994 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/15 03:05:41.251116 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/15 03:05:41.251228 crawler.go:38: INFO Loading Prospectors: 1
2022/04/15 03:05:41.251571 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/15 03:05:41.251772 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/15 03:05:41.251824 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/15 03:05:41.251848 registrar.go:236: INFO Starting Registrar
2022/04/15 03:05:41.251919 sync.go:41: INFO Start sending events to output
2022/04/15 03:05:41.251980 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/15 03:06:01.257273 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/15 03:06:01.258417 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/15 03:06:01.258636 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/15 03:06:01.258860 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/15 03:06:01.259126 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/15 03:06:06.276863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:06.276940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:07.283217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:07.283253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:09.289310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:09.289363 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:11.245042 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 publish.events=2 registrar.states.current=2 registrar.states.update=2 registrar.writes=2
2022/04/15 03:06:13.295817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:13.295852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:21.302070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:21.303243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:37.322265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:37.322355 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:06:41.244872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:07:09.340782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:07:09.340824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:07:11.244877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:07:41.245016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:08:09.359064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:08:09.359107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:08:11.244885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:08:41.244849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:09:09.378865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:09:09.378913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:09:11.244899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:09:41.244824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:10:09.396488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:10:09.396529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:10:11.244926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:10:41.244888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:11:06.275267 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/15 03:11:06.275263 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/15 03:11:06.275259 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/15 03:11:06.275325 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/15 03:11:09.414569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:11:09.414635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:11:11.245252 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/04/15 03:11:16.275764 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/15 03:11:41.244914 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/04/15 03:12:09.432583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:12:09.432619 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:12:11.244856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:12:41.244937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:13:09.451199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:13:09.451256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:13:11.244915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:13:41.244908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:14:09.468510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:14:09.468553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:14:11.244865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:14:41.244842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:15:09.486588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:15:09.486648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:15:11.244914 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:15:41.244853 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:16:09.504446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:16:09.504492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:16:11.244808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:16:41.244857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:17:09.529245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:17:09.529311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:17:11.244890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:17:41.244841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:18:09.547223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:18:09.547273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:18:11.244924 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:18:41.245298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:19:09.566150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:19:09.566197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:19:11.244848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:19:41.244855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:20:09.583117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:20:09.583160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:20:11.245673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:20:41.244878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:21:09.599867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:21:09.599913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:21:11.244935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:21:41.244862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:22:09.618732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:22:09.618776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:22:11.244909 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:22:41.244906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:23:09.637187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:23:09.637482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:23:11.244904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:23:41.244835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:24:09.655270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:24:09.655533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:24:11.244907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:24:41.244864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:25:09.672827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:25:09.672892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:25:11.244854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:25:41.244927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:26:09.690742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:26:09.690785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:26:11.244897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:26:41.244911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:27:09.708066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:27:09.708116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:27:11.244947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:27:41.244865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:28:09.726013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:28:09.726042 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:28:11.244861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:28:41.244840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:29:09.744617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:29:09.744667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:29:11.244908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:29:41.244949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:30:09.764412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:30:09.764452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:30:11.244858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:30:41.244831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:31:09.781222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:31:09.781267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:31:11.244837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:31:41.244951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:32:09.799219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:32:09.799272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:32:11.244896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:32:41.244879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:33:09.820284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:33:09.820348 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:33:11.244859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:33:41.245066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:34:09.838488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:34:09.838553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:34:11.244817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:34:41.244907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:35:09.870858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:35:09.871056 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:35:11.244772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:35:41.244871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:36:09.889144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:36:09.889194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:36:11.244809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:36:41.244814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:37:09.906414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:37:09.906599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:37:11.244871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:37:41.244818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:38:09.926029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:38:09.926074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:38:11.244950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:38:41.244934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:39:09.951268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:39:09.951318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:39:11.244883 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:39:41.244919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:40:09.969555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:40:09.969611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:40:11.244925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:40:41.244867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:41:09.987751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:41:09.987787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/15 03:41:11.244896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/15 03:41:41.244830 metrics.go:34: INFO No non-zero metrics in the last 30s