By type
2022/03/14 03:03:41.510267 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/14 03:03:41.510345 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/14 03:03:41.510475 logstash.go:90: INFO Max Retries set to: 3
2022/03/14 03:03:41.510618 metrics.go:23: INFO Metrics logging every 30s
2022/03/14 03:03:41.510710 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/14 03:03:41.510881 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-5l2zj
2022/03/14 03:03:41.511199 async.go:63: INFO Flush Interval set to: 1s
2022/03/14 03:03:41.511228 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/14 03:03:41.513856 beat.go:221: INFO filebeat start running.
2022/03/14 03:03:41.514110 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/14 03:03:41.527071 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/14 03:03:41.527236 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/14 03:03:41.527351 crawler.go:38: INFO Loading Prospectors: 1
2022/03/14 03:03:41.527435 registrar.go:236: INFO Starting Registrar
2022/03/14 03:03:41.527562 sync.go:41: INFO Start sending events to output
2022/03/14 03:03:41.527636 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/14 03:03:41.527642 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/14 03:03:41.527803 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/14 03:03:41.527838 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/14 03:04:01.531012 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/14 03:04:01.531212 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/14 03:04:01.531246 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/14 03:04:01.531415 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/14 03:04:01.531442 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/14 03:04:06.542160 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:06.542201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:07.547424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:07.547543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:09.553122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:09.553169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:11.511504 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=70 registrar.writes=1
2022/03/14 03:04:13.576345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:13.576393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:21.594891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:21.594944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:37.607281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:37.607326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:04:41.511151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:05:09.627556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:05:09.627629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:05:11.511621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:05:41.511208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:06:09.637339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:06:09.637385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:06:11.511120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:06:41.511219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:07:09.644236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:07:09.644293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:07:11.511116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:07:41.511197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:08:09.654478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:08:09.654522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:08:11.511633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:08:41.511171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:09:06.551574 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/14 03:09:09.661136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:09:09.661186 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:09:11.511480 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/14 03:09:41.511110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:10:09.672187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:10:09.672248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:10:11.511102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:10:41.511129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:11:09.680773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:11:09.680821 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:11:11.511129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:11:41.511006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:12:09.687867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:12:09.687917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:12:11.511048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:12:41.511120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:13:09.694020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:13:09.694066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:13:11.511188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:13:41.510955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:14:09.701574 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:14:09.701632 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:14:11.511074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:14:41.511170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:15:09.707889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:15:09.707949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:15:11.510941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:15:41.511076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:16:09.724435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:16:09.724479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:16:11.511141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:16:41.511067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:17:09.733479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:17:09.733543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:17:11.511025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:17:41.510990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:18:09.740399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:18:09.740436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:18:11.510977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:18:41.511214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:19:09.749631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:19:09.749665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:19:11.511097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:19:41.511343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:09.761014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:20:09.761083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:20:11.511113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:20:41.511061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:09.776546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:21:09.776584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:21:11.511113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:21:41.510968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:09.782733 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:22:09.782778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:22:11.511036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:22:41.510999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:09.794406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:23:09.794455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:23:11.511010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:23:41.510949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:24:09.801298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:24:09.801342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:24:11.511011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:24:41.511113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:09.814966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:25:09.815035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:25:11.511193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:25:41.511286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:09.821372 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:26:09.821425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:26:11.511085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:26:41.511023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:09.829167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:27:09.829226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:27:11.511142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:27:41.510968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:09.835050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:28:09.835201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:28:11.511109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:28:41.511113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:09.841323 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:29:09.841358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:29:11.510986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:29:41.511196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:09.848135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:30:09.848197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:30:11.511132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:30:41.511040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:09.854280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:31:09.854334 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:31:11.511068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:31:41.511065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:09.859607 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:32:09.859657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:32:11.512764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:32:41.511537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:09.867408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:33:09.867466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:33:11.511046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:33:41.511101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:09.881438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:34:09.881493 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:34:11.511069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:34:41.510985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:09.887659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:35:09.887716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:35:11.511042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:35:41.511024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:09.894177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:36:09.894225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:36:11.511174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:36:41.511636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:09.900016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:37:09.900054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:37:11.511143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:37:41.511020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:09.906960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:38:09.907016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:38:11.511110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:38:41.511086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:09.915199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:39:09.915233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:39:11.511125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:39:41.511112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:09.923385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:40:09.923434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:40:11.511275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:40:41.511141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:09.930068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:41:09.930121 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/14 03:41:11.511024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/14 03:41:41.511036 metrics.go:34: INFO No non-zero metrics in the last 30s