Apache

andreiut

Verified User
Joined
Apr 7, 2014
Messages
11
Hello, i have a strange problem with apache server, the websites suddenly stopped worked so i restarted apache, the sites are working for about 1 minutes, then they are stop responding.. both port 80 or 443, interesting that when connecting to :2222 on directadmin it's working.
apache status also shows its working, and no errors are showing in /var/log/httpd/error_log.
Code:
service httpd status
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/etc/systemd/system/httpd.service; enabled)
   Active: active (running) since Fri 2017-05-12 11:48:33 EEST; 2min 2s ago
  Process: 6012 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=0/SUCCESS)
 Main PID: 6018 (httpd)
   Status: "Total requests: 1912; Idle/Busy workers 97/2;Requests/sec: 16.6; Bytes served/sec: 2.3MB/sec"
   CGroup: /system.slice/httpd.service
           ├─6018 /usr/sbin/httpd -DFOREGROUND
           ├─6041 /usr/sbin/httpd -DFOREGROUND
           └─6066 /usr/sbin/httpd -DFOREGROUND
May 12 11:48:33 server.site.xom systemd[1]: Started The Apache HTTP Server.
and here-s error log after restarting apache:
Code:
[Fri May 12 11:48:32.181288 2017] [auth_digest:notice] [pid 6018:tid 139650096129856] AH01757: generating secret for digest authentication ...
[Fri May 12 11:48:33.077452 2017] [ssl:warn] [pid 6018:tid 139650096129856] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Fri May 12 11:48:33.078212 2017] [ssl:warn] [pid 6018:tid 139650096129856] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Fri May 12 11:48:33.078413 2017] [lbmethod_heartbeat:notice] [pid 6018:tid 139650096129856] AH02282: No slotmem from mod_heartmonitor
[Fri May 12 11:48:33.081439 2017] [mpm_event:notice] [pid 6018:tid 139650096129856] AH00489: Apache/2.4.25 (Unix) OpenSSL/1.0.1t configured -- resuming normal operations
[Fri May 12 11:48:33.081479 2017] [core:notice] [pid 6018:tid 139650096129856] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
it now shows me, Status: "Total requests: 18469; Idle/Busy workers 76/23;Requests/sec: 14.9; Bytes served/sec: 3.0MB/sec"
can it be because of the total requests? what else can i do? as i noticed sometimes websites are starting to work.. then stop responding and so on.
thank you.
 
Last edited:

andreiut

Verified User
Joined
Apr 7, 2014
Messages
11
I updated the web server to nginx_apache and works fine now (hope to stay like this), don't know what's happening with apache only, no errors in logs, but websites were giving error_timed_out .. only directadmin on port 2222 worked.
 

vlijmenlive

Verified User
Joined
Nov 13, 2013
Messages
64
Location
Belgium
It seems to me that the number of connections is indeed causing the issue. I don't know what kind of sites you are running but using nginx_reverse is a good start. You also might want to look into the option to serve static content directly from disk when possible.
 

andreiut

Verified User
Joined
Apr 7, 2014
Messages
11
It seems to me that the number of connections is indeed causing the issue. I don't know what kind of sites you are running but using nginx_reverse is a good start. You also might want to look into the option to serve static content directly from disk when possible.
how can I do that?
 

vlijmenlive

Verified User
Joined
Nov 13, 2013
Messages
64
Location
Belgium
Hi,

You could use try_files for this to check if the file exists in the root path of the user. The nginx documentation has a lot of information to optimize your settings.
 
Top