Results

          2022/03/24 02:59:47.791168 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/24 02:59:47.791230 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/24 02:59:47.791317 logstash.go:90: INFO Max Retries set to: 3
2022/03/24 02:59:47.791443 metrics.go:23: INFO Metrics logging every 30s
2022/03/24 02:59:47.791433 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/24 02:59:47.791616 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-jqwbh
2022/03/24 02:59:47.791858 async.go:63: INFO Flush Interval set to: 1s
2022/03/24 02:59:47.791876 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/24 02:59:47.792495 beat.go:221: INFO filebeat start running.
2022/03/24 02:59:47.792566 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/24 02:59:47.801515 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/24 02:59:47.801599 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/24 02:59:47.801641 crawler.go:38: INFO Loading Prospectors: 1
2022/03/24 02:59:47.801876 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/24 02:59:47.801981 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/24 02:59:47.801997 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/24 02:59:47.802010 registrar.go:236: INFO Starting Registrar
2022/03/24 02:59:47.802045 sync.go:41: INFO Start sending events to output
2022/03/24 02:59:47.802083 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/24 03:00:07.804998 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/24 03:00:07.805855 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/24 03:00:07.805976 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/24 03:00:07.806113 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/24 03:00:07.806229 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/24 03:00:12.826048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:12.826102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:13.830875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:13.830905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:15.834150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:15.834182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:17.791857 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=200 publish.events=4 registrar.states.current=4 registrar.states.update=4 registrar.writes=2
2022/03/24 03:00:19.840826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:19.840867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:27.847306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:27.847338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:43.865811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:43.865843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:00:47.791830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:01:15.884674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:01:15.884713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:01:17.791886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:01:47.792206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:02:15.904169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:02:15.904225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:02:17.791758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:02:47.791743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:03:15.929976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:03:15.930026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:03:17.791762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:03:47.791845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:04:15.947764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:04:15.947814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:04:17.792622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:04:47.791759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:05:12.817044 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:05:12.817207 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:05:12.817287 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:05:12.817363 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:05:15.965251 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:05:15.965296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:05:17.791762 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/24 03:05:18.826854 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/24 03:05:47.791748 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/24 03:06:15.983601 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:06:15.983640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:06:17.791777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:06:47.791802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:07:16.001809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:07:16.001845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:07:17.791753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:07:47.791731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:08:16.021094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:08:16.021138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:08:17.791765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:08:47.791777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:09:16.040943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:09:16.040973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:09:17.791778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:09:47.791758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:10:16.058048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:10:16.058082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:10:17.791767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:10:47.791850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:11:16.076915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:11:16.076977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:11:17.791796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:11:47.791833 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:12:16.110302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:12:16.110354 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:12:17.791983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:12:47.791835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:13:16.130313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:13:16.130355 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:13:17.791945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:13:47.791848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:16.148060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:14:16.148101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:14:17.791819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:14:47.791984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:16.165165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:15:16.165207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:15:17.791698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:15:47.791834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:16.182879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:16:16.182928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:16:17.791811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:16:47.791731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:16.200655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:17:16.200694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:17:17.791704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:17:47.791804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:16.219759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:18:16.219800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:18:17.791807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:18:47.791886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:16.236340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:19:16.236377 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:19:17.791751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:19:47.791753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:16.253735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:20:16.253785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:20:17.791890 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:20:47.791741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:16.271404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:21:16.271443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:21:17.791859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:21:47.791806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:16.290016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:22:16.290058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:22:17.791884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:22:47.791854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:16.314273 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:23:16.314321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:23:17.791810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:23:47.791808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:16.331676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:24:16.331718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:24:17.791801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:24:47.791974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:16.348698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:25:16.348735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:25:17.791882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:25:47.791737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:16.367182 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:26:16.367212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:26:17.791812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:26:47.791802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:16.386114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:27:16.386171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:27:17.791918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:27:47.791823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:16.418025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:28:16.418068 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:28:17.791776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:28:47.791772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:16.436212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:29:16.436248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:29:17.791730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:29:47.791827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:16.453550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:30:16.453588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:30:17.791771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:30:47.791827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:16.471846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:31:16.471891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:31:17.791750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:31:47.791738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:16.491454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:32:16.491492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:32:17.791801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:32:47.791808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:16.512256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:33:16.512290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:33:17.791839 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:33:47.791803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:16.538373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:34:16.538439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/24 03:34:17.791771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/24 03:34:47.791769 metrics.go:34: INFO No non-zero metrics in the last 30s