-1

Afternoon all

I am using apache to host a node.js application. It suddenly stopped working. I am using a virtual host for the port. I have been debugging through errors but now I have this error message.

I used journalctl -xe to view the errors. Apologies, I am certainly no expert with apache but I am just a bit baffled what a preauth on these IP's is for(its not the one my application is hosted on so I have no idea what it is)

So clearly an authentication issue, I just have no idea where to start?

[root@3xv5 ~]# sudo systemctl restart httpd
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
[root@3xv5 ~]# journalctl -xe
Nov 13 17:09:54 3xv5.c.time4vps.cloud sshd[25682]: Connection closed by 139.59.95.112 port 51572 [preauth]
Nov 13 17:09:55 3xv5.c.time4vps.cloud sshd[25685]: Connection closed by 139.59.95.112 port 51580 [preauth]
Nov 13 17:09:56 3xv5.c.time4vps.cloud sshd[25688]: Connection closed by 139.59.95.112 port 51594 [preauth]
Nov 13 17:09:57 3xv5.c.time4vps.cloud sshd[25691]: Connection closed by 139.59.95.112 port 51598 [preauth]
Nov 13 17:09:58 3xv5.c.time4vps.cloud sshd[25694]: Connection closed by 139.59.95.112 port 51614 [preauth]
Nov 13 17:09:59 3xv5.c.time4vps.cloud sudo[25699]:     root : TTY=pts/1 ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl restart httpd
Nov 13 17:09:59 3xv5.c.time4vps.cloud sudo[25699]: pam_unix(sudo:session): session opened for user root by root(uid=0)
Nov 13 17:09:59 3xv5.c.time4vps.cloud systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit httpd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has begun starting up.
Nov 13 17:09:59 3xv5.c.time4vps.cloud systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Nov 13 17:09:59 3xv5.c.time4vps.cloud systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Nov 13 17:09:59 3xv5.c.time4vps.cloud systemd[1]: Unit httpd.service entered failed state.
Nov 13 17:09:59 3xv5.c.time4vps.cloud systemd[1]: httpd.service failed.
Nov 13 17:09:59 3xv5.c.time4vps.cloud sudo[25699]: pam_unix(sudo:session): session closed for user root
Nov 13 17:10:00 3xv5.c.time4vps.cloud sshd[25697]: Connection closed by 139.59.95.112 port 51628 [preauth]
Nov 13 17:10:01 3xv5.c.time4vps.cloud sshd[25707]: Connection closed by 139.59.95.112 port 51654 [preauth]
Nov 13 17:10:02 3xv5.c.time4vps.cloud sshd[25710]: Connection closed by 139.59.95.112 port 51664 [preauth]
Nov 13 17:10:03 3xv5.c.time4vps.cloud sshd[25713]: Connection closed by 139.59.95.112 port 51678 [preauth]
Improve this question
4
  • In most configurations Apache httpd will log to files and not to the systemd journal as to why it failed and/or fails to restart (Somewhere in /var/log )
    – HBruijn
    Nov 13 at 15:35
  • thankyou for that, I had a look in /var/log/httpd/eror_log and received this " [ssl:emerg] [pid 19601] SSL Library Error: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch [Sun Nov 12 16:52:16.078555 2023] [ssl:emerg] [pid 19601] AH02312: Fatal error initialising mod_ssl, exiting. [Mon Nov 13 17:07:32.793010 2023] [suexec:notice] [pid 25566] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Mon Nov 13 17:07:32.793912 2023] [ssl:emerg] [pid 25566] AH02238: Unable to configure RSA server private key" so i assume thats just a ssl key error?
    – jitsujoseph
    Nov 13 at 15:44
  • Based on that log event that indeed a looks like an SSL key problem
    – HBruijn
    Nov 13 at 15:55
  • 1
    Apache 2.2? ftp? Suexec? Have I fallen into a black hole and arrived in 2006?
    – symcbean
    Nov 13 at 16:34

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .