October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-221) jps can't see server process in Openshift

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-221?page=com.atlassian.jira.plugin.... ] Jean Francois Denise commented on WFWIP-221: -------------------------------------------- [~jbliznak], did you try to delete /tmp/hsperfdata_jboss (if possible) and start the pod. > jps can't see server process in Openshift > ----------------------------------------- > > Key: WFWIP-221 > URL: https://issues.jboss.org/browse/WFWIP-221 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Critical > > This is somewhat curious issue. > When pod of app image is deployed (server is started) and switch to terminal in Openshift GUI, doing `jps -l` does nothing although I can see in logs that server is up and I can find java process in /proc/*/cmdline (image has no `ps` utility). > This happens only in Openshift environment and it is a regression to what was working with latest published CD image. > Funnily, when I try to run the image in docker and start the server by /opt/eap/bin/openshift-launch.sh, then jps can see the java process. > {code:java} > # this works fine > docker run -it docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... sh > sh-4.4$ /opt/eap/bin/openshift-launch.sh & > sh-4.4$ jps -l > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-187: ------------------------------------ [~jmesnil] I can agree on removal scenario. But what about update scenario? > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-221) jps can't see server process in Openshift

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFWIP-221?page=com.atlassian.jira.plugin.... ] Jan Blizňák edited comment on WFWIP-221 at 10/1/19 11:58 AM: ------------------------------------------------------------- Additional info - jps can't see even itself if that is of any help. I googled this: https://stackoverflow.com/questions/3805376/jps-returns-no-output-even-wh... This led me to test the content of /tmp and indeed there is difference: released CD image 17.0.5: {code:java} $ id uid=1000290000(jboss) gid=0(root) groups=0(root),185(jboss),1000290000 $ ls -lna /tmp total 4 drwxrwxrwt. 1 0 0 30 Oct 1 15:56 . drwxr-xr-x. 1 0 0 58 Oct 1 15:56 .. drwxr-xr-x. 2 1000290000 0 17 Oct 1 15:56 hsperfdata_jboss drwxr-xr-x. 2 0 0 16 Sep 6 14:42 hsperfdata_root -rwx------. 1 0 0 1379 Jul 23 16:18 ks-script-4c1pmxe1 {code} eap-cd-openshift-rhel8:18.0-EAP7-1216: {code:java} $ id uid=1000290000(jboss) gid=0(root) groups=0(root),185(jboss),1000290000 $ $ ls -lna /tmp total 12 drwxrwxrwt. 1 0 0 83 Oct 1 15:36 . drwxr-xr-x. 1 0 0 58 Oct 1 15:35 .. -rw-r--r--. 1 1000290000 0 93 Oct 1 15:35 cli-script-property-1569944155.cli -rw-r--r--. 1 1000290000 0 410 Oct 1 15:35 ds-timer-service-data-store drwxr-xr-x. 2 185 0 6 Sep 30 17:01 hsperfdata_jboss drwxr-xr-x. 2 0 0 16 Sep 30 16:59 hsperfdata_root -rwx------. 1 0 0 1379 Sep 16 12:25 ks-script-mr2oi4id {code} See the difference at hsperfdata_jboss user, maybe that can help. I don't know why jboss user has different. was (Author: jbliznak): Additional info - jps can't see even itself if that is of any help. I googled this: https://stackoverflow.com/questions/3805376/jps-returns-no-output-even-wh... This led me to test the content of /tmp and indeed there is difference: released CD image 17.0.5: {code:java} $ id uid=1000290000(jboss) gid=0(root) groups=0(root),185(jboss),1000290000 $ ls -l /tmp total 4 drwxr-xr-x. 2 jboss root 17 Oct 1 15:23 hsperfdata_jboss drwxr-xr-x. 2 root root 16 Sep 6 14:42 hsperfdata_root -rwx------. 1 root root 1379 Jul 23 16:18 ks-script-4c1pmxe1 {code} eap-cd-openshift-rhel8:18.0-EAP7-1216: {code:java} $ id uid=1000290000(jboss) gid=0(root) groups=0(root),185(jboss),1000290000 $ ls -l /tmp total 12 -rw-r--r--. 1 jboss root 93 Oct 1 15:26 cli-script-property-1569943601.cli -rw-r--r--. 1 jboss root 410 Oct 1 15:26 ds-timer-service-data-store drwxr-xr-x. 2 185 root 6 Sep 30 17:01 hsperfdata_jboss drwxr-xr-x. 2 root root 16 Sep 30 16:59 hsperfdata_root -rwx------. 1 root root 1379 Sep 16 12:25 ks-script-mr2oi4id {code} See the difference at hsperfdata_jboss user, maybe that can help. I don't know why jboss user has different. > jps can't see server process in Openshift > ----------------------------------------- > > Key: WFWIP-221 > URL: https://issues.jboss.org/browse/WFWIP-221 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Critical > > This is somewhat curious issue. > When pod of app image is deployed (server is started) and switch to terminal in Openshift GUI, doing `jps -l` does nothing although I can see in logs that server is up and I can find java process in /proc/*/cmdline (image has no `ps` utility). > This happens only in Openshift environment and it is a regression to what was working with latest published CD image. > Funnily, when I try to run the image in docker and start the server by /opt/eap/bin/openshift-launch.sh, then jps can see the java process. > {code:java} > # this works fine > docker run -it docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... sh > sh-4.4$ /opt/eap/bin/openshift-launch.sh & > sh-4.4$ jps -l > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFWIP-187: ------------------------------ Comment: was deleted (was: [~mchoma] I think this comment ^^ was for WFWIP-211) > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-187: ----------------------------------- [~mchoma] I think this comment ^^ was for WFWIP-211 > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-221) jps can't see server process in Openshift

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFWIP-221?page=com.atlassian.jira.plugin.... ] Jan Blizňák commented on WFWIP-221: ----------------------------------- BTW I don't know if this is the repo for CD image but this looks like something that needs to be done here.. ? https://github.com/jboss-openshift/cct_module/blob/master/jboss/container... > jps can't see server process in Openshift > ----------------------------------------- > > Key: WFWIP-221 > URL: https://issues.jboss.org/browse/WFWIP-221 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Critical > > This is somewhat curious issue. > When pod of app image is deployed (server is started) and switch to terminal in Openshift GUI, doing `jps -l` does nothing although I can see in logs that server is up and I can find java process in /proc/*/cmdline (image has no `ps` utility). > This happens only in Openshift environment and it is a regression to what was working with latest published CD image. > Funnily, when I try to run the image in docker and start the server by /opt/eap/bin/openshift-launch.sh, then jps can see the java process. > {code:java} > # this works fine > docker run -it docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... sh > sh-4.4$ /opt/eap/bin/openshift-launch.sh & > sh-4.4$ jps -l > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-221) jps can't see server process in Openshift

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFWIP-221?page=com.atlassian.jira.plugin.... ] Jan Blizňák edited comment on WFWIP-221 at 10/1/19 11:51 AM: ------------------------------------------------------------- BTW I don't know if this is the correct repo for CD image but this looks like something that needs to be done here.. ? https://github.com/jboss-openshift/cct_module/blob/master/jboss/container... was (Author: jbliznak): BTW I don't know if this is the repo for CD image but this looks like something that needs to be done here.. ? https://github.com/jboss-openshift/cct_module/blob/master/jboss/container... > jps can't see server process in Openshift > ----------------------------------------- > > Key: WFWIP-221 > URL: https://issues.jboss.org/browse/WFWIP-221 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Critical > > This is somewhat curious issue. > When pod of app image is deployed (server is started) and switch to terminal in Openshift GUI, doing `jps -l` does nothing although I can see in logs that server is up and I can find java process in /proc/*/cmdline (image has no `ps` utility). > This happens only in Openshift environment and it is a regression to what was working with latest published CD image. > Funnily, when I try to run the image in docker and start the server by /opt/eap/bin/openshift-launch.sh, then jps can see the java process. > {code:java} > # this works fine > docker run -it docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... sh > sh-4.4$ /opt/eap/bin/openshift-launch.sh & > sh-4.4$ jps -l > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-221) jps can't see server process in Openshift

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFWIP-221?page=com.atlassian.jira.plugin.... ] Jan Blizňák commented on WFWIP-221: ----------------------------------- Additional info - jps can't see even itself if that is of any help. I googled this: https://stackoverflow.com/questions/3805376/jps-returns-no-output-even-wh... This led me to test the content of /tmp and indeed there is difference: released CD image 17.0.5: {code:java} $ id uid=1000290000(jboss) gid=0(root) groups=0(root),185(jboss),1000290000 $ ls -l /tmp total 4 drwxr-xr-x. 2 jboss root 17 Oct 1 15:23 hsperfdata_jboss drwxr-xr-x. 2 root root 16 Sep 6 14:42 hsperfdata_root -rwx------. 1 root root 1379 Jul 23 16:18 ks-script-4c1pmxe1 {code} eap-cd-openshift-rhel8:18.0-EAP7-1216: {code:java} $ id uid=1000290000(jboss) gid=0(root) groups=0(root),185(jboss),1000290000 $ ls -l /tmp total 12 -rw-r--r--. 1 jboss root 93 Oct 1 15:26 cli-script-property-1569943601.cli -rw-r--r--. 1 jboss root 410 Oct 1 15:26 ds-timer-service-data-store drwxr-xr-x. 2 185 root 6 Sep 30 17:01 hsperfdata_jboss drwxr-xr-x. 2 root root 16 Sep 30 16:59 hsperfdata_root -rwx------. 1 root root 1379 Sep 16 12:25 ks-script-mr2oi4id {code} See the difference at hsperfdata_jboss user, maybe that can help. I don't know why jboss user has different. > jps can't see server process in Openshift > ----------------------------------------- > > Key: WFWIP-221 > URL: https://issues.jboss.org/browse/WFWIP-221 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Critical > > This is somewhat curious issue. > When pod of app image is deployed (server is started) and switch to terminal in Openshift GUI, doing `jps -l` does nothing although I can see in logs that server is up and I can find java process in /proc/*/cmdline (image has no `ps` utility). > This happens only in Openshift environment and it is a regression to what was working with latest published CD image. > Funnily, when I try to run the image in docker and start the server by /opt/eap/bin/openshift-launch.sh, then jps can see the java process. > {code:java} > # this works fine > docker run -it docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... sh > sh-4.4$ /opt/eap/bin/openshift-launch.sh & > sh-4.4$ jps -l > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-211) emptyDir.sizeLimit not propagated to Pod Spec

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-211?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-211: ------------------------------------ It is really ignored. I am trying on OpenShift with wildfly-operator. If I add `sizeLimit: 2Mi` directly to StatefulSet it is throw away on Save. This behaves the same if I add any unknow parameter e.g. `a: b` I will create OpenShift issue for that to be explained. > emptyDir.sizeLimit not propagated to Pod Spec > --------------------------------------------- > > Key: WFWIP-211 > URL: https://issues.jboss.org/browse/WFWIP-211 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > # {code:yaml} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > name: operator-empty-dir > namespace: mchoma > spec: > applicationImage: 'registry.access.redhat.com/jboss-eap-7/eap72-openshift:1.1' > size: 1 > storage: > emptyDir: > medium: Memory > sizeLimit: 1Mi > {code} > # wait until pod are started and look into pod yaml definition "1 Mi" is not there > {code:yaml} > ... > serviceAccount: default > serviceAccountName: default > subdomain: operator-empty-dir-headless > terminationGracePeriodSeconds: 30 > volumes: > - emptyDir: > medium: Memory > name: operator-empty-dir-volume > - name: default-token-j2grg > secret: > defaultMode: 420 > secretName: default-token-j2grg > status: > conditions: > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFWIP-187: ------------------------------- Comment: was deleted (was: It is really ignored. I am trying on OpenShift with wildfly-operator. If I add `sizeLimit: 2Mi` directly to StatefulSet it is throw away on Save. This behaves the same if I add any unknow parameter e.g. `a: b` I will create OpenShift issue for that to be explained.) > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019