EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #07503
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] duplicate key value violates unique constraint "event_queue_pkey"
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] duplicate key value violates unique constraint "event_queue_pkey"
- From: Maher Abdellatif Ahmad Qahwash <qahwash@kfupm.edu.sa>
- Date: Mon, 1 Oct 2018 13:59:43 +0000
Hi We have installed the latest ePrints 3.4 with Postgresql 9.4 , adding a new item to the repository works fine but we are receiving this error continuously in the logs: ERROR: duplicate key value violates unique constraint "event_queue_pkey" DETAIL: Key (eventqueueid)=(e9210339587b3507d2bdafc95a238a39) already exists. at /opt/eprints3/perl_lib/EPrints/Database.pm line 1387. EPrints::Database::add_record('EPrints::Database::Pg=HASH(0x55aa5922a478)', 'EPrints::DataSet=HASH(0x55aa57023030)', 'HASH(0x55aa592f77c8)') called at /opt/eprints3/perl_lib/EPrints/DataObj.pm line 294 EPrints::DataObj::create_from_data('EPrints::DataObj::EventQueue', 'EPrints::Repository=HASH(0x55aa55a83468)', 'HASH(0x55aa592f72d0)', 'EPrints::DataSet=HASH(0x55aa57023030)') called at /opt/eprints3/perl_lib/EPrints/DataObj/EventQueue.pm line 109 EPrints::DataObj::EventQueue::create_unique('EPrints::DataObj::EventQueue', 'EPrints::Repository=HASH(0x55aa55a83468)', 'HASH(0x55aa592f72d0)') called at /opt/eprints3/perl_lib/EPrints/DataObj/EPrint.pm line 534 EPrints::DataObj::EPrint::update_triggers('EPrints::DataObj::EPrint=HASH(0x55aa59246210)') called at /opt/eprints3/perl_lib/EPrints/DataObj/EPrint.pm line 1013 EPrints::DataObj::EPrint::commit('EPrints::DataObj::EPrint=HASH(0x55aa59246210)') called at /opt/eprints3/perl_lib/EPrints/Workflow/Stage.pm line 221 EPrints::Workflow::Stage::update_from_form('EPrints::Workflow::Stage=HASH(0x55aa5926a530)', 'EPrints::ScreenProcessor=HASH(0x55aa5922e510)') called at /opt/eprints3/perl_lib/EPrints/Workflow.pm line 401 EPrints::Workflow::update_from_form('EPrints::Workflow=HASH(0x55aa592ee8e8)', 'EPrints::ScreenProcessor=HASH(0x55aa5922e510)') called at /opt/eprints3/perl_lib/EPrints/Plugin/Screen/EPrint/Edit.pm line 189 EPrints::Plugin::Screen::EPrint::Edit::action_next('EPrints::Plugin::Screen::EPrint::Edit=HASH(0x55aa5914bc58)') called at /opt/eprints3/perl_lib/EPrints/Plugin/Screen.pm line 240 EPrints::Plugin::Screen::from('EPrints::Plugin::Screen::EPrint::Edit=HASH(0x55aa5914bc58)') called at /opt/eprints3/perl_lib/EPrints/Plugin/Screen/EPrint/Edit.pm line 117 EPrints::Plugin::Screen::EPrint::Edit::from('EPrints::Plugin::Screen::EPrint::Edit=HASH(0x55aa5914bc58)') called at /opt/eprints3/perl_lib/EPrints/ScreenProcessor.pm line 316 EPrints::ScreenProcessor::process('EPrints::ScreenProcessor', 'session', 'EPrints::Repository=HASH(0x55aa55a83468)', 'template', undef, 'url', '/cgi/users/home') called at /opt/eprints3/cgi/users/home line 25 ModPerl::ROOT::ModPerl::Registry::opt_eprints3_cgi_users_home::handler('Apache2::RequestRec=SCALAR(0x55aa5445a690)') called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 207 eval {...} called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 207 ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x55aa592206f8)') called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 173 ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x55aa592206f8)') called at /usr/lib64/perl5/vendor_perl/ModPerl/Registry.pm line 32 ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x55aa5445a690)') called at -e line 0 eval {...} called at -e line 0 doing a query in the "event_queue" with the same (eventqueueid)=(e9210339587b3507d2bdafc95a238a39) shows that the pluginid is "Event::RDF" and is "waiting". It seems other events for some reason are trying to use the same (eventqueueid)=(e9210339587b3507d2bdafc95a238a39) which results in the "ERROR: duplicate key value violates unique constraint "event_queue_pkey" Thank you for your suggestions to solve this issue. Thanks
- Follow-Ups:
- [EP-tech] duplicate key value violates unique constraint "event_queue_pkey"
- From: Maher Abdellatif Ahmad Qahwash <qahwash@kfupm.edu.sa>
- [EP-tech] duplicate key value violates unique constraint "event_queue_pkey"
- References:
- [EP-tech] duplicate key value violates unique constraint "event_queue_pkey"
- From: Maher Abdellatif Ahmad Qahwash <qahwash@kfupm.edu.sa>
- [EP-tech] duplicate key value violates unique constraint "event_queue_pkey"
- Prev by Date: Re: [EP-tech] Restricting access to CGI Scripts
- Next by Date: [EP-tech] download report for each user
- Previous by thread: [EP-tech] EPrints/CRIS
- Next by thread: [EP-tech] DOI handling in orcid_support_advance
- Index(es):