Closed sfphh4 closed 11 months ago
There are many reasons why the initialization process might fail. See the Troubleshooting section for instructions.
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.
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.
Closing this because of lack of activity.
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.