• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Apache stoped after upgrading to plesk 9.2.1

A

ali sayyed

Guest
Hello,
I have linux redhat 4 enterprise SE.
when I have upgraded the plesk to 9.2.1 the apache stopped and the sites still not activated until now.
ASAP,can any man help me?
Regards.
 
hi,

two options:

i can check your server to find the bug...

or enter

apache2 -k configtest

and post the output

ys
manuel :)
 
Try to suspend all Domains in plesk. Restart or try to start apache2 and after that's working fine. Active all domains.

This help me in many cases, because configfiles are completly new written to harddisk.
 
in my case, port 80 and 443 are already in used (changing the two ports in config makes httpd start)
if i do lsof -i tcp:80, here's what i get:
sshd 14815 root 3u IPv4 66608966 TCP *:http (LISTEN)
sshd 15740 root 3u IPv4 66608966 TCP *:http (LISTEN)
sshd 17405 root 3u IPv4 66608966 TCP *:http (LISTEN)
sshd 17850 root 3u IPv4 66608966 TCP *:http (LISTEN)
sshd 19096 root 3u IPv4 66608966 TCP *:http (LISTEN)
sshd 19126 root 3u IPv4 66608966 TCP *:http (LISTEN)
sshd 19480 root 3u IPv4 66608966 TCP *:http (LISTEN)
sshd 19587 root 3u IPv4 66608966 TCP *:http (LISTEN)
sshd 19719 root 3u IPv4 66608966 TCP *:http (LISTEN)
sshd 23283 root 3u IPv4 66608966 TCP *:http (LISTEN)

restarting sshd does not change anything
 
SELinux rules could be preventing Apache from startup:

Try this command:

# getenforce
Enforcing

If the response is "Enforcing" temporally disable it with the following command:

# setenforce 0

Try starting Apache:

# /etc/init.d/httpd start
Starting httpd: [ OK ]

Check status:

# /etc/init.d/httpd status
httpd (pid 11557 11556 11555 11554 11553 11552 11551 11550 11549 11548 11540) is running...
 
Back
Top