Knowledge base

Emergency stop

entries in this scenario: 13
How to name a queue in a commandcriticalMechanismHow to name a queue in a command argument: the same “receiving server and sending address” pair with asterisks added.Two tags the sender puts on a messagecriticalMechanismA job groups messages, an envelope identifier identifies one; the submitting side sets both, and only by them can you later select your mail in the node’s queue.Node backup and restoreProcedureFive directories make up the node’s recoverable state; restoring means stopping the engine, putting the directories back and starting it again.Switching over to a standby nodeProcedureThe procedure for handing work to another machine: redirect submission, attach the failed node’s spool as a second one if possible, restart the standby, and do the reverse on return.Starting and stopping the engineProcedureThe engine runs as a service on Windows and as a daemon on Unix; after start the watchdog must be running next to it, and a stop halts delivery without touching the messages on disk.deletecriticalCommandDeletes recipients from the queue by selection; it does not run without –queue or –jobId.pause queuecriticalCommandStops delivery for the selected queues; the messages stay in place.resume queuecriticalCommandResumes delivery of paused queues.set queuecriticalCommandSwitches queues to backoff or normal mode; stars change many queues at once.pause jobCommandStops delivery of one job’s messages.Run a command over the networkcriticalAPI endpointRuns a node console command passed in the request and returns the result as a structure or as text.Queue depthMetricRecipients, recipient domains and kilobytes in the queue.ConsoleMonitor screenRuns node console commands right from the browser; the page link exists only while the service is running.