D
Deleted member 1158
Last edited by a moderator:
Hello,
I join you because I can't find a solution to my problem! Sorry for my English, I am French.
After trying to stop Apache 2.4 from the package center, access to DSM via the Web no longer works!
Shortly before, I had followed this to customize 404 errors: Personnaliser la page d’erreur 404 pour Synology WebStation
Accessing via local IP or reverse proxy gives the same error.
The other run services (Docker, SSH, VPN Server ...)
I tried to look in the logs / var / log / upstart below what I found, if someone would have a track for me ... Thanks
vim pkg-WebStation-apache.log :
vim nginx.log
vim pkgctl-Apache2.4.log
vim pkg-apache24.log
There is a character limit per message, so I cannot measure everything, in this post you will also find the results of the command: synoservice --status
I join you because I can't find a solution to my problem! Sorry for my English, I am French.
After trying to stop Apache 2.4 from the package center, access to DSM via the Web no longer works!
Shortly before, I had followed this to customize 404 errors: Personnaliser la page d’erreur 404 pour Synology WebStation
Accessing via local IP or reverse proxy gives the same error.
The other run services (Docker, SSH, VPN Server ...)
I tried to look in the logs / var / log / upstart below what I found, if someone would have a track for me ... Thanks
vim pkg-WebStation-apache.log :
Code:
2020-05-29T17:20:51+0200 Update web success
2020-05-29T17:20:51+0200 Update vhost success
2020-05-29T17:20:51+0200 Update php success
2020-05-29T17:20:51+0200 pkg-webstation-php-844257d5-dd27-4885-8fd8-96cf320e39ac start/running, process 30381
2020-05-29T17:20:51+0200 pkg-webstation-php-1a8f6234-b0c1-44fb-9306-a65ec946c7c8 start/running, process 30384
2020-05-29T17:20:51+0200 start: Job is already running: pkg-webstation-php-1a8f6234-b0c1-44fb-9306-a65ec946c7c8
2020-05-29T17:20:51+0200 start: Job is already running: pkg-webstation-php-844257d5-dd27-4885-8fd8-96cf320e39ac
2020-05-29T17:20:51+0200 reload: Unknown job: pkg-apache22
2020-05-29T17:20:51+0200 reload: Unknown instance:
2020-05-29T17:20:51+0200 reload: Unknown instance:
2020-05-29T17:20:51+0200 reload: Unknown instance:
2020-05-29T17:20:51+0200 reload: Unknown instance:
vim nginx.log
Code:
2020-05-29T17:17:55+0200 Start Nginx Server in Normal Mode ......
2020-05-29T17:40:51+0200 Stop Nginx Server ......
vim pkgctl-Apache2.4.log
Code:
2020-05-29T17:28:14+0200 ======== start Apache2.4 ========
vim pkg-apache24.log
Code:
2020-05-29T17:28:15+0200 pre-start
2020-05-29T17:28:15+0200 Start Apache Server .....
2020-05-29T17:28:16+0200 AH00558: httpd24: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
AH00316: WARNING: MaxRequestWorkers of 150 is not an integer multiple of ThreadsPerChild of 32, decreasing to nearest multiple 128, for a maximum of 4 servers.
There is a character limit per message, so I cannot measure everything, in this post you will also find the results of the command: synoservice --status
Acces a DSM impossible
Bonjour, Je viens demander un peu d'aide ! j'avoue être perdu sur ce coup ! Après avoir voulu redémarrer Apache 2.4, l’accès au DSM via Web ne marche plus ! J'ai le droit a : J'ai essayé de fouiller dans les logs /var/log/upstart plus bas se que j'ai trouvé, si quelqu'un aurait une piste pour moi...
www.nas-forum.com
Attachments
-
1590780493461.gif43 bytes · Views: 52
-
1590780493418.gif43 bytes · Views: 27
-
1590780493584.gif43 bytes · Views: 22
-
1590780493505.gif43 bytes · Views: 19
-
1590780493548.gif43 bytes · Views: 20
-
1590780493687.gif43 bytes · Views: 13
-
1590780493721.gif43 bytes · Views: 15
-
1590780493653.gif43 bytes · Views: 11
-
1590780493618.gif43 bytes · Views: 11
-
1590780493756.gif43 bytes · Views: 21