Stopping and restarting Yate - Revision history

Monica: /* Yate started as a service */

2013-11-04T09:39:39Z

‎Yate started as a service

Dana at 15:37, 15 January 2013

2013-01-15T15:37:40Z

Dana: /* Telnet commands */

2013-01-15T15:36:20Z

‎Telnet commands

Dana at 15:29, 15 January 2013

2013-01-15T15:29:12Z

Dana: /* Yate as a service */

2013-01-15T15:24:39Z

‎Yate as a service

Dana: /* Yate as a service */

2013-01-15T15:23:16Z

‎Yate as a service

Dana at 15:21, 15 January 2013

2013-01-15T15:21:42Z

Dana at 10:40, 14 January 2013

2013-01-14T10:40:33Z

Dana at 10:34, 14 January 2013

2013-01-14T10:34:50Z

Dana: Created page with " 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 reinitia..."

2012-11-20T13:39:01Z

Created page with " 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 reinitia..."

New page

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

If you have [[rmanager]] module you can also connect to port 5038 and use "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.

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.

← Older revision		Revision as of 09:39, 4 November 2013
Line 43:		Line 43:
	* [[Paths and Directories]]		* [[Paths and Directories]]
	* [[Modules]]		* [[Modules]]
		+
		+	[[Category:Administrate]]

← Older revision		Revision as of 15:37, 15 January 2013
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]]

← Older revision		Revision as of 15:36, 15 January 2013
Line 14:		Line 14:

	'''Note''' that the modules are not reloaded, only their [[Configuration Files\|configuration files]] are read. Also note that some modules have options that are read only on the first initialization.		'''Note''' that the modules are not reloaded, only their [[Configuration Files\|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!

	=== Yate started in supervised mode===		=== Yate started in supervised mode===

← Older revision		Revision as of 15:29, 15 January 2013
Line 1:		Line 1:

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

	=== Signals and keys for a running Yate===		=== Signals and keys for a running Yate===

@@ Line 18: / Line 18: @@
 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.
-=== Yate as a service===
+=== Yate started as a service===
 If Yate was set as a service use commands:

← Older revision		Revision as of 15:23, 15 January 2013
Line 24:		Line 24:
	service yate stop		service yate stop
	service yate restart		service yate restart
		+
		+	As a general note, use '''restart''' instead of '''start''' to avoid accidentally running multiple instances.

@@ Line 1: / Line 1: @@
 While running the following signals and keys are trapped and used:
@@ Line 5: / Line 8: @@
    - SIGHUP and SIGQUIT (Ctrl-\) will reinitialize the modules
-If you have [[rmanager]] module you can also connect to port 5038 and use "stop" to stop the engine, and "reload" to reload the configurations.
+=== Telnet commands ===
 '''Note''' that the modules are not reloaded, only their [[Configuration Files|configuration files]] are read. Also note that some modules have options that are read only on the first initialization.
 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.