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:

AW: Loadbalancer traffic distribution question

Thomas, Connection != User You’re talking about technical users. Maybe some interfaces, which uses the same technical user and therefore you’ll see that many connections. You should be able to see (without the help of the LB Guys), how many connections are directed to each backend by using

AW: Load Balancing and Session Timeouts

Hi, don’t know if it’s a good idea to have a setup like this. From my point of view session sharing is used to provide some kind of high availability. We setup session sharing and had a config mistake regarding too short timeouts. This led to frequent session “hopping” between several midtier

AW: Load Balancing and Session Timeouts

Connection Settings are only relevant for midtier -> ar-server connections. And indeed, there is no need to have any persistence on this type of connection. If this connection is also routed through a loadbalancer in front of your ar-servers, you can disable persistence there. But this will

AW: How to run a job on individual servers?

Hi Thomas, it seems like you‘re using SET-Fields $PROCESS$, which is used to get the STDOUT of the started process assigned to a field. This makes no sense as you’re redirecting STDOUT to /dev/null. So in this case use RUN-PROCESS instead of Set-Fields. But your problem seems to be, that ssh

AW: DSO creating duplicates

We also had issues with DSO and ours was fixed with 9.1.07 KR Conny -Ursprüngliche Nachricht- Von: ARSList Im Auftrag von Thomas Miskiewicz Gesendet: Freitag, 23. August 2019 17:34 An: ARSList Betreff: Re: DSO creating duplicates Thank you for the quick reaction, Jeff. It’s

AW: How to run a job on individual servers?

I would not recommend to run arsystem as root (from a security point of view) For ssh you can use whatever user you like, which has sufficient permissions to run your “licensetracker”. You’ll have to make sure, that the user running arsystem is able to do ssh to the target servers/user without

AW: How to run a job on individual servers?

Hi, if you're on *x, you can do something like RUN-PROCESS ssh server1 /path/to/your/licensetracker RUN-PROCESS ssh server2 /path/to/your/licensetracker RUN-PROCESS ssh server3 /path/to/your/licensetracker within an escalation. If escalations are running on server1 it will connect via ssh to