I can’t load the monitors, the app is blocked on the splash screen. According my webmin, the app is marked as “auto-start”, and in journalctl, i got this:
Nov 26 16:55:45 stemy.me systemd[1]: netdata.service: Scheduled restart job, restart counter is at 23477.
Nov 26 16:55:45 stemy.me systemd[1]: Stopped Real time performance monitoring.
Nov 26 16:55:45 stemy.me systemd[1]: Starting Real time performance monitoring...
Nov 26 16:55:45 stemy.me systemd[1]: Started Real time performance monitoring.
Nov 26 16:55:45 stemy.me netdata[32482]: CONFIG: cannot load cloud config '/opt/netdata/var/lib/netdata/cloud.d/cloud.conf'. Running with internal defaults.
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata INFO : MAIN : CONFIG: cannot load cloud config '/opt/netdata/var/lib/netdata/cloud.d/cloud.conf'. Running with internal defaults.
Nov 26 16:55:45 stemy.me netdata[32482]: SIGNAL: Not enabling reaper
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata INFO : MAIN : SIGNAL: Not enabling reaper
Nov 26 16:55:45 stemy.me netdata[32482]: LISTENER: IPv4 bind() on ip '0.0.0.0' port 19999, socktype 1 failed.
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata ERROR : MAIN : LISTENER: IPv4 bind() on ip '0.0.0.0' port 19999, socktype 1 failed. (errno 98, Address already in use)
Nov 26 16:55:45 stemy.me netdata[32482]: LISTENER: Cannot bind to ip '0.0.0.0', port 19999
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata ERROR : MAIN : LISTENER: Cannot bind to ip '0.0.0.0', port 19999
Nov 26 16:55:45 stemy.me netdata[32482]: LISTENER: IPv6 bind() on ip '::' port 19999, socktype 1 failed.
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata ERROR : MAIN : LISTENER: IPv6 bind() on ip '::' port 19999, socktype 1 failed. (errno 98, Address already in use)
Nov 26 16:55:45 stemy.me netdata[32482]: LISTENER: Cannot bind to ip '::', port 19999
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata ERROR : MAIN : LISTENER: Cannot bind to ip '::', port 19999
Nov 26 16:55:45 stemy.me netdata[32482]: LISTENER: Cannot listen on any API socket. Exiting...
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata FATAL : netdata : LISTENER: Cannot listen on any API socket. Exiting... # : Success
Nov 26 16:55:45 stemy.me netdata[32482]: EXIT: netdata prepares to exit with code 1...
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata INFO : MAIN : EXIT: netdata prepares to exit with code 1...
Nov 26 16:55:45 stemy.me netdata[32482]: EXIT: cleaning up the database...
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata INFO : MAIN : EXIT: cleaning up the database...
Nov 26 16:55:45 stemy.me netdata[32482]: Cleaning up database [0 hosts(s)]...
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata INFO : MAIN : Cleaning up database [0 hosts(s)]...
Nov 26 16:55:45 stemy.me netdata[32482]: EXIT: removing netdata PID file '/opt/netdata/var/run/netdata/netdata.pid'...
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata INFO : MAIN : EXIT: removing netdata PID file '/opt/netdata/var/run/netdata/netdata.pid'...
Nov 26 16:55:45 stemy.me netdata[32482]: EXIT: cannot unlink pidfile '/opt/netdata/var/run/netdata/netdata.pid'.
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata ERROR : MAIN : EXIT: cannot unlink pidfile '/opt/netdata/var/run/netdata/netdata.pid'. (errno 2, No such file or directory)
Nov 26 16:55:45 stemy.me netdata[32482]: EXIT: all done - netdata is now exiting - bye bye...
Nov 26 16:55:45 stemy.me netdata[32482]: 2020-11-26 16:55:45: netdata INFO : MAIN : EXIT: all done - netdata is now exiting - bye bye...
Nov 26 16:55:45 stemy.me systemd[1]: netdata.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 16:55:45 stemy.me systemd[1]: netdata.service: Failed with result 'exit-code'.
OS / Environment
Linux stemy.me 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1 (2020-10-18) x86_64 GNU/Linux
etc/os-release:PRETTY_NAME=“Debian GNU/Linux 10 (buster)”
(actually Yunohost, wich is debian based)
According to these messages, it looks like that some process is already running and listening the port 19999, so Netdata cannot start using it. Please, can you run the command netstat -antp and give us the output? This will help us to identify the software that is listening the port.
This does the things a little bit complicate, but let us move forward. I won’t require you to install any new package, please, run the following commands:
The first command will display if there is netdata process running.
The second command will stop any Netdata running, if the first command showed that there was a process running.
Finally we will check if there is a different process listen top the port 19999( Hex value 4E1F).
If the last step does not show any port, you will be able to start Netdata.
These tests are assuming that Netdata is up and running, so we are trying to open an instance before to start a new.
According this output, we have 18 incoming connections for Netdata, probably this is the motive you cannot access it. Are you using a script or other software to call Netdata dashboard?
This last output also did not help us to discover if there was a Netdata running, or another process using this port. Did you run the other two commands?
Finally, do you have other Netdata processes streaming for this host?
Sorry for the delay, but I am at vacation, let me try to help you.
It looks like that Netdata is running, but the sockets opened somehow cannot be closed and it is not possible to open another connection. When you run the following commands:
after the second command, can you see a netdata process running? If there are, we are not able to stop completely Netdata, please, run the next command:
$ sudo killall netdata
$ ps aux| grep netdata
It is expected that after the next command sequence, Netdata won’t be running, after this, try to start Netdata again:
$ sudo systemctl start netdata
Please, let us know if this helped you.
I am in vacation next few days, but I will try to answer you. I am really sorry for this delay to answer you!