RTR_CheckAdminCommandStatus Error #415

qoolqool · 2021-11-04T08:16:22Z

qoolqool
Nov 4, 2021

Attempt to perform runscript on a target host and check the output with
execute_admin_command
check_admin_command_status

Got 'status_code': 201 for execute_admin_command

However, got status 403 for check_admin_command_status
on the following error message.

{'body': {'errors': [{'code': 403, 'message': 'unknown user'}],
          'meta': {'powered_by': 'empower-api',
                   'query_time': 0.001344533,
                   'trace_id': 'ceb24049-079b-42e6-8088-0a4d397e2946'},

What is the root cause of the error message unknown user ?

Answered by jshcodes

Feb 25, 2022

Hi @jsdjjsd!

I believe I've worked out a solution example for you. This one gets pretty verbose, so before we begin, a quick summary:

This is not well documented, but persist_all is not the correct keyword to force your command to queue offline. You are receiving the 'unknown user' error as the session is not queued and it needs to be. This is handled using queue_offline when you initialize the sessions using batch_init_session. Coincidentally, there is also a bug impacting versions 1.0.4 and below that made using this method more difficult than it should have been. (Body Payload Abstraction was not working properly for boolean values when using this method.) This bug is resolved in v1.0.5.

View full answer

jshcodes · 2021-11-04T08:18:33Z

jshcodes
Nov 4, 2021
Maintainer

Hi @qoolqool -

Can I see a sanitized version of your code? (Make sure API keys, CID's, etc. are removed)

I'd like to try and recreate this in one of my test environments.

2 replies

jsdjjsd Feb 24, 2022

Hi @jshcodes

I have the same issue as @qoolqool and was wondering if you perhaps can take a look at what might be wrong here.

I run a batch command towards three test machines, two are offline and one is online. The one online completes the command, and the other two are then queued.

target_hosts = ['a', 'b', 'c']
falcon = APIHarness(client_id='abc', client_secret='def')

BODY = {
    'host_ids': target_hosts,
    'queue_offline': True
}
init_response = falcon.command('BatchInitSessions', body=BODY)

batch_id = init_response['body']['batch_id']

BODY = {
    'base_command': 'runscript',
    'batch_id': batch_id,
    'command_string': 'runscript -Raw=```whoami```',
    'persist_all': True
}
batch_exec_response = falcon.command('BatchAdminCmd', body=BODY)

BODY = {
    'ids': list_of_pending_machines
}
listqueued_response = falcon.command('RTR_ListQueuedSessions', body=BODY)

When I then want to check the status of the commands for the two queued machines I run:

for i in blabla_pending_machines:
    checkadmincmd_response = falcon.command('RTR_CheckAdminCommandStatus', cloud_request_id=i['cloud_request_id'], sequence_id=i['sequence_id'])

And get the same response as @qoolqool, 'unknown user'.

jshcodes Feb 24, 2022
Maintainer

Hi @jsdjjsd!

That's something I should be able to recreate. I'll start working on this and see what I come up with.

jshcodes · 2022-02-25T04:55:16Z

jshcodes
Feb 25, 2022
Maintainer

Hi @jsdjjsd!

I believe I've worked out a solution example for you. This one gets pretty verbose, so before we begin, a quick summary:

This is not well documented, but persist_all is not the correct keyword to force your command to queue offline. You are receiving the 'unknown user' error as the session is not queued and it needs to be. This is handled using queue_offline when you initialize the sessions using batch_init_session. Coincidentally, there is also a bug impacting versions 1.0.4 and below that made using this method more difficult than it should have been. (Body Payload Abstraction was not working properly for boolean values when using this method.) This bug is resolved in v1.0.5.

If you have any questions, feel free to reply back here. 😄

Scenario

We have three instances deployed to AWS. All three instances have the latest version of the Falcon sensor installed, and all are connected to the same CID.

These instances are running AWS Linux 2 and are named:

discussion-415-a
discussion-415-b
discussion-415-c

We will use these instances as our targets for different variations of our testing.

Solution

A new sample has been developed that is a variation of the bulk execution sample recently released.

This code works similarly to the example it was ported from, with the addition of a handler for when a sensor does not respond to the RTR session initialization request. Now when this happens, the session ID is queued for later lookup using list_queued_sessions.

Note: When you first turn an instance off, RTR will still try to make this connection and throw a connection error. You may have to wait up to 5 minutes for the sensor to be shown as offline and your session to queue.

Once the results for online sensors are displayed, the solution runs a loop to wait for the offline sensors to return to service so that it can execute the queued command.

This is an example. In a real world scenario, it would be wiser to log the session and cloud request IDs and then check for these results on a periodic basis using some sort of scheduler.

Once the sensor is back online, the command is executed and the results displayed.

Source code

The source for this example can be found in our samples library here.

Executing the solution

If you have the FALCON_CLIENT_ID and FALCON_CLIENT_SECRET environment variables set, you will not need to provide API credentials to run this exercise. If you do not, you will need to provide these values using the -k and -s arguments respectively. You must provide a search string to use as a match against host names (-f argument). If you do not provide a command (-c argument), the command executed will be ls -al.

Command line

The command line used for all tests: python3 queued_execute.py -f "discussion"

Testing

What follows are the results of my testing this example in several different scenarios.

Test example 1

My first test has all three sensors online, but only two of them had finished installing their policies, so I received an error message from the third one.

Starting sessions with target hosts.
Session with discussion-415-b started successfully. [48493959-e708-4bfb-96c7-54659c68e1d5]
Session with discussion-415-a started successfully. [14cab6e1-1d36-40d5-a66f-81006affc378]
Session with discussion-415-c started successfully. [245f716b-07d1-482c-b0df-227514208b8b]

Executing command (`ls -al`) against target hosts.

Closing sessions with target hosts.
Session 48493959-e708-4bfb-96c7-54659c68e1d5 deleted successfully.
Session 14cab6e1-1d36-40d5-a66f-81006affc378 deleted successfully.
Session 245f716b-07d1-482c-b0df-227514208b8b deleted successfully.

discussion-415-b
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 24 15:46 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:54 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:54 opt
dr-xr-xr-x 120 root root    0 Feb 24 15:46 proc
dr-xr-x---   3 root root  124 Feb 24 15:53 root
drwxr-xr-x  28 root root  980 Feb 24 15:54 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 24 15:46 sys
drwxrwxrwt   8 root root  172 Feb 24 15:54 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var

discussion-415-a
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 24 15:46 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:50 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:50 opt
dr-xr-xr-x 120 root root    0 Feb 24 15:46 proc
dr-xr-x---   3 root root  124 Feb 24 15:52 root
drwxr-xr-x  28 root root  980 Feb 24 15:50 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 24 15:46 sys
drwxrwxrwt   8 root root  216 Feb 24 15:50 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var

discussion-415-c
runscript is disabled by policy

Test example 2

The second test had all three sensors online and ready to receive commands.

Starting sessions with target hosts.
Session with discussion-415-b started successfully. [0614db16-18e5-4352-b352-d77c3e213e2a]
Session with discussion-415-a started successfully. [6b0cc2fe-e9e3-4f49-be51-f372b7f71a6f]
Session with discussion-415-c started successfully. [310b5229-0661-4842-ae33-0df16027f1f3]

Executing command (`ls -al`) against target hosts.

Closing sessions with target hosts.
Session 0614db16-18e5-4352-b352-d77c3e213e2a deleted successfully.
Session 6b0cc2fe-e9e3-4f49-be51-f372b7f71a6f deleted successfully.
Session 310b5229-0661-4842-ae33-0df16027f1f3 deleted successfully.

discussion-415-b
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 24 22:19 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:54 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:54 opt
dr-xr-xr-x 123 root root    0 Feb 24 22:19 proc
dr-xr-x---   3 root root  124 Feb 24 15:53 root
drwxr-xr-x  28 root root  980 Feb 24 22:19 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 24 22:20 sys
drwxrwxrwt   8 root root  172 Feb 24 22:19 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var

discussion-415-a
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 24 22:10 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:50 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:50 opt
dr-xr-xr-x 119 root root    0 Feb 24 22:09 proc
dr-xr-x---   3 root root  124 Feb 24 15:52 root
drwxr-xr-x  28 root root  980 Feb 24 22:10 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 24 22:10 sys
drwxrwxrwt   8 root root  216 Feb 24 22:10 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var

discussion-415-c
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 24 22:19 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:55 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:55 opt
dr-xr-xr-x 123 root root    0 Feb 24 22:19 proc
dr-xr-x---   3 root root  124 Feb 24 15:55 root
drwxr-xr-x  28 root root  980 Feb 24 22:20 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 24 22:21 sys
drwxrwxrwt   8 root root  172 Feb 24 22:20 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var

Test example 3

Then I turned one of the instances off and re-ran the solution. Since I hadn't waited very long, the sensor was shown as "unable to connect", so our session did not queue.

Starting sessions with target hosts.
Session with discussion-415-b started successfully. [41ab629e-3e70-41fc-a499-494cd26c5a8f]
Session with discussion-415-a started successfully. [393e59fe-1ece-486f-a0ea-f25a29525cb6]
Session with discussion-415-c FAILED. [50401] Exceeded maximum connect timeout: 30.00s

Executing command (`ls -al`) against target hosts.

Closing sessions with target hosts.
Session 41ab629e-3e70-41fc-a499-494cd26c5a8f deleted successfully.
Session 393e59fe-1ece-486f-a0ea-f25a29525cb6 deleted successfully.

discussion-415-b
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 25 03:29 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:54 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:54 opt
dr-xr-xr-x 123 root root    0 Feb 25 03:29 proc
dr-xr-x---   3 root root  124 Feb 24 15:53 root
drwxr-xr-x  28 root root  980 Feb 25 03:30 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 25 03:31 sys
drwxrwxrwt   8 root root  172 Feb 25 03:30 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var

discussion-415-a
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 25 03:29 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:50 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:50 opt
dr-xr-xr-x 123 root root    0 Feb 25 03:29 proc
dr-xr-x---   3 root root  124 Feb 24 15:52 root
drwxr-xr-x  28 root root  980 Feb 25 03:30 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 25 03:30 sys
drwxrwxrwt   8 root root  216 Feb 25 03:30 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var

Test example 4

Re-running this exercise after waiting 5 minutes, and my session with the last instance is queued and my command is pending. I then turned the instance back on and waited.

Starting sessions with target hosts.
Session with discussion-415-b started successfully. [44a904eb-fab9-4109-847a-0658309209d6]
Session with discussion-415-a started successfully. [e5504ab9-2941-447f-9761-4bff856c4f71]
Session with discussion-415-c QUEUED.

Executing command (`ls -al`) against target hosts.

Closing sessions with target hosts.
Session 44a904eb-fab9-4109-847a-0658309209d6 deleted successfully.
Session e5504ab9-2941-447f-9761-4bff856c4f71 deleted successfully.

discussion-415-b
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 25 03:29 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:54 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:54 opt
dr-xr-xr-x 118 root root    0 Feb 25 03:29 proc
dr-xr-x---   3 root root  124 Feb 24 15:53 root
drwxr-xr-x  28 root root  980 Feb 25 03:30 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 25 03:31 sys
drwxrwxrwt   8 root root  172 Feb 25 03:30 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var

discussion-415-a
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 25 03:29 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:50 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:50 opt
dr-xr-xr-x 118 root root    0 Feb 25 03:29 proc
dr-xr-x---   3 root root  124 Feb 24 15:52 root
drwxr-xr-x  28 root root  980 Feb 25 03:30 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 25 03:30 sys
drwxrwxrwt   8 root root  216 Feb 25 03:30 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var
Device offline (discussion-415-c). Request is queued (08f233fb-7a1c-4a8c-acfe-8e10a197d103).
[ 22:38:04 ] Queued session not ready, sleeping for 20 seconds.
[ 22:38:25 ] Queued session not ready, sleeping for 20 seconds.
[ 22:38:45 ] Queued session not ready, sleeping for 20 seconds.
[ 22:39:06 ] Queued session not ready, sleeping for 20 seconds.
[ 22:39:26 ] Queued session not ready, sleeping for 20 seconds.

discussion-415-c
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 25 03:38 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:55 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:55 opt
dr-xr-xr-x 123 root root    0 Feb 25 03:38 proc
dr-xr-x---   3 root root  124 Feb 24 15:55 root
drwxr-xr-x  28 root root  980 Feb 25 03:38 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 25 03:38 sys
drwxrwxrwt   8 root root  172 Feb 25 03:38 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var

Test example 5

Last, we recreate the scenario you originally describe. e.g. What happens when I turn two of these instances off and try the solution again?

Starting sessions with target hosts.
Session with discussion-415-b QUEUED.
Session with discussion-415-a QUEUED.
Session with discussion-415-c started successfully. [8357ca19-87d3-4ed5-a32f-517efee468a4]

Executing command (`ls -al`) against target hosts.

Closing sessions with target hosts.
Session 8357ca19-87d3-4ed5-a32f-517efee468a4 deleted successfully.

discussion-415-c
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 25 03:38 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:55 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:55 opt
dr-xr-xr-x 119 root root    0 Feb 25 03:38 proc
dr-xr-x---   3 root root  124 Feb 24 15:55 root
drwxr-xr-x  28 root root  980 Feb 25 03:38 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 25 03:39 sys
drwxrwxrwt   8 root root  172 Feb 25 04:37 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var
Device offline (discussion-415-b).  Request is queued (3f58f117-81ba-4e6f-b459-bf5f6c163f07).
Device offline (discussion-415-a).  Request is queued (b5f66b38-dd77-43d6-90fb-5a13bf7baa10).
[ 23:51:49 ] Queued session not ready, sleeping for 20 seconds.
[ 23:52:09 ] Queued session not ready, sleeping for 20 seconds.
[ 23:52:30 ] Queued session not ready, sleeping for 20 seconds.
[ 23:52:50 ] Queued session not ready, sleeping for 20 seconds.
[ 23:53:11 ] Queued session not ready, sleeping for 20 seconds.

discussion-415-b
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 25 04:52 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:54 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:54 opt
dr-xr-xr-x 123 root root    0 Feb 25 04:52 proc
dr-xr-x---   3 root root  124 Feb 24 15:53 root
drwxr-xr-x  28 root root  980 Feb 25 04:52 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 25 04:52 sys
drwxrwxrwt   8 root root  172 Feb 25 04:52 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var


discussion-415-a
total 16
dr-xr-xr-x  18 root root  257 Feb 24 15:47 .
dr-xr-xr-x  18 root root  257 Feb 24 15:47 ..
-rw-r--r--   1 root root    0 Feb 24 15:46 .autorelabel
lrwxrwxrwx   1 root root    7 Feb  7 22:14 bin -> usr/bin
dr-xr-xr-x   4 root root 4096 Feb  7 22:15 boot
drwxr-xr-x  15 root root 2820 Feb 25 04:52 dev
drwxr-xr-x  81 root root 8192 Feb 24 15:50 etc
drwxr-xr-x   3 root root   22 Feb 24 15:46 home
lrwxrwxrwx   1 root root    7 Feb  7 22:14 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Feb  7 22:14 lib64 -> usr/lib64
drwxr-xr-x   2 root root    6 Feb  7 22:13 local
drwxr-xr-x   2 root root    6 Apr  9  2019 media
drwxr-xr-x   2 root root    6 Apr  9  2019 mnt
drwxr-xr-x   5 root root   46 Feb 24 15:50 opt
dr-xr-xr-x 123 root root    0 Feb 25 04:52 proc
dr-xr-x---   3 root root  124 Feb 24 15:52 root
drwxr-xr-x  28 root root  980 Feb 25 04:52 run
lrwxrwxrwx   1 root root    8 Feb  7 22:14 sbin -> usr/sbin
drwxr-xr-x   2 root root    6 Apr  9  2019 srv
dr-xr-xr-x  13 root root    0 Feb 25 04:52 sys
drwxrwxrwt   8 root root  216 Feb 25 04:52 tmp
drwxr-xr-x  13 root root  155 Feb  7 22:14 usr
drwxr-xr-x  19 root root  269 Feb 24 15:46 var

1 reply

jsdjjsd Mar 21, 2022

Hi @jshcodes

I have now tested my code with your newest version and it works perfectly, thanks a lot for spending the time checking and implementing a fix for it, much appreciated.

Best regards,
jsdjjsd

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

RTR_CheckAdminCommandStatus Error #415

{{title}}

Replies: 2 comments 3 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

RTR_CheckAdminCommandStatus Error #415

qoolqool Nov 4, 2021

Replies: 2 comments · 3 replies

jshcodes Nov 4, 2021 Maintainer

jsdjjsd Feb 24, 2022

jshcodes Feb 24, 2022 Maintainer

jshcodes Feb 25, 2022 Maintainer

Scenario

Solution

Source code

Executing the solution

Command line

Testing

Test example 1

Test example 2

Test example 3

Test example 4

Test example 5

jsdjjsd Mar 21, 2022

qoolqool
Nov 4, 2021

Replies: 2 comments 3 replies

jshcodes
Nov 4, 2021
Maintainer

jshcodes Feb 24, 2022
Maintainer

jshcodes
Feb 25, 2022
Maintainer