EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #10398
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] after Upgrade to 3.4.7: unknown UUID requested
- To: Thomas Lauke <th.lauke@arcor.de>, <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] after Upgrade to 3.4.7: unknown UUID requested
- From: David R Newman <drn@ecs.soton.ac.uk>
- Date: Thu, 30 Jul 2026 14:27:29 +0100
Hi Thomas, I believe it should be sufficient just to do an EPrints database update: EPRINTS_PATH/bin/epadmin update ARCHIVE_IDSubstituting EPRINTS_PATH and ARCHIVE_ID, as appropriate. I would also reload Apache and the EPrints indexer. However, the reason you got this error is likely due to Apache being reloaded after you upgraded to 3.4.7 but had not updated the database. Reloading Apache and the EPrints indexer together is good practice after an upgrade, to make sure they are running the same code and configuration.
If this does not fix your issue. Please take a look at the known issues section for EPrints 3.4.7 - https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FEPrints_3.4.7%23Known_Issues&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C1428fd1ffcb041f5999008deee3e4e38%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C639210148520062442%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=FlZjkszI4RaAHrgVfWBR3j6QBu2PLLpY6qfDyV09ADk%3D&reserved=0 ; There is an issue relating to UUIDs for search caches but not the error message is not the same as yours. Also, this issue should not impact users, it just might appear regularly in the Apache error log, which may be a concern to system admins.
For background, This issues relates to [1] which changes the ID used to recover caches of previous searches from an auto-incremented ID to a UUID, so they cannot be guessed. This is mainly to ensure privacy of search results but also adding capability that may allow EPrints to better handle bots that make lots of search requests using an existing search ID, as they are reusing URLs they discovered on a previous pass of your EPrints repository.
Regards David Newman [1] https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feprints%2Feprints3.4%2Fissues%2F465&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C1428fd1ffcb041f5999008deee3e4e38%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C639210148520115791%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=44jYUeqF7VLg%2FBsouebconYmozmUfMih1xO3k6II22w%3D&reserved=0 On 30/07/2026 11:55, Thomas Lauke wrote:
CAUTION: This e-mail originated outside the University of Southampton. CAUTION: This e-mail originated outside the University of Southampton. Hi folks, when searching for some users with http://.../cgi/users/home?screen=Staff%3A%3AUserSearch&name_merge=ALL&name=&username=&userid=&dept%2Forg_merge=ALL&dept%2Forg=&address%2Fcountry_merge=ALL&address%2Fcountry=&usertype=user&email=&satisfyall=ALL&order=name%2Fjoined&_action_search=Suchen I received following error messages: DBD::mysql::st execute failed: Unknown column 'uuid' in 'SET' at /usr/share/eprints/perl_lib/EPrints/Database.pm line 1196. UPDATE `cachemap` SET `uuid`=?, `oneshot`=?, `created`=?, `userid`=?, `searchexp`=?, `lastused`=? WHERE `cachemapid`='6696': 1054 at /usr/share/eprints/perl_li b/EPrints/Database.pm line 1086. EPrints::Database::update(EPrints::Database::mysql=HASH(0x55db176460c8), EPrints::DataSet=HASH(0x55db15b60410), HASH(0x55db176297b0), HASH(0x55db176297 b0)) called at /usr/share/eprints/perl_lib/EPrints/Database.pm line 1914 EPrints::Database::add_record(EPrints::Database::mysql=HASH(0x55db176460c8), EPrints::DataSet=HASH(0x55db15b60410), HASH(0x55db176297b0)) called at /us r/share/eprints/perl_lib/EPrints/DataObj.pm line 317 EPrints::DataObj::create_from_data("EPrints::DataObj::Cachemap", EPrints::Repository=HASH(0x55db147350a0), HASH(0x55db17617560), EPrints::DataSet=HASH( 0x55db15b60410)) called at /usr/share/eprints/perl_lib/EPrints/DataObj/Cachemap.pm line 135 EPrints::DataObj::Cachemap::create_from_data("EPrints::DataObj::Cachemap", EPrints::Repository=HASH(0x55db147350a0), HASH(0x55db17617560), EPrints::Dat aSet=HASH(0x55db15b60410)) called at /usr/share/eprints/perl_lib/EPrints/DataSet.pm line 1013 EPrints::DataSet::create_dataobj(EPrints::DataSet=HASH(0x55db15b60410), HASH(0x55db17617560)) called at /usr/share/eprints/perl_lib/EPrints/DataSet.pm line 1007 EPrints::DataSet::create_object(EPrints::DataSet=HASH(0x55db15b60410), EPrints::Repository=HASH(0x55db147350a0), HASH(0x55db17617560)) called at /usr/s hare/eprints/perl_lib/EPrints/Search.pm line 1100 EPrints::Search::perform_search(EPrints::Search=HASH(0x55db176381d0)) called at /usr/share/eprints/perl_lib/EPrints/Plugin/Screen/AbstractSearch.pm lin e 127 EPrints::Plugin::Screen::AbstractSearch::run_search(EPrints::Plugin::Screen::Staff::UserSearch=HASH(0x55db175fb118)) called at /usr/share/eprints/perl_ lib/EPrints/Plugin/Screen/AbstractSearch.pm line 101 EPrints::Plugin::Screen::AbstractSearch::action_search(EPrints::Plugin::Screen::Staff::UserSearch=HASH(0x55db175fb118)) called at /usr/share/eprints/pe rl_lib/EPrints/Plugin/Screen.pm line 245 EPrints::Plugin::Screen::from(EPrints::Plugin::Screen::Staff::UserSearch=HASH(0x55db175fb118)) called at /usr/share/eprints/perl_lib/EPrints/Plugin/Scr een/AbstractSearch.pm line 295 EPrints::Plugin::Screen::AbstractSearch::from(EPrints::Plugin::Screen::Staff::UserSearch=HASH(0x55db175fb118)) called at /usr/share/eprints/perl_lib/EP rints/Plugin/Screen/Staff/UserSearch.pm line 63 EPrints::Plugin::Screen::Staff::UserSearch::from(EPrints::Plugin::Screen::Staff::UserSearch=HASH(0x55db175fb118)) called at /usr/share/eprints/perl_lib /EPrints/ScreenProcessor.pm line 358 EPrints::ScreenProcessor::process("EPrints::ScreenProcessor", "session", EPrints::Repository=HASH(0x55db147350a0), "template", undef, "url", "/cgi/user s/home") called at /usr/share/eprints/cgi/users/home line 43 ModPerl::ROOT::ModPerl::Registry::usr_share_eprints_cgi_users_home::handler(Apache2::RequestRec=SCALAR(0x55db17657210)) called at /usr/lib/x86_64-linux -gnu/perl5/5.40/ModPerl/RegistryCooker.pm line 207 eval {...} called at /usr/lib/x86_64-linux-gnu/perl5/5.40/ModPerl/RegistryCooker.pm line 207 ModPerl::RegistryCooker::run(ModPerl::Registry=HASH(0x55db17629420)) called at /usr/lib/x86_64-linux-gnu/perl5/5.40/ModPerl/RegistryCooker.pm line 173 ModPerl::RegistryCooker::default_handler(ModPerl::Registry=HASH(0x55db17629420)) called at /usr/lib/x86_64-linux-gnu/perl5/5.40/ModPerl/Registry.pm lin e 32 ModPerl::Registry::handler("ModPerl::Registry", Apache2::RequestRec=SCALAR(0x55db17657210)) called at -e line 0 eval {...} called at -e line 0 How to overcome this failure? Can someone point me to some helpful references? Thanks in advance Thomas *** Options: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FEprints-tech_Mailing_List&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C1428fd1ffcb041f5999008deee3e4e38%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C639210148520174783%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=agpR8ErhzCpQUEDljVPcFPUTfXkVT%2BeFc7ATN5RT79U%3D&reserved=0 *** Archive: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C1428fd1ffcb041f5999008deee3e4e38%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C639210148520227903%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=5jfOliYaxJSoo1RXHyGbb8WoZkwsADw2JeleoPFr0sU%3D&reserved=0 *** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C1428fd1ffcb041f5999008deee3e4e38%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C639210148520273012%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=5AdL%2FxtY6lppA%2FCMnI90ltmyBZ7ghX7Yd76mdJ9oOhY%3D&reserved=0
- References:
- [EP-tech] after Upgrade to 3.4.7: unknown UUID requested
- From: Thomas Lauke <th.lauke@arcor.de>
- [EP-tech] after Upgrade to 3.4.7: unknown UUID requested
- Prev by Date: [EP-tech] after Upgrade to 3.4.7: unknown UUID requested
- Next by Date: [EP-tech] anubis with eprints
- Previous by thread: [EP-tech] after Upgrade to 3.4.7: unknown UUID requested
- Next by thread: Re: [EP-tech] after Upgrade to 3.4.7: unknown UUID requested
- Index(es):
