issue while running manageprofile

[ghost]

Hello,

I have created a container using my own image that contains the instructions to install WAS Base 8.5.5.13 binaries and was sdk install. When I ran manageprofiles command inside that container there is no errors or logs but at the same time the JVM is not getting created .Any idea? We were working with IBM for the past two months for this issue and now they suggested us to create an issue ID here.

[bensonlatibm]

Hi,

What specific manageprofiles command are you trying?

[ghost]

Hi,

This is the command am trying to run.

/opt/app/was/WAS8.5_BASE/bin/manageprofiles.sh -create -debug -profileName WASBASE_JVM1 -startingPort 15000 -profilePath /opt/app/was/WASBASE_JVM1 -templatePath /opt/app/was/WAS8.5_BASE/profileTemplates/default

From: bensonlatibm notifications@github.com Sent: Friday, August 10, 2018 12:36 AM To: WASdev/ci.docker.websphere-traditional ci.docker.websphere-traditional@noreply.github.com Cc: WSAS WSAS@bnymellon.com; Author author@noreply.github.com Subject: Re: [WASdev/ci.docker.websphere-traditional] issue while running manageprofile (#92)

Hi,

What specific manageprofiles command are you trying?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/WASdev/ci.docker.websphere-traditional/issues/92#issuecomment-411863781, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AoR5ITo7N-j2eMcm5xEToqtwVQDQyBJSks5uPIgKgaJpZM4V1V1z.

The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses.

Please refer to https://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. We take our data protection and privacy responsibilities seriously and our privacy notice explains how we collect, use and share personal information in the course of our business activities. It can be accessed at the privacy section of www.bnymellon.com.

[bensonlatibm]

@bnymwas , after looking at this, I am able to reproduce this on my own build.

Can you try the following as a diagnostic step?

ls -al /bin/sh

If that points to /bin/dash, change the link to /bin/sh

e.g. ln -sf /bin/bash /bin/sh

and then retry the manageprofiles command.

Alternatively in the Docker.v855.prereq file, add the following lines before ARG USER=was

RUN echo "dash dash/sh boolean false" | debconf-set-selections RUN DEBIAN_FRONTEND=noninteractive dpkg-reconfigure dash

[ghost]

Hi,

I tried the step which was suggested. Still no luck. And also we are not using the docker file from IBM. We have created one on our own based on the steps from IBM.

Thanks, Vinodhini Vijayakumar TSG – Application Platform and Services - Web Hosting Services and DevOps BNY Mellon Technology Tidel Park, Chennai, India. Office: +1-646-782-2657 Email: Vinodhini.Vijayakumar@bnymellon.commailto:Vinodhini.Vijayakumar@bnymellon.com

From: bensonlatibm notifications@github.com Sent: Wednesday, August 29, 2018 9:34 PM To: WASdev/ci.docker.websphere-traditional ci.docker.websphere-traditional@noreply.github.com Cc: WSAS WSAS@bnymellon.com; Author author@noreply.github.com Subject: Re: [WASdev/ci.docker.websphere-traditional] issue while running manageprofile (#92)

After looking at this, I am able to reproduce this on my own build.

Can you try the following as a diagnostic step?

ls -al /bin/sh

If that points to /bin/dash, change the link to /bin/sh

e.g. ln -sf /bin/bash /bin/sh

and then retry the manageprofiles command.

Alternatively in the Docker.v855.prereq file, add the following lines before ARG USER=was

RUN echo "dash dash/sh boolean false" | debconf-set-selections RUN DEBIAN_FRONTEND=noninteractive dpkg-reconfigure dash

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/WASdev/ci.docker.websphere-traditional/issues/92#issuecomment-417006259, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AoR5Ic9JZi0VZzj8tAEigfBGkJ8phNnNks5uVrtpgaJpZM4V1V1z.

The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses.

Please refer to https://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. We take our data protection and privacy responsibilities seriously and our privacy notice explains how we collect, use and share personal information in the course of our business activities. It can be accessed at the privacy section of www.bnymellon.com.

[arthurdm]

hi @bnymwas - unfortunately we're no longer supporting the Dockerfiles for pre-v9 WAS. Can you please try out the new v9 images?

[shareauto]

@arthurdm I did try with V9 images same as @bnymwas , but I too face the same problem....

[bensonlatibm]

@shareauto, @bnymwas, when I saw this, the Docker container was configured to use the dash shell instead of bash: you can check by running (inside the docker container) ls -al /bin/sh

If that points to /bin/dash, change the link to /bin/sh

To change this to bash instead of dash, run the following inside the docker container. ln -sf /bin/bash /bin/sh

Does that work?

[ghost]

Hi,

Please close this issue and also remove the ids associated to this account ASAP.

Thanks, Vinodhini Vijayakumar

From: bensonlatibm notifications@github.com Sent: Monday, September 23, 2019 11:26 PM To: WASdev/ci.docker.websphere-traditional ci.docker.websphere-traditional@noreply.github.com Cc: WSAS WSAS@bnymellon.com; Mention mention@noreply.github.com Subject: Re: [WASdev/ci.docker.websphere-traditional] issue while running manageprofile (#92)

@shareautohttps://clicktime.symantec.com/3BBwjEUiQfkx2mU3R9zPMoR7Vc?u=https%3A%2F%2Fgithub.com%2Fshareauto, @bnymwashttps://clicktime.symantec.com/33AoxyVHhtnruL7TU8ffdvd7Vc?u=https%3A%2F%2Fgithub.com%2Fbnymwas, when I saw this, the Docker container was configured to use the dash shell instead of bash: you can check by running (inside the docker container) ls -al /bin/sh

If that points to /bin/dash, change the link to /bin/sh

To change this to bash instead of dash, run the following inside the docker container. ln -sf /bin/bash /bin/sh

Does that work?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://clicktime.symantec.com/3GNgTEtzb8iM9CLU3ERe4od7Vc?u=https%3A%2F%2Fgithub.com%2FWASdev%2Fci.docker.websphere-traditional%2Fissues%2F92%3Femail_source%3Dnotifications%26email_token%3DAKCHSIJECUKLQ26HJN37DV3QLD7JPA5CNFSM4FOVLVZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7LW5CQ%23issuecomment-534212234, or mute the threadhttps://clicktime.symantec.com/3Pzxntqa5hnpQd8b7PMY58V7Vc?u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKCHSILNOBB44EM3AHBASI3QLD7JPANCNFSM4FOVLVZQ.

The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses.

Please refer to https://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. We take our data protection and privacy responsibilities seriously and our privacy notice explains how we collect, use and share personal information in the course of our business activities. It can be accessed at the privacy section of www.bnymellon.com.

[leochr]

Closing issue as per the originator's request.