Logspout sendet alte Docker-Protokolle

306
Applemann

Hallo, ich habe Logspout für das Senden meiner Protokolle vom Docker-Container in Papertrail, aber jetzt habe ich herausgefunden, dass Docker Container Logspout nach dem Neustart auch alle alten Protokolle sendet.
Hier ist ein Beispiel:

Oct 06 15:37:09 gridhub r-Default-gridhub-1-96bd5cd9: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)  Oct 06 15:37:09 gridhub r-Default-gridhub-1-96bd5cd9: 172.30.100.112 - - [03/Oct/2017 12:39:05] "GET / HTTP/1.1" 200 -  Oct 06 15:37:09 gridhub r-Default-gridhub-1-96bd5cd9: 172.30.100.112 - - [03/Oct/2017 12:39:06] "GET /static/favicon.ico HTTP/1.1" 200 -  Oct 06 15:37:09 gridhub r-Default-gridhub-1-96bd5cd9: 172.30.100.112 - - [03/Oct/2017 12:39:06] "GET /static/issue_count_low.png HTTP/1.1" 200 -  Oct 06 15:37:09 gridhub r-Default-gridhub-1-96bd5cd9: 172.30.100.112 - - [03/Oct/2017 12:39:06] "GET /static/issue_count_high.png HTTP/1.1" 200 -  Oct 06 15:37:09 gridhub r-Default-gridhub-1-96bd5cd9: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)  Oct 11 10:21:38 gridhub r-Default-gridhub-1-96bd5cd9: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)  Oct 11 10:21:38 gridhub r-Default-gridhub-1-96bd5cd9: 172.30.100.112 - - [03/Oct/2017 12:39:05] "GET / HTTP/1.1" 200 -  Oct 11 10:21:38 gridhub r-Default-gridhub-1-96bd5cd9: 172.30.100.112 - - [03/Oct/2017 12:39:06] "GET /static/favicon.ico HTTP/1.1" 200 -  Oct 11 10:21:38 gridhub r-Default-gridhub-1-96bd5cd9: 172.30.100.112 - - [03/Oct/2017 12:39:06] "GET /static/issue_count_low.png HTTP/1.1" 200 -  Oct 11 10:21:38 gridhub r-Default-gridhub-1-96bd5cd9: 172.30.100.112 - - [03/Oct/2017 12:39:06] "GET /static/issue_count_high.png HTTP/1.1" 200 -  Oct 11 10:21:38 gridhub r-Default-gridhub-1-96bd5cd9: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)  Oct 11 10:21:38 gridhub r-Default-gridhub-1-96bd5cd9: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)

und im Docker-Container ist nur:

10/3/2017 2:38:50 PM * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit) 10/3/2017 2:39:05 PM172.30.100.112 - - [03/Oct/2017 12:39:05] "GET / HTTP/1.1" 200 - 10/3/2017 2:39:06 PM172.30.100.112 - - [03/Oct/2017 12:39:06] "GET /static/favicon.ico HTTP/1.1" 200 - 10/3/2017 2:39:06 PM172.30.100.112 - - [03/Oct/2017 12:39:06] "GET /static/issue_count_low.png HTTP/1.1" 200 - 10/3/2017 2:39:06 PM172.30.100.112 - - [03/Oct/2017 12:39:06] "GET /static/issue_count_high.png HTTP/1.1" 200 - 10/6/2017 3:37:09 PM * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit) 10/11/2017 10:21:38 AM * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)

Wissen Sie jemand, wie nur letzte Protokolle nach dem Neustart gesendet werden?

0
Ok, endlich habe ich das Problem behoben, indem in der Logspout-Containerumgebung `BACKLOG = false` hinzugefügt wurde. Applemann vor 6 Jahren 0

1 Antwort auf die Frage

0
Applemann

Ok, endlich habe ich das BACKLOG=falseProblem behoben, indem ich es in die Logspout-Containerumgebung einfügte.
Https://github.com/gliderlabs/logspout#suppressing-backlog-tail

Verwandte Probleme