Troubleshooting “already been bootstrapped” Message on IBM i

Setting up the open source environment on IBM i from Access Client Solutions (ACS) is usually easy, but sometimes you can run into problems. The most common error is when ACS claims that the environment is already set up (“bootstrapped”), when in fact it isn’t. Confusing!

IBM i warning message when the open source installer believes the system has already been bootstrapped

“This system has already been bootstrapped!”

The “system has already been bootstrapped!” message is often caused by an interrupted installation. One way installations get interrupted is when the ACS progress bar does not move, leading people to believe the process got stuck (when it’s actually still downloading). Thus, someone could get impatient and close the process.

ACS checks only for the existence of the RPM database—one small element of the installation—when it displays the “already been bootstrapped” warning. The easiest way to fix it is:

 

  1. Remove the RPM database by deleting the /QOpenSys/var/lib/rpm directory. Then go back to ACS to set up the environment again. If that does not work, try option 2.
  2. When ACS installs the open source environment, it downloads the bootstrap script and archive into /tmp. After it runs it, if the script fails, it tells you the flag to use to forcibly install a new environment. You can run this from a PASE shell like so:
    1. Open a PASE shell through CALL QP2TERM or SSH.
    2. Run cd /tmp
    3. Run ./bootstrap.sh --yes-this-is-unsupported-but-i-know-what-i-am-doing

Once you follow the steps above, the open source environment is set up anew, and you can get to work with it.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.