By type
2022/03/25 03:03:32.630834 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/25 03:03:32.630918 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/25 03:03:32.631100 logstash.go:90: INFO Max Retries set to: 3
2022/03/25 03:03:32.631295 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/25 03:03:32.631431 metrics.go:23: INFO Metrics logging every 30s
2022/03/25 03:03:32.631501 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-m645v
2022/03/25 03:03:32.631800 async.go:63: INFO Flush Interval set to: 1s
2022/03/25 03:03:32.631832 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/25 03:03:32.632338 beat.go:221: INFO filebeat start running.
2022/03/25 03:03:32.632415 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/25 03:03:32.638740 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/25 03:03:32.638820 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/25 03:03:32.638859 crawler.go:38: INFO Loading Prospectors: 1
2022/03/25 03:03:32.639002 registrar.go:236: INFO Starting Registrar
2022/03/25 03:03:32.639076 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/25 03:03:32.639070 sync.go:41: INFO Start sending events to output
2022/03/25 03:03:32.639246 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/25 03:03:32.639342 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/25 03:03:32.639280 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/25 03:03:52.641847 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/25 03:03:52.642010 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/25 03:03:52.642365 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/25 03:03:52.642475 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/25 03:03:52.642637 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/25 03:03:52.664140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:52.664189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:53.669009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:53.669054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:55.673885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:55.674140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:59.687781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:03:59.687824 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:02.632082 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=63 registrar.writes=1
2022/03/25 03:04:07.701627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:07.701666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:23.727076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:23.727154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:32.631766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:04:55.745084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:04:55.745162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:05:02.631838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:32.633622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:55.765224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:05:55.765270 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:06:02.633113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:32.631888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:55.784138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:06:55.784190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:07:02.631814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:32.631798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:55.806392 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:07:55.806451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:02.631738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:32.631735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:55.825605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:55.825651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:08:57.657076 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:09:02.631869 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/25 03:09:32.631831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:09:55.845063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:09:55.845125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:10:02.631848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:32.631797 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:55.864727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:10:55.864775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:11:02.631762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:32.632068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:55.883040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:11:55.883107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:12:02.631753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:32.631683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:57.903666 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:12:57.903718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:13:02.631749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:32.631754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:57.921829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:13:57.921870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:14:02.631812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:32.631794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:57.940918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:14:57.940970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:15:02.631826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:32.632254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:57.959040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:15:57.959092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:16:02.632299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:32.631744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:57.978184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:16:57.978234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:17:02.635384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:32.635345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:57.995771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:17:57.995815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:18:02.631715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:32.631879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:58.015226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:18:58.015709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:19:02.631777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:32.631810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:58.035351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:19:58.035412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:20:02.631729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:32.631725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:58.054415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:20:58.054463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:21:02.631812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:32.631812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:58.073874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:21:58.073932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:22:02.631961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:32.631790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:58.093456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:22:58.093496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:23:02.631806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:32.631866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:58.113960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:23:58.114019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:24:02.631787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:32.632410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:58.137028 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:24:58.137090 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:25:02.631761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:32.631958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:58.159074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:25:58.159179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:26:02.631781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:32.631778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:58.180879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:26:58.181130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:27:02.631810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:32.631904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:58.201855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:27:58.201902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:28:02.631845 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:32.631866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:58.220144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:28:58.220230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:29:02.631778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:32.631724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:58.242051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:29:58.242095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:30:02.631781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:32.631854 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:58.260197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:30:58.260236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:31:02.631798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:32.631763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:58.281339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:31:58.281395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:32:02.631818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:32.631823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:58.301591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:32:58.301783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:33:02.631800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:32.631793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:58.320399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:33:58.320441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:34:02.631724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:32.631712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:58.339691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:34:58.339845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:35:02.631766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:32.631727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:58.367651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:35:58.367713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:36:02.631747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:36:32.632568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:36:58.387066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:36:58.387107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:37:02.631803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:37:32.631819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:37:58.404710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:37:58.404764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:38:02.631756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:38:32.631754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:38:58.424472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:38:58.424529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:39:02.631783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:39:32.631888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:39:58.442277 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:39:58.442315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/25 03:40:02.631846 metrics.go:34: INFO No non-zero metrics in the last 30s