Custombuild Apache+Php-fpm

B

bsoft08

New member
Joined
Feb 16, 2017
Messages
5
Hi,

I have upgraded to Apache+Php-fpm56
Everything seams to be ok on the normal websites but on the https websites after a day they dont work anymore i have to do service httpd restart and everithing starts working for another day.

All websites are wordpress, there are 4 sites on a vps 4 cores / 8.192 MB / CentOS 7

Also i noticed that after a time if i do httpd status i get the following:
[root@nl custombuild]# service httpd status
Redirecting to /bin/systemctl status httpd.service
httpd.service - The Apache HTTP Server
Loaded: loaded (/etc/systemd/system/httpd.service; enabled)
Active: active (running) since Thu 2017-02-16 11:43:03 CET; 19min ago
Process: 30076 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 30069 ExecReload=/usr/sbin/httpd $OPTIONS -k graceful (code=exited, status=0/SUCCESS)
Main PID: 30088 (httpd)
Status: "Total requests: 274; Idle/Busy workers 100/0;Requests/sec: 0.239; Bytes served/sec: 13KB/sec"
CGroup: /system.slice/httpd.service
├─ 915 /usr/sbin/httpd -DFOREGROUND
├─ 3069 /usr/sbin/httpd -DFOREGROUND
├─ 8641 /usr/sbin/httpd -DFOREGROUND
├─ 8690 /usr/sbin/httpd -DFOREGROUND
├─ 8730 /usr/sbin/httpd -DFOREGROUND
├─ 8737 /usr/sbin/httpd -DFOREGROUND
├─ 8738 /usr/sbin/httpd -DFOREGROUND
├─30088 /usr/sbin/httpd -DFOREGROUND
├─30097 /usr/sbin/httpd -DFOREGROUND
├─30106 /usr/sbin/httpd -DFOREGROUND
└─30108 /usr/sbin/httpd -DFOREGROUND

But the strange thing is that everithing is working....
also php-fpm56.log
[16-Feb-2017 11:43:03] NOTICE: reloading: execvp("/usr/local/php56/sbin/php-fpm56", {"/usr/local/php56/sbin/php-fpm56", "--nodaemonize"})
[16-Feb-2017 11:43:03] NOTICE: using inherited socket fd=7, "/usr/local/php56/sockets/webapps.sock"
[16-Feb-2017 11:43:03] NOTICE: using inherited socket fd=7, "/usr/local/php56/sockets/webapps.sock"
[16-Feb-2017 11:43:03] NOTICE: using inherited socket fd=8, "/usr/local/php56/sockets/admin.sock"
[16-Feb-2017 11:43:03] NOTICE: using inherited socket fd=8, "/usr/local/php56/sockets/admin.sock"
[16-Feb-2017 11:43:03] NOTICE: using inherited socket fd=9, "/usr/local/php56/sockets/bsoft.sock"
[16-Feb-2017 11:43:03] NOTICE: using inherited socket fd=9, "/usr/local/php56/sockets/bsoft.sock"
[16-Feb-2017 11:43:03] NOTICE: using inherited socket fd=10, "/usr/local/php56/sockets/delbianco.sock"
[16-Feb-2017 11:43:03] NOTICE: using inherited socket fd=10, "/usr/local/php56/sockets/delbianco.sock"
[16-Feb-2017 11:43:03] NOTICE: using inherited socket fd=11, "/usr/local/php56/sockets/tech.sock"
[16-Feb-2017 11:43:03] NOTICE: using inherited socket fd=11, "/usr/local/php56/sockets/tech.sock"
[16-Feb-2017 11:43:03] NOTICE: fpm is running, pid 24864
[16-Feb-2017 11:43:03] NOTICE: ready to handle connections
[16-Feb-2017 11:43:03] NOTICE: systemd monitor interval set to 10000ms


Nothing strange
 
I think i found out what was caussing the problem is clamv that was previously install with custombuild that was blocking apache every night.
I disable it and we will se if it happens again.
 
I got it now...
My only question is if the only sollutions are:
1. Downgrade apache
2. Add a cron with a apache restart and wait for the newes version of apache

thanks
 
Sorry for my english...
I read the page, but after my understanding there is a problem with the http2, and after reading i understand that the fix will come out with Apache 2.4.26

Because i have this problem only on the https sites on the rest everithing is ok.
 
I only know ( also out of own experience):
That using Apache 2.4.25 in combination with http2 and some other things as config/settings this kind of problems you could have.

Where with DA boxes then for example the gracefull restarts of httpd give problems.

You can try to change the conf for DA not doing gracefull restarts, then only a few cronjobs / updates that still doing this gracefull are left.
( you have to take care of that:
For example we have 1 almost every 7 days and 1 i think once a month ore 14 days, also if loggs are getting to large i didn't managed to solve here) ( But knowing for the one Server when , so doing a manual restart after)

Others that don't want to check or "suprises" putting version back to 2.4.24, while i was expecting soon a 2.4.26 update this is sadly not the case for now.

2.4.25 have some security fixes for the older apache versions, so you have to take care of. ;)
 
I was thinking as solution putting a cron with httpd restart at least for now.
Dont know if is a good ideea but ill take the risk.
 
You must log in or register to reply here.
Back
Top