How to restore the work of actions on the minute crown after problems with the server "DDoS attack on VPS servers"

Good afternoon. If nothing is done, the minute cron will automatically start after 90 minutes from the start of the previous one.

Ok, thanks for the answer to the second question, please also answer the first question "1. I understand correctly that in order for the actions to start working again, you need to go to the ..../cron/ directory and delete the file with the PID extension there or you need is there anything else to do to start the functions?

Good afternoon. According to claim 1, that's right. For one thing, check in memory if the script remains there, if it remains, then delete it too. But you need to be sure that at this time the script does nothing (something planned that just works out for a long time, unloading, mass mailing of letters ...). On Saturday, the cron remained in memory, apparently due to the attack, the connection to the external service was in the installed state but no data was transmitted.

[quote] Tasun Sergey Vladimirovich Employee wrote: Good afternoon. According to claim 1, that's right. For one thing, check in memory if the script remains there, if it remains, then delete it too. But you need to be sure that at this time the script does nothing (something planned that just works out for a long time, unloading, mass mailing of letters ...). On Saturday, the cron remained in memory, apparently due to the attack, the connection to the external service was in the installed state but no data was transmitted. [/quote] OK thanks And what is the risk of not deleting the script from memory "is there a script left in memory, if it remains, then delete it too", that is, if the PID file was deleted, but the script is not in memory, then what can this result in?

You do not know for what reason the script takes a long time and what it uses to work. Removing a script from memory is, in fact, stopping the program code, this will release everything that the script interacted with and kept open (files, connections, transactions...)

[quote] Tasun Sergey Vladimirovich Employee wrote: You do not know for what reason the script takes a long time and what it uses to work. Removing a script from memory is, in fact, stopping the program code, this will release everything that the script interacted with and kept open (files, connections, transactions...) [/quote] I have another question Everything stopped, I went in and deleted the PID file The script remains in memory What will happen next, he will live there forever or he will cease to exist immediately after the actions on the minute crone start and form a new launch of this script, or 2 scripts will live in memory (new and old)

[quote] Tasun Sergey Vladimirovich Employee wrote: If you don't remove the script, two will live. [/quote] Do you think it would be logical to "kill" the old script when starting the script, or is this a moot point?

In suggesting this solution, you are guided by the fact that cron runs less than a minute, but if you want to upload or send emails (just as an example), this will cause the cron to take more than a minute to complete. And your suggestion to "kill" the old script doesn't make any sense. You don't know why the script is running for a long time.

[quote] Tasun Sergey Vladimirovich OneBox production wrote: Good afternoon. If nothing is done, the minute cron will automatically start after 90 minutes from the start of the previous one. [/quote] Good afternoon! 1. You wrote earlier that "it will start in 90 minutes" but it didn't start, the fine cron started at 20:08, I went to "/cron/" at 23:35 and there the cron-minute PID file is why the fine cron did not start after 90 hours, tobto approximately at 22:00 ? 2. [quote] Tasun Sergey Vladimirovich OneBox production wrote: If you don't remove the script, two will live. [/quote] 2. So I’ll get the script from the memory more easily (it’s not clear how to know the script) so you can fix the problem in this way, reboot the server, and then get the PID file (to reboot by logical fault, clear the memory of the script , and the PID file is checked by the logic to run the cron) ?