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
Hi Conny,
I setup the ssh stuff on the boxes and it work from the command line, however
from a filter it doesn’t
Der angeforderte Prozess kann nicht ausgeführt werden. (ARERR 341)
--> Bestanden - Aktionen durchf�hren
0 : Felder einstellen
Aktion
Hi Thomas,
I wrote a workflow solution to this problem some time ago, and it still seems
to work (Just tried it on 9.1.3)
It is basically one form with 2 escalations.
The following information is recorded in the form
* User Login Name
* License Name (AR User, Change , Incident … etc)
Hi Thomas,
Conny has a very good idea. If your organization’s security policies allow for
it, it will work just fine.
If you wanted / were forced to use a more old-school AR System-based approach,
you will need to create two dummy forms populated with a record for each server
in the
Thomas,
There are a variety of techniques you could use.
1) If what you are doing is just analyzing a user log file (I seem to
remember that this was what you were having your program do from somewhere in
the thread….)….What if you just specified to put the user log onto a shared
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
Fabulous idea. As which use shall I do the ssh? The system is running as
root
On Wed 21. Aug 2019 at 13:46, wrote:
> 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
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
We're collecting license information on each individual server reading the
user.log I’m looking for a way to trigger the action on each individual server
without having to use a cron job.
> On 21. Aug 2019, at 13:18, Tauf Chowdhury wrote:
>
> Do you mean escalations? Also is this during a
Job = Escalation
We don’t have and use AI. It’s Remedy core only. We don’t want cron either...
> On 21. Aug 2019, at 13:16, Danny Kellett
> wrote:
>
> Escalation will only run from one AR Server at a time. So workflow on it's
> own might not cut it.
> Not quite sure what "Job" is in the
Do you mean escalations? Also is this during a maintenance period or scheduled
outage? You could always bring up one server at a time and that way you can
ensure escalations are running on that server if you’re in a server group with
the failover configured.
Sent from my iPhone
> On Aug 21,
Escalation will only run from one AR Server at a time. So workflow on
it's own might not cut it.
Not quite sure what "Job" is in the subject. But if something has to be
run on each server then you will need something external like a cron to
trigger it.
AI typically is run from one server at a
Hi there
we got three servers in the group and would like to collect information on
every individual server. We did that in the past using a cron job but would
prefer escalation which can be controlled by workflow. The problem is
explanations run only on one of the three servers. Any idea how
13 matches
Mail list logo
