Operating NVFLARE - Admin Client, Commands, FLARE API

The FL system is operated by the packages of type admin configured at provisioning. The admin packages contain key and certificate files to connect and authenticate with the server, and the administration can be done through an included command prompt with the Admin Console by running fl_admin.sh or programmatically through the FLARE API.

Admin command prompt

After running fl_admin.sh, log in by following the prompt and entering the name of the participant that the admin package was provisioned for (or for poc mode, “admin” as the name and password).

Typing “help” or “?” will display a list of the commands and a brief description for each. Typing “? “ before a command like “? check_status” or “?ls” will provide additional details for the usage of a command. Provided below is a list of commands shown as examples of how they may be run with a description.






Exit from the client



Get command help information



Print local workspace root directory of the admin client



Show folder setup info (upload and download sources and destinations)


check_status server

The FL job id, FL server status, and the registered clients with their names and tokens are displayed. If training is running, the round information is also displayed.

check_status client

The name, token, and status of each connected client are displayed.

check_status client clientname

The name, token, and status of the specified client with clientname are displayed.


submit_job job_folder_name

Submits the job to the server.



Lists the jobs on the server. (Options: [-n name_prefix] [-d] [job_id_prefix])


abort_job job_id

Aborts the job of the specified job_id if it is running or dispatched


clone_job job_id

Creates a copy of the specified job with a new job_id


abort job_id client

Aborts the job for the specified job_id for all clients. Individual client jobs can be aborted by specifying clientname.

abort job_id server

Aborts the server job for the specified job_id.


download_job job_id

Download folder from the job store containing the job and workspace. Please note that for larger jobs there may be extra delay for workspace creation in the job store (If you try to download the job before that you may not be able to get the workspace data)


delete_job job_id

Delete the job from the job store


cat server startup/fed_server.json -ns

Show content of a file (-n: number all output lines; -s: suppress repeated empty output lines)

cat clientname startup/docker.sh -bT

Show content of a file (-b: number nonempty output lines; -T: display TAB characters as ^I)


grep server "info" -i log.txt

Search for a pattern in a file (-n: print line number; -i: ignore case)


head clientname log.txt

Print the first 10 lines of a file

head server log.txt -n 15

Print the first 15 lines of a file (-n: print the first N lines instead of the first 10)


tail clientname log.txt

Print the last 10 lines of a file

tail server log.txt -n 15

Print the last 15 lines of a file (-n: output the last N lines instead of the last 10)


ls server -alt

List files in workspace root directory (-a: all; -l: use a long listing format; -t: sort by modification time)

ls clientname -SR

List files in workspace root directory (-S: sort by file size; -R: list subdirectories recursively)


pwd server

Print the name of workspace root directory

pwd clientname

Print the name of workspace root directory


sys_info server

Get system information

sys_info client *clientname*

Get system information. Individual clients can be shutdown by specifying clientname.


remove_client clientname

Issue command for server to release client before the 10 minute timeout to allow client to rejoin after manual restart.


restart client

Restarts all of the clients. Individual clients can be restarted by specifying clientname.

restart server

Restarts the server. Clients will also be restarted. Note that the admin client will need to log in again after the server restarts.


shutdown client

Shuts down all of the clients. Individual clients can be shutdown by specifying clientname. Please note that this may not be instant but may take time for the command to take effect.

shutdown server

Shuts down the active server. Clients must be shut down first before the server is shut down. Note this will not shut down the Overseer or other SPs.



Get information on the active SP (service provider or FL server).



Get data from last heartbeat of the active and available SP endpoint information.


promote_sp sp_end_point

promote a specified SP to become the active SP (promote_sp example1.com:8002:8003)



Shut down entire system by setting the system state to shutdown through the overseer


The commands promote_sp and shutdown_system both go to the Overseer and have a different mechanism of authorization than the other commands sent to the FL server. The Overseer keeps track of a list of privileged users, configured to be admin users with the role of “super”. Only users owning certificates whose cn is in the privileged user list can call these commands.


Outputs of any command can be redirected into a file by using the greater-than symbol “>”, however there must be no whitespace before the filename. For example, you may run sys_info server >serverinfo.txt. To only save the file output without printing it, use two greater-than symbols “>>” instead: sys_info server >>serverinfo.txt.

The FLARE API is the redesigned FLAdminAPI with a better user experience introduced in version 2.3.0. We recommend using the FLARE API as the FLAdminAPI is now deprecated and will soon sunset.