Deploy script fails when installing EaaSI manually

EaaSI Support Center
1

Deployment: I’m trying to set up self-hosting, running Ubuntu 22.04.4 LTS on the target machine and Arch Linux on the controller machine.

Description: I followed the steps on Setup and Deployment — EaaSI documentation but running ./scripts/deploy.sh failed with the following message:

TASK [ensure eaas-server is restarted] ************************************************************************************************
fatal: [eaas-gateway]: FAILED! => changed=false
  msg: |-
    Unable to start service eaas.service: Job for eaas.service failed because the control process exited with error code.
    See "systemctl status eaas.service" and "journalctl -xeu eaas.service" for details.

PLAY RECAP ****************************************************************************************************************************
eaas-gateway               : ok=104  changed=19   unreachable=0    failed=1    skipped=39   rescued=0    ignored=0

Running systemctl status eaas.service also fails with the message Unit eaas.service could not be found while journalctl -xeu eaas.service showed no entries. Rerunning the script gave the same error.

What could cause this, and is it fixable?

2

Hello @antones - at a glance, off the bat I can note that the v2021.10 EaaSI release components do not/did not support Ubuntu 22.04, it was maintained for 18.04, 20.04 and CentOS/RHEL 7. It is highly likely that there are multiple dependency/version issues in the chain. At a minimum you are likely experiencing the same jboss/keycloak deprecation issues described in ERROR when installing from scratch (jboss/keycloak, repository does not exist) - #2 by ethan.gates

Please be aware, as I noted in that thread as well, that we are currently largely stepping back from active feature development and maintenance of the now-aging v2021.10 codebase in order to examine dependency and tooling issues throughout the dev workflow, so our ability to continue supporting deployments, especially self-deployments, of these older versions and components from ~2021 will be extremely limited. We’re in a transitional moment and working hard to ultimately make the platform and its development both more maintainable - there will be more details posted soon in the Program Announcements and both the Handbook and the Forum here will be updated shortly in order to more accurately reflect our current status, and we’ll make instructions for testing a more up-to-date version of the software available when able, I apologize for any confusion

1 Like