EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #09324
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] Reindex errors
- To: <eprints-tech@ecs.soton.ac.uk>, James Kerwin <jkerwin2101@gmail.com>
- Subject: Re: [EP-tech] Reindex errors
- From: David R Newman <drn@ecs.soton.ac.uk>
- Date: Tue, 30 May 2023 16:47:09 +0100
Hi James,
I think the GitHub issue and commit you found should fix the
issue you reported, that was my intention when I made the change.
With regards to the other error:
Internal Error: xref num 779 not found but needed, try to
reconstruct<0a>
I think this may be fixed by
https://github.com/eprints/eprints3.4/issues/310
Regards
David Newman
On 30/05/2023 16:41, James Kerwin via
Eprints-tech wrote:
CAUTION: This e-mail originated outside the University of Southampton.Found this:
With this solution:
My indexing.pl 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@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
*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/
- References:
- [EP-tech] Reindex errors
- From: James Kerwin <jkerwin2101@gmail.com>
- Re: [EP-tech] Reindex errors
- From: James Kerwin <jkerwin2101@gmail.com>
- [EP-tech] Reindex errors
- Prev by Date: Re: [EP-tech] Reindex errors
- Next by Date: Re: [EP-tech] distinguish the name of the author even though different people
- Previous by thread: [EP-tech] EPrints/CRIS
- Next by thread: [EP-tech] DOI handling in orcid_support_advance
- Index(es):