Re: Problem about logging in openshift origin

[Yu Wei]

@Mateus Caruccio

I run the commands you mentioned and did not find any useful information.

It indicated that no pods named logging-es-data-master-lf6al5rb-5.

No event logs found either.


Thanks,

Jared, (韦煜）
Software developer
Interested in open source software, big data, Linux


From: Mateus Caruccio 
Sent: Friday, September 15, 2017 6:19:36 PM
To: Yu Wei
Cc: d...@lists.openshift.redhat.com; users
Subject: Re: Problem about logging in openshift origin

You can look into two places for clues.  The pod's log itself (oc -n logging 
logs -f logging-es-data-master-lf6al5rb-5) and project events (oc -n logging 
get events)

Em 15 de set de 2017 07:10, "Yu Wei" 
> escreveu:

Hi,

I setup OpenShift origin 3.6 cluster successfully and enabled metrics and 
logging.

Metrics worked well and logging didn't worked.

Pod logging-es-data-master-lf6al5rb-5-deploy in logging frequently crashed with 
below logs,

--> Scaling logging-es-data-master-lf6al5rb-5 to 1
--> Waiting up to 10m0s for pods in rc logging-es-data-master-lf6al5rb-5 to 
become ready
error: update acceptor rejected logging-es-data-master-lf6al5rb-5: pods for rc 
"logging-es-data-master-lf6al5rb-5" took longer than 600 seconds to become ready


I didn't find other information. How could I debug such problem?


Thanks,

Jared, (韦煜）
Software developer
Interested in open source software, big data, Linux

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Upgrading Grafana

[Lionel Orellana]

Hi,

I've done 2 upgrades to the metrics system and noticed that Grafana doesn't
get updated.

During the initial installation the Grafana image was pushed to the
Openshift registry as an image stream. Do I have to manually push it again?
Shouldn't this be part of the metrics playbook?

Thanks

Lionel.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: 1.5 Metrics upgrade did nothing to origin-metrics-cassandra

[Lionel Orellana]

For reference I believe the issue was the presence of Ansible @retry files.
The metrics playbook simply stopped after one master and didn't complete
the upgrade. I removed the retry files and cassandra was updated correctly.

On 23 August 2017 at 21:05, Lionel Orellana  wrote:

> Hello
>
> As the last step in upgrading my cluster from 1.4. to 1.5 I ran the
> metrics playbook.
>
> It upgraded origin-metrics-hawkular-metrics and origin-metrics-heapster
> to 1.5.1 but not  origin-metrics-cassandra which is still showing 1.4.1.
> There is a tag in docker hub for it so I was expecting it to be used.
>
> Is this a bug in the playbook? Can I/should I change the cassandra rc to
> use 1.5.1?
> I am planning on upgrading to 3.6 next so maybe that will take care of it?
>
> Thanks
>
> Lionel
>
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users