Re: Hard Disk is full because of OpenShift Origin

2017-10-31 Thread Sam Padgett
There are some known problems in Docker for Mac where disk usage never decreases that you might be running into: https://github.com/docker/for-mac/issues/371 On Mon, Oct 30, 2017 at 4:06 PM, Graham Dumpleton wrote: > If you don't mind having everything trashed, and aren't

Re: Logging seems to be working, but no logs are collected

2017-10-31 Thread Jeff Cantrill
Please provide additional information, logs, etc or post the output of [1] someplace for review. Additionally, consider reviewing [2]. [1] https://github.com/openshift/origin-aggregated-logging/blob/master/hack/logging-dump.sh [2]

Re: Logging seems to be working, but no logs are collected

2017-10-31 Thread Tim Dudgeon
$ sudo docker info | grep -i log  WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device. Logging Driver: journald WARNING: bridge-nf-call-iptables is disabled WARNING: bridge-nf-call-ip6tables

Re: Logging seems to be working, but no logs are collected

2017-10-31 Thread Tim Dudgeon
Thanks. Those links are useful. It looks to me like its a problem at the fluentd level. This is what I see on on of the fluentd pods: sh-4.2# cat /var/log/es-containers.log.pos cat: /var/log/es-containers.log.pos: No such file or directory sh-4.2# cat /var/log/journal.pos

Re: Logging seems to be working, but no logs are collected

2017-10-31 Thread Rich Megginson
# docker info | grep -i log # journalctl -r -n 1 --show-cursor On 10/31/2017 11:12 AM, Tim Dudgeon wrote: Thanks. Those links are useful. It looks to me like its a problem at the fluentd level. This is what I see on on of the fluentd pods: sh-4.2# cat /var/log/es-containers.log.pos cat:

Re: Logging seems to be working, but no logs are collected

2017-10-31 Thread Rich Megginson
Very strange.  It would appear that fluentd was not able to keep up with the log rate to the journal for such an extent that the fluentd current cursor position was rotated away . . . You can "reset" fluentd by shutting it down, then removing that cursor file.  That will tell fluentd to start

Re: Logging seems to be working, but no logs are collected

2017-10-31 Thread Tim Dudgeon
On 31/10/2017 18:15, Rich Megginson wrote: Very strange.  It would appear that fluentd was not able to keep up with the log rate to the journal for such an extent that the fluentd current cursor position was rotated away . . . That would be strange - the nodes (4 of them) and fluentd have been

Logging seems to be working, but no logs are collected

2017-10-31 Thread Tim Dudgeon
Hi All, I've deployed logging using the ansible installer (v3.6.0) for a fairly simple openshift setup and everything appears to running: NAME   READY STATUS RESTARTS   AGE logging-curator-1-gvh73    1/1   Running 24 3d

Re: Origin 3.6 update master certificate issue

2017-10-31 Thread Marcello Lorenzi
Hi; I can use this approach and remove the passthrough termination with the new re-encrypt termination using the wilcard certificate. The only problem is retrrieve the self signed CA generated by the registry. Marcello On Tue, Oct 31, 2017 at 2:38 AM, Louis Santillan wrote: