• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx

  • We are developing a new feature in Plesk that will help you promote your websites or business on social media. We want to conduct a one-hour online UX test to present the prototype and collect feedback. If you are interested in the feature, please book a meeting via this link.
    Thank you in advance!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Unable to start Apache

anirudh79

New Pleskian
I am new to VPS and optimizing Apache and web servers. I was trying to disable modules using Plesk. And I also took a backup of apache modules file just in case if anything goes wrong. Disabled some modules (recommended by people on the internet) and then apache failed to start. I also tried recovering my backup apache module files but the apache isn't starting at all.

Here's the out of systemctl status httpd.service

Code:
httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/httpd.service.d └─respawn.conf Active: activating (auto-restart) (Result: exit-code) since Sun 2020-09-27 02:29:08 CEST; 179ms ago Docs: man:httpd(8) man:apachectl(8) Process: 10815 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=0/SUCCESS) Process: 28995 ExecReload=/usr/sbin/httpd $OPTIONS -k graceful (code=exited, status=0/SUCCESS) Process: 19388 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE) Main PID: 19388 (code=exited, status=1/FAILURE)



Sep 27 02:29:08 02.hostsallserver.xyz systemd[1]: Failed to start The Apache ... Sep 27 02:29:08 02.hostsallserver.xyz systemd[1]: Unit httpd.service entered ... Sep 27 02:29:08 02.hostsallserver.xyz systemd[1]: httpd.service failed. Hint: Some lines were ellipsized, use -l to show in full.

And here's the output of journalctl -xe

Code:
Sep 27 02:30:03 02.hostsallserver.xyz systemd[1]: Unit httpd.service entered failed state. Sep 27 02:30:03 02.hostsallserver.xyz systemd[1]: httpd.service failed. Sep 27 02:30:05 02.hostsallserver.xyz sshd[19551]: Failed password for invalid user bitbucketuser from 84.51.36.86 port 44336 ssh2 Sep 27 02:30:06 02.hostsallserver.xyz sshd[19551]: Received disconnect from 84.51.36.86 port 44336:11: Normal Shutdown, Thank you for playing [preauth] Sep 27 02:30:06 02.hostsallserver.xyz sshd[19551]: Disconnected from 84.51.36.86 port 44336 [preauth] Sep 27 02:30:07 02.hostsallserver.xyz sshd[19564]: reverse mapping checking getaddrinfo for host-84-51-36-86.teletektelekom.com [84.51.36.86] failed - POSSIBL Sep 27 02:30:07 02.hostsallserver.xyz sshd[19564]: Invalid user ali from 84.51.36.86 port 33454 Sep 27 02:30:07 02.hostsallserver.xyz sshd[19564]: input_userauth_request: invalid user ali [preauth] Sep 27 02:30:07 02.hostsallserver.xyz sshd[19564]: pam_unix(sshd:auth): check pass; user unknown Sep 27 02:30:07 02.hostsallserver.xyz sshd[19564]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.51.36.86
 
Back
Top