[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] Reindex errors



CAUTION: This e-mail originated outside the University of Southampton.
Found this:

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feprints%2Feprints3.4%2Fissues%2F247&data=05%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Ca7ea08db6c08488b0f4d08db61245498%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638210580883833034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Xq60BoEL4heRNEHVrf1CShxYAwRyLf7Zcb9cNHV9ZaI%3D&reserved=0

With this solution:

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feprints%2Feprints3.4%2Fcommit%2F5e9826c41c8990c5053b1cff53d7f7ef76194365&data=05%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Ca7ea08db6c08488b0f4d08db61245498%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638210580883833034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=A8mODKoNovFrRyEwcrKoa8FG2j81C%2B7SXLM8AblnV88%3D&reserved=0

My indexing.pl<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Findexing.pl%2F&data=05%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Ca7ea08db6c08488b0f4d08db61245498%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638210580883833034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oUrd%2FK8UfVClOdQBiz4xDaDBZfQkRWvg6kEwlMHcRHk%3D&reserved=0> file isn't quite the same, but I get the general idea. In case it's helpful to anyone else.

Thanks,
James

On Tue, May 30, 2023 at 3:51?PM James Kerwin <jkerwin2101 at gmail.com<mailto:jkerwin2101 at gmail.com>> wrote:
Hi All,

Wondering if anyone can lend me some knowledge. Crawling towards the end of my test repository server upgrade. Managed to import the MySQL database after some fussing about.

Doing a reindex of the eprint dataset. Got a few missing phrase errors which is quite helpful.

Got this one twice that I've no idea about:

 Internal Error: xref num 779 not found but needed, try to reconstruct<0a>

A quick Google suggests it's something to do with PDFs? Should I be worried?

This one has appeared a lot:

DBD::mysql::st execute failed: Data too long for column 'word' at row 1 at /opt/eprints3/bin/../perl_lib/EPrints/Database.pm line 1283.

It looks as though the column "word" appears in:

document__rindex
eprint__rindex
request__rindex
saved_search__rindex
subject__rindex
user__rindex

In the eprint__rindex table the "word" column is varchar(128). I imagine if I change the length/type this error might go away. Is this the correct thing to do or is it a sign of something more serious?

As this is my Test server it's a dry run for the Live server upgrade and I don't want to just ignore errors. The Live upgrade will need to be a much quicker affair and have as few delays as possible.

Thanks,
James


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20230530/e08b3d0a/attachment-0001.html