Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic installation script fails #1922

Open
karatekaneen opened this issue Mar 24, 2021 · 0 comments
Open

Automatic installation script fails #1922

karatekaneen opened this issue Mar 24, 2021 · 0 comments

Comments

@karatekaneen
Copy link

Steps to reproduce and/or test case demonstrating the problem

I followed the guide for automatic installation by:

Running on a fresh VM on Google Cloud Platform in CentOS 8.

Expected behavior

Expected to get the application running.

Actual behavior

Installation fails silently and from what I can see isn't running.

Installation

The installation outputs a huge amount of logs so couldn't read it all. The last part looks suspicious though:

essarch_install: 2021-03-24_10_02_31
---------------------------------------

Install ESSArch
Looking in links: /ESSArch_setup/packages/pypi
ERROR: Could not find a version that satisfies the requirement ESSArch[libreoffice_file_conversion,mysql]
ERROR: No matching distribution found for ESSArch[libreoffice_file_conversion,mysql]
Looking in links: /ESSArch_setup/packages/pypi
Collecting mod_wsgi
  Downloading mod_wsgi-4.7.1.tar.gz (498 kB)
Building wheels for collected packages: mod-wsgi
  Building wheel for mod-wsgi (setup.py): started
  Building wheel for mod-wsgi (setup.py): finished with status 'done'
  Created wheel for mod-wsgi: filename=mod_wsgi-4.7.1-cp37-cp37m-linux_x86_64.whl size=786165 sha256=19766d86119bbe72d09852f5815eff70006e5b525c4bef7c8b38b291a16ba531
  Stored in directory: /home/arch/.cache/pip/wheels/c3/b2/93/f173e3207d97ada7d56f5516cf1cdff34b38111e41d4a0bad0
Successfully built mod-wsgi
Installing collected packages: mod-wsgi
Successfully installed mod-wsgi-4.7.1
cp: cannot stat '/ESSArch/pd/python/lib/python3.7/site-packages/ESSArch_Core/config/wsgi.py': No such file or directory
Generating a RSA private key
..........................+++++
................................................+++++
writing new private key to 'server_essarch.key'
-----
problems making Certificate Request
140031624869696:error:0D07A097:asn1 encoding routines:ASN1_mbstring_ncopy:string too long:crypto/asn1/a_mbstr.c:107:maxsize=64
-bash: essarch: command not found
-bash: essarch: command not found
python: can't open file '/ESSArch/pd/python/lib/python3.7/site-packages/ESSArch_Core/install/install_profiles_se.py': [Errno 2] No such file or directory
-bash: django-admin: command not found
Configure SELinux for ESSArch
sudo: checkmodule: command not found
semodule_package:  Could not open file No such file or directory:  /ESSArch_setup/scripts/essarch_selinux.mod
libsemanage.map_file: Unable to open /ESSArch_setup/scripts/essarch_selinux.pp
 (No such file or directory).
libsemanage.semanage_direct_install_file: Unable to read file /ESSArch_setup/scripts/essarch_selinux.pp
 (No such file or directory).
semodule:  Failed on /ESSArch_setup/scripts/essarch_selinux.pp!
Attempting to install module '/ESSArch_setup/scripts/essarch_selinux.pp':
Created symlink /etc/systemd/system/multi-user.target.wants/celerydessarch.service → /usr/lib/systemd/system/celerydessarch.service.
Created symlink /etc/systemd/system/multi-user.target.wants/celerybeatessarch.service → /usr/lib/systemd/system/celerybeatessarch.service.
Created symlink /etc/systemd/system/multi-user.target.wants/daphneessarch.service → /usr/lib/systemd/system/daphneessarch.service.
Created symlink /etc/systemd/system/multi-user.target.wants/esshttpd.service → /usr/lib/systemd/system/esshttpd.service.
Job for celerydessarch.service failed because the control process exited with error code.
See "systemctl status celerydessarch.service" and "journalctl -xe" for details.
Job for esshttpd.service failed because the control process exited with error code.
See "systemctl status esshttpd.service" and "journalctl -xe" for details.
Installation complete: 2021-03-24_10_02_58
------------------------------------------

Installation complete: 2021-03-24_10_02_58
------------------------------------------

So when complete I tried to find where the application was running. I tried curl on:

Then I checked the status as mentioned in the logs:

[robin@essarch-centos ~]$ systemctl status esshttpd.service
● esshttpd.service - ESSArch - apache2 httpd
   Loaded: loaded (/usr/lib/systemd/system/esshttpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2021-03-24 10:02:58 UTC; 1min 54s ago
  Process: 107181 ExecStart=/bin/sh -c ${apachectl} -f ${apacheconfig} -k start (code=exited, status=127)

Mar 24 10:02:58 essarch-centos systemd[1]: Starting ESSArch - apache2 httpd...
Mar 24 10:02:58 essarch-centos sh[107181]: /bin/sh: -f: command not found
Mar 24 10:02:58 essarch-centos systemd[1]: esshttpd.service: Control process exited, code=exited status=127
Mar 24 10:02:58 essarch-centos systemd[1]: esshttpd.service: Failed with result 'exit-code'.
Mar 24 10:02:58 essarch-centos systemd[1]: Failed to start ESSArch - apache2 httpd.
[robin@essarch-centos scripts]$ journalctl -xe
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Automatic restarting of the unit daphneessarch.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Mar 24 10:02:59 essarch-centos systemd[1]: Stopped ESSArch - daphne.
-- Subject: Unit daphneessarch.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Unit daphneessarch.service has finished shutting down.
Mar 24 10:02:59 essarch-centos systemd[1]: Started ESSArch - daphne.
-- Subject: Unit daphneessarch.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Unit daphneessarch.service has finished starting up.
-- 
-- The start-up result is done.
Mar 24 10:02:59 essarch-centos systemd[107202]: daphneessarch.service: Failed to execute command: No such file or directory
Mar 24 10:02:59 essarch-centos systemd[107202]: daphneessarch.service: Failed at step EXEC spawning /ESSArch/pd/python/bin/daphne: No such file or directory
-- Subject: Process /ESSArch/pd/python/bin/daphne could not be executed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- The process /ESSArch/pd/python/bin/daphne could not be executed and failed.
-- 
-- The error number returned by this process is 2.
Mar 24 10:02:59 essarch-centos systemd[1]: daphneessarch.service: Main process exited, code=exited, status=203/EXEC
Mar 24 10:02:59 essarch-centos systemd[1]: daphneessarch.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- The unit daphneessarch.service has entered the 'failed' state with result 'exit-code'.
Mar 24 10:02:59 essarch-centos systemd[1]: daphneessarch.service: Service RestartSec=100ms expired, scheduling restart.
Mar 24 10:02:59 essarch-centos systemd[1]: daphneessarch.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Automatic restarting of the unit daphneessarch.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Mar 24 10:02:59 essarch-centos systemd[1]: Stopped ESSArch - daphne.
-- Subject: Unit daphneessarch.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Unit daphneessarch.service has finished shutting down.
Mar 24 10:02:59 essarch-centos systemd[1]: daphneessarch.service: Start request repeated too quickly.
Mar 24 10:02:59 essarch-centos systemd[1]: daphneessarch.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- The unit daphneessarch.service has entered the 'failed' state with result 'exit-code'.
Mar 24 10:02:59 essarch-centos systemd[1]: Failed to start ESSArch - daphne.
-- Subject: Unit daphneessarch.service has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Unit daphneessarch.service has failed.
-- 
-- The result is failed.

Did I miss something that is a prerequisite or is something broken?

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

No branches or pull requests

1 participant