Skip to content
This repository has been archived by the owner on Jul 11, 2022. It is now read-only.

published docker hub image rhqproject/rhq-nodb does not work #5

Open
tarilabs opened this issue Aug 6, 2016 · 0 comments
Open

published docker hub image rhqproject/rhq-nodb does not work #5

tarilabs opened this issue Aug 6, 2016 · 0 comments

Comments

@tarilabs
Copy link

tarilabs commented Aug 6, 2016

The published docker image rhqproject/rhq-nodb on the docker hub does not work and hangs forever once started.

I believe this is because the run script file invoke the installer rhqctl install, the installer does not find in the server properties a default admin password, hence prompts the user with:

The [rhq.autoinstall.server.admin.password] property is required but not set in [rhq-server.properties].
Do you want to set [rhq.autoinstall.server.admin.password] value now?

(I've checked by running this manually myself); but the installer is running as a java process inside the container itself, hence there is no way this is going to ever move on or start the application itself.

I've solved by proving a default rhq.autoinstall.server.admin.password property for the user rhqadmin as rhqadmin:

$ ./rhq-encode-value.sh 
Property rhq.autoinstall.server.admin.password [y/n]: y
Password: rhqadmin

Encoded password for rhq-server.properties:
     rhq.autoinstall.server.admin.password=x1XwrxKuPvYUILiOnOZTLg==

I believe that would be the solution, as additionally it would also follow similar style of already defined default passwords for other admins users (e.g.: rhq.server.database.password) in the server properties file. If there is a better solution kindly let me know.

Meanwhile, I will raise a PR accordingly to make explicit my proposed solution.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant