I think maybe it’s a problem with disable-transparent-hugepages unit. because of following error in the log:
fatal: [localhost]: FAILED! => {“changed”: false, “failed”: true, “msg”: “Unable to start service disable-transparent-hugepages: Job for disable-transparent-hugepages.service failed because the control process exited with error code. See "systemctl status disable-transparent-hugepages.service" and "journalctl -xe" for details.\n”}
When I try to connect to the server , I’m redirected to server-error.html
Thanks for your help
TASK [mongo_3_2 : Enable/start disable transparent huge pages service (http://docs.mongodb.org/manual/tutorial/transparent-huge-pages/)] ***
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to start service disable-transparent-hugepages: Job for disable-transparent-hugepages.service failed because the control process exited with error code. See \"systemctl status disable-transparent-hugepages.service\" and \"journalctl -xe\" for details.\n"}
to retry, use: --limit @/var/tmp/configuration/playbooks/openedx_native.retry
@garage_num, What does systemctl status disable-transparent-hugepages.service show?
Since transparent hugepages is a kernel level option, certain virtualization technologies won’t allow it to be modified from within a container. I think Gandi Cloud Server uses Xen virtualization, which may not allow transparent hugepages to be disable for your server.
Mongo will still function with them enabled, though it may affect performance.
To skip installing the service which disables transparent hugepages, you can download the native.sh script, and add an option when running.
Instead of the last step where you download native.sh and pipe it directly to bash, try running the following: