EPrints Technical Mailing List Archive

Message: #07524

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] duplicate key value violates unique constraint "event_queue_pkey"



Hi Thomas

Thank you for your input.  The "2019," error had been resolved as it was a wrong syntax we had in the document default pl file.

My question "could it be caused because we are using Postgresql instead of Mysql? " Is referring to the below error we are continuesly receiving in the error logs when we create a new item:

ERROR:  duplicate key value violates unique constraint "event_queue_pkey" 
DETAIL:  Key (eventqueueid)=(e9210339587b3507d2bdafc95a238a39) already exists. at /opt/eprints3/perl_lib/EPrints/Database.pmline 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.pmline 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 another event is created with 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 
Maher


____________________________________________________________
Hi Maher,

> could it be caused because we are using Postgresql instead of Mysql?
presumably not, because your error message
> Argument "2019," isn't numeric in sprintf at /opt/eprints3/perl_lib/EPrints/MetaField/Date.pm line 56
indicates a bad date format: 2019,10,... (instead 2019-10-10)!?

As already assumed by Karl this is caused by your input or a misconfigured localization.

Hth
Thomas
*** Options: https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=""> *** Archive: https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=""> *** EPrints community wiki: https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=""> *** EPrints developers Forum: https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url="">