Aggregated post are marked as "created locally"

.. and BTW: I have the same problem on several sites, all running on the same server: FastCGI, PHP Version 5.3.2, MySQL version 5.0.96 – (Hostgator VPS server)…

Peter

…If it can help, I enabled the debug to see the post metadata in “Edit Post”.

For a syndicated post, wrongly defined as “created locally”, I get the following:

ID: 	2645602886
GUID: 	https://allafrica.com/stories/201212240538.html
Custom Fields
_edit_lock: 1356443240:1

For a syndicated post, correctly stored, this is the metadata

ID: 	2645602884
GUID: 	https://www.voanews.com/content/india-prime-minister-appeals-calm/1570710.html
Custom Fields
enclosure: https://gdb.voanews.eu/9C7CA086-ED65-4407-9EFA-D4D1FDBFB764_cx0_cy0_cw0_w800_r1.jpg?nocache=1
3123
image/jpeg
syndication_source: aidnews
syndication_source_uri: https://pipes.yahoo.com/pipes/pipe.info?_id=4e203c7a0de5d4476986c85747776c83
syndication_source_id: https://pipes.yahoo.com/pipes/pipe.run?_id=4e203c7a0de5d4476986c85747776c83&_render=rss
syndication_feed: https://pipes.yahoo.com/pipes/pipe.run?_id=4e203c7a0de5d4476986c85747776c83&_render=rss
syndication_feed_id: 8
syndication_permalink: https://www.voanews.com/content/india-prime-minister-appeals-calm/1570710.html
syndication_item_hash: 76f905b2618d311ef4e78a2ed6f204a3
_edit_lock: 1356443408:1

So it looks like the metadata for the wrongly syndicated post, is not written (or not the write was not completed)

Any help on where to look what the problem is? PHP timeout for write operations?

After quite a bit of debugging, it seems the MySQLserver was very busy
and gave timeouts when FWP was aggregating posts.

The strange thing is that the posts themselves are stored correctly, but there is no metadata for it.

@radgeek: would it be reasonable to suggest FWP does an error check, and when an error occurs when aggregating the post, the post itself is not stored at all, rather than stored “incorrectly”? i.e. do an error check if the metadata for the post is stored correctly?