Closed DHS1001 closed 2 years ago
By adding the priority=x
to the supervisord.conf
in the[program:httpd]
and [program:php-fpm]
sections seems fix this issue.
The service is up and running after each synology reboot.
Doesn't work changing priority
.
I think it's related to this issue
https://stackoverflow.com/questions/39803465/why-does-apache2-does-not-remove-pid-file-on-reboot-on-docker-image
I added these lines in [program:httpd]
. Weird fix, but it works
redirect_stderr=true
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr
stderr_logfile_maxbytes=0
hi there,
after installing the leantime 2.1.8 in the synology nas via docker, leantime is inaccessible randomly after each synology reboot or docker container restart and the browser showing error 502 when inaccessible. Reverse proxy has also been config to allow access via https address.
The log of the container showed below:
Looks like the issue is related to httpd httpd entered FATAL state, too many start retries too quickly. I have tried to put the
startsecs = 0
insupervisord.conf
file under[program:httpd]
. However looks like it is still the same, after each reboot the nas or restart the container, leantime is not accessible due to the same issue.The env added are as below: