文件操作 - README.md
返回文件管理
返回主菜单
删除本文件
文件: /usr/local/src/netdata/packaging/installer/README.md
编辑文件内容
<!-- --- title: "Installation guide" custom_edit_url: https://github.com/netdata/netdata/edit/master/packaging/installer/README.md --- --> # Installation guide Netdata is a monitoring agent designed to run on all your systems: physical and virtual servers, containers, even IoT/edge devices. Netdata runs on Linux, FreeBSD, macOS, Kubernetes, Docker, and all their derivatives. The best way to install Netdata is with our [**automatic one-line installation script**](#automatic-one-line-installation-script), which works with all Linux distributions, or our [**.deb/rpm packages**](/packaging/installer/methods/packages.md), which seamlessly install with your distribution's package manager. If you want to install Netdata with Docker, on a Kubernetes cluster, or a different operating system, see [Have a different operating system, or want to try another method?](#have-a-different-operating-system-or-want-to-try-another-method) Some third parties, such as the packaging teams at various Linux distributions, distribute old, broken, or altered packages. We recommend you install Netdata using one of the methods listed below to guarantee you get the latest checksum-verified packages. Starting with v1.12, Netdata collects anonymous usage information by default and sends it to Google Analytics. Read about the information collected, and learn how to-opt, on our [anonymous statistics](/docs/anonymous-statistics.md) page. The usage statistics are _vital_ for us, as we use them to discover bugs and prioritize new features. We thank you for _actively_ contributing to Netdata's future. ## Automatic one-line installation script   This method is fully automatic on all Linux distributions, including Ubuntu, Debian, Fedora, CentOS, and others. To install Netdata from source and get _automatic nightly updates_, run the following as your normal user: ```bash bash <(curl -Ss https://my-netdata.io/kickstart.sh) ``` To see more information about this installation script, including how to disable automatic updates, get nightly vs. stable releases, or disable anonymous statistics, see the [`kickstart.sh` method page](/packaging/installer/methods/kickstart.md). Scroll down for details about [automatic updates](#automatic-updates) or [nightly vs. stable releases](#nightly-vs-stable-releases). When you finish installing Netdata, be sure to visit our [step-by-step guide](/docs/guides/step-by-step/step-00.md) for a fully-guided tour into Netdata's capabilities and how to configure it according to your needs. Or, if you're a monitoring and system administration pro, skip ahead to our [getting started guide](/docs/getting-started.md) for a quick overview. ## Have a different operating system, or want to try another method? Netdata works on many different operating systems, each with a few possible installation methods. To see the full list of approved methods for each operating system/version we support, see our [distribution matrix](/packaging/DISTRIBUTIONS.md). Below, you can find a few additional installation methods, followed by separate instructions for a variety of unique operating systems. ### Alternative methods <div class="installer-grid" markdown="1"> [ Install with .deb or .rpm packages](/packaging/installer/methods/packages.md) [ Install with a pre-built static binary for 64-bit systems](/packaging/installer/methods/kickstart-64.md) [ Install Netdata on Docker](/packaging/docker/README.md) [ Install Netdata on Kubernetes with a Helm chart](https://github.com/netdata/helmchart#netdata-helm-chart-for-kubernetes-deployments) [ Install Netdata on cloud providers (GCP/AWS/Azure)](/packaging/installer/methods/cloud-providers.md) [ Install Netdata on macOS](/packaging/installer/methods/macos.md) [ Install Netdata on FreeBSD](/packaging/installer/methods/freebsd.md) [ Install manually from source](/packaging/installer/methods/manual.md) [ Install on offline/air-gapped systems](/packaging/installer/methods/offline.md) [ Installation on PFSense](/packaging/installer/methods/pfsense.md) [ Install Netdata on Synology](/packaging/installer/methods/synology.md) [ Manual installation on FreeNAS](/packaging/installer/methods/freenas.md) [ Manual installation on Alpine](/packaging/installer/methods/alpine.md) </div> ## Automatic updates By default, Netdata's installation scripts enable automatic updates for both nightly and stable release channels. If you would prefer to update your Netdata agent manually, you can disable automatic updates by using the `--no-updates` option when you install or update Netdata using the [automatic one-line installation script](#automatic-one-line-installation-script). ```bash bash <(curl -Ss https://my-netdata.io/kickstart.sh) --no-updates ``` With automatic updates disabled, you can choose exactly when and how you [update Netdata](/packaging/installer/UPDATE.md). ## Nightly vs. stable releases The Netdata team maintains two releases of the Netdata agent: **nightly** and **stable**. By default, Netdata's installation scripts will give you **automatic, nightly** updates, as that is our recommended configuration. **Nightly**: We create nightly builds every 24 hours. They contain fully-tested code that fixes bugs or security flaws, or introduces new features to Netdata. Every nightly release is a candidate for then becoming a stable release—when we're ready, we simply change the release tags on GitHub. That means nightly releases are stable and proven to function correctly in the vast majority of Netdata use cases. That's why nightly is the _best choice for most Netdata users_. **Stable**: We create stable releases whenever we believe the code has reached a major milestone. Most often, stable releases correlate with the introduction of new, significant features. Stable releases might be a better choice for those who run Netdata in _mission-critical production systems_, as updates will come more infrequently, and only after the community helps fix any bugs that might have been introduced in previous releases. **Pros of using nightly releases:** - Get the latest features and bug fixes as soon as they're available - Receive security-related fixes immediately - Use stable, fully-tested code that's always improving - Leverage the same Netdata experience our community is using **Pros of using stable releases:** - Protect yourself from the rare instance when major bugs slip through our testing and negatively affect a Netdata installation - Retain more control over the Netdata version you use ## Installation notes and known issues We are tracking a few issues related to installation and packaging. ### Older distributions (Ubuntu 14.04, Debian 8, CentOS 6) and OpenSSL If you're running an older Linux distribution or one that has reached EOL, such as Ubuntu 14.04 LTS, Debian 8, or CentOS 6, your Agent may not be able to securely connect to Netdata Cloud due to an outdated version of OpenSSL. These old versions of OpenSSL cannot perform [hostname validation](https://wiki.openssl.org/index.php/Hostname_validation), which helps securely encrypt SSL connections. We recommend you reinstall Netdata with a [static build](/packaging/installer/methods/kickstart-64.md), which uses an up-to-date version of OpenSSL with hostname validation enabled. If you choose to continue using the outdated version of OpenSSL, your node will still connect to Netdata Cloud, albeit with hostname verification disabled. Without verification, your Netdata Cloud connection could be vulnerable to man-in-the-middle attacks. ### CentOS 6 and CentOS 8 To install the Agent on certain CentOS and RHEL systems, you must enable non-default repositories, such as EPEL or PowerTools, to gather hard dependencies. See the [CentOS 6](/packaging/installer/methods/manual.md#centos-rehel-6-x) and [CentOS 8](/packaging/installer/methods/manual.md#centos-rehel-8-x) sections for more information. ### Multiple versions of OpenSSL We've received reports from the community about issues with running the `kickstart.sh` script on systems that have both a distribution-installed version of OpenSSL and a manually-installed local version. The Agent's installer cannot handle both. We recommend you install Netdata with the [static binary](/packaging/installer/methods/kickstart-64.md) to avoid the issue altogether. Or, you can manually remove one version of OpenSSL to remove the conflict. ### Clang compiler on Linux Our current build process has some issues when using certain configurations of the `clang` C compiler on Linux. See [the section on `nonrepresentable section on output` errors](/packaging/installer/methods/manual.md#nonrepresentable-section-on-output-errors) for a workaround.
修改文件时间
将文件时间修改为当前时间的前一年
删除文件