Advertisement
Guest User

Filebeat debug

a guest
Jan 20th, 2017
87
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. 10:45:41.167694 output.go:109: DBG  output worker: publish 1 events
  2. 10:45:41.167734 context.go:93: DBG  forwards msg with attempts=-1
  3. 10:45:41.167792 context.go:98: DBG  message forwarded
  4. 10:45:41.167850 context.go:138: DBG  events from worker worker queue
  5. 10:45:41.167892 sync.go:107: DBG  Try to publish 1 events to logstash with window size 10
  6. 10:45:41.168300 client.go:194: DBG  handle error: write tcp 172.17.0.2:59032-><ip.to.Indexer01>:5000: write: connection reset by peer
  7. 10:45:41.168376 sync.go:78: DBG  0 events out of 1 events sent to logstash. Continue sending
  8. 10:45:41.168413 sync.go:58: DBG  close connection
  9. 10:45:41.168447 client.go:110: DBG  closing
  10. 10:45:41.168562 sync.go:85: ERR Failed to publish events caused by: write tcp 172.17.0.2:59032-><ip.to.Indexer01>:5000: write: connection reset by peer
  11. 10:45:41.168611 sync_worker.go:167: INFO Error publishing events (retrying): write tcp 172.17.0.2:59032-><ip.to.Indexer01>:5000: write: connection reset by peer
  12. 10:45:41.168648 context.go:93: DBG  forwards msg with attempts=-1
  13. 10:45:41.168707 context.go:98: DBG  message forwarded
  14. 10:45:41.169911 context.go:136: DBG  events from retries queue
  15. 10:45:41.169969 sync.go:107: DBG  Try to publish 1 events to logstash with window size 10
  16. 10:45:41.170369 client.go:194: DBG  handle error: write tcp 172.17.0.2:57698-><ip.to.Indexer02>:5000: write: connection reset by peer
  17. 10:45:41.170417 sync.go:78: DBG  0 events out of 1 events sent to logstash. Continue sending
  18. 10:45:41.170456 sync.go:58: DBG  close connection
  19. 10:45:41.170510 client.go:110: DBG  closing
  20. 10:45:41.170568 sync.go:85: ERR Failed to publish events caused by: write tcp 172.17.0.2:57698-><ip.to.Indexer02>:5000: write: connection reset by peer
  21. 10:45:41.170610 sync_worker.go:167: INFO Error publishing events (retrying): write tcp 172.17.0.2:57698-><ip.to.Indexer02>:5000: write: connection reset by peer
  22. 10:45:41.170643 context.go:93: DBG  forwards msg with attempts=-1
  23. 10:45:41.170701 context.go:98: DBG  message forwarded
  24. 10:45:41.170738 context.go:136: DBG  events from retries queue
  25. 10:45:41.170772 sync.go:107: DBG  Try to publish 1 events to logstash with window size 10
  26. 10:45:41.171702 client.go:194: DBG  handle error: read tcp 172.17.0.2:60408-><ip.to.Indexer03>:5000: read: connection reset by peer
  27. 10:45:41.171765 sync.go:78: DBG  0 events out of 1 events sent to logstash. Continue sending
  28. 10:45:41.171799 sync.go:58: DBG  close connection
  29. 10:45:41.171829 client.go:110: DBG  closing
  30. 10:45:41.171913 sync.go:85: ERR Failed to publish events caused by: read tcp 172.17.0.2:60408-><ip.to.Indexer03>:5000: read: connection reset by peer
  31. 10:45:41.171954 sync_worker.go:167: INFO Error publishing events (retrying): read tcp 172.17.0.2:60408-><ip.to.Indexer03>:5000: read: connection reset by peer
  32. 10:45:41.171987 context.go:93: DBG  forwards msg with attempts=-1
  33. 10:45:41.172020 context.go:98: DBG  message forwarded
  34. 10:45:41.172080 context.go:136: DBG  events from retries queue
  35. 10:45:41.172117 sync.go:107: DBG  Try to publish 1 events to logstash with window size 10
  36. 10:45:41.172467 client.go:194: DBG  handle error: write tcp 172.17.0.2:60410-><ip.to.Indexer03>:5000: write: connection reset by peer
  37. 10:45:41.172515 sync.go:78: DBG  0 events out of 1 events sent to logstash. Continue sending
  38. 10:45:41.172571 sync.go:58: DBG  close connection
  39. 10:45:41.172604 client.go:110: DBG  closing
  40. 10:45:41.172658 sync.go:85: ERR Failed to publish events caused by: write tcp 172.17.0.2:60410-><ip.to.Indexer03>:5000: write: connection reset by peer
  41. 10:45:41.172724 sync_worker.go:167: INFO Error publishing events (retrying): write tcp 172.17.0.2:60410-><ip.to.Indexer03>:5000: write: connection reset by peer
  42. 10:45:41.172757 context.go:93: DBG  forwards msg with attempts=-1
  43. 10:45:41.172789 context.go:98: DBG  message forwarded
  44. 10:45:41.172846 context.go:136: DBG  events from retries queue
  45. 10:45:41.172883 sync.go:107: DBG  Try to publish 1 events to logstash with window size 15
  46. 10:45:41.174872 client.go:194: DBG  handle error: read tcp 172.17.0.2:57696-><ip.to.Indexer02>:5000: read: connection reset by peer
  47. 10:45:41.174930 sync.go:78: DBG  0 events out of 1 events sent to logstash. Continue sending
  48. 10:45:41.174966 sync.go:58: DBG  close connection
  49. 10:45:41.174998 client.go:110: DBG  closing
  50. 10:45:41.175081 sync.go:85: ERR Failed to publish events caused by: read tcp 172.17.0.2:57696-><ip.to.Indexer02>:5000: read: connection reset by peer
  51. 10:45:41.175123 sync_worker.go:167: INFO Error publishing events (retrying): read tcp 172.17.0.2:57696-><ip.to.Indexer02>:5000: read: connection reset by peer
  52. 10:45:41.175157 context.go:93: DBG  forwards msg with attempts=-1
  53. 10:45:41.175212 context.go:98: DBG  message forwarded
  54. 10:45:41.175249 context.go:136: DBG  events from retries queue
  55. 10:45:41.175283 sync.go:107: DBG  Try to publish 1 events to logstash with window size 10
  56. 10:45:41.176007 client.go:194: DBG  handle error: read tcp 172.17.0.2:59030-><ip.to.Indexer01>:5000: read: connection reset by peer
  57. 10:45:41.176063 sync.go:78: DBG  0 events out of 1 events sent to logstash. Continue sending
  58. 10:45:41.176098 sync.go:58: DBG  close connection
  59. 10:45:41.176128 client.go:110: DBG  closing
  60. 10:45:41.176206 sync.go:85: ERR Failed to publish events caused by: read tcp 172.17.0.2:59030-><ip.to.Indexer01>:5000: read: connection reset by peer
  61. 10:45:41.176247 sync_worker.go:167: INFO Error publishing events (retrying): read tcp 172.17.0.2:59030-><ip.to.Indexer01>:5000: read: connection reset by peer
  62. 10:45:41.176280 context.go:93: DBG  forwards msg with attempts=-1
  63. 10:45:41.176312 context.go:98: DBG  message forwarded
  64. 10:45:41.294651 prospector.go:137: DBG  Run prospector
  65. 10:45:41.294771 prospector_log.go:71: DBG  Start next scan
  66. 10:45:41.294947 prospector_log.go:201: DBG  Check file for harvesting: /host/var/lib/docker/containers/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c-json.log
  67. 10:45:41.295020 prospector_log.go:236: DBG  Update existing file for harvesting: /host/var/lib/docker/containers/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c-json.log, offset: 11781662
  68. 10:45:41.295059 prospector_log.go:290: DBG  File didnt change: /host/var/lib/docker/containers/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c-json.log
  69. 10:45:41.295094 prospector_log.go:79: DBG  Prospector states cleaned up. Before: 17, After: 17
  70. 10:45:41.947969 log_file.go:84: DBG  End of file reached: /host/var/log/messages; Backoff now.
  71. 10:45:42.167562 spooler.go:89: DBG  Flushing spooler because of timeout. Events flushed: 0
  72. 10:45:42.168891 sync_worker.go:73: DBG  close client (done=false)
  73. 10:45:42.168957 sync.go:58: DBG  close connection
  74. 10:45:42.168993 sync.go:53: DBG  connect
  75. 10:45:42.170870 sync_worker.go:73: DBG  close client (done=false)
  76. 10:45:42.170920 sync.go:58: DBG  close connectio
  77. 10:45:42.170953 sync.go:53: DBG  connect
  78. 10:45:42.172212 sync_worker.go:73: DBG  close client (done=false)
  79. 10:45:42.172265 sync.go:58: DBG  close connection
  80. 10:45:42.172297 sync.go:53: DBG  connect
  81. 10:45:42.172955 sync_worker.go:73: DBG  close client (done=false)
  82. 10:45:42.173004 sync.go:58: DBG  close connection
  83. 10:45:42.173040 sync.go:53: DBG  connect
  84. 10:45:42.175298 sync_worker.go:73: DBG  close client (done=false)
  85. 10:45:42.175350 sync.go:58: DBG  close connection
  86. 10:45:42.175384 sync.go:53: DBG  connect
  87. 10:45:42.176504 sync_worker.go:73: DBG  close client (done=false)
  88. 10:45:42.176553 sync.go:58: DBG  close connection
  89. 10:45:42.176584 sync.go:53: DBG  connect
  90. 10:45:42.251165 context.go:126: DBG  events from retries queue
  91. 10:45:42.251243 sync.go:107: DBG  Try to publish 1 events to logstash with window size 5
  92. 10:45:42.257172 sync.go:78: DBG  1 events out of 1 events sent to logstash. Continue sending
  93. 10:45:42.257235 sync.go:68: DBG  Events sent: 2
  94. 10:45:42.257277 registrar.go:250: DBG  Processing 2 events
  95. 10:45:42.257336 registrar.go:236: DBG  Registrar states cleaned up. Before: 17 , After: 17
  96. 10:45:42.257380 registrar.go:273: DBG  Write registry file: /data/registry
  97. 10:45:42.257607 registrar.go:295: DBG  Registry file updated. 17 states written.
  98. 10:45:42.295328 prospector.go:137: DBG  Run prospector
  99. 10:45:42.295387 prospector_log.go:71: DBG  Start next scan
  100. 10:45:42.295528 prospector_log.go:201: DBG  Check file for harvesting: /host/var/lib/docker/containers/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c-json.log
  101. 10:45:42.295577 prospector_log.go:236: DBG  Update existing file for harvesting: /host/var/lib/docker/containers/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c-json.log, offset: 11781662
  102. 10:45:42.295614 prospector_log.go:290: DBG  File didnt change: /host/var/lib/docker/containers/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c/35e7a4a4d71c32687d2e43d46ef989770dd55ab5327234433df2b9250787982c-json.log
  103. 10:45:42.295673 prospector_log.go:79: DBG  Prospector states cleaned up. Before: 17, After: 17
  104. 10:45:42.948288 log_file.go:84: DBG  End of file reached: /host/var/log/messages; Backoff now.
  105. 10:45:43.167897 spooler.go:89: DBG  Flushing spooler because of timeout. Events flushed: 0
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement