tblerrorlog filling up with errors after update

[Faizal1]

Hi there,

Every 5 mins when the cron runs  tblerrorlog is filling up with the errors shown in the image. Just wondering what's causing it?

Thanks

[WHMCS John]

Hi @Faizal1,

Whilst a PHP warning doesn't typically cause a functional problem, it would be good to get to the bottom of them.

Can you please share the fill contents of the message field please?

[Faizal1]

1 hour ago, WHMCS John said:

Hi @Faizal1,

Whilst a PHP warning doesn't typically cause a functional problem, it would be good to get to the bottom of them.

Can you please share the fill contents of the message field please?

Sure: 

session_start(): Cannot start session when headers already sent

array_key_exists() expects parameter 2 to be array, null given

session_name(): Cannot change session name when headers already sent

session_set_cookie_params(): Cannot change session cookie parameters when headers already sent

Edited October 5, 2020 by Faizal1

[Faizal1]

Ok so out of curiosity since it was filling the log every 5 mins since the upgrade I decided to check the cron command listed in the automation status and it was different from the one we have always used. Copied that command over and the errors seem to have stopped and automation status still looks good. Could that have been it? Had over 5000  entries since the upgrade so nice to see them stopped. 

Also, are we ok to go ahead and empty  old tblerrorlog entries?

Thanks for all your help

Edited October 5, 2020 by Faizal1

[WHMCS John]

Hi @Faizal1,

I'm glad you were able to resolve the error.

In v8.0.2 we've implemented automated pruning of the table, so it will not exceed 10K rows. You should not need to manually empty this table once the update is applied.

[wsa]

Well i still see alot them everyday 

[zomex]

We are also seeing the same issue in v8.0.2

[carl^]

We're seeing a lot of these too, there really needs to be a way to control what is logged as buggy modules cause performance issues.

[carl^]

This causes quite a bit of performance overhead, we see up-to a dozen MySQL inserts per second, check yours:

```
MariaDB [whmcs]> select (select created_at from tblerrorlog order by created_at desc limit 1) as start, (select created_at from tblerrorlog order by created_at asc limit 1) as end, (select created_at from tblerrorlog order by created_at desc limit 1)-(select created_at from tblerrorlog order by created_at asc limit 1) as seconds, (select count(*) from tblerrorlog) as totalrows;
+---------------------+---------------------+---------+-----------+
| start               | end                 | seconds | totalrows |
+---------------------+---------------------+---------+-----------+
| 2020-12-30 09:54:32 | 2020-12-30 09:38:33 |    1599 |     14005 |
+---------------------+---------------------+---------+-----------+
1 row in set (0.02 sec)
```

[carl^]

WHMCS replied to a ticket:

> However there are some issues in version 8.0.4 that can cause it to not function as expected, that have since been resolved in version 8.1.0 and updating should resolve this going forward.

[Surc0uf]

Hello,

 

I'm still getting theses error on WHMCS 8.1.3, (PHP 7.4.16)...

I have update my cron job to fit exaclty what whmcs automation says (starting by /usr/bin/php -q ...)

Are u able to fix this ? ( @carl^, @zomex, @wsa)

Thank you.

 

[ithaki]

Has anyone come up with a solution to this problem as we have just upgraded to version 8.1 and whmcs almost comes to a standstill in the clients client area. 
Way too many of these "tblerrorlog filling up with errors after update"