502 again !
Now I will completely disable Fail2Ban for 24h.
I've said that ModSecurity was installed but never enabled ^^
502 again without Fail2Ban and ModSecurity.
HEY PLESK, THIS IS A CRITICAL BUG !
502 again !
Now I will completely disable Fail2Ban for 24h.
BTW, we have updated https://kb.plesk.com/en/128431 for Ubuntu case.
I've installed a new plesk server and the bug still present, when will you fix this critical bug ?
Yes, it's still an ubuntu server :/
I don't like Centos-Redhat-Fedora
And of course, I can't open a ticket because my licence come from a provider..
Very disappointed to pay for a partially functional software
EXAMPLE ( old ):
...
postrotate
if /etc/init.d/apache2 status > /dev/null ; then \
/etc/init.d/apache2 reload > /dev/null; \
fi;
...
EXAMPLE ( new ):
...
postrotate
if /etc/init.d/apache2 status > /dev/null ; then \
/etc/init.d/apache2 restart > /dev/null; \
fi;
...
Even that you both resist on stating, that this is a Plesk-related bug, you really should consider to investigate your issue a bit better:
To make this clear:
Investigating your provided informations at this thread, it is obvious, that the daily logrotation configurations still contain an apache - RELOAD - process, instead of an suggested apache - RESTART - process.
=> https://talk.plesk.com/search/search?&keywords="apache"+"logrotate"
AND the already mentioned KB - article can be found at:
=> Apache crashes on reload: seg fault or similar nasty error detected in the parent process ( KB - article 128431 )
With all these informations, you should as well be able to notice, that "apache" itself is not at all a Plesk component and the mentioned apache - bug with the result of possible segfaults are as well not Plesk-related. Pls. see as well the mentioned links at => #17 for example!
The recommendation to solve your issue is still the same:
- Pls. change your apache version from "mpm_event" to "mpm_prefork". ( Home > Tools & Settings > Apache Web Server )
- Pls. set the "Apache restart interval" to a higher value, than the standard "0" seconds. ( Home > Tools & Settings > Apache Web Server )
- Pls. change EVERY "apache2 reload" - setting to a "apache2 restart" - setting at your depending logrotation definitions under "/etc/logrotate.d/".
Code:EXAMPLE ( old ): ... postrotate if /etc/init.d/apache2 status > /dev/null ; then \ /etc/init.d/apache2 reload > /dev/null; \ fi; ... EXAMPLE ( new ): ... postrotate if /etc/init.d/apache2 status > /dev/null ; then \ /etc/init.d/apache2 restart > /dev/null; \ fi; ...
If you still experience issues/errors/problems, after you followed the recommendations, it is essential, that you provide ACTUAL informations from your log - files and don't forget your current operating system, your used Plesk version ( incl. MU ) and consider to include as well informations about your changes, that you have done to solve the issue! It will help no one ( especially not yourself! ), if you waste time with "chatting" about your issue and it will help no one as well, if you try for the umpteenth time, to make Plesk responsible for the issue.
Could you pls. state, what advantages do you expect when using "mpm_event" ? Are you aware, that some apache - modules ( for example "mod_php" ) are not working with "mpm_event"?if so when can we begin to use mpm_event?
Hi Burak Özdemir,
Could you pls. state, what advantages do you expect when using "mpm_event" ? Are you aware, that some apache - modules ( for example "mod_php" ) are not working with "mpm_event"?
Correct.using mpm_prefork (with other 2 more recommended settings) will resolve the issue, right?