Stopping and restarting Yate

From Yate Documentation
(Difference between revisions)
Jump to: navigation, search
(Telnet commands)
(Yate started as a service)
 
(One intermediate revision by one user not shown)
Line 37: Line 37:
  
 
As a general note, use '''restart''' instead of '''start''' to avoid accidentally running multiple instances.
 
As a general note, use '''restart''' instead of '''start''' to avoid accidentally running multiple instances.
 +
 +
 +
'''See also'''
 +
 +
* [[Paths and Directories]]
 +
* [[Modules]]
 +
 +
[[Category:Administrate]]

Latest revision as of 11:39, 4 November 2013

There are different ways of stopping and restarting Yate depending on how Yate was installed and configured.

Contents

[edit] Signals and keys for a running Yate

While running the following signals and keys are trapped and used:

 - SIGTERM and SIGINT (Ctrl-C) will cleanly stop the engine
 - SIGHUP and SIGQUIT (Ctrl-\) will reinitialize the modules

[edit] Telnet commands

If you have rmanager module enabled, you can also connect to port 5038 and use command "stop" to stop the engine, and "reload" to reload the configurations.

Note that the modules are not reloaded, only their configuration files are read. Also note that some modules have options that are read only on the first initialization.

telnet 127.0.0.1 5038
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
YATE 4.2.1-alpha1 (http://YATE.null.ro) ready on localhost.localdomain.
reload
Reinitializing...
stop
Engine shutting down - bye!

[edit] Yate started in supervised mode

If Yate is started in supervised mode (command line option -s) it can also be restarted from rmanager using "stop 128" - in fact any code between 128 and 255. The program will be stopped cleanly then the supervisor will restart it with the same command line options.

[edit] Yate started as a service

If Yate was set as a service use commands:

service yate stop
service yate restart

As a general note, use restart instead of start to avoid accidentally running multiple instances.


See also

Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers