NATS Docs
NATS Docs
NATS.io
Twitter
Slack
GitHub
Introduction
What's New!
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
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
Creating a Kubernetes Cluster
NATS Streaming Cluster with FT Mode
NATS and Prometheus Operator
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

SIGINT

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:

# Quit the server
nats-server --signal quit
​
# Stop the server
nats-server --signal stop
​
# Reopen log file for log rotation
nats-server --signal reopen
​
# Reload server configuration
nats-server --signal reload
​
# Lame duck mode server configuration
nats-server --signal ldm

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:

nats-server --signal stop=<pid>
nats-server --signal stop=/path/to/pidfile

See the Windows Service section for information on signaling the NATS server on Windows.

Previous
Slow Consumers
Next
Lame Duck Mode
Last updated 1 year ago
Edit on GitHub