Timeouts on Specific Websites

[perabyte]

@sahsanu

Thank you, the script to update the firewall worked as expected

Awesome, glad to hear it!

@sahsanu

Could you please modify the cron job to redirect the output to a file?

I redirected the output to a file and it looks like it ran fine:

A theory… The specific complaint from the site owner is that tasks that are scheduled to happen ->daily(); aren’t taking place. I know that Laravel’s daily() will strictly only run in a cron job that was started at 00:00:xx.

It does look like the crons start when they should, when I look at the syslog:

I wonder if something is interrupting them. Is there something Hestia could be doing at midnight that is interrupting the cron jobs?

[perabyte]

I think I figured out the issue!

I looked at the logs for the sites and I noticed that Laravel’s scheduler is throwing this error:

The Process class relies on proc_open, which is not available on your PHP installation.

I removed proc_open from disable_functions in php.ini. Going to see if that fixes it.

I have no idea why it added it in just a few days ago, though, and it’s never been present in the disable_functions on my second server as far as I’m aware. Could something did Hestia did cause it to “reset” or change my php.ini?

[sahsanu]

@perabyte

I have no idea why it added it in just a few days ago, though, and it’s never been present in the disable_functions on my second server as far as I’m aware. Could something did Hestia did cause it to “reset” or change my php.ini?

Hestia doesn’t reset that directive, but it does add it if you use v-add-web-php X.Y. Maybe you reinstalled it a few days ago.