Anyone observed high server load these days?

[datakick]

Hi everyone,

we just had a support request related to high server load. Looks like there is a potential for infinite loop. That can have quite negative impact on server performance.

This issue is actually not a bug in the thirty bees core. It looks like a bug in PHP itself, and only for some combinations of PHP and server time zones. I was able to reproduce the issue on PHP7, time zone US/Central. Not reproducible on PHP8 US/Central, or on PHP7 Europe/Prague.

The issue is related to adding time interval to \DateTime object shortly before the Daylight Saving Time threshold.

https://github.com/thirtybees/thirtybees/issues/1569

Just to be sure, you can look into your database:

SELECT from_unixtime(last_execution), from_unixtime(last_checked) FROM tb_scheduled_task;

if any of the returned datatime is around the DST threshold, your server is probably affected.

To fix this, simply update all scheduled tasks:

UPDATE tb_scheduled_task SET last_checked = UNIX_TIMESTAMP(), last_execution = UNIX_TIMESTAMP();

[wakabayashi]

28 minutes ago, datakick said:

SELECT from_unixtime(last_execution), from_unixtime(last_checked) FROM tb_scheduled_task;

This table does not exist for me 🙃

#1146 - Tabelle 'tb_scheduled_task' existiert nicht

And core updater doesn't show anything wrong under "database".

Edited November 29, 2022 by wakabayashi

[datakick]

table should exists since 1.3.0

[wakabayashi]

Maybe other merchants can check, if they have it. 🤔

[datakick]

of course, db prefix can be different:

<PREFIX>scheduled_task

 

[wakabayashi]

30 minutes ago, datakick said:

of course, db prefix can be different:

<PREFIX>scheduled_task

 

Man it's not my day. 🤕 Sorry! Yeah it's there with the right prefix - obviously.

Looks clean, right?

[datakick]

Looks good. Congrats, you are not affected 🙂