netdata / binary-packages Goto Github PK

Shell 100.00%

binary-packages's Introduction

IMPORTANT NOTICE

Over the past few months, we have deprecated the usage of this repository. Our netdata is supported through https://github.com/netdata/netdata repository. Our nightly releases are no longer hosted here, we have moved to a different hosting solution for this. Should you wish to install netdata, you should read our documentation section in https://netdata.cloud and follow the relative instructions on how to do so.

binary-packages (DEPRECATED)

This repo hosts older binary packages for netdata. Please use the releases page for newer binary packages.

netdata `.run` files

Files ending in .run are Linux binary self-extracting shell scripts, generated with makeself.

To use one, download it and run it.

To install the latest version use this:

bash <(curl -Ss https://my-netdata.io/kickstart-static64.sh)

If your shell fails to handle the above one liner, do this:

curl -Ss https://my-netdata.io/kickstart-static64.sh >/tmp/kickstart-static64.sh
sh /tmp/kickstart-static64.sh

installs in `/opt/netdata`

The package will install everything in /opt/netdata (remember to prepend /opt/netdata to command examples found in the netdata wiki).

The following changes will be made to the system:

user netdata will be added.
group netdata will be added.
logrotate configuration will be added at /etc/logrotate.d/netdata.
if the system is running systemd, the file /etc/systemd/system/netdata.service will be created.
if the system is not running systemd, then depending on the distribution and version the file /etc/init.d/netdata will be added. This works for older Ubuntu, Debian, CentOS and for OpenRC based Gentoo systems.

Other than the above, the system is not altered in any way.

Statically linked

All programs included in the package are statically linked and do not depend on any system library. The operating system is expected to provide very basic tools, like tar, gzip, etc, so they can be used even if the system is just a busybox. For example, these packages run on CirrOS.

You can use these binary files for installing netdata:

On ancient Linux installations, that you cannot update for a reason.
On Linux distributions that do not provide a package management system (CirrOS, CoreOS, etc).

Key dependencies included

These packages include:

statically linked BASH, version 4+
statically linked curl, version 7.53.1+
statically linked fping, version 4.0+
statically linked netdata, version 1.6+, with statically linked apps.plugin.

install and update

The packages can be used to update an existing installation made by another version of them.

If you want to use these packages on systems that you have installed netdata from source, we suggest to uninstall the previous version first. If you don't uninstall it, these package will fail to update your system properly (i.e. they will not overwrite the existing /etc/systemd/system/netdata.service, /etc/logrotate.d/netdata, /etc/init.d/netdata).

binary-packages's People

Contributors

Stargazers

Watchers

Forkers

henry-spanka ehekatl batsman2skip yuvapradeep jweede masterscott jahau isabella232

binary-packages's Issues

/opt

[bug] stop netdata daemon take too long time

stop netdata daemon take too long time when I use binary-package.
Maybe some thread deadlock?

System Environment

OS: CentOS 6.3
CPU Core: 1
memory: 4GB
netdata version: netdata-v1.9.0-46-g87cff3fd

binary_package:

sudo sh -c 'time /sbin/service netdata stop'
Stopping netdata...                                        [  OK  ]

real	1m1.122s
user	0m0.009s
sys	0m0.004s

error.log:

2017-12-26 18:49:38: netdata INFO : SIGNAL: Received SIGTERM. Cleaning up to exit...
2017-12-26 18:49:38: netdata INFO : Cleaning up database [1 hosts(s)]...
2017-12-26 18:49:38: netdata INFO : Cleaning up database of host '***********'...
2017-12-26 18:49:38: netdata INFO : DISKSPACE thread exiting
2017-12-26 18:49:38: netdata INFO : CGROUP thread exiting
2017-12-26 18:49:38: netdata INFO : PROC thread exiting
2017-12-26 18:49:38: netdata ERROR: PLUGINSD: plugin '/opt/netdata/usr/libexec/netdata/plugins.d/apps.plugin' disconnected.
2017-12-26 18:49:38: netdata INFO : PLUGINSD: '/opt/netdata/usr/libexec/netdata/plugins.d/apps.plugin' on pid 20034 stopped after 104 successful data collections (ENDs).
2017-12-26 18:49:38: netdata ERROR: child pid 20034 killed by signal 15. (errno 9, Bad file descriptor)
2017-12-26 18:49:38: netdata INFO : PLUGINSD: '/opt/netdata/usr/libexec/netdata/plugins.d/apps.plugin' thread exiting
2017-12-26 18:49:38: netdata INFO : netdata exiting. Bye bye...
2017-12-26 18:49:39: netdata ERROR: PLUGINSD: plugin '/opt/netdata/usr/libexec/netdata/plugins.d/python.d.plugin' disconnected.
2017-12-26 18:49:39: netdata INFO : PLUGINSD: '/opt/netdata/usr/libexec/netdata/plugins.d/python.d.plugin' on pid 20032 stopped after 39 successful data collections (ENDs).
2017-12-26 18:49:39: netdata INFO : IDLEJITTER thread exiting
2017-12-26 18:49:46: netdata INFO : HEALTH thread exiting
2017-12-26 18:49:46: netdata INFO : PLUGINSD: '/opt/netdata/usr/libexec/netdata/plugins.d/charts.d.plugin' thread exiting
2017-12-26 18:50:36: netdata INFO : PLUGINS.D thread exiting

source build:

$ sudo sh -c 'time /sbin/service netdata stop'
Stopping netdata...                                        [  OK  ]

real	0m0.116s
user	0m0.009s
sys	0m0.003s

error.log:

2017-12-26 18:49:38: netdata INFO : SIGNAL: Received SIGTERM. Cleaning up to exit...
2017-12-26 18:49:38: netdata INFO : Cleaning up database [1 hosts(s)]...
2017-12-26 18:49:38: netdata INFO : Cleaning up database of host '****************'...
2017-12-26 18:49:38: netdata INFO : DISKSPACE thread exiting
2017-12-26 18:49:38: netdata ERROR: PLUGINSD: plugin '/opt/netdata/usr/libexec/netdata/plugins.d/apps.plugin' disconnected.
2017-12-26 18:49:38: netdata INFO : PLUGINSD: '/opt/netdata/usr/libexec/netdata/plugins.d/apps.plugin' on pid 12761 stopped after 104 successful data collections (ENDs).
2017-12-26 18:49:38: netdata ERROR: child pid 12761 killed by signal 15. (errno 9, Bad file descriptor)
2017-12-26 18:49:38: netdata INFO : PLUGINSD: '/opt/netdata/usr/libexec/netdata/plugins.d/apps.plugin' thread exiting
2017-12-26 18:49:38: netdata ERROR: Cannot unlink pidfile '/opt/netdata/var/run/netdata.pid'. (errno 13, Permission denied)
2017-12-26 18:49:38: netdata INFO : netdata exiting. Bye bye...
2017-12-26 18:49:39: python.d FATAL: cannot send data to netdata: [Errno 32] Broken pipe
2017-12-26 18:49:39: python.d FATAL: cannot send data to netdata: [Errno 32] Broken pipe
2017-12-26 18:49:39: python.d FATAL: cannot send data to netdata: [Errno 32] Broken pipe
2017-12-26 18:49:39: python.d FATAL: cannot send data to netdata: [Errno 32] Broken pipe
2017-12-26 18:49:39: python.d FATAL: cannot send data to netdata: [Errno 32] Broken pipe
2017-12-26 18:49:39: python.d FATAL: no more jobs

Openldap deployment on existing server

Hello,

I have configured Openldap directory server in my environment with a test client server running Linux OS to evaluate logins and authentications. However, now I'm looking to bring some existing servers in my non-prod environment which are running Linux OS and on which users are created locally on each server from before and their login authentication is also happening locally.

I need to configure the already existing servers as ldap client and migrate the users password sitting on the /etc/shadow file to my Openldap server so that their login is now authenticated from the directory server. Could someone please explain, how would I go about this process, what things do I need to do in order to achieve this?

Thanks

Check version of netdata installation from command line?

How to find out what version of netdata is installed?

All I've been able to find is:

# cat /opt/netdata/netdata-web-files/version.txt
16886efb0d56a244fafd73307544e58eae0ab9a5
#

But,

how to look this up to see its exact meaning (I can't find it in the commits through the GitHub UI), and
how to find a human-readable version number from the command line?

Uninstall binary netdata package?

After installing from netdata-latest.gz.run, it appears there is no automated way to uninstall.

If this is the case, can such a method please be added or created? Or if there is already such a method, can it please be documented? :)

If there is no automated uninstall method - what manual steps can I take to uninstall?

ipmi plugin for binary package

Is there a way to build the binary packages with IMPI monitoring support?

I've tried doing it myself by running build-latest.sh on a system that has libipmimonitoring-dev installed, and while IPMI showed up after the build script installed netdata from source, once I remove that and installed the .run file it generated there was no ipmi monitoring.