On 3/21/19 2:31 PM, Neale Ferguson wrote:
Are you asking how to erase everything and start over?
- No, just how to get information out of the elasticsearch container to tell me
why it's failing.
Can you share your inventory files with the logging parameters (be sure to redact
On 3/21/19 1:56 PM, Neale Ferguson wrote:
> - So this leads to the question of how to debug the elasticsearch
container not coming up. The console log information in the 1st email came from me
running it manually so I could add the -v option to the elasticsearch command.
Setting the
On 3/21/19 1:41 PM, Neale Ferguson wrote:
elasticsearch 5 is not tech preview in 3.11 - it is fully supported - and
2.x is gone
- Understood. Did that change with the move from 3.10 to 3.11?
Yes
I must've been scanning another host which was running 3.10 to spot those
preview vars.
On 3/21/19 1:33 PM, Neale Ferguson wrote:
On 3/21/19, 15:33, "Neale Ferguson" wrote:
Right. The image is now
https://hub.docker.com/r/openshift/origin-logging-elasticsearch5/tags - there
are similar changes for origin-logging-curator5, origin-logging-kibana5,
On 3/21/19 1:23 PM, Neale Ferguson wrote:
If I want to use the techpreview elasticsearch5 images are there any other
changes I need to make as I am seeing this on startup:
Found index level settings on node level configuration.
Since elasticsearch 5.x index level settings can NOT be set on
https://github.com/openshift/release/pull/2042
On 11/13/18 6:17 AM, devops036 devops036 wrote:
When installing okd 3.11 with the recently made available CentOS PaaS repo (http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/), I can't activate the logging module
On 10/17/18 3:38 AM, Daniel Comnea wrote:
Hi,
We would like to announce that OKD v3.11 rpms are available for testing at [1].
As such we are calling for help from community to start testing and let us know
if there are issues with the rpms and its dependencies.
And in the spirit of
fine.
Thanks!
On Oct 9, 2018, at 10:10 PM, Rich Megginson wrote:
Was this ever fixed? Is this the cause of the website being currently
unresponsive?
On 9/10/18 2:33 PM, Clayton Coleman wrote:
Interesting, might be an HAProxy router bug. Can you file one?
On Mon, Sep 10, 2018 at 3:08 PM
Was this ever fixed? Is this the cause of the website being currently
unresponsive?
On 9/10/18 2:33 PM, Clayton Coleman wrote:
Interesting, might be an HAProxy router bug. Can you file one?
On Mon, Sep 10, 2018 at 3:08 PM Seth Jennings mailto:sjenn...@redhat.com>> wrote:
There is a
Thanks for this! Will follow up in the PRs.
On 08/20/2018 01:47 AM, Alessandro Menti wrote:
Hi Rich And Louis,
Please submit PRs against origin-aggregated-logging and
openshift-ansible. Note that for origin-aggregated-logging we will
require integration testing, which may require the
Please submit PRs against origin-aggregated-logging and
openshift-ansible. Note that for origin-aggregated-logging we will
require integration testing, which may require the installation of kafka
by the test, and some form of documentation i.e. a markdown doc for the
docs/ subdir.
To
On 04/13/2018 09:58 AM, Troy Dawson wrote:
On Fri, Apr 13, 2018 at 8:42 AM, Rich Megginson <rmegg...@redhat.com> wrote:
On 04/13/2018 09:39 AM, Troy Dawson wrote:
On Fri, Apr 13, 2018 at 7:58 AM, Rich Megginson <rmegg...@redhat.com>
wrote:
On 04/12/2018 07:32 AM, Troy Dawson wro
On 04/13/2018 09:39 AM, Troy Dawson wrote:
On Fri, Apr 13, 2018 at 7:58 AM, Rich Megginson <rmegg...@redhat.com> wrote:
On 04/12/2018 07:32 AM, Troy Dawson wrote:
We have origin packages for 3.7.2, 3.8.0 and 3.9.0. We also have the
corresponding openshift-ansible packages. They have be
On 04/12/2018 07:32 AM, Troy Dawson wrote:
We have origin packages for 3.7.2, 3.8.0 and 3.9.0. We also have the
corresponding openshift-ansible packages. They have been put in our
testing repos.
DO NOT USE ORIGIN 3.8.0, IT IS FOR UPGRADE PURPOSES ONLY
These will not be released until
master commit.
Please talk to upstream about doing an alpha5, or rc0, or whatever
they feel is next.
Troy
On Wed, Mar 7, 2018 at 2:33 PM, Rich Megginson <rmegg...@redhat.com> wrote:
The current 3.9 centos paas repos are at v3.9.0-alpha.4. However, I cannot
deploy origin 3.9.0-alpha.4 using
t was used for v3.7.0-rc.0
On Fri, Oct 27, 2017 at 7:15 PM, Rich Megginson <rmegg...@redhat.com
<mailto:rmegg...@redhat.com>> wrote:
What about logging and metrics?
On 10/27/2017 11:09 AM, Clayton Coleman wrote:
v3.6.1 and v3.7.0-rc.0 have been released on GitHub and
ole...@redhat.com> wrote:
We could support setting that on the Kubelet when we launch the
containers. I think it's reasonable - if you open a Kube issue Derek
and I can chime in.
On Fri, May 20, 2016 at 12:12 PM, Rich Megginson <rmegg...@redhat.com> wrote:
When using OpenShift with the standar
When using OpenShift with the standard docker log driver, there are
container logs in the following format:
/var/log/containers/$name_of_pod-$name_of_project-$name_of_container-$containeruuid.log
The fluentd log collector uses $name_of_pod and $name_of_project to look
up in k8s additional
18 matches
Mail list logo
