-
Notifications
You must be signed in to change notification settings - Fork 2
Description
I have tried to import and index 5 Noark 5 extractions of the same arhival system, though different periods and parts.
They all fails at the end if indexing reporting "Could not find sphinx_index.conf" in \rapporter\yyyy\m\dd\nnnn\vedlegg.log
This error is experienced in all released versions:
- Piql Insight v1.0.0
- Piql Insight v1.1.0
- Piql Insigh v1.2.0-beta3
v1.0.0 does not report this as an error, while v1.1.0 and v1.2.0-beta3 says:
"Failed to start indexer! See import log for more detail."
Final part of vedlegg.log
pdftotext -nopgbrk -enc UTF-8 F:\arkiv-work...\vedlegg\0000037731.txt: OK
Starter indeksering: index.cmd .\rapporter\2022\3\11\115000\ .\rapporter\2022\3\11\115000\vedlegg\ id2b1846ba39d0667231ee2b2770a8754
Indeksering feilet:
Could Not Find F:\arkiv-innsyn\1505_insight_v1.1.0-beta3\rapporter\2022\3\11\115000\sphinx_index.conf
inedexer.log shows this error below
- What is the cause of this error
- What does happen to our search and use of the index, useless or no implications?
- What is te uuid/reference number below pointing/referring to (need to know for debugging)?
Sphinx 2.2.11-id64-release (95ae9a6)
Copyright (c) 2001-2016, Andrew Aksyonoff
Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com/)
using config file '.\rapporter\2022\3\11\104942\sphinx.conf'...
indexing index 'id2b1846ba39d0667231ee2b2770a8754'...
ERROR: index 'id2b1846ba39d0667231ee2b2770a8754': source 'src_id2b1846ba39d0667231ee2b2770a8754': XML parse error: not well-formed (invalid token) (line=3569, pos=47, docid=9).
indexer.log
total 0 docs, 0 bytes
total 0.040 sec, 0 bytes/sec, 0.00 docs/sec
total 0 reads, 0.000 sec, 0.0 kb/call avg, 0.0 msec/call avg
total 0 writes, 0.000 sec, 0.0 kb/call avg, 0.0 msec/call avg