Hourly cron (cron-hour.php) is down since Thursday 12/09/21

Anton, since your power supply is not yet disabled, you can correct ssh access to the server at info@integrator.com.ua, I'll try to clarify

Good afternoon. [quote] Mordach Anton Vladimirovich wrote: Starting from Thursday 09.12.21 from 12 noon, our load on the server increased, we immediately contacted our SheBo manager, found out that the maximum load is exactly when hourly crowns work, [/quote] The load on the server was given not by hourly crowns, but by DDOS attacks. Your server is maintained by your specialists (or specialists hired by you) who should have seen this fact. But in their opinion, nothing strange happened. And so you decided that the watch crowns were to blame. Boxing is a constructor that you have the ability to customize, and the system does exactly what you configured. Hourly actions are called such because they will run once an hour. But if you set up an integration or something that takes more time to work out, then cron will run until everything is done. In your case, the cron worked for too long and the system restarted it after 4 hours (this is the logic of work). At the request of your manager that the hourly cron does not work, and there are no logs for working out import actions that are on a separate cron, it was determined that the script for processing import actions was REMOVED from the server, by whom and why it was removed, this is a question for those who serve your server. This script was restored and launched, and the watch cron was running at that time. This answer was given to the manager of SheBo on Friday 10/12/2021 11:52 AM. To an additional question, (asked on 12/10/2021, Friday, 13:31) - "what does the hourly kroner take so long?" - the answer was given (absolutely free 12/10/2021, Friday, 13:56) that cron will connect to this host: yavshoke.ua:38232->ec2-35-156-180-29.eu-central-1.compute.amazonaws.com:https We also do not know what external integrations you have, and what external resources store data on Amazon. Now hourly cron runs in 2,054.63 s (~ 34 minutes). We do not monitor client servers, we do not know what has changed. We can only see what is happening on the server at the moment we look at it.

There was no DDOS attack and there was no close, the SheBo manager reported that the problem was with the watch crown. But the SheBo integrator could not find the problem for us, I wrote the whole day on Fri 10.12., the integrator Igor Susyak, helped to solve the issue quickly on Sun 12.12, thank you very much! The problem was with the watch cron, we went through all the actions of the watch cron together, now it works because the "Translate product fields into the specified language" action is disabled, it did not work with the cron action enabled and restarted after 4-5 hours. We haven't made any changes to the settings of the "Translate product fields into the specified language" action, and we've had improvements to this action for a long time. The next step is to find out why cron does not work with the action enabled (key, if you can check what the problem is, I will be grateful for any help.

[quote] Tasun Sergey Vladimirovich OneBox production wrote: Apparently it takes more than 4 hours to complete all your settings. [/quote] I wrote in what action there was a problem and this has already been confirmed, do not write such nonsense, please. [quote] Susyak Igor Integrator Integrator.com.ua wrote: Anton, since your power supply is not yet disabled, you can correct ssh access to the server at info@integrator.com.ua, I'll try to clarify [/quote] Thanks again for your help, issue closed.

[quote] Mordach Anton Vladimirovich wrote: I wrote in what action there was a problem and this has already been confirmed, do not write such nonsense, please. [/quote] The nonsense is that in any of your service, you are trying to shift it to someone ....

[quote] Tasun Sergey Vladimirovich OneBox production wrote: The nonsense is that in any of your service, you are trying to shift it to someone .... [/quote] We did not try to shift the complexity to anyone, we have TP, they did not solve the issue and we turned to the forum. As a result, in one action, a complete freeze occurred on the watch crown, we wrote in which one. Using the brute-force method (disabled all actions and turned them on in turn), we found in which action there was a problem. When it was on, nothing else was running, the hourly cron would freeze and restart after 5 hours, and in normal mode it works for us up to 30 minutes.