2022/03/25 03:03:03.827378 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:03.827432 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/25 03:03:03.827504 metrics.go:23: INFO Metrics logging every 30s
2022/03/25 03:03:03.827508 logstash.go:90: INFO Max Retries set to: 3
2022/03/25 03:03:03.827617 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/25 03:03:03.827751 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-9fmw5
2022/03/25 03:03:03.827968 async.go:63: INFO Flush Interval set to: 1s
2022/03/25 03:03:03.827995 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/25 03:03:03.828421 beat.go:221: INFO filebeat start running.
2022/03/25 03:03:03.828519 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/25 03:03:03.832788 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/25 03:03:03.832876 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/25 03:03:03.832914 crawler.go:38: INFO Loading Prospectors: 1
2022/03/25 03:03:03.832943 registrar.go:236: INFO Starting Registrar
2022/03/25 03:03:03.833188 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/25 03:03:03.833218 sync.go:41: INFO Start sending events to output
2022/03/25 03:03:03.833351 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/25 03:03:03.833358 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/25 03:03:03.833561 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/25 03:03:23.835774 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/25 03:03:23.836020 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/25 03:03:23.836229 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/25 03:03:23.836298 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/25 03:03:23.836394 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/25 03:03:28.852616 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:28.852659 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:29.856421 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:29.856452 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:31.862123 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:31.862153 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:33.827867 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/25 03:03:35.866872 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:35.866900 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:43.873994 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:43.874246 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.898156 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.898229 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:03.827910 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:04:31.915143 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:31.915184 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:33.827827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:03.827787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:05:31.930982 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:31.931018 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:33.827807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:03.827832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:06:31.948022 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:31.948066 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:33.827881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:03.829392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:07:31.965735 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:31.965772 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:33.827821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:03.827892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:08:28.845571 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:08:28.845587 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:08:28.845632 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:08:28.845671 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:08:31.984338 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:31.984369 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:33.827867 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/25 03:08:35.851915 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/25 03:09:03.827847 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/25 03:09:32.001850 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:32.002038 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:09:33.827757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:03.827968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:10:32.017700 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:32.017734 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:33.827809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:03.827761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:11:32.036466 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:32.036498 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:33.827755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:03.827817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:12:32.053276 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:32.053314 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:33.827837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:03.828170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:13:32.072613 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:32.072643 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:33.827849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:03.827775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:14:32.091648 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:32.091696 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:33.827942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:03.827824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:15:32.109752 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:32.109798 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:33.827732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:03.828268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:16:32.127398 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:32.127432 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:33.827784 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:03.830511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:17:32.144434 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:32.144494 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:33.827762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:03.827786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:18:32.162915 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:32.162970 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:33.827877 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:03.827804 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:19:32.179947 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:32.179983 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:33.827868 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:03.827836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:20:32.200401 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:32.200559 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:33.827803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:03.827925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:21:32.221030 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:32.221079 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:33.827819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:03.827872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:22:32.238526 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:32.238565 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:33.827778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:03.827985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:23:32.256742 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:32.256786 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:33.827899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:03.827778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:24:32.278384 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:32.278439 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:33.827791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:03.827825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:25:32.296524 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:32.296553 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:33.827726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:03.827802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:26:32.314224 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:32.314291 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:33.827756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:03.827857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:27:32.333203 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:32.333240 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:33.827849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:03.827843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:28:32.352739 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:32.352878 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:33.827987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:03.827757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:29:32.371171 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:32.371213 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:33.827753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:03.827848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:30:32.390270 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:32.390308 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:33.827863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:03.827889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:31:32.412085 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:32.412135 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:33.827886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:03.828122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:32:32.429915 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:32.430090 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:33.827809 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:03.827761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:33:32.450460 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:32.450507 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:33.827782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:03.827813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:34:32.468518 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:32.468560 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:33.829133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:03.827828 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:35:32.485181 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:32.485219 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:33.827789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:36:03.827778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:36:32.503630 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:32.503673 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:33.827872 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:37:03.827817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:37:32.520572 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:32.520636 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:33.827841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:38:03.828056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:38:32.538411 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:32.538457 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:33.827875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:39:03.827973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:39:32.559570 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:32.559605 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:33.827818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/25 03:40:03.827805 metrics.go:34: INFO No non-zero metrics in the last 30s