phopwood Absent Member.
Absent Member.
3525 views

Indexing And Document Conversion Errors

48 hours on, I'm still waiting for a single post office re-index to complete. I'm running a single Linux POA and a DVA on the same virtual machine. The system does not seem to be resource bound, with ample available CPU. Memory and disk I/O available in the VM.

I am seeing the following error on the POA by the tens of thousands:

12:10:44 EF34 TCP/IP read timeout [8912] (/gwsystem/gwpo/oftemp/gwdca/in/4f2ac2a9.tmp) (see GWDCA log)


Far less frequently, I am also seeing this:
12:10:44 EF34   [01F4] (/gwsystem/gwpo/oftemp/gwdca/in/4f2ac2a7.tmp) (see GWDCA log)


There are no errors in the GWDCA log. There are also no events with corresponding time stamps. There are also no indications at all in the DVA logs. Does anyone have any insight with regard to these errors? Are they meaningful or just cosmetic?
Labels (2)
0 Likes
4 Replies
Knowledge Partner
Knowledge Partner

Re: Indexing And Document Conversion Errors

Hi.

On 02.02.2012 18:26, phopwood wrote:
>
> 48 hours on, I'm still waiting for a single post office re-index to
> complete. I'm running a single Linux POA and a DVA on the same virtual
> machine. The system does not seem to be resource bound, with ample
> available CPU. Memory and disk I/O available in the VM.
>
> I am seeing the following error on the POA by the tens of thousands:


I would say your DCA is completely failing. Some of these errors are
normal, tens of thousands totally aren't.


> There are no errors in the GWDCA log.


Is there *anything* in the dca log? Does it even run?

> There are also no events with
> corresponding time stamps. There are also no indications at all in the
> DVA logs.


Don't confuse the DVA and DCA. The DVA is for webaccess only, has
nothing to do with indexing.

> Does anyone have any insight with regard to these errors? Are
> they meaningful or just cosmetic?


THey mean that the poa timed out waiting for the DCA to convert the
document it passed to it. In that amount, I'd say the dca is failing fully.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
phopwood Absent Member.
Absent Member.

Re: Indexing And Document Conversion Errors

mrosen;2172863 wrote:
Hi.

On 02.02.2012 18:26, phopwood wrote:
>
> 48 hours on, I'm still waiting for a single post office re-index to
> complete. I'm running a single Linux POA and a DVA on the same virtual
> machine. The system does not seem to be resource bound, with ample
> available CPU. Memory and disk I/O available in the VM.
>
> I am seeing the following error on the POA by the tens of thousands:


I would say your DCA is completely failing. Some of these errors are
normal, tens of thousands totally aren't.


> There are no errors in the GWDCA log.


Is there *anything* in the dca log? Does it even run?


> There are also no events with
> corresponding time stamps. There are also no indications at all in the
> DVA logs.


Don't confuse the DVA and DCA. The DVA is for webaccess only, has
nothing to do with indexing.

> Does anyone have any insight with regard to these errors? Are
> they meaningful or just cosmetic?


THey mean that the poa timed out waiting for the DCA to convert the
document it passed to it. In that amount, I'd say the dca is failing fully.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
Untitled Document



Massimo, thanks for your input. You contributions to these forums over the years have been a great help to me and others. I do appreciate it.

Prior to enabling the DVA the only stuff that would show up in the GWDCA log, while the POA was streaming error messages, looked like this:
GWDCA Log

02-02-12 09:56:08 >> Worker process 1: Processing file conversion request...
02-02-12 09:56:08 << WP1: elapsed time: 1 sec


I've since set the POA to use the DVA with the --usedva switch. It is my understanding that this disables the DCA and that the POA uses the DVA for document conversion to .htm for indexing. The documentation states that the standalone process DVA performs much better than the DCA which is integrated into the POA. Is the documentation incorrect on this?

The DVA log shows nothing other than the normal startup configuration dump. Zero errors. Watching the Linux processes via top or looking at the counters on the DVA web console clearly shows that the DVA is hard at work during this re-index operation and the DCA is no where to be found. The stats on the DVA presently show ~100,000 conversion requests and 500 failures. But, the POA continues to stream the originally mentioned TCP/IP time out errors by the thousands.

Did I mention that there are over 500,000 messages in this post office, or that 70% of this post office is a single mailbox?
0 Likes
Knowledge Partner
Knowledge Partner

Re: Indexing And Document Conversion Errors

Hi.

On 02.02.2012 21:56, phopwood wrote:
> I've since set the POA to use the DVA with the --usedva switch. It is
> my understanding that this disables the DCA and that the POA uses the
> DVA for document conversion to .htm for indexing. The documentation
> states that the standalone process DVA performs much better than the DCA
> which is integrated into the POA. Is the documentation incorrect on
> this?


I can't judge this, but your POA errors clearly seem to say that the
*DCA* is used. Did you also configure the dva addresses properly? As the
docs state, the POA will fall back to the dca when the dva doesn't work.
What happens when you actually remove the --usedva again, and let the
dca do it's thing?

> Did I mention that there are over 500,000 messages in this post office,
> or that 70% of this post office is a single mailbox?


That's not much. 😉

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
phopwood Absent Member.
Absent Member.

Re: Indexing And Document Conversion Errors

While typing my reply to you, this appeared on the POA console:

16:45:48 EF34 Document caused worker process abend [8F14] (/gwsystem/gwpo/oftemp/gwdca/in/4f2c4eae.tmp) (see GWDCA log)
16:46:01 EF34 Document conversion error: unable to convert document [8F17] (/gwsystem/gwpo/oftemp/gwdca/in/4f2c4ec6.tmp) (see GWDCA log)
16:46:04 EF34 Document conversion error: unable to convert document [8F17] (/gwsystem/gwpo/oftemp/gwdca/in/4f2c4eca.tmp) (see GWDCA log)


After this abend, the five running gwdva processes all disappeared and the gwdca process has started again.

The poa continues to log these errors:

17:01:17 EF34 TCP/IP read failed [8910] (/gwsystem/gwpo/oftemp/gwdca/in/4f2c5454.tmp) (see GWDCA log)
17:07:26 EF34 TCP/IP disconnected [890F] (/gwsystem/gwpo/oftemp/gwdca/in/4f2c55b8.tmp) (see GWDCA log)
17:07:47 EF34 TCP/IP read timeout [8912] (/gwsystem/gwpo/oftemp/gwdca/in/4f2c55db.tmp) (see GWDCA log)
17:07:48 EF34 TCP/IP read timeout [8912] (/gwsystem/gwpo/oftemp/gwdca/in/4f2c55dc.tmp) (see GWDCA log)


The DCA log shows:

02-02-12 16:45:43 >> Worker process 1: Processing file conversion request...
02-02-12 16:45:43 << WP1: elapsed time: 1 sec
02-02-12 16:45:43 >> Worker process 1: Processing file conversion request...
02-02-12 16:45:43 << WP1: elapsed time: <1 sec
02-02-12 16:45:44 >> Worker process 1: Processing file conversion request...
02-02-12 16:45:49 >> Worker process 1: Processing file conversion request...
02-02-12 16:45:50 << WP1: elapsed time: <1 sec
02-02-12 16:45:50 >> Worker process 1: Processing file conversion request...
02-02-12 16:45:50 << WP1: elapsed time: <1 sec


top now shows gwdca doing the work while the re-index continues.

You say that this post office message count isn't much, but it takes over 24 hours to index on an old version of GroupWise with old hardware and without documents. With GroupWise 2012 including documents it has already exceeded 48 hours and is still grinding. That's terrible!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.