Re: simple hello world in python keeps crashing how to see why?

2018-05-22 Thread Brian Keyes 
thanks so much , I would be LOST with out the help I am getting here

the oc debug POD_NAME was great but the  oc logs -p podname really told me
what is going on

I am attempting to get just a python example that is long running and
persistent

thanks again ALL!

On Mon, May 21, 2018 at 5:17 PM, Graham Dumpleton 
wrote:

> If that is really your whole application then as soon as the loop
> completes, the container will exit and the pod restarted. If that happens
> quick enough and keeps happening it would go into a fail state. For a
> normal deployment, you need to have an application, such as a WSGI
> application running on a WSGI server, which runs permanently. You wouldn't
> use a normal deployment for a short lived program that exits straight away.
>
> What is it that you are ultimately wanting to do?
>
> Graham
>
> On 22 May 2018, at 7:04 am, Brian Keyes  wrote:
>
> I have an very very simple hello python
>
>
> #start loop
> for x in range(0, 30):
> print ("hello python ")
>
> but every time I run this on openshift it keeps crashing , why , would it
> be best to scale this up so it is on all worker nodes let it crash and ssh
> into the worker node and look at the docker logs ?
>
> it has 2gb of ram allocated so I am not thinking that this is a memory
> issue
>
> any advice ?
> --
> thanks 
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
>


-- 
Brian Keyes
Systems Engineer, Vizuri
703-855-9074(Mobile)
703-464-7030 x8239 (Office)

FOR OFFICIAL USE ONLY: This email and any attachments may contain
information that is privacy and business sensitive.  Inappropriate or
unauthorized disclosure of business and privacy sensitive information may
result in civil and/or criminal penalties as detailed in as amended Privacy
Act of 1974 and DoD 5400.11-R.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: simple hello world in python keeps crashing how to see why?

2018-05-21 Thread Graham Dumpleton 
If that is really your whole application then as soon as the loop completes, 
the container will exit and the pod restarted. If that happens quick enough and 
keeps happening it would go into a fail state. For a normal deployment, you 
need to have an application, such as a WSGI application running on a WSGI 
server, which runs permanently. You wouldn't use a normal deployment for a 
short lived program that exits straight away.

What is it that you are ultimately wanting to do?

Graham

> On 22 May 2018, at 7:04 am, Brian Keyes  wrote:
> 
> I have an very very simple hello python 
> 
> 
> #start loop
> for x in range(0, 30):
> print ("hello python ") 
> 
> 
> but every time I run this on openshift it keeps crashing , why , would it be 
> best to scale this up so it is on all worker nodes let it crash and ssh into 
> the worker node and look at the docker logs ?
> 
> it has 2gb of ram allocated so I am not thinking that this is a memory issue 
> 
> any advice ?
> -- 
> thanks 
> 
> ___
> 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: simple hello world in python keeps crashing how to see why?

2018-05-21 Thread Ben Parees 
On Mon, May 21, 2018 at 5:04 PM, Brian Keyes  wrote:

> I have an very very simple hello python
>
>
> #start loop
> for x in range(0, 30):
> print ("hello python ")
>
> but every time I run this on openshift it keeps crashing , why , would it
> be best to scale this up so it is on all worker nodes let it crash and ssh
> into the worker node and look at the docker logs ?
>

I assume it's not crashing, it's exiting after finishing the loop.
Openshift expects your pod containers to run a long-lived process (if you
don't want it to be long-lived, use Jobs), so if it exists it restarts it
for you.

If you do want to see the logs for a "crashing"(exiting) container, you can
use "oc logs -p podname" to see the "previous" logs for the pod, which will
show you the output from the previous run that "crashed"(exited).




> it has 2gb of ram allocated so I am not thinking that this is a memory
> issue
>
> any advice ?
> --
> thanks 
>
>
> ___
> 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: simple hello world in python keeps crashing how to see why?

2018-05-21 Thread Clayton Coleman 
Find the name of one of your crashing pods and run:

$ oc debug POD_NAME

That'll put you into a copy of that pod at a shell and you can debug
further from there.


On Mon, May 21, 2018 at 5:04 PM, Brian Keyes  wrote:

> I have an very very simple hello python
>
>
> #start loop
> for x in range(0, 30):
> print ("hello python ")
>
> but every time I run this on openshift it keeps crashing , why , would it
> be best to scale this up so it is on all worker nodes let it crash and ssh
> into the worker node and look at the docker logs ?
>
> it has 2gb of ram allocated so I am not thinking that this is a memory
> issue
>
> any advice ?
> --
> thanks 
>
>
> ___
> 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

simple hello world in python keeps crashing how to see why?

2018-05-21 Thread Brian Keyes 
I have an very very simple hello python


#start loop
for x in range(0, 30):
print ("hello python ")

but every time I run this on openshift it keeps crashing , why , would it
be best to scale this up so it is on all worker nodes let it crash and ssh
into the worker node and look at the docker logs ?

it has 2gb of ram allocated so I am not thinking that this is a memory
issue

any advice ?
-- 
thanks 
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users