Support Forum

Simple:Press 6 General Topics

Duplicate Entry Errors in SP Logs

Duplicate Entry Errors in SP Logs

jim

Here and Now

Member

Pro Subscribers

Offline

Mar 19, 2015 - 2:05 pm

SP Admin: Toolbox - Error Log

Errors should be reported to Simple:Press support as they may effect the proper behaviour of your forum...

Troubleshooting recent site performance issues, I just discovered the following in our SP Error log...

16 February 2015 9:53 pm | spaErrError | 1 | database

file: /problem-with-post-edit-buttonome/tripawds/public_html/wp-content/plugins/simple-press/sp-startup/forum/sp-forum-framework.php

line: 450

function: sp_move_post

error: Duplicate entry '10978' for key 'PRIMARY'

UPDATE wp_1_sfwaiting SET forum_id=15, topic_id=10978 WHERE post_id=141917

And...

18 March 2015 8:32 pm | spaErrError | 17 | database

file: /problem-with-post-edit-buttonome/tripawds/public_html/wp-content/plugins/simple-press/forum/content/classes/sp-group-view-class.php

line: 248

function: sp_add_cache

error: Duplicate entry '0*group' for key 'PRIMARY'

INSERT INTO wp_1_sfcache(cache_id, cache_out, cache) VALUES...

We have numerous other getimagesize() warnings, and a bunch of other notices, but I thought I would share the error as suggested in the dashboard. Please advise if any further info is required or if I should take any action to troubleshoot or resolve.

Thanks!

Simple:Press powers the Tripawds Discussion Forums.

It's better to hop on three legs than to limp on four.

The Tripawds Blogs Community is made possible by The Tripawds Foundation.

Yellow Swordfish

Glinton, England

SP Master

Offline

Mar 19, 2015 - 5:00 pm

Ha! the first one makes no sense at all which means I will have to look into it smile

The other one is, I think, finally resolved in the next update (5.5.5).

The good news is that neither should have any adverse effect on anything.

And thanks for the information.

YELLOW

SWORDFISH

jim

Here and Now

Member

Pro Subscribers

Offline

Mar 19, 2015 - 6:35 pm

Thanks for the quick feedback!

That first one (wp_1_sfwaiting) only caught my eye since the sysadmin reviewing our server logs in an attempt to identify the cause of load spikes mentioned an, "excessive TIME_WAIT connection to Apache port 80."

Perhaps totally unrelated, I know.

Simple:Press powers the Tripawds Discussion Forums.

It's better to hop on three legs than to limp on four.

The Tripawds Blogs Community is made possible by The Tripawds Foundation.