Error in Docs Installation #50
-
|
When installing Docs I receive the following Ansible error : TASK [docs : Run the Docs Conversion installer] ******************************** The log file conversion_install.log has the message: 2021-01-24 08:58:20,056 INFO server scope is Cluster Will be grateful for you assistance in resolving the problem. The system is set up as the quickstart guide, although DB2 is is running on a separate server and cnx07.campbellreith.com is the Dmgr and WAS server. Many thanks. Michael Lawson |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 12 replies
-
|
Hi Michael, Adding @sabrina-yee as she is more SME on the topc of Docs. Btw. can you just try to rerun it? I did see that 'broken pipe' error before, and that mostly means that network connection broke while task was executing (or Ansible decided for whatever reason to break it, can be a hickup anywhere). Sometimes it makes sense to also go and remove the temporary folder and then rerun it again (in your case it is /home/sysadmin/.ansible on the server). Btw. if simply rerunning it doesn't work just update it here, I will ask @sabrina-yee tomorrow to check it out during our working hours. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @michallawson, Trying to isolate the issue a bit, if you go to the node where you want to install Conversion and run the installer directly (without Ansible): Do you get the same error? |
Beta Was this translation helpful? Give feedback.
-
|
I was seeing that broken pipe so far in two scenarios - one was when whatever network issue happens, and another was when actually disk space issues happen. For SSH, Ansible just keeps the connection, and I would also check if there is enough CPU power and if maybe kernel OOM killer kills the session once memory gets consumed. I am no expert in WAS, but I did see in multiple instances that installation itself uses like 2x RAM of what is actually needed to run the components once the installation is done. |
Beta Was this translation helpful? Give feedback.
-
|
What I observed is that the steps to download and unzip the Docs installers take over a gig of RAM and is not being released. Although my all in one deployment didn't run out of memory, it was cutting thin. If increasing RAM is not possible, as a workaround I'd suggest to comment out the download and extract then do it manually to at least see if my theory checks out. The default location to store the extracted installer is Then run the install again to see if Conversion can be installed. |
Beta Was this translation helpful? Give feedback.
-
|
Actually, we are using unarchive module for this. It is downloading and unpacking the file 'on the fly', and considering that Docs alone is ~800MB, and that it is both downloading and unpacking, I can imagine it is using that amount of memory before it finishes. |
Beta Was this translation helpful? Give feedback.
-
|
I am setting up a test environment to make sure the installation works, so the Dmgr and WAS are located on a single server. This has 32GB of RAM and over 20GB free space on the HDD. From what I have managed to find online I suspect the issue is related to the way Ansible runs the script and is consuming all of the available RAM. |
Beta Was this translation helpful? Give feedback.
-
|
@michallawson do you mind sharing how much RAM you had on that machine where you saw the issues initially, just to try to reproduce that as well, and see if something can be tuned on automation side? |
Beta Was this translation helpful? Give feedback.
-
|
Dejan,
The server has 32GB of Ram and about 20GB of spare capacity on the HDD.
It has coped with the installation of Connections and Customizer so far
without any problems.
I have noticed the shell module is used to run install.sh instead of the
command module. Could this have anything to do with it?
This is the first time I have used Ansible, so no expert.
Regards
Michael
If you have received this e-mail in error please immediately notify the sender by email and delete it and any attachments from your system. This email has been sent from CampbellReith, which is the trading name of Campbell Reith Hill LLP, a limited liability partnership registered in England and Wales. Registered number, OC300082. Registered address: 15 Bermondsey Square, London, SE1 3UN. No employee or agent is authorised to conclude any binding agreement(s) on behalf of Campbell Reith Hill LLP with any other party by email unless it is an attachment on headed paper. Opinions, conclusions and other information in this email and any attachments which do not relate to the official business of Campbell Reith Hill LLP are neither given or endorsed by it. Please note that email traffic and content may be monitored.
As this e-mail has been transmitted over a public network the accuracy, completeness and virus status of the transmitted information is not secure and cannot be guaranteed. If verification is required please telephone the sender of the email.
This message has been scanned for malware by Websense. www.websense.com
|
Beta Was this translation helpful? Give feedback.
-
|
Sabrina,
Thank you.
How much ram did you have?
If you have received this e-mail in error please immediately notify the sender by email and delete it and any attachments from your system. This email has been sent from CampbellReith, which is the trading name of Campbell Reith Hill LLP, a limited liability partnership registered in England and Wales. Registered number, OC300082. Registered address: 15 Bermondsey Square, London, SE1 3UN. No employee or agent is authorised to conclude any binding agreement(s) on behalf of Campbell Reith Hill LLP with any other party by email unless it is an attachment on headed paper. Opinions, conclusions and other information in this email and any attachments which do not relate to the official business of Campbell Reith Hill LLP are neither given or endorsed by it. Please note that email traffic and content may be monitored.
As this e-mail has been transmitted over a public network the accuracy, completeness and virus status of the transmitted information is not secure and cannot be guaranteed. If verification is required please telephone the sender of the email.
This message has been scanned for malware by Websense. www.websense.com
|
Beta Was this translation helpful? Give feedback.
-
|
Mine had only 16GB of RAM. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Seems as though it was the wasadmin password which caused the issue. I reset the password and removed the "&" and the scripts are now running correctly. Not sure why that is as the password with the "&" has worked with every part of the installation up until now. Many thanks for your help. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot Michael for letting us know. My guess here would be that it is a combination of & in the password and us using shell module. Shell is used specifically when you want to pass in a raw way to Ansible stuff like in this case variables, and I wouldn't be surprised if there is a bug in Ansible somewhere where it was using & the way bash would interpret it, spinning up processes in memory to the point where there was no enough memory anymore. I will take a look into this and try to sanitise it on our side a bit and try to reproduce then. Cheers, |
Beta Was this translation helpful? Give feedback.
Seems as though it was the wasadmin password which caused the issue. I reset the password and removed the "&" and the scripts are now running correctly. Not sure why that is as the password with the "&" has worked with every part of the installation up until now.
Many thanks for your help.