I got about 15 pages of php error messages in my log similar to this. I've posted the last one

Duplicate entry 'admin/build/panels/layouts/list/%/revert' for key 1 query: INSERT INTO menu_router (path, load_functions, to_arg_functions, access_callback, access_arguments, page_callback, page_arguments, fit, number_parts, tab_parent, tab_root, title, title_callback, title_arguments, type, block_callback, description, position, weight, file) VALUES ('admin/build/panels/layouts/list/%/revert', 'a:1:{i:5;a:1:{s:21:\"ctools_export_ui_load\";a:1:{i:0;s:14:\"panels_layouts\";}}}', '', 'ctools_export_ui_task_access', 'a:3:{i:0;s:14:\"panels_layouts\";i:1;s:6:\"revert\";i:2;i:5;}', 'ctools_export_ui_switcher_page', 'a:3:{i:0;s:14:\"panels_layouts\";i:1;s:6:\"delete\";i:2;i:5;}', 125, 7, '', 'admin/build/panels/layouts/list/%/revert', 'Revert', 't', '', 4, '', '', '', 0, 'sites/all/modules/ctools/includes/export-ui.inc') in /home/glumboco/public_html/new/includes/menu.inc on line 2460.

The only problem I see with the site now is that one of the views isn't displaying a field. What can I do to fix this view and what is the problem exactly?

Comments

vradul’s picture

for the first time, yesterday - multiple pages of:

Duplicate entry 'admin/build/panels/layouts/list/%/revert' for key 1 query: INSERT INTO menu_router (path, load_functions, to_arg_functions, access_callback, access_arguments, page_callback, page_arguments, fit, number_parts, tab_parent, tab_root, title, title_callback, title_arguments, type, block_callback, description, position, weight, file) VALUES ('admin/build/panels/layouts/list/%/revert', 'a:1:{i:5;a:1:{s:21:\"ctools_export_ui_load\";a:1:{i:0;s:14:\"panels_layouts\";}}}', '', 'ctools_export_ui_task_access', 'a:3:{i:0;s:14:\"panels_layouts\";i:1;s:6:\"revert\";i:2;i:5;}', 'ctools_export_ui_switcher_page', 'a:3:{i:0;s:14:\"panels_layouts\";i:1;s:6:\"delete\";i:2;i:5;}', 125, 7, '', 'admin/build/panels/layouts/list/%/revert', 'Revert', 't', '', 4, '', '', '', 0, 'sites/all/modules/ctools/includes/export-ui.inc') in /home/antem0/public_html/includes/menu.inc on line 2460.

Anyone have any ideas? I don't seem to be missing any views fields.

I had previously, on January 29, applied patch: http://drupal.org/files/issues/147000-protect-rebuild-81-D6.patch to install.php, NEW includes/lock-install.inc, includes/module.inc, and modules/system/system.module to fix other duplicate entry errors in logs.

This new duplicate entry error was not appearing before I applied the patch. Installation is Drupal 6.20 (upgrade from 5.23) Acquia-Prosper, with Panels 3 and various other contrib modules.

Possibly unrelated - I had to truncate 'sessions' table yesterday (before this error appeared), to be able to import database dump into wamp server.

jan_v’s picture

have you looked for existing issues regarding the modules in the watchdog messages?

vradul’s picture

There are none specific to any module... although I also get reams of page not founds for things that were in my old theme (which no longer exists in any folders)

Some I assume would be from people whose browser caches haven't cleared - but I also get them from myself..... so I'm assuming there is leftover crap in the database related to the old theme, and I'm slowly trying to find it and remove it

vradul’s picture

Went to import another database dump into my wamp server, and the import died again - duplicate primary key in 'search_index'.

Backed up search_index, truncated it, dumped the DB again, and it imported with no problem.

...

Also found 2 records in table 'variable' for name:'theme_addari_settings' and 'theme_framework_settings' - I had removed both themes during my upgrade. Deleted the two records in 'variable' and we'll see if my own page not founds referencing those themes stop now...

jan_v’s picture

Yes. Before you import a db script, you should exclude (or truncate ) search_index and all the cache tables. These tables can cause "duplicate entry" errors with the import.
Also if you clear cache before dumping an sql-file, it could be just half the size or less then a dump with cache records.

vradul’s picture

What about the other search_ tables? search_dataset, search_node_links, and search_total? Ok to clear those as well?

jan_v’s picture

It's ok to truncateall the search_* tables, but you'll lose your search records and search history. Also drupal has to re-index your site for accurate search results (happens in cron).

I usually only clear cache tables.

But this is way off the original post, isn't it? :p sorry.

vradul’s picture

At this point I'm not sure that it isn't all related to the duplicate entry problem.

Thanks for your help, though.

zazinteractive’s picture

For me I just rebuilt the view that was causing problems and everything seems to be ok now

BigEd’s picture

I recently had the same, to reolve it I removed the panels dicpalying the views.

I rebuilt the search index and ran cron till it was back up again.

It turned out I had put some duplicate php into the head secton in the same view.