VERIFIED SOLUTION i
X

Resolve ERROR 70509 after file ingests successfully but is not returned in searches in EngageOne Vault

Issue

EngageOne Vault ingests a file without error, but a search for an account in that file returns:

ERROR 70509: no records match the selection criteria

Cause

e2loaderd log shows successful indexing of the file: 
 
06:08:21 start indexing document file [E:\Storagevault\2013\08\20130814somefile.drd] 
0 10 20 30 40 50 60 70 80 90 100 
| | | | | | | | | | | 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 
0 10 20 30 40 50 60 70 80 90 100 
| | | | | | | | | | | 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 
06:09:15 <reset1> connected to [server_ip_address:6001] 
06:09:15 <reset1> sent to [server_ip_address:6001] 
0 10 20 30 40 50 60 70 80 90 100 
| | | | | | | | | | | 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 
0 10 20 30 40 50 60 70 80 90 100 
| | | | | | | | | | | 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 
06:09:21 flushing index cache 
06:09:21 e:\pbbi ccm\e2 vault\server1\index\data\account.dri 
06:09:21 file size [249278464] 
06:09:21 disk read [7687] 
06:09:21 disk write [141] 
06:09:21 stack depth [5] 
06:09:21 cache read hit [530587] 
06:09:21 cache read miss [7686] 
06:09:21 cache write hit [168] 
06:09:21 cache write miss [2] 
06:09:21 add duplicate [591] 
06:09:21 add unique [166] 
06:09:21 e:\pbbi ccm\e2 vault\server1\index\data\address.dri 
06:09:21 file size [2827456512] 
06:09:21 disk read [8172] 
06:09:21 disk write [1466] 
06:09:21 stack depth [6] 
06:09:21 cache read hit [14923] 
06:09:21 cache read miss [8171] 
06:09:21 cache write hit [1512] 
06:09:21 cache write miss [16] 
06:09:21 add duplicate [2989] 
06:09:21 add unique [1496] 
06:09:21 e:\pbbi ccm\e2 vault\server1\index\data\invlink.dri 
06:09:21 file size [1763377152] 
06:09:21 disk read [22879] 
06:09:21 disk write [23909] 
06:09:21 stack depth [6] 
06:09:21 cache read hit [670562] 
06:09:21 cache read miss [22878] 
06:09:21 cache write hit [135978] 
06:09:21 cache write miss [2367] 
06:09:21 add unique [133611] 
06:09:21 e:\pbbi ccm\e2 vault\server1\index\data\invnum.dri 
06:09:21 file size [1298767872] 
06:09:21 disk read [9] 
06:09:21 disk write [1919] 
06:09:21 stack depth [5] 
06:09:21 cache read hit [528227] 
06:09:21 cache read miss [8] 
06:09:21 cache write hit [131610] 
06:09:21 cache write miss [1911] 
06:09:21 add unique [129699] 
06:09:21 e:\pbbi ccm\e2 vault\server1\index\data\name.dri 
06:09:21 file size [2074251264] 
06:09:21 disk read [5637] 
06:09:21 disk write [715] 
06:09:21 stack depth [6] 
06:09:21 cache read hit [9698] 
06:09:21 cache read miss [5636] 
06:09:21 cache write hit [748] 
06:09:21 cache write miss [16] 
06:09:21 add duplicate [2299] 
06:09:21 add unique [732] 
06:09:21 e:\pbbi ccm\e2 vault\server1\index\data\phone.dri 
06:09:21 file size [264548352] 
06:09:21 disk read [8074] 
06:09:21 disk write [94] 
06:09:21 stack depth [5] 
06:09:21 cache read hit [508163] 
06:09:21 cache read miss [8073] 
06:09:21 cache write hit [115] 
06:09:21 cache write miss [1] 
06:09:21 add duplicate [128857] 
06:09:21 add unique [114] 
06:09:21 finished indexing document file [E:\Storagevault\2013\08\20130814somefile.drd], [0] errors 
 
When the user attempt to render the document, the e2renderd log file shows file not found: 
 
06:40:46 ip_address:2128 <connection1> database.search returned record, [4] rows, [4] columns, more [0], fixed [0], elapsed [1] 
06:41:07 ip_address:2128 <connection1> database.search request, database [anydb], account [987654321 ], fields [doc.date;doc.type;int.file;int.pointer], titles [Date;Type;File;Offset] 
06:41:07 ip_address:2128 <connection1> database.search returned record, [4] rows, [4] columns, more [0], fixed [0], elapsed [32] 
06:41:19 ip_address:2128 <connection1> database.search request, database [webndtl], account [987654321 ], fields [doc.date;doc.type;int.file;int.pointer], titles [Date;Type;File;Offset] 
06:41:19 ip_address:2128 <connection1> database.search returned record, [4] rows, [4] columns, more [0], fixed [0], elapsed [53] 
06:41:27 ip_address:2128 <connection1> database.resolve request, database [anydb], account [123456789 ], date [2013/08/30], type [AFP], file [20130831somefile], offset [00761C790003F748] 
06:41:27 ip_address:2128 <connection1> <database1> ERROR 70509: no records match the selection criteria 
06:41:27 ip_address:2128 <connection1> database.resolve failed, status [70509] 
06:41:38 ip_address:2128 <connection1> database.search request, database [anydb], account [123456789 ], fields [doc.date;doc.type;int.file;int.pointer], titles [Date;Type;File;Offset] 
06:41:38 ip_address:2128 <connection1> database.search returned record, [4] rows, [4] columns, more [0], fixed [0], elapsed [53] 
06:41:49 ip_address:2128 <connection1> database.search request, database [anydb], account [123456789 ], fields [doc.date;doc.type;int.file;int.pointer], titles [Date;Type;File;Offset]

Resolution

UPDATED: March 21, 2017


If a specific environment is configured to use more than one e2serverd and multiple renders, but they don't have the e2loaderd.ini set to notify all the e2serverd instances when a new file is ingested, not all servers will be updated.

In this situation, the environment was set up to have 6 renders talking to 3 e2serverd, but only one e2serverd was being notified when a new file loaded.  That meant that only 2 of the 6 renders were aware of new files loading.
 
1. one e2loaderd;
2. three servers : server1 -> 6001, server2 -> 7001, server3 -> 8001
3. six renders :
render1 ==> port:9001 ==> server:MYSERVER.company.net:6001
render2 ==> port:9002 ==> server:MYSERVER.company.net:6001
render3 ==> port:9003 ==> server:MYSERVER.company.net:7001
render4 ==> port:9004 ==> server:MYSERVER.company.net:7001
render5 ==> port:9005 ==> server:MYSERVER.company.net:8001
render6 ==> port:9006 ==> server:MYSERVER.company.net:8001 
 
in e2loaderd.ini, RESET is only setup for 6001 which is SERVER1.
which means SERVER2 and SERVER3 will not synchronized correctly.

Check the e2renderd log files, search for "notice.cacheflush".  If there are no "notice.cacheflush" in the render log this indicates that the render is not getting these updates.

The user needs to make the following adjustments in e2loaderd.ini:

change

[server1]
service=*:6002
 
[connection1]
service=MYSERVER.company.net:6001
 
 
[reset1]
enable=1
service=MYSERVER.company.net:6001
 
to
 
[server1]
service=*:6002
 
[connection1]
service=MYSERVER.company.net:6001
 
[reset1]
enable=1
service=MYSERVER.company.net:6001, MYSERVER.company.net:7001, MYSERVER.company.net:8001

Note that:

[reset1]
enable=1

By default has an interval of 300 seconds, so after you ingest a file you may not see it for 300 seconds.  This can be adjusted using 

[reset1]
enable=1
interval=  (put in the required value in seconds)

Downloads

  • No Downloads