Results

          2022/03/29 03:02:06.796473 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/29 03:02:06.796531 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/29 03:02:06.796660 logstash.go:90: INFO Max Retries set to: 3
2022/03/29 03:02:06.796758 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/29 03:02:06.796904 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-2nmkz
2022/03/29 03:02:06.797123 async.go:63: INFO Flush Interval set to: 1s
2022/03/29 03:02:06.797143 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/29 03:02:06.797576 metrics.go:23: INFO Metrics logging every 30s
2022/03/29 03:02:06.797813 beat.go:221: INFO filebeat start running.
2022/03/29 03:02:06.797935 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/29 03:02:06.802831 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/29 03:02:06.802922 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/29 03:02:06.802956 crawler.go:38: INFO Loading Prospectors: 1
2022/03/29 03:02:06.803035 registrar.go:236: INFO Starting Registrar
2022/03/29 03:02:06.803111 sync.go:41: INFO Start sending events to output
2022/03/29 03:02:06.803160 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/29 03:02:06.803264 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/29 03:02:06.803283 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/29 03:02:06.803329 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/29 03:02:16.804946 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/29 03:02:16.805203 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/29 03:02:16.805538 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/29 03:02:16.805613 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/29 03:02:16.805748 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/29 03:02:21.823930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:21.823985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:22.828102 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:22.828139 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:24.832071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:24.832146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:28.841035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:28.841093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:36.797919 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=59 registrar.writes=1
2022/03/29 03:02:36.847319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:36.847351 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:52.872059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:52.872094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:03:06.797856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:03:24.890540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:03:24.890589 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:03:36.798109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:04:06.797886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:04:24.909704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:04:24.909786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:04:36.797870 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:05:06.797878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:05:24.928275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:05:24.928321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:05:36.797875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:06:06.797847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:06:24.947081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:06:24.947146 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:06:36.797877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:07:06.797851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:07:21.815276 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/29 03:07:24.963711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:07:24.963748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:07:28.836398 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/29 03:07:28.836454 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/29 03:07:28.836425 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/29 03:07:36.797898 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/29 03:07:39.820001 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/29 03:08:06.797865 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/29 03:08:24.985659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:08:24.985693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:08:36.797942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:09:06.797893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:09:25.003236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:09:25.003272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:09:36.797850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:10:06.797821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:10:25.024397 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:10:25.024431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:10:36.797850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:11:06.797965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:11:25.045009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:11:25.045040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:11:36.797955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:12:06.797855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:12:25.063082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:12:25.063124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:12:36.797944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:13:06.797919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:13:25.082850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:13:25.082893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:13:36.797878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:14:06.797850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:14:25.100788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:14:25.100863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:14:36.798339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:15:06.797966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:15:25.123349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:15:25.123396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:15:36.797901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:16:06.797854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:16:25.142930 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:16:25.142975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:16:36.797916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:17:06.797889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:17:27.162508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:17:27.162577 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:17:36.797858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:18:06.797825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:18:27.180542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:18:27.180591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:18:36.797900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:19:06.797844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:19:27.198364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:19:27.198402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:19:36.797849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:20:06.797822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:20:27.219399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:20:27.219429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:20:36.797913 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:21:06.797904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:21:27.238471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:21:27.238506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:21:36.797871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:22:06.797947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:22:27.255015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:22:27.255046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:22:36.797884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:23:06.797932 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:23:27.275845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:23:27.275958 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:23:36.797884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:24:06.797898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:24:27.294661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:24:27.294712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:24:36.797874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:25:06.797884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:25:27.313776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:25:27.313807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:25:36.797965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:26:06.797877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:26:27.331940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:26:27.331995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:26:36.797820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:27:06.797864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:27:27.351566 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:27:27.351635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:27:36.797871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:28:06.797923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:28:27.371324 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:28:27.371357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:28:36.797856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:29:06.797902 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:29:27.389897 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:29:27.389965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:29:36.797895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:30:06.797933 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:30:27.407416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:30:27.407533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:30:36.797888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:31:06.797934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:31:27.428453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:31:27.428484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:31:36.797937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:32:06.797887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:32:27.446725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:32:27.446791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:32:36.797878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:33:06.797977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:33:27.464985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:33:27.465028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:33:36.797907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:34:06.797863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:34:27.483996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:34:27.484052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:34:36.797963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:35:06.797912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:35:27.501900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:35:27.501943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:35:36.797860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:36:06.797893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:36:27.519839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:36:27.519883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:36:36.797815 metrics.go:34: INFO No non-zero metrics in the last 30s