• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Can't start Apache Server..

Jiji

New Pleskian
Hello,
Since last update, my website is offline. in the service window, i found that Apache server is not running, when i try to activate it i see : Unable to start service: Unable to manage service by apache_control_adapter: ('start', 'web'). Error:
when i try to open my website : 502 Bad Gateway OR 403 Forbidden.
I am running Plesk on Debian.
Any Help please ?
 
Hi thank you for your reply, i already tried to repare web :
Checking Plesk version .............................................. [OK]

Checking for custom configuration templates ......................... [OK]

Checking the JkWorkersFile directive in the Apache configuration .... [OK]

Checking associations between domains and IP addresses .............. [OK]

Checking for corrupted reference between IP collections and
IPaddresses ......................................................... [OK]

Checking for links between APS applications and subscriptions ....... [OK]

Checking for the Zend extension declaraion in php.ini ............... [OK]

Check symbolic links for latest virtual host config files ........... [OK]

Checking for system users home directories consistency .............. [OK]

Checking for records with empty name field in the Configurations table
................................................................... [OK]

Checking for nginx ULIMIT value ..................................... [OK]

Checking for extra configurations in database not owned by any object
................................................................... [OK]

Checking the configuration of Apache modules ........................ [OK]

Repairing web server configuration
Reinstalling SSL/TLS certificates ............................... [OK]
Applying the default SSL/TLS certificate to all IP addresses .... [OK]
Repairing server-wide configuration parameters for web servers .. [2019-01-30 12:24:49.355] ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/httpdmng' '--reconfigure-server'] with exit code [1]
[FAILED]
- httpdmng failed: [2019-01-30 12:24:48.008] ERR [util_exec]
proc_close() failed
['/opt/psa/admin/bin/apache_control_adapter' '--restart'
'--restart-interval' '1800' '--http-port' '7080' '--https-port'
'7081'] with exit code [255]
[2019-01-30 12:24:48.870] ERR [panel] Apache config
(15488473320.72425900) generation failed: Template_Exception:
Can not restart web server:
file: /opt/psa/admin/plib/Service/Driver/Web/Server/Apache.php
line: 109
code: 0
Can not restart web server:
Updating the file of sharing passwords and permissions of users
according to actual information ................................. [OK]
Repairing web server configuration for all domains. This aspect
can be used with individual domains ("plesk repair web
example.com"), and on the server level ("plesk repair web") ..... [OK]

Checking the usage of PHP handlers .................................. [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0


exit status 1

And when i try #apachectl -t i have : No syntax errors
 
My website is still offline with "502 Bad Gateway" and in the logs i found :
8828#0: *4 connect() failed (111: Connection refused) while connecting to upstream


nginx error
 
Could you please post the output of the apache-error-log?
Code:
 /var/log/httpd/error_log

And the output of:
Code:
service httpd status


Please also have a look here
 
Could you please post the output of the apache-error-log?
Code:
 /var/log/httpd/error_log

And the output of:
Code:
service httpd status


Please also have a look here

Thak you for the reply, the output of the commande is :
service httpd status
● httpd.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
 
You are on Debian, there it is
# service apache2 status

Hi the output is :

● apache2.service - LSB: Apache2 web server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─forking.conf
Active: inactive (dead) since Wed 2019-01-30 17:20:48 CET; 6min ago
Process: 19252 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
Process: 19235 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)

Jan 30 17:20:48 stock.ovh systemd[1]: Starting LSB: Apache2 web server...
Jan 30 17:20:48 stock.ovh apache2[19235]: Starting web server: apache2Action....
Jan 30 17:20:48 stock.ovh apache2[19235]: The Apache error log may have more....
Jan 30 17:20:48 stock.ovh apache2[19235]: .
Jan 30 17:20:48 stock.ovh apache2[19252]: Stopping web server: apache2.
Jan 30 17:20:48 stock.ovh systemd[1]: Started LSB: Apache2 web server.
Hint: Some lines were ellipsized, use -l to show in full.
 
How about /var/log/apache2/error.log or /var/log/apache2/error_log?

Please also try
# apachectl -t

It checks the syntax of your configuration files. Most issues result from faulty configuration files or SSL configurations.
 
Here is the content of /var/log/apache2/error.log :
[Wed Jan 30 12:20:56.460664 2019] [unique_id:alert] [pid 6661] (EAI 2)Name or service not known: AH01564: unable to find IPv4 address of "stock.ovh"
AH00016: Configuration Failed
[Wed Jan 30 12:22:13.902989 2019] [unique_id:alert] [pid 6959] (EAI 2)Name or service not known: AH01564: unable to find IPv4 address of "stock.ovh"
AH00016: Configuration Failed
[Wed Jan 30 12:23:31.239968 2019] [unique_id:alert] [pid 7748] (EAI 2)Name or service not known: AH01564: unable to find IPv4 address of "stock.ovh"
AH00016: Configuration Failed
[Wed Jan 30 12:54:48.580795 2019] [unique_id:alert] [pid 13421] (EAI 2)Name or service not known: AH01564: unable to find IPv4 address of "stock.ovh"
AH00016: Configuration Failed
[Wed Jan 30 12:56:05.915076 2019] [unique_id:alert] [pid 14195] (EAI 2)Name or service not known: AH01564: unable to find IPv4 address of "stock.ovh"
AH00016: Configuration Failed
[Wed Jan 30 17:20:48.636425 2019] [unique_id:alert] [pid 19248] (EAI 2)Name or service not known: AH01564: unable to find IPv4 address of "stock.ovh"
AH00016: Configuration Failed
[Wed Jan 30 17:49:28.786599 2019] [unique_id:alert] [pid 19906] (EAI 2)Name or service not known: AH01564: unable to find IPv4 address of "stock.ovh"
AH00016: Configuration Failed
 
Hi, thank you M. Peter it work fine for me :) can you tell me please why i found this after resolving the problem :
8828#0: *3364 open() "/httpdocs/wp-includes/js/jquery/ui/position.min.js" failed (13: Permission denied)

and the website don't work correctly
 
This can have various reasons. For example, the owner of /httpdocs is not set to <username>:psaserv, or the permissions of /wp-includes is not <username>:psacln. Maybe a security setting was applied that direct access to /wp-includes paths is disabled. Maybe the file or directory modes are incorrect (e.g. no read access for psaserv or psacln). Yo could start with
# plesk repair web <domainname>
(repairs web server configuration)
# plesk repair fs <domainname>
(repairs file permissions)
You could then remove security settings from the wordpress toolkit security page.
 
i see thank you, here is the output of # plesk repair fs <domainname>
There are files or directories with suspicious permissions in the
root directory of the domain 'my domain .................... [WARNING]
httpdocs/wp-config.php

How can i remove security settings from the wordpress toolkit security page please ? and excuse my questions i'am new on Plesk usdaly i use cpanel :/
 
Back
Top