Skip to main content
Version: 3.23

Managing the Application

caution

It is possible to visualize application logs saved in files to be recorded and indexed in elasticsearch. There is a second instance in the cluster that makes the log files visualization possible, and those logs are up to 10.000 registers.

If you try to run without lifting, you will receive a warning message. You can manage the senhasegura application status of this instance with the command orbit application.

mt4adm@vmdf-giskard:~$ sudo orbit application --help
Usage: orbit application [<command>]

Application settings tools.

Arguments:
[<command>]    Control the application services status:
                [start|stop|restart|status|master|version]

Flags:
    --help       Show context-sensitive help.

    --version    Show the application components versions
    --force      Force the command execution, never prompt
    --show

  • start: Activates the instance for users' use.

  • stop: Inactivates the instance for users' use.

  • restart: Restart the services used to distribute the Web application, with the exception of the database, proxy systems and services started by Cron.

  • status: Displays the status of this instance.

  • master: Sets this instance to Master in a cluster scenario.

  • version: Displays the installed version of the Orbini platform and senhasegura .

Application status​

The orbit application status command displays the status of each primary function of the instance. Being:

  • Application: Status of the instance as to its activation. "Active" to be available for users use and "Inactive" to be unavailable for users use;

  • Replication: Replication/cluster status of this instance. "Active" to indicate you are a cluster member and "Inactive" to indicate you are not part of a cluster;

  • Instance: Role of the instance in the cluster. "Primary" for main instance (Master), "Secondary" for support instance (Slave);

mt4adm@vmdf-giskard:~$ sudo orbit application status

Application: Active
Replication: Inactive
Instance:    Primary

Inactivating use of the instance​

The orbit application stop command inactivates the application for user use. This action does not affect the activation of the license or the execution of the robots in the instance.

This action is equivalent to activating the instance in the menu Orbit ➔ Settings ➔ Application.

mt4adm@vmdf-giskard:~$ sudo orbit application stop
The application services will be stopped or restarted during the process.
Are you sure you want to proceed: y

Application: Inactive
Replication: Inactive
Instance:    Primary

Activating the use of the instance​

The orbit application start command activates the application for user use. This action does not affect the activation of the license or the execution of the robots on the instance.

This action is equivalent to activating the instance in the menu Orbit ➔ Settings ➔ Application.

mt4adm@vmdf-giskard:~$ sudo orbit application start
The application services will be stopped or restarted during the process.
Are you sure you want to proceed: y

Application: Active
Replication: Inactive
Instance:    Primary

Defining the instance as master​

The orbit application master command configures the instance as Master instance. If the instance is inactive, it will be automatically activated and raised to Master.

caution

The Master instance is responsible for the execution of unique services that are not executed in the other instances of the Cluster.

mt4adm@vmdf-giskard:~$ sudo orbit application master
The application services will be stopped or restarted during the process.
Are you sure you want to proceed: y

Application: Active
Replication: Inactive
Instance:    Primary

Restarting application services​

The orbit application restart command restarts the services used to distribute the Web application, with the exception of the database, proxy systems and services started by Cron.

Basically restarts only the services used by the Webserver.

mt4adm@vmdf-giskard:/home/mt4adm## sudo orbit application restart
The application services will be stopped or restarted during the process.
Are you sure you want to proceed: y█

Application: Active
Replication: Inactive
Instance:    Primary

Getting the installed version​

The orbit application version command presents the Orbini platform and framework version. Its operation is similar to the orbit version command, described above.

mt4adm@vmdf-giskard:~$ sudo orbit application version
Applications
Orbini           5.10.13.27
senhasegura      3.2.0.1