Re: Trouble getting rrrchive to run

Yes thats what we do , we transferred a whole Change Management from one server to another consolidated Server last year with two laptops , millions of records in the Change Management form and related Data , no problem . On 4 May 2018 at 18:31, Kevin M Candelaria wrote: >

Re: Trouble getting rrrchive to run

Why don't you just get rrrchive for windows and run it on your desktop and not the server. Sent from my Verizon, Samsung Galaxy smartphone. Excuse any spelling or formatting errors. Original message From: Ben Chernys Date: 5/4/18 11:26

RE: Trouble getting rrrchive to run

Like Conny said, export ARAPILOGGING=x where x is 1 or 29 or some other number – in the same bash shell where you set the LD_LIBRARY_PATH and where you will run rrrchive. Log file(s) show up in the current working directory. Do a set | grep -e LD_LIBRARY -e AR and email the

Re: AW: Trouble getting rrrchive to run

Thanks, Conny! Where would that Log show up then? > On 4. May 2018, at 14:33, > wrote: > > export ARAPILOGGING=1 > > If client side api logging is working, you should see files created in your > current working directory. This works

Re: Trouble getting rrrchive to run

Hi Ben, I actually did set the LD_LIBRARY_PATH but it makes no difference. The only thing I don’t get is how to enable that API Logging on that Linux Server. Thomas > On 4. May 2018, at 16:11, Ben Chernys > wrote: > > Thomas, > > It IS compatible. I

RE: Trouble getting rrrchive to run

Thomas, It IS compatible. I know this without using the tool. The API is compatible across all releases with only a few minor problems related to AR_INFO selection values introduced in 9 - which are not affecting you. It is not Misi’s tool. I can run stuff linked with any version

RE: Trouble getting rrrchive to run

Hallo Thomas, Conny, Misi, I always use the value 29. From the doc: (These are bits that must be or'd) 0 No logging - Setting ARAPILOGGING to 0 or not setting it at all turns ARAPILOGGING off. 1 Logging on - ARAPILOGGING is on and minimum output is recorded in the arapicmd.log and

Re: Trouble getting rrrchive to run

Hi Misi, the only last idea I have is: your version is 9.1.00 and ours is 9.1.04. Maybe it’s incompatible. Disappointing experience with this tool Thomas > On May 3, 2018, at 8:37 AM, Misi Mladoniczky wrote: > > Hi, > > You see exactly what the problem is in the log with

Re: Trouble getting rrrchive to run

Hi Misi, we also maxed out ulimit but get the very same error. Thomas > On May 3, 2018, at 8:37 AM, Misi Mladoniczky wrote: > > Hi, > > You see exactly what the problem is in the log with normal logging turned on. > > You get ARERR 91 with the additional text "RPC: Unable to

AW: Trouble getting rrrchive to run

export ARAPILOGGING=1 If client side api logging is working, you should see files created in your current working directory. This works with every AR-Api Client using the native api libs KR Conny Von: ARSList [mailto:arslist-boun...@arslist.org] Im Auftrag von Thomas Miskiewicz Gesendet:

Re: Trouble getting rrrchive to run

Hi Misi, driver utility works just fine, i.e. I can connect from source to target without any delay. API logs show on both source and target show no errors with rrrchive. Connecting with alias, hostname or ip address makes no difference. rrrchive throws ARERR 91 and would explain why.

Re: Trouble getting rrrchive to run

Misi, you said: You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the exact API-calls and data to feed to driver in order to reproduce this. How do I do that on a Linux box? Thomas > On May 3, 2018, at 8:37 AM, Misi Mladoniczky wrote: > > Hi, > > You see