You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the setup script I observed that the generated root has the script user option appended to it. Please see the attached images, and that is, the '--user={someUser}'.
It rendered the query plan viewer unreachable.
Observed on
MarkLogic Server : 10.0-8
AWS BYOL ami: note, the image is running on AWS Linux 2
Directory: regardless of where the queryplan-viewer directory exists
Script: setup.sh ran as follows, without specifying DIR, and according to the README
Actual
When running the setup script I observed that the generated root has the script user option appended to it. Please see the attached images, and that is, the
'--user={someUser}'.
It rendered the query plan viewer unreachable.
Observed on
MarkLogic Server : 10.0-8
AWS BYOL ami: note, the image is running on AWS Linux 2
Directory: regardless of where the queryplan-viewer directory exists
Script: setup.sh ran as follows, without specifying DIR, and according to the README
Desired
The setup.sh script should set up the application server root in such a way that it is not suffixed by the --user option.
Workaround
Workaround Option A
Edit line 38 of setup.sh
Workaround Option B
From the Admin console at 8001, go to the Configure tab of the application server. Then, remove the trailing '--user=someUser' from the root textfield
Attachments below
The attached screenshots show both the FIXED state and the NON-WORKING state.
setup.sh generated this root configuration
workaround applied
.
The text was updated successfully, but these errors were encountered: