1.2.0 on master build is only for testing, have you done already apt-get install --reinstall hestia after the release from yesterday? If not, please repeat it, then change in $HESTIA/conf/hestia.conf the branch from master to release, so you are again on the right track.
That change would not help much, this is basicly just a cosmetic thing .
You wrote you have the issues since 2 days - since when are you using 1.2.0? It doesnt sounds like it is related to the release, also infact you upgraded/reinstalled it yesterday. DId you changed anything else?
I 'm using this version since I report with awstats and I changed to test some updates.
I never rollback to release (AWStats | Country origin)
I couldn’t say that release version upgrade fixed it, but I can’t negate it
I found that /etc/php/7.3/fpm/pool.d/*.conf had a low max_children value.
Maybe I am wrong, but I set to 64 (default value = 8 ) and restart php-fpm and start to work
I have this problem with all php versions installed, so I did
tar /backup/suicide_sed.tar /etc/php/
sed -i 's|max_children = 8|max_children = 64|g' /etc/php/*/fpm/*/*
for i in `ls -1 /etc/init.d/php*`; do $i restart; done
Everything seems to be working since 20 minutes ago, with some jobs to do, but I hope I can manage
@changeme my guess is your php-fpm wasn’t running at all. probably not the change in the config helped, but simply restarting it… I’d recommend to reset the setting. you don’t want to have max 64 children processes there unless it’s a big server with lot’s of RAM and very high traffic pages.