Re: 500 Error when pushing to internal registry

2017-09-18 Thread Ben Parees 
On Mon, Sep 18, 2017 at 12:47 PM, Graigry Henrie 
wrote:

> We recently installed openshift origin using an ansible playbook.  We had
> used the same one before without issue, except that now when projects
> attempt to push to the internal registry, it results in a 500 error.
>
> Attached is the log from attempting to build the Django Example project.
> The build itself proceeds perfectly, but fails with a "500 Internal Server
> Error" when attempting to push to the internal registry.  Checking the logs
> of the registry itself only shows health checks, indicating that container
> has come up properly.
>
> What makes it more confusing is that we have installed with this same file
> multiple times and sometimes it works and sometime it doesn't.  We believe
> that it is a permissions issue.  We have checked and rechecked our ansible
> hosts file, but we cannot see what the problem is.  I have included it as
> well.
>

can you try manually pushing to the registry using the service account's
token?  (ie docker login to the registry w/ the token and then tag an
image+push to it).

There is a known issue that the registry returns 500 errors when it should
return 403s, so your theory that it is a permission issue is plausible but
it is strange that some of your clusters work.  When it is not working, it
sounds like it is broken for all projects in the cluster, not just some or
fails randomly?

Adding our registry gurus to CC.



>
> We are happy to include any additional information as needed.
>
> Thank you,
>
> Graigry Henrie
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>


-- 
Ben Parees | OpenShift
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Metrics not accessible

2017-09-18 Thread Mateus Caruccio 
In fact there is
​a
var openshift_hosted_metrics_deployer_version=3.6.0
​ [1]​ but looks like default value "3.6.0" is not being enforced.

[1]
https://github.com/openshift/openshift-ansible/blob/release-3.6/inventory/byo/hosts.origin.example#L561



Em 18 de set de 2017 11:04, "Tim Dudgeon"  escreveu:

> That worked for me too.
> I used web console to look at the hawkular-metrics replication controller
> definition, edited its yaml and changed the image from
> docker.io/openshift/origin-metrics-hawkular-metrics:latest to
> docker.io/openshift/origin-metrics-hawkular-metrics:v3.6.0 and then it
> ran OK.
>
> So what is the best way to deal with this?
>
> My ansible inventory is specifying:
> openshift_release=v3.6
> though the openshift/openshift-ansible repo is checked out from master.
> Does not the openshift_release variable tell the installer to use images
> tagged with v3.6?
>
> Is there a way to specify the right images to use to the ansible installer.
>
> And, presumably this is a bug that should be reported to the issues for
> openshift/openshift-ansible? Happy to do so if someone can confirm.
>
> Tim
>
>
> On 14/09/2017 11:29, Daniel Kučera wrote:
>
>> Thank you! That helped. I was running latest from ansible installation.
>>
>> Changing to v3.6.0 helped and now it runs ok.
>>
>> 2017-09-14 12:11 GMT+02:00 Mateus Caruccio > m>:
>>
>>> Check if you are running the latest version of the images. If that is
>>> your
>>> case change it to v3.6.0 for cassandra, metrics and heapster and restart
>>> all
>>> of them as stated before.
>>>
>>> Ansible always installs the :latest tag of the images by default.
>>>
>>> Em 14 de set de 2017 07:05, "Daniel Kučera" 
>>> escreveu:
>>>
 I'm getting the same error, is there any workaround?


 2017-09-14 09:50:00,572 SEVERE
 [com.google.common.util.concurrent.ExecutionList]
 (cluster3-nio-worker-7) RuntimeException while executing runnable
 rx.observable.ListenableFutureObservable$2$1@54d5c01c with executor

 com.google.common.util.concurrent.MoreExecutors$ListeningDec
 orator@29a43cd3:
 java.util.concurrent.RejectedExecutionException: Task
 rx.observable.ListenableFutureObservable$2$1@54d5c01c rejected from
 java.util.concurrent.ThreadPoolExecutor@2d127c2f[Terminated, pool size
 = 0, active threads = 0, queued tasks = 0, completed tasks = 78]

 --

 S pozdravom / Best regards
 Daniel Kucera.

 ___
 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
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

500 Error when pushing to internal registry

2017-09-18 Thread Graigry Henrie 
We recently installed openshift origin using an ansible playbook.  We had
used the same one before without issue, except that now when projects
attempt to push to the internal registry, it results in a 500 error.

Attached is the log from attempting to build the Django Example project.
The build itself proceeds perfectly, but fails with a "500 Internal Server
Error" when attempting to push to the internal registry.  Checking the logs
of the registry itself only shows health checks, indicating that container
has come up properly.

What makes it more confusing is that we have installed with this same file
multiple times and sometimes it works and sometime it doesn't.  We believe
that it is a permissions issue.  We have checked and rechecked our ansible
hosts file, but we cannot see what the problem is.  I have included it as
well.

We are happy to include any additional information as needed.

Thank you,

Graigry Henrie
Cloning "https://github.com/openshift/django-ex.git; ...
Commit: 30ec0ddd17efc60eaa7b151f7cd2100b7e6ef80a (Merge pull request 
#97 from jim-minter/wait-completion-fixups)
Author: Ben Parees 
Date:   Fri Aug 18 13:22:27 2017 -0400
---> Installing application source ...
---> Installing dependencies ...
Collecting django<1.9,>=1.8 (from -r requirements.txt (line 1))
Downloading Django-1.8.18-py2.py3-none-any.whl (6.2MB)
Collecting django-debug-toolbar==1.5 (from -r requirements.txt (line 2))
Downloading django_debug_toolbar-1.5-py2.py3-none-any.whl (204kB)
Collecting gunicorn==19.4.5 (from -r requirements.txt (line 3))
Downloading gunicorn-19.4.5-py2.py3-none-any.whl (112kB)
Collecting psycopg2==2.6.1 (from -r requirements.txt (line 4))
Downloading psycopg2-2.6.1.tar.gz (371kB)
Collecting whitenoise==3.0 (from -r requirements.txt (line 5))
Downloading whitenoise-3.0-py2.py3-none-any.whl
Collecting sqlparse>=0.2.0 (from django-debug-toolbar==1.5->-r requirements.txt 
(line 2))
Downloading sqlparse-0.2.3-py2.py3-none-any.whl
Installing collected packages: django, sqlparse, django-debug-toolbar, 
gunicorn, psycopg2, whitenoise
Running setup.py install for psycopg2
Successfully installed django-1.8.18 django-debug-toolbar-1.5 gunicorn-19.4.5 
psycopg2-2.6.1 sqlparse-0.2.3 whitenoise-3.0
You are using pip version 7.1.2, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
---> Collecting Django static files ...
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/calendar.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/jquery.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/core.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/actions.min.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/LICENSE-JQUERY.txt'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/collapse.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/timeparse.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/actions.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/jquery.min.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/prepopulate.min.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/urlify.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/related-widget-wrapper.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/SelectFilter2.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/jquery.init.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/inlines.min.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/SelectBox.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/collapse.min.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/prepopulate.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/inlines.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/css/dashboard.css'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/css/ie.css'
Copying 
'/opt/app-root/lib/python3.5/site-packages/django/contrib/admin/static/admin/css/base.css'

Re: DevOps With OpenShift issues on Ubuntu 16.04

2017-09-18 Thread Vyacheslav Semushin 
I agree that it looks like a bug that is Ubuntu-specific. Most of the users
don't run OpenShift on Ubuntu, so bugs are possible. It could be related to
SELinux, for example.

If I were you, I'd try to compare the output of the command oc get pod
cotd-xxx -o yaml on Ubuntu and under Mac. If there won't be some suspicious
differences, then you need to debug deeply. I'd start from checking under
which user a container is running, which privileges it has, what
permissions a file has and so on. I woudn't surprise if it will be a bug in
Kubernetes or Docker itself.

2017-09-18 10:10 GMT+02:00 Benjamin :

> Hi Daniel,
>
> That makes sense, but I'm confused as to why it runs correctly on
> macOS/Mac OS X. Is this a bug in the book?
>


-- 
Slava Semushin | OpenShift
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: [aos-int-services] Problem about logging in openshift origin

2017-09-18 Thread Jeff Cantrill 
The images you reference may not even be the latest 3.6.x version of the
image.  I recommend you rebuild them yourself.

Access to the OCP imags require a valid RedHat subscription.

On Mon, Sep 18, 2017 at 2:24 AM, Yu Wei  wrote:

> Hi Jeff,
>
> The image used is docker.io/openshift/origin-logging-elasticsearch:v3.6.0.
>
> It's fetched from docker hub.
>
> How could I get images from OCP?
>
>
> Thanks,
>
> Jared, (韦煜）
> Software developer
> Interested in open source software, big data, Linux
> --
> *From:* Jeff Cantrill 
> *Sent:* Saturday, September 16, 2017 1:32:19 AM
> *To:* Peter Portante
> *Cc:* Yu Wei; d...@lists.openshift.redhat.com;
> users@lists.openshift.redhat.com; aos-int-services
> *Subject:* Re: [aos-int-services] Problem about logging in openshift
> origin
>
> Can you also post the image Tag you are using?  Is this from an OCP based
> image or upstream images you may find on dockerhub?
>
> On Fri, Sep 15, 2017 at 7:20 AM, Peter Portante 
> wrote:
>
>>
>>
>> On Fri, Sep 15, 2017 at 6:10 AM, Yu Wei  wrote:
>>
>>> 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?
>>>
>> ​Hi Yu,​
>>
>> Added aos-int-services ...
>>
>> ​How many indices do you have in the Elasticsearch instance?
>>
>> What is the storage configuration for the Elasticsearch pods?
>>
>> ​Regards, -peter
>>
>>
>>
>>>
>>> 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
>>>
>>>
>>
>
>
> --
> --
> Jeff Cantrill
> Senior Software Engineer, Red Hat Engineering
> OpenShift Integration Services
> Red Hat, Inc.
> *Office*: 703-748-4420 <(703)%20748-4420> | 866-546-8970 ext. 8162420
> <(866)%20546-8970>
> jcant...@redhat.com
> http://www.redhat.com
>



-- 
--
Jeff Cantrill
Senior Software Engineer, Red Hat Engineering
OpenShift Integration Services
Red Hat, Inc.
*Office*: 703-748-4420 | 866-546-8970 ext. 8162420
jcant...@redhat.com
http://www.redhat.com
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Problem about logging in openshift origin

2017-09-18 Thread Peter Portante 
On Mon, Sep 18, 2017 at 2:33 AM, Yu Wei  wrote:

> Hi Peter,
>
> The storage is EmptyDir for es pods.
>

​How much storage do you have available for each ES pod to use?  ES can
fill TBs of storage if the amount of logging is high enough.

How big are your ES indices?

-peter​

> What's the meaning of aos-int-services? I only enabled logging feature
> during ansible installation.
>
>
> Thanks,
>
> Jared, (韦煜）
> Software developer
> Interested in open source software, big data, Linux
> --
> *From:* Peter Portante 
> *Sent:* Friday, September 15, 2017 7:20:18 PM
> *To:* Yu Wei
> *Cc:* users@lists.openshift.redhat.com; d...@lists.openshift.redhat.com;
> aos-int-services
> *Subject:* Re: Problem about logging in openshift origin
>
>
>
> On Fri, Sep 15, 2017 at 6:10 AM, Yu Wei  wrote:
>
>> 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?
>>
> ​Hi Yu,​
>
> Added aos-int-services ...
>
> ​How many indices do you have in the Elasticsearch instance?
>
> What is the storage configuration for the Elasticsearch pods?
>
> ​Regards, -peter
>
>
>
>>
>> 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

Re: DevOps With OpenShift issues on Ubuntu 16.04

2017-09-18 Thread Benjamin 
Hi Daniel,

That makes sense, but I'm confused as to why it runs correctly on macOS/Mac
OS X. Is this a bug in the book?

Thanks,
~ Benjamin

On Mon, Sep 18, 2017 at 4:05 PM, Daniel Kučera 
wrote:

> Hi Benjamin,
>
> the image you are using probably expects httpd to run under root
> account and this is not permitted by default (because it is a security
> threat).
>
> Read this post to get more info how to enable it:
> https://blog.openshift.com/getting-any-docker-image-
> running-in-your-own-openshift-cluster/
>
> 2017-09-18 8:42 GMT+02:00 Benjamin :
> > Hi there,
> >
> > I am trying to follow the book "DevOps With OpenShift" and having some
> > trouble. When I get to the point of launching the 'cotd' container demo,
> > specifically this line:
> >
> > oc new-app --name='cotd' --labels name='cotd'
> > php~https://github.com/devops-with-openshift/cotd.git -e SELECTOR=cats
> >
> > It appears to spool up and build okay, but then fails in a crash loop:
> >
> > AH00558: httpd: Could not reliably determine the server's fully qualified
> > domain name, using 172.17.0.2. Set the 'ServerName' directive globally to
> > suppress this message
> > (13)Permission denied: AH00058: Error retrieving pid file
> > /opt/rh/httpd24/root/var/run/httpd/httpd.pid
> > AH00059: Remove it before continuing if it is corrupted.
> >
> > I'm running Ubuntu 16.04 64-bit, fully up-to-date including the kernel,
> and
> > using the latest stable oc binary (Origin v3.6.0), and running Docker
> from
> > its official repos. OpenShift itself seems to work great and has no major
> > issues.
> >
> > FWIW I've used this exact same book and exact same commands and
> processes to
> > successfully get the demo up and running on two different Macs, so it
> looks
> > like this is a Ubuntu-specific issue. I would switch to Fedora but my
> > workstation requires Ubuntu for various annoying reasons. I want to get
> this
> > up and running as my workstation has 32GB of RAM which is 2-4x more than
> all
> > my other machines!
> >
> > Version information follows:
> >
> > foo@bar:~$ oc version
> > oc v3.6.0+c4dd4cf
> > kubernetes v1.6.1+5115d708d7
> > features: Basic-Auth GSSAPI Kerberos SPNEGO
> >
> > Server https://127.0.0.1:8443
> > openshift v3.6.0+c4dd4cf
> > kubernetes v1.6.1+5115d708d7
> >
> > foo@bar:~$ docker -v
> > Docker version 17.06.1-ce, build 874a737
> >
> > foo@bar:~$ lsb_release -a
> > No LSB modules are available.
> > Distributor ID: Ubuntu
> > Description: Ubuntu 16.04.3 LTS
> > Release: 16.04
> > Codename: xenial
> >
> > foo@bar:~$ uname -a
> > Linux bar 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017
> > x86_64 x86_64 x86_64 GNU/Linux
> >
> > ___
> > users mailing list
> > users@lists.openshift.redhat.com
> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> >
>
>
>
> --
>
> S pozdravom / Best regards
> Daniel Kucera.
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: DevOps With OpenShift issues on Ubuntu 16.04

2017-09-18 Thread Daniel Kučera 
Hi Benjamin,

the image you are using probably expects httpd to run under root
account and this is not permitted by default (because it is a security
threat).

Read this post to get more info how to enable it:
https://blog.openshift.com/getting-any-docker-image-running-in-your-own-openshift-cluster/

2017-09-18 8:42 GMT+02:00 Benjamin :
> Hi there,
>
> I am trying to follow the book "DevOps With OpenShift" and having some
> trouble. When I get to the point of launching the 'cotd' container demo,
> specifically this line:
>
> oc new-app --name='cotd' --labels name='cotd'
> php~https://github.com/devops-with-openshift/cotd.git -e SELECTOR=cats
>
> It appears to spool up and build okay, but then fails in a crash loop:
>
> AH00558: httpd: Could not reliably determine the server's fully qualified
> domain name, using 172.17.0.2. Set the 'ServerName' directive globally to
> suppress this message
> (13)Permission denied: AH00058: Error retrieving pid file
> /opt/rh/httpd24/root/var/run/httpd/httpd.pid
> AH00059: Remove it before continuing if it is corrupted.
>
> I'm running Ubuntu 16.04 64-bit, fully up-to-date including the kernel, and
> using the latest stable oc binary (Origin v3.6.0), and running Docker from
> its official repos. OpenShift itself seems to work great and has no major
> issues.
>
> FWIW I've used this exact same book and exact same commands and processes to
> successfully get the demo up and running on two different Macs, so it looks
> like this is a Ubuntu-specific issue. I would switch to Fedora but my
> workstation requires Ubuntu for various annoying reasons. I want to get this
> up and running as my workstation has 32GB of RAM which is 2-4x more than all
> my other machines!
>
> Version information follows:
>
> foo@bar:~$ oc version
> oc v3.6.0+c4dd4cf
> kubernetes v1.6.1+5115d708d7
> features: Basic-Auth GSSAPI Kerberos SPNEGO
>
> Server https://127.0.0.1:8443
> openshift v3.6.0+c4dd4cf
> kubernetes v1.6.1+5115d708d7
>
> foo@bar:~$ docker -v
> Docker version 17.06.1-ce, build 874a737
>
> foo@bar:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 16.04.3 LTS
> Release: 16.04
> Codename: xenial
>
> foo@bar:~$ uname -a
> Linux bar 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017
> x86_64 x86_64 x86_64 GNU/Linux
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>



-- 

S pozdravom / Best regards
Daniel Kucera.

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

DevOps With OpenShift issues on Ubuntu 16.04

2017-09-18 Thread Benjamin 
Hi there,

I am trying to follow the book "DevOps With OpenShift" and having some
trouble. When I get to the point of launching the 'cotd' container demo,
specifically this line:

oc new-app --name='cotd' --labels name='cotd' php~https://github.com/devops-
with-openshift/cotd.git -e SELECTOR=cats

It appears to spool up and build okay, but then fails in a crash loop:

AH00558: httpd: Could not reliably determine the server's fully qualified
domain name, using 172.17.0.2. Set the 'ServerName' directive globally to
suppress this message
(13)Permission denied: AH00058: Error retrieving pid file
/opt/rh/httpd24/root/var/run/httpd/httpd.pid
AH00059: Remove it before continuing if it is corrupted.

I'm running Ubuntu 16.04 64-bit, fully up-to-date including the kernel, and
using the latest stable oc binary (Origin v3.6.0), and running Docker from
its official repos. OpenShift itself seems to work great and has no major
issues.

FWIW I've used this exact same book and exact same commands and processes
to successfully get the demo up and running on two different Macs, so it
looks like this is a Ubuntu-specific issue. I would switch to Fedora but my
workstation requires Ubuntu for various annoying reasons. I want to get
this up and running as my workstation has 32GB of RAM which is 2-4x more
than all my other machines!

Version information follows:

foo@bar:~$ oc version
oc v3.6.0+c4dd4cf
kubernetes v1.6.1+5115d708d7
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://127.0.0.1:8443
openshift v3.6.0+c4dd4cf
kubernetes v1.6.1+5115d708d7

foo@bar:~$ docker -v
Docker version 17.06.1-ce, build 874a737

foo@bar:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

foo@bar:~$ uname -a
Linux bar 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Problem about logging in openshift origin

2017-09-18 Thread Yu Wei 
Hi Peter,

The storage is EmptyDir for es pods.

What's the meaning of aos-int-services? I only enabled logging feature during 
ansible installation.


Thanks,

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


From: Peter Portante 
Sent: Friday, September 15, 2017 7:20:18 PM
To: Yu Wei
Cc: users@lists.openshift.redhat.com; d...@lists.openshift.redhat.com; 
aos-int-services
Subject: Re: Problem about logging in openshift origin



On Fri, Sep 15, 2017 at 6:10 AM, Yu Wei 
> wrote:

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?

​Hi Yu,​

Added aos-int-services ...

​How many indices do you have in the Elasticsearch instance?

What is the storage configuration for the Elasticsearch pods?

​Regards, -peter




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