Filebeat connect Logstash 항상 I/O 시간 초과

Question

elasticsearch의 암호를 변경하기 전에 Filebeat가 잘 작동합니다. 그건 그렇고, 나는 도커 - 작성 서비스를 시작하는 데 사용, 여기에 내 파일 비트에 대한 몇 가지 정보입니다. 콘솔 로그 :

filebeat | 2017/05/11 05:21:33.020851 beat.go:285: INFO Home path: [/] Config path: [/] Data path: [//data] Logs path: [//logs] 
filebeat | 2017/05/11 05:21:33.020903 beat.go:186: INFO Setup Beat: 
filebeat; Version: 5.3.0 
filebeat | 2017/05/11 05:21:33.021019 logstash.go:90: INFO Max Retries set to: 3 
filebeat | 2017/05/11 05:21:33.021097 outputs.go:108: INFO Activated 
logstash as output plugin. 
filebeat | 2017/05/11 05:21:33.021908 publish.go:295: INFO Publisher name: fd2f326e51d9 
filebeat | 2017/05/11 05:21:33.022092 async.go:63: INFO Flush Interval set to: 1s 
filebeat | 2017/05/11 05:21:33.022104 async.go:64: INFO Max Bulk Size set to: 2048 
filebeat | 2017/05/11 05:21:33.022220 modules.go:93: ERR Not loading modules. Module directory not found: /module 
filebeat | 2017/05/11 05:21:33.022291 beat.go:221: INFO filebeat start running. 
filebeat | 2017/05/11 05:21:33.022334 registrar.go:68: INFO No registry file found under: /data/registry. Creating a new registry file. 
filebeat | 2017/05/11 05:21:33.022570 metrics.go:23: INFO Metrics logging every 30s 
filebeat | 2017/05/11 05:21:33.025878 registrar.go:106: INFO Loading registrar data from /data/registry 
filebeat | 2017/05/11 05:21:33.025918 registrar.go:123: INFO States Loaded from registrar: 0 
filebeat | 2017/05/11 05:21:33.025970 crawler.go:38: INFO Loading Prospectors: 1 
filebeat | 2017/05/11 05:21:33.026119 prospector_log.go:61: INFO Prospector with previous states loaded: 0 
filebeat | 2017/05/11 05:21:33.026278 prospector.go:124: INFO Starting prospector of type: log; id: 5816422928785612348 
filebeat | 2017/05/11 05:21:33.026299 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1 
filebeat | 2017/05/11 05:21:33.026323 registrar.go:236: INFO Starting Registrar 
filebeat | 2017/05/11 05:21:33.026364 sync.go:41: INFO Start sending events to output 
filebeat | 2017/05/11 05:21:33.026394 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s 
filebeat | 2017/05/11 05:21:33.026731 log.go:91: INFO Harvester started for file: /data/logs/biz.log 
filebeat | 2017/05/11 05:22:03.023313 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 
filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.publisher.published_events=98 registrar.writes=1 
filebeat | 2017/05/11 05:22:08.028292 single.go:140: ERR Connecting error publishing events (retrying): dial tcp 47.93.121.126:5044: i/o timeout 
filebeat | 2017/05/11 05:22:33.023370 metrics.go:34: INFO No non-zero metrics in the last 30s 
filebeat | 2017/05/11 05:22:39.028840 single.go:140: ERR Connecting error publishing events (retrying): dial tcp 47.93.121.126:5044: i/o timeout 
filebeat | 2017/05/11 05:23:03.022906 metrics.go:34: INFO No non-zero metrics in the last 30s 
filebeat | 2017/05/11 05:23:11.029517 single.go:140: ERR Connecting error publishing events (retrying): dial tcp 47.93.121.126:5044: i/o timeout 
filebeat | 2017/05/11 05:23:33.023450 metrics.go:34: INFO No non-zero metrics in the last 30s 
filebeat | 2017/05/11 05:23:45.030202 single.go:140: ERR Connecting error publishing events (retrying): dial tcp 47.93.121.126:5044: i/o timeout 
filebeat | 2017/05/11 05:24:03.022864 metrics.go:34: INFO No non-zero metrics in the last 30s 
filebeat | 2017/05/11 05:24:23.030749 single.go:140: ERR Connecting error publishing events (retrying): dial tcp 47.93.121.126:5044: i/o timeout 
filebeat | 2017/05/11 05:24:33.024029 metrics.go:34: INFO No non-zero metrics in the last 30s 
filebeat | 2017/05/11 05:25:03.023338 metrics.go:34: INFO No non-zero metrics in the last 30s 
filebeat | 2017/05/11 05:25:09.031348 single.go:140: ERR Connecting error publishing events (retrying): dial tcp 47.93.121.126:5044: i/o timeout 
filebeat | 2017/05/11 05:25:33.023976 metrics.go:34: INFO No non-zero metrics in the last 30s 
filebeat | 2017/05/11 05:26:03.022900 metrics.go:34: INFO No non-zero metrics in the last 30s 
filebeat | 2017/05/11 05:26:11.032346 single.go:140: ERR Connecting error publishing events (retrying): dial tcp 47.93.121.126:5044: i/o timeout 
filebeat | 2017/05/11 05:26:33.022870 metrics.go:34: INFO No non-zero metrics in the last 30s 

filebeat.yml :

filebeat: 
    prospectors: 
    - 
    paths: 
    - /data/logs/*.log 
    input_type: log 
    document_type: biz-log 
registry_file: /etc/registry/mark 
output: 
    logstash: 
    enabled: true 
    hosts: ["logstash:5044"] 

고정 표시기-compose.yml :

version: '2' 
services: 
filebeat: 
    build: ./ 
    container_name: filebeat 
    restart: always 
    network_mode: "bridge" 
    extra_hosts: 
    - "logstash:47.93.121.126" 
    volumes: 
    - ./conf/filebeat.yml:/filebeat.yml 
    - /mnt/logs/appserver/app/biz:/data/logs 
    - ./registry:/data 

Answer 1

레지스트리 파일을 저장 Filebeat 어디를 추적하는 데 사용하는 상태 및 위치 정보 그것은 마지막 독서였습니다. 그럼 레지스트리 파일을 업데이트하거나 삭제할 수 있습니다

cd /var/lib/filebeat 
sudo mv registry registry.bak 
sudo service filebeat restart