jhpyle / docassemble

A free, open-source expert system for guided interviews and document assembly, based on Python, YAML, and Markdown.
https://docassemble.org
MIT License
786 stars 254 forks source link

Docker Image Not Working #657

Closed sfphh4 closed 11 months ago

sfphh4 commented 1 year ago

Upon running the latest docker image, I am getting "Please wait while docassemble starts . . ." at the browser.

Here is the log after 15 minutes of letting it run.

2023-06-09 06:42:24,861 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. 2023-06-09 06:42:24,861 INFO Included extra file "/etc/supervisor/conf.d/docassemble.conf" during parsing 2023-06-09 06:42:24,868 INFO RPC interface 'supervisor' initialized 2023-06-09 06:42:24,869 CRIT Server 'inet_http_server' running without any HTTP authentication checking 2023-06-09 06:42:24,869 INFO RPC interface 'supervisor' initialized 2023-06-09 06:42:24,869 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2023-06-09 06:42:24,869 INFO supervisord started with pid 1 2023-06-09 06:42:25,875 INFO spawned: 'initialize' with pid 7 2023-06-09 06:42:25,876 INFO spawned: 'nascent' with pid 8 2023-06-09 06:42:25,878 INFO spawned: 'watchdog' with pid 9 2023-06-09 06:42:25,886 INFO success: initialize entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2023-06-09 06:42:25,886 INFO success: nascent entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2023-06-09 06:42:26,954 INFO success: watchdog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

jhpyle commented 1 year ago

There are many reasons why the initialization process might fail. See the Troubleshooting section for instructions.

sfphh4 commented 1 year ago

I did the debugging and I still have the issue. When I enter into the docker container, i looked at the component causing the issue.

The issue is apache2 is not working and supervisorctl keeps trying to invoke it. So i stopped it and tried to run it manually and I get the following error:

`root@498f36d73202:/etc/supervisor/conf.d# bash /usr/share/docassemble/webapp/run-apache.sh

Module remoteip already disabled

Conf docassemble-behindlb already disabled

Module ssl already disabled

apache2: Syntax error on line 146 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/wsgi.load: Cannot load /usr/lib/apache2/modules/mod_wsgi.so into server: /usr/lib/apache2/modules/mod_wsgi.so: cannot open shared object file: No such file or directory

Action '-DFOREGROUND' failed.

The Apache error log may have more information. `

I checked the apache error log, and the same was empty.

Any idea how to proceed further? I always thought that Docker Container method should never require debugging, so please guide me as to how to proceed further.

jhpyle commented 1 year ago

The Apache option is a legacy feature. The Docker image used to use Apache, but docassemble switched to NGINX many years ago. I kept the Apache option around for users who had been using Apache and didn't want to switch to NGINX because they had customized the Apache configuration. I haven't been testing the Apache option.

Anyway, in the latest version of the Docker image, I think I fixed the issues with Apache. I would suggest using the default NGINX web server rather than Apache, but if you really want to use Apache can can try the latest version of the Docker image.

jhpyle commented 11 months ago

Closing this because of lack of activity.