OnDemand User Group
Support Forums => Report Indexing => Topic started by: MHassan on July 07, 2020, 04:33:09 AM
-
I am trying to load PDF data from windows to AIX and arsload fails immediately see the attachment for an example.
I have latest version of CMOD on the Windows platform and also on AIX platform, and arsload not working , and the sample i am trying to load is on my windows platform and when i try to run the arsload command i stand on the directory where the samples exists and here is my arsload command:
arsload -I IP_address -u admin -p demodemo -g PDF_XY -a PDF_XY TEST.pdf
Does anyone have any tips for remote loading of PDFs from Windows to a CMOD server on a UNIX platform? Is there something we're missing?
-
Well, the load is failing at the indexing step. However, this shouldn't result in a crash, and is likely a bug. It's probably best to open a Service Request with IBM to help them determine the cause and get the bug fixed for the next CMOD Fixpack. Here's a shortlink to the IBM Service Request page: http://CMOD.co/sr
-JD.
-
Well, the load is failing at the indexing step. However, this shouldn't result in a crash, and is likely a bug. It's probably best to open a Service Request with IBM to help them determine the cause and get the bug fixed for the next CMOD Fixpack. Here's a shortlink to the IBM Service Request page: http://CMOD.co/sr
-JD.
Thank you Justin for your reply , but this error appear to me in cmd is this familiar to you or this is a bug as you said - you can find the screenshot of the error attached
-
Again, you're not providing enough information. You've only given a portion of the output, and it makes it impossible to tell what's happening. Also, you can cut and paste the text of the output, instead of posting photos. There isn't an obvious error, just what appears to be the indexer stopping.
Does the arsload process crash with a segfault or core dump on AIX, in the same way it does on windows?
-JD.
-
Again, you're not providing enough information. You've only given a portion of the output, and it makes it impossible to tell what's happening. Also, you can cut and paste the text of the output, instead of posting photos. There isn't an obvious error, just what appears to be the indexer stopping.
Does the arsload process crash with a segfault or core dump on AIX, in the same way it does on windows?
-JD.
First of all ,sorry for not giving enough information here is the output that appear in cmd:
2020-07-07 16:47:44.350414: ARS4309E Indexing failed
2020-07-07 16:47:45.678331: ARS4318E Processing failed for file >GRN.pdf<
ARS1107E An error occurred. Contact your system administrator and/or consult the System Log. File=arsload.c, Line=16870
ARS4323E Unable to log load information
2020-07-07 16:47:59.240128: ARS4327E Processing has stopped. The remaining files will NOT be processed.
and when i try to open log from system log in client it show me error message :
The document is not displayable or printable
I didn't try on AIX because the CMOD administrator and client and pdf Indexer is on Windows , so thats what i am using in my project
-
Does the client crash on your windows machine consistently?
I would second JD's suggestion to open a service request.
It shows you are running 10.1.0.0 which makes you a "test pilot" :)
being risk averse, I would prefer to be at 10.1.0.1 as soon as it is available.
-
The only next step in this case is to run with tracing enabled on arsload, so you can get more information about the indexing failure.
-JD.
-
...
It shows you are running 10.1.0.0 which makes you a "test pilot" :)
being risk averse, I would prefer to be at 10.1.0.1 as soon as it is available.
10.1.0.0 is about as fresh as the pyramids.
https://www.ibm.com/support/pages/node/347373 (https://www.ibm.com/support/pages/node/347373)
Recommend you get to 10.1.0.6 before you do anything else.
Ed
-
actually a typing mistake on my part, the screen shot shows version 10.5.0.0 .
-
actually a typing mistake on my part, the screen shot shows version 10.5.0.0 .
Very good - that's the latest.
Definitely follow JD's recommendations, then.
Ed
-
Thanks all for all for your replies , i will open a PMR with IBM because i can't find the cause of the problem
-
Did you try enabling trace? You can post those results and we'll examine them.
-JD.