By type
2022/04/05 02:57:06.761593 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/05 02:57:06.761662 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/05 02:57:06.761712 metrics.go:23: INFO Metrics logging every 30s
2022/04/05 02:57:06.761789 logstash.go:90: INFO Max Retries set to: 3
2022/04/05 02:57:06.761882 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/05 02:57:06.762062 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-9pt8j
2022/04/05 02:57:06.762391 async.go:63: INFO Flush Interval set to: 1s
2022/04/05 02:57:06.762424 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/05 02:57:06.763044 beat.go:221: INFO filebeat start running.
2022/04/05 02:57:06.763114 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/05 02:57:06.767543 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/05 02:57:06.767624 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/05 02:57:06.767682 crawler.go:38: INFO Loading Prospectors: 1
2022/04/05 02:57:06.767749 sync.go:41: INFO Start sending events to output
2022/04/05 02:57:06.767901 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/05 02:57:06.768123 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/05 02:57:06.768162 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/05 02:57:06.768201 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/05 02:57:06.767865 registrar.go:236: INFO Starting Registrar
2022/04/05 02:57:26.770144 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/04/05 02:57:26.770318 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/04/05 02:57:26.770627 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/04/05 02:57:26.771090 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/04/05 02:57:26.771093 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/04/05 02:57:31.777963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:31.778003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:32.783014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:32.783154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:34.789246 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:34.789298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:36.763886 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=72 registrar.writes=1
2022/04/05 02:57:38.794904 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:38.794954 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:46.808308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:46.808357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:02.814280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:02.814347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:06.762197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 02:58:34.822318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:34.822360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:36.762131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 02:59:06.762174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 02:59:34.835985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:59:34.836049 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:59:36.762336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:00:06.762035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:00:34.842359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:00:34.842395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:00:36.762049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:01:06.762134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:01:34.847880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:01:34.847973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:01:36.762012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:02:06.761979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:02:31.790913 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/05 03:02:34.855984 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:02:34.856025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:02:36.762128 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/04/05 03:03:06.762061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:03:34.862170 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:03:34.862233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:03:36.762149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:04:06.762037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:04:34.868427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:04:34.868474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:04:36.762027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:05:06.762277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:05:34.875988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:05:34.876033 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:05:36.762060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:06:06.762057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:06:34.882500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:06:34.882565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:06:36.762157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:07:06.762141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:07:34.888949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:07:34.888984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:07:36.762051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:08:06.762056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:08:34.894497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:08:34.894539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:08:36.762102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:09:06.762061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:09:34.901100 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:09:34.901149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:09:36.762064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:10:06.761991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:10:34.936810 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:10:34.936846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:10:36.763000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:11:06.762020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:11:34.954901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:11:34.954977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:11:36.762234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:12:06.762177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:12:34.962060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:12:34.962238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:12:36.762025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:13:06.762183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:13:34.967898 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:13:34.967952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:13:36.762006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:14:06.763329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:14:34.977703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:14:34.977752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:14:36.762120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:15:06.762006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:15:34.983267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:15:34.983316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:15:36.762019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:16:06.761979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:16:34.990006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:16:34.990059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:16:36.762081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:17:06.762241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:17:34.996143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:17:34.996206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:17:36.762249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:18:06.762874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:18:35.001816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:18:35.001855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:18:36.762054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:19:06.764177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:19:35.023902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:19:35.023992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:19:36.762044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:20:06.764199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:20:35.032193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:20:35.032356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:20:36.762174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:21:06.762118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:21:35.038279 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:21:35.038335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:21:36.762030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:22:06.762123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:22:35.043876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:22:35.043909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:22:36.762087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:23:06.762135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:23:35.049686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:23:35.049732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:23:36.762090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:24:06.762162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:24:35.055389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:24:35.055429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:24:36.762042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:25:06.761999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:25:35.071427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:25:35.071653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:25:36.762107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:26:06.762065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:26:35.074971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:26:35.075196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:26:36.762140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:27:06.762501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:27:35.079019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:27:35.079193 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:27:36.762076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:28:06.761984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:28:35.082971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:28:35.083007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:28:36.762127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:29:06.762208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:29:35.090501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:29:35.090573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:29:36.762161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:30:06.762067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:30:35.094412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:30:35.094446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:30:36.762077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:31:06.762084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:31:35.098855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:31:35.098896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:31:36.762078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:32:06.762213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:32:35.102549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:32:35.102583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:32:36.762053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:33:06.762022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:33:35.106123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:33:35.106159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:33:36.762101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:34:06.764314 metrics.go:34: INFO No non-zero metrics in the last 30s