I cannot get the multi_node_add to work with more than 2 or 3 nodes. Consistently only one or at most two nodes are added to the node table. seems to be the last one created that wins. EG attempting to create six nodes with titles A B C D E F, the watchdog reports

page not found 08/08/2015 - 17:55 multi_node_add/status/timesheet/42731
page not found 08/08/2015 - 17:55 multi_node_add/status/timesheet/42727
content 08/08/2015 - 17:55 timesheet: added E
content 08/08/2015 - 17:55 timesheet: added D.
content 08/08/2015 - 17:55 timesheet: added F.
page not found 08/08/2015 - 17:55 multi_node_add/status/timesheet/42728
page not found 08/08/2015 - 17:55 multi_node_add/status/timesheet/42730
content 08/08/2015 - 17:55 timesheet: added B.
page not found 08/08/2015 - 17:55 multi_node_add/status/timesheet/42729
content 08/08/2015 - 17:55 timesheet: added A.
content 08/08/2015 - 17:55 timesheet: added C.

The node table has
| 42726 | 171613 | An earlier node | 1439016622 |
| 42732 | 171619 | E | 1439020520 |

I see messages 'Timesheet A has been created' for titles A,B,C,D. These messages are generated by node_form_submit
so its generated the node but then I get a page not found error and the status page tries to load.

No error messages in the system logs, initially there were lockout errors but thats no longer happening since increasing the lockout_timeout to 180. Node table is a mysql innodb type.

Given the only nid number present is the last one created it appears the quick creation overwrites the data?
Or is the db lockout still happening, no retry, failing silently and rolling the transaction back?

Has anyone experienced this? Surely most uses of the this module would be creating more than a few nodes?

Thoughts as to where to look to resolve this?

Comments

Louis Delacretaz created an issue. See original summary.

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Status: Active » Postponed (maintainer needs more info)

It would be good to see other error reports for this, I successfully test the module with 10+ nodes. Potentially other contributed modules play role in such errors too.
So if anyone encounters such issues, a list of activated modules would be helpful, also the field list of the given content-type.