Jump to content
Sign in to follow this  
Faizal1

tblerrorlog filling up with errors after update

Recommended Posts

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

error database.png

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites
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 by Faizal1

Share this post


Link to post
Share on other sites

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 by Faizal1

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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)
```

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated