The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.
Zen

Source string Source string

44/10000 · 44
English Actions
$ tt start demo
• Starting an instance [demo:router]...
• Starting an instance [demo:storage1]...
• Starting an instance [demo:storage2]...
Check the status of ``demo`` instances:
$ tt status demo
INSTANCE STATUS PID
demo:router RUNNING 55
demo:storage1 RUNNING 56
demo:storage2 RUNNING 57
Check the status of a specific instance:
$ tt status demo:router
INSTANCE STATUS PID
demo:router RUNNING 55
Connect to an instance:
$ tt connect demo:router
• Connecting to the instance...
• Connected to /var/run/tarantool/demo/router/router.control

/var/run/tarantool/demo/router/router.control>
Stop a specific instance:
$ tt stop demo:storage1
• The Instance demo:storage1 (PID = 56) has been terminated.
Stop all running instances of the ``demo`` application:
$ tt stop demo
• The Instance demo:router (PID = 55) has been terminated.
• can't "stat" the PID file. Error: "stat /var/run/tarantool/demo/storage1/storage1.pid: no such file or directory"
• The Instance demo:storage2 (PID = 57) has been terminated.
The error message indicates that ``storage1`` is already not running.
Running Tarantool locally
Sometimes you may need to run a Tarantool instance locally, for example, for test purposes. ``tt`` runs in a local environment if it finds a ``tt.yaml`` configuration file in the current directory or any of its enclosing directories.
To set up a local environment for ``tt``:
Create a home directory for the environment.
Run ``tt init`` in this directory:
$ tt init
• Environment config is written to 'tt.yaml'
This command creates a default ``tt`` configuration file ``tt.yaml`` for a local environment and the directories for instance files, control sockets, logs, and other artifacts:
$ ls
bin distfiles include instances.enabled modules templates tt.yaml
To run a Tarantool instance in the local environment:
Place the instance file into the ``instances.enabled/`` directory inside the current directory.
$ tt start
After the instance is started, you can find its artifacts in their locations inside the current directory:
logs in ``var/log/<instance_name>``
snapshots and write-ahead logs in ``var/lib/<instance_name>``
control sockets and PID files in ``var/run/<instance_name>``
To work with a local environment from a directory outside it, issue ``tt`` calls with the ``-L`` or ``--local`` argument with the path to this environment as its value:
$ tt --local=/usr/tt/env/ start
Using systemd tools
If you start an instance using ``systemd`` tools, like this (the instance name is ``my_app``):

Loading…

User avatar None

New source string

testing_project / Documentation: book/admin/start_stop_instance — English

Create a home directory for the environment.
a year ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatched colon: Russian, Russian

Reset

Glossary

English English
No related strings found in the glossary.

String information

Flags
read-only
String age
a year ago
Last updated
a year ago
Source string age
a year ago
Translation file
string 73