I have just upgraded from 4.7 to 5.1 (no problems upgrading) and I noticed that when creating new nodes their NID has started from 1 again, and drupal is overwriting my existing nodes with no alert or error message. seems like the NID counter has been reset. any clue?

Comments

steko’s picture

steko commented

I looked again at this problem, that is blocking the use of the site. These are the error logs related to the problem. These nodes haven't been overwritten, but their creation has not been executed due to the duplicate.

Duplicate entry '5' for key 1 query: INSERT INTO drupal_node_comment_statistics (nid, last_comment_timestamp, last_comment_name, last_comment_uid, comment_count) VALUES (5, 1172167084, NULL, 1, 0) in /home/mhd-01/www.iosa.it/htdocs/www/includes/database.mysql.inc on line 172.

Duplicate entry '5' for key 1 query: INSERT INTO drupal_node_revisions (nid, vid, title, body, teaser, timestamp, uid, format, log) VALUES (5, 5, 'Cleanup', 'The site has undergone a minor tuning.', 'The site has undergone a minor tuning.', 1172167084, 1, 1, '') in /home/mhd-01/www.iosa.it/htdocs/www/includes/database.mysql.inc on line 172.

Duplicate entry '5-5' for key 1 query: INSERT INTO drupal_node (nid, vid, title, type, uid, status, created, changed, comment, promote, sticky) VALUES (5, 5, 'Cleanup', 'blog', 1, 1, 1172167084, 1172167084, 2, 0, 0) in /home/mhd-01/www.iosa.it/htdocs/www/includes/database.mysql.inc on line 172.

Hope that helps understanding where my problem is. I'm trying with http://drupal.org/node/69722 this way.

steko’s picture

steko commented

http://drupal.org/node/69722 Duplicate entry error

this solves my problem. But I guess the bug itself still exists..

alpritt’s picture

alpritt commented
Status: Active » Fixed

Since Drupal 6 the sequences table is deprecated, so this should no longer be an issue.

gpk’s picture

gpk commented

It could still be an issue in 5.x, which is still supported ... except that I did not encounter this problem upgrading from 4.7 to 5.1. Looks like the {sequences} table must have been damaged or did not import properly.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.