nano v2.0.10
nano v2.0.10 is the minimum licensed Self-run release. It adds a per-install ID to license check-ins, upgrades from the signed bundle and fixes HEC limits.
v2.0.10 includes everything in v2.0.9.
To upgrade to v2.0.10 from v2.0.9 or earlier, run the installer again from the v2.0.10 bundle on each host, in order, as Upgrade a self-hosted deployment describes. From v2.0.10 on, scripts/nano upgrade upgrades from the bundle for you.
Self-run licensing
- v2.0.10 is the minimum licensed release for nano Self-run. Every Self-run install on an earlier v2 release must upgrade. At its next license check-in, an earlier v2 build gets a locked license with the reason "Upgrade required: this release can't be licensed for Self-run. Install v2.0.10 or later." The upgrade's license check accepts that lock, and only that one, so you can still upgrade.
- Each install sends an install ID. The license check-in and the daily usage report carry a random ID for the install in the
X-Nano-Install-Idheader. Every server of a multi-server install shares it. The ID is random: it says nothing about your servers or your data. - One Self-run license covers 2 installs, each with its own install ID. Usage is the sum across them.
- Proxies must forward the
X-Nano-Install-Idheader. If an outbound proxy strips it, the check-in still succeeds, but nano can't tell your installs apart. If you route nano's outbound traffic through a proxy, allow the header.
Fixes
- Upgrades from the installer bundle. The upgrade guide pointed at an offline image bundle,
nano-<version>-enterprise.tar, that releases for registry installs don't publish, so the documented upgrade couldn't be run.scripts/nano upgrade --bundlenow also accepts the signed installer bundle,nano-compose-enterprise-<version>.tar.gz. It checks the bundle's signature, reads the image digests, migrations and upgrade requirements from inside it, and pulls each image from the registry by its signed digest. Unpack the bundle over~/nanoon every server first, and log in to the registry. When it can't download or verify something, it now says why instead ofcommand failed. See Upgrade a self-hosted deployment. - Data disk not mounted after a reboot. When a server's data disk failed to mount at boot, Docker started on an empty
/var/lib/dockeron the root disk and reported itself running. The installer now refuses to run in that state, and warns when Docker doesn't depend on the data disk. The install guides now add aRequiresMountsFor=drop-in so Docker waits for the disk and never starts without it. See Prepare the data disk. - HEC
429at low volume (multi-node). The ingest hostname admitted HEC requests at a steady rate with no burst allowance, so a sender that posted two batches within 20 ms got429even at a few events per second. Each limit now has a burst allowance; the sustained limits are unchanged. See Request limits. - Shared
.envdrift (multi-node). Some installer runs appended a setting that was already in.env, or rewrote the file in a different order, so the copies on different servers stopped matching. The installer now replaces settings in place and says when the shared.envchanged and must be copied to the other servers.
Documentation
- PostgreSQL failover after a hard failure of the primary's server takes about 20–25 seconds (measured 20–24 seconds), not a few seconds; a planned switchover takes a few seconds.
- What a multi-node backup pauses, and for how long: detections and API writes, about a minute and a half on a 7-server test. See High availability.
- Sign-in rate limits and the few seconds a new ingest token takes to reach every ingest server. See Test failover.
- What to do for the load-balancer edge without a floating IP or a DNS provider. See Load balancer options.
Who should upgrade
Every nano Self-run install on v2 must upgrade: v2.0.10 is the minimum licensed release, and earlier v2 builds are locked at their next license check-in. Upgrade from v2.0.9 or earlier by running the installer again on each host, in order; see Upgrade a self-hosted deployment. Open-core installs aren't licensed and can upgrade as usual.