OD MP 8.5.04 - arsload daemon terminates after sucessful ingestion

[ERIEOD]

We recently upgraded our development environment to version OD MP 8.5.04 (linux).  Our arsload daemon terminates after it successfully ingests.  Has anyone experienced this issue?

[demaya]

You tried using -v for verbose mode for seeing more information...?

Here is what we use to load files with 8.4.1.5:
/usr/lpp/ars/bin/arsload -I ARCHIVE -A DATASET -G FORMS -v -f -d /path/to/folder -t 30

[Alessandro Perucchi]

you could also use the option -1 and -2 in order to have more tracing information.

Sincerely yours,
Alessandro

[ERIEOD]

Thank you for your suggestions.  We had already enable the trace on the daemon.  The trace did document an error condition:
27483:47067532140128 02/27/2012 15:51:41:236687 ERROR arssock.c(2422)ArcSOCKETP_Startup:ICC_GetValue ICC_SEED_GENERATOR icc_status.majRC=2 icc_status.minRC=1 icc_status.mode=1 icc_status.desc=Attempted to get an invalid value ID . 

We have uploaded the trace files to a PMR for IBM assistance but have not received a response.

The verbose also showed the file ingesting properly with the daemon terminating after the ingestion without a specific error.

arsload: 02/27/12 15:51:41 Loading completed
arsload: Processing successful for file >/afpdata/LAS.LAS.LASDOCID.SaveDeletedDocuments.X.X.ARD<
An error occurred.  Contact your system administrator and/or consult the System Log.  File=arsadmin.c, Line=2587

arsload: Unable to log load information
arsload: The arsload instance dondd is terminating

[Alessandro Perucchi]

Hello ERIEOD,

Looking at your error message:

arsload: Unable to log load information

I'm wondering if everything is correctly configured in your CMOD, like permissions. Are your "System Log" and "System Load" correctly defined? Have you checked your "System Log" for further information? I mean, you will see your error message in the system log, but around this message you might have other message that are maybe related to that...

Have you loaded other files without problems before?

Sincerely yours,
Alessandro

[ERIEOD]

Hello Alessandro,

Our System Log seems to be behaving properly.  The files are ingested sucessfully and an 87 is inserted into the system log....then the daemon terminates.  Running arsload at the command line produces the same error.  We reviewed the system log and found no other error messages logged.

We have not installed the System Load app group.  Our understanding was that it was optional.

[Alessandro Perucchi]

Hello ERIEOD,

try to add the "System Load" just to be sure that it solves the problem.
Maybe it is not as optional as it seems!

Sincerely yours,
Alessandro

[jeffs42885]

Hello All,

Was this ever resolved? If so, any idea what the root cause was?

[ERIEOD]

This issue was resolved by deactivating the report distribution functionality in our development environment.

[jeffs42885]

Just out of curiousity, what are you using to convert AFP?

[demaya]

Just to make sure someone has the same problem. Since upgrade to 8.5.0.5 we had an dump in arsload with several documents. I opened an apar and they found an conversion problem.

Genericindexer:
GROUP_FIELD_NAME:ASDF
GROUP_FIELD_VALUE:Stra?e 4711

The field asdf is set to upper cases in application group and the field length is 11/String. Now the conversion of the ? (yeah we need this here in germany :-)) is done to SS. But the string length exceeds 11 characters and the arsload daemon dumps without any related information. They think about an fix right now.

Just fyi, if you ever have this curious issue.

Cheers