Search results

Just to follow up on this, indeed, when I changed the scheduled crons to 5:30, the bad gateway also started at that time. I'll look deeper into the scripts.

I do think the blame is on one of the jobs that run at 6:30, or a combination of them. I tried running all the jobs individually, but none of them caused the error. I just changed the time to 5:30 to see if the theory is right, let's see what happens tomorrow. And if it was just the backup job...

Yes, the fail2ban is one of the first suggestions I've found in forums. The machine ip is listed as trusted. And anyway, why would it only ban at 6:30 am? The whole day it works properly and stops serving out of nowhere.

It restarts with no problem, but the 504 continues.

Yes. I tried restarting nginx and apache separately and at the same time, it doesn't work. The way I have it running now is having a cron job that reboots the system every day. But it doesn't seem like a proper solution. In fact, for some reason the cron job from within plesk (both through...

Thanks for your help. I really can't find anything wrong in nginx access and error logs at the time it creashes. I'm pasting them below. The wget requests are my scripts that let me know when the system crashes. There is a series of errors at 7:02, but that is when I restart the system...

Oh well. I guess this is goodbye to plesk. Going back to barebone ops.

Yes, sorry, I realized this right after I posted! I edited for clarification.

OK, so also I ran all script in /etc/cron.daily and the site did not hang. But it would make sense to be somthing in there, since it is scheduled for 6:25, right before the daily crash.

Thanks. I ran all tasks one by one and it did not hang. The crontab looks quite different than yours, though: 47 23 * * * /usr/sbin/ntpdate -b -s 2.pool.ntp.org 0 1 * * 1 /opt/psa/libexec/modules/watchdog/cp/secur-check 0 1 *...

Hi I'm having an issue since I updated to version 18.0.27 on Debian. Every morning, at 6:30, nginx starts to hang with a 504 error on all sites. Accessing plesk's panel in its own port works fine, though. I tried restarting nginx and apache with no avail. The only solution I've found is to...