VERIFIED SOLUTION i
X

Understanding Vault error 18018

UPDATED: October 18, 2017


What does it mean when I get 18018 in the e2loaderd log, as below:

05:15:16 processing resource packs for guids [675fffbf419f4025b1ea70b38c2cf415]
05:15:32 renaming file [20130611025038_phi_dpd_evc] to [20130611005840-bill01-0180179553d2e211aaf3000169e62098]
05:15:32 start indexing document file [/opt/ebilldata/vault/docdata/20130611005840-bill01-0180179553d2e211aaf3000169e62098.drd]
         0    10   20   30   40   50   60   70   80   90   100
         |    |    |    |    |    |    |    |    |    |    |
         X
05:15:32 ERROR 18018: unable to open index account index in database [c3bills]
05:15:32 flushing index cache
05:15:32 finished indexing document file [/opt/ebilldata/vault/docdata/20130611005840-bill01-0180179553d2e211aaf3000169e62098.drd], [1] errors
05:15:32 <reset1> notice.cacheflush request
05:15:32 <reset1> notice.cacheflush returned, elapsed [0]
05:15:32 ERROR 10132: indexing failed for file [20130611005840-bill01-0180179553d2e211aaf3000169e62098]
05:15:32 building [/opt/ebilldata/vault/work/20130611025038_phi_dpm_evc.drd] profile [CDelmarva_STMTS] document build engine [xmljournal]
         0    10   20   30   40   50   60   70   80   90   100
         |    |    |    |    |    |    |    |    |    |    |
         XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
05:16:14 [/opt/ebilldata/vault/work/20130611025038_phi_dpm_evc.drd] has been successfully built, [11217] documents, [33519] pages
05:16:14 processing resource packs for guids [675fffbf419f4025b1ea70b38c2cf415]
05:17:37 renaming file [20130611025038_phi_dpm_evc] to [20130611002619-bill01-81672a104fd2e211b662000169e62098]
05:17:37 start indexing document file [/opt/ebilldata/vault/docdata/20130611002619-bill01-81672a104fd2e211b662000169e62098.drd]
         0    10   20   30   40   50   60   70   80   90   100
         |    |    |    |    |    |    |    |    |    |    |
         X
05:17:37 ERROR 18018: unable to open index account index in database [c3bills]
05:17:37 flushing index cache
05:17:37 finished indexing document file [/opt/ebilldata/vault/docdata/20130611002619-bill01-81672a104fd2e211b662000169e62098.drd], [1] errors
05:17:37 <reset1> notice.cacheflush request
 


This error can happen for a few different reasons:

1) If the vault server somehow loses access to the drive containing the indexes, you'll get the error.  Restarting can solve this because the underlying connection could be re-established.

2) if the index is not configured correctly in profiles.ini or database.ini this can happen. (Although if this was the cause, restarting and reindexing the file would not change the results)

3) if there was a memory leak in the e2serverd or e2loaderd process memory would eventually run out and this error could happen.  In this case a restart would also resolve the issue temporarily, but you would want to monitor memory usage over time and see if there is a leak.  If so, this should be reported to support with accompanying resources so that Engineering could create a patch to resolve the issue.

Environment Details

e2 Vault 5.4, 5.5, 6.0, 6.1

Downloads

  • No Downloads