NATS Docs
NATS.ioTwitterSlackGitHub
Search…
Introduction
What's New!
NATS 2.2
NATS 2.0
Compare NATS
FAQ
NATS Concepts
What is NATS
Subject-Based Messaging
Publish-Subscribe
Request-Reply
Queue Groups
Acknowledgements
Sequence Numbers
Developing With NATS
Introduction
Connecting
Automatic Reconnections
Securing Connections
Receiving Messages
Sending Messages
Monitoring the Connection
Tutorials
NATS Server
Installing
Running
Clients
Flags
Configuration
Managing A NATS Server
Upgrading a Cluster
Slow Consumers
Signals
Lame Duck Mode
NATS and Docker
JetStream
About JetStream
Concepts
Getting Started
Administration & Usage from CLI
Monitoring
Data Replication
Clustering
Configuration Management
Disaster Recovery
Encryption at Rest
Model Deep Dive
NATS API Reference
Multi-tenancy & Resource Mgmt
Leaf Nodes
NATS Tools
Introduction
nats
nk
nsc
nats-account-server
nats-top
nats-bench
NATS Streaming Concepts
Introduction
Relation to NATS
Client Connections
Channels
Store Interface
Store Encryption
Clustering
Fault Tolerance
Partitioning
Monitoring
Developing With NATS Streaming
Introduction
Connecting to NATS Streaming
Publishing to a Channel
Receiving Messages from a Channel
Durable Subscriptions
Queue Subscriptions
Acknowledgements
The Streaming Protocol
NATS Streaming Server
Important Changes
Installing
Running
Configuring
Process Signaling
Windows Service
Embedding NATS Streaming Server
Docker Swarm
NATS Protocol
Protocol Demo
Client Protocol
NATS Cluster Protocol
NATS on Kubernetes
Introduction
Basic NATS and NATS Streaming Setup
Deploying NATS with Helm
Creating a Kubernetes Cluster
NATS Streaming Cluster with FT Mode
NATS Cluster and Cert Manager
Securing a NATS Cluster with cfssl
Using a Load Balancer for External Access to NATS
Creating a NATS Super Cluster in Digital Ocean with Helm
From Zero to K8S to Leafnodes using Helm
Powered By GitBook
Signals
On Unix systems, the NATS server responds to the following signals:
Signal
Result
SIGKILL
Kills the process immediately
SIGQUIT
Kills the process immediately and performs a core dump
SIGINT
Stops the server gracefully
SIGTERM
Stops the server gracefully
SIGUSR1
Reopens the log file for log rotation
SIGHUP
Reloads server configuration file
SIGUSR2
Stops the server after evicting all clients (lame duck mode)
The nats-server binary can be used to send these signals to running NATS servers using the -sl flag:
1
# Quit the server
2
nats-server --signal quit
3
​
4
# Stop the server
5
nats-server --signal stop
6
​
7
# Reopen log file for log rotation
8
nats-server --signal reopen
9
​
10
# Reload server configuration
11
nats-server --signal reload
12
​
13
# Lame duck mode server configuration
14
nats-server --signal ldm
Copied!
If there are multiple nats-server processes running, or if pgrep isn't available, you must either specify a PID or the absolute path to a PID file:
1
nats-server --signal stop=<pid>
Copied!
1
nats-server --signal stop=/path/to/pidfile
Copied!
See the Windows Service section for information on signaling the NATS server on Windows.
Previous
Slow Consumers
Next
Lame Duck Mode
Last modified 1mo ago
Export as PDF
Copy link