By type
2022/03/10 14:47:24.699203 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/10 14:47:24.699293 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0 2022/03/10 14:47:24.699450 metrics.go:23: INFO Metrics logging every 30s 2022/03/10 14:47:24.699496 logstash.go:90: INFO Max Retries set to: 3 2022/03/10 14:47:24.699592 outputs.go:108: INFO Activated logstash as output plugin. 2022/03/10 14:47:24.699729 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-x5s88 2022/03/10 14:47:24.700010 async.go:63: INFO Flush Interval set to: 1s 2022/03/10 14:47:24.700033 async.go:64: INFO Max Bulk Size set to: 2048 2022/03/10 14:47:24.700586 beat.go:221: INFO filebeat start running. 2022/03/10 14:47:24.700662 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file. 2022/03/10 14:47:24.705228 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry 2022/03/10 14:47:24.705380 registrar.go:123: INFO States Loaded from registrar: 0 2022/03/10 14:47:24.705453 crawler.go:38: INFO Loading Prospectors: 1 2022/03/10 14:47:24.705507 registrar.go:236: INFO Starting Registrar 2022/03/10 14:47:24.705713 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s 2022/03/10 14:47:24.705734 sync.go:41: INFO Start sending events to output 2022/03/10 14:47:24.705887 prospector_log.go:65: INFO Prospector with previous states loaded: 0 2022/03/10 14:47:24.706189 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 2022/03/10 14:47:24.706246 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1 2022/03/10 14:47:44.708978 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log 2022/03/10 14:47:44.709328 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log 2022/03/10 14:47:44.709497 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log 2022/03/10 14:47:44.709576 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log 2022/03/10 14:47:44.709674 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log 2022/03/10 14:47:49.735245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:47:49.735298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:47:50.741879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:47:50.741937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:47:52.751239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:47:52.751365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:47:54.700649 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 registrar.writes=1 2022/03/10 14:47:56.759052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:47:56.759151 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:48:04.767495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:48:04.767672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:48:20.784365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:48:20.784647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:48:24.699958 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:48:52.804457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:48:52.804500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:48:54.699811 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:49:24.699898 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:49:52.825763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:49:52.825829 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:49:54.700140 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:50:24.699773 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:50:52.846212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:50:52.846260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:50:54.699784 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:51:24.699843 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:51:52.867755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:51:52.867878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:51:54.699814 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:52:24.699827 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:52:49.721020 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached. 2022/03/10 14:52:49.721012 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached. 2022/03/10 14:52:49.721039 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached. 2022/03/10 14:52:49.721230 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached. 2022/03/10 14:52:52.889338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:52:52.889393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:52:54.699851 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/10 14:52:59.727401 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached. 2022/03/10 14:53:24.699790 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/10 14:53:52.908907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:53:52.908963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:53:54.699814 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:54:24.699993 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:54:52.927099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:54:52.927138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:54:54.699804 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:55:24.699843 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:55:52.949610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:55:52.949669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:55:54.699859 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:56:24.699812 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:56:52.969041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:56:52.969108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:56:54.699822 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:57:24.699805 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:57:52.987348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:57:52.987391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:57:54.699868 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:58:24.699728 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:58:53.007194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:58:53.007268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:58:54.699949 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:59:24.699747 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 14:59:53.039074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:59:53.039145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 14:59:54.705393 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:00:24.699790 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:00:53.058006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:00:53.058066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:00:54.699828 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:01:24.700429 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:01:53.086857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:01:53.086905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:01:54.702774 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:02:24.699832 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:02:53.105410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:02:53.105456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:02:54.699846 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:03:24.699874 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:03:53.124329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:03:53.124372 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:03:54.699848 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:04:24.700190 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:04:53.141792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:04:53.141856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:04:54.699763 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:05:24.700052 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:05:53.162277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:05:53.162332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:05:54.699794 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:06:24.699926 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:06:53.179361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:06:53.179412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:06:54.699784 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:07:24.700001 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:07:53.198646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:07:53.198690 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:07:54.699844 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:08:24.700031 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:08:53.220283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:08:53.220322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:08:54.699922 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:09:24.699927 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:09:53.238941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:09:53.238998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:09:54.700160 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:10:24.699798 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:10:53.259094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:10:53.259152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:10:54.699799 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:11:24.699768 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:11:53.278763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:11:53.278817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:11:54.699795 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:12:24.699757 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:12:53.297769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:12:53.297810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:12:54.699852 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:13:24.700093 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:13:53.320488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:13:53.320541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:13:54.699845 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:14:24.699845 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:14:53.339058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:14:53.339209 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:14:54.699876 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:15:24.699822 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:15:53.360055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:15:53.360126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:15:54.699890 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:16:24.699745 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:16:53.379359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:16:53.379401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:16:54.699828 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:17:24.699787 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:17:53.399013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:17:53.399058 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:17:54.699806 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:18:24.700058 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:18:53.431191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:18:53.431244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:18:54.699815 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:19:24.699776 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:19:53.449835 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:19:53.449877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:19:54.699737 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:20:24.699840 metrics.go:34: INFO No non-zero metrics in the last 30s 2022/03/10 15:20:53.468803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:20:53.468857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host 2022/03/10 15:20:54.699749 metrics.go:34: INFO No non-zero metrics in the last 30s