Skip to content

Installation Complete and Database loading OK in a Debian 12 bookworm but unable to view results via Web_App #38

@jsaizm

Description

@jsaizm

Hello you all, greetings from Valencia (Spain)

After installing Philologic5 in my Debian GNU/Linux 12 (bookworm) machine running Apache/2.4.66 and loading without any problem the XML database correctly, there is a bug that I hope you could help me with because the APP works but I cannot view the web_app interface.

Image Image Image

First of all, just to mention that If you add, as you recommeded, the ProxyTimeout value to the Location tag in the <VirtualHost *:80>
000-default-config file

_<Location "/philologic5">
    ProxyPass unix:/var/run/philologic/gunicorn.sock|http://localhost/philologic5
    ProxyPassReverse unix:/var/run/philologic/gunicorn.sock|http://localhost/philologic5
    ProxyTimeout 300
</Location>_

the Apache2 service reports the following error:

A start job for unit apache2.service has begun execution.
The job identifier is 6620.
feb 18 12:08:42 mmm apachectl[25082]: AH00526: Syntax error on line 37 of /etc/apache2/sites-enabled/000-default.conf:
feb 18 12:08:42 mmm apachectl[25082]: ProxyTimeout not allowed in context
feb 18 12:08:42 mmm apachectl[25078]: Action 'start' failed.
feb 18 12:08:42 mmm apachectl[25078]: The Apache error log may have more information.
feb 18 12:08:42 mmm systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Subject: Unit process exited
Defined-By: systemd
Support: https://www.debian.org/support
An ExecStart= process belonging to unit apache2.service has exited.
The process' exit code is 'exited' and its exit status is 1.
feb 18 12:08:42 mmm systemd[1]: apache2.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: https://www.debian.org/support
The unit apache2.service has entered the 'failed' state with result 'exit-code'.
feb 18 12:08:42 mmm systemd[1]: Failed to start apache2.service - The Apache HTTP Server.
Subject: A start job for unit apache2.service has failed
Defined-By: systemd
Support: https://www.debian.org/support

On the other hand, the gunicorn-error.log file reports this:
[2026-02-18 09:58:17 +0100] [1670] [INFO] Shutting down: Master
[2026-02-18 10:02:57 +0100] [5143] [INFO] Starting gunicorn 25.1.0
[2026-02-18 10:02:57 +0100] [5143] [INFO] Listening at: unix:/var/run/philologic/gunicorn.sock (5143)
[2026-02-18 10:02:57 +0100] [5143] [INFO] Using worker: sync
[2026-02-18 10:02:57 +0100] [5143] [ERROR] Control server error: [Errno 13] Permission denied
[2026-02-18 10:02:57 +0100] [5150] [INFO] Booting worker with pid: 5150
[2026-02-18 10:02:57 +0100] [5151] [INFO] Booting worker with pid: 5151
[2026-02-18 10:02:57 +0100] [5152] [INFO] Booting worker with pid: 5152
[2026-02-18 10:02:57 +0100] [5153] [INFO] Booting worker with pid: 5153
[2026-02-18 10:02:57 +0100] [5155] [INFO] Booting worker with pid: 5155

In this image, a previous error dealing with several files and lines:
Image

In this case, just to mention that the Global Configuration you show via this [online tutorial (https://artfl-project.github.io/PhiloLogic5/installation.html)] is not correct because the installer do not copy the web_app_dir to the "/etc/philologic/web_app/" so that, you can get confused while adding this variable while configuring the "/etc/philologic/philologic5.cfg" file.

Should the line/path "/var/lib/philologic5/web_app" be added to the "web_app_dir" variable within this configuration.file?

any idea to fix this bug will be more than welcome!

I did find the same bug located at MARAT website in this link

https://marat.uchicago.edu/philologic5/GreekTest23/

Is this a problem with Apache2 config? What is the difference between this site and the official website available at

https://artflsrv04.uchicago.edu/philologic5/journauxdemarat

Digital Regards

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions