Hello,
We are getting constant errors in regards to Max load reached. I am aware that you are able to change the load - threshold, but before doing so we would like to know what this actually means. It is currently set at 10.000000, but can sometimes reach 600/10.
[06-20-2017 08:28:34] NPCD: WARN: MAX load reached: load 45.420000/10.000000 at i=1
[06-20-2017 08:28:52] NPCD: WARN: MAX load reached: load 44.500000/10.000000 at i=1
[06-20-2017 08:29:15] NPCD: WARN: MAX load reached: load 45.730000/10.000000 at i=1
[06-20-2017 08:29:34] NPCD: WARN: MAX load reached: load 50.220000/10.000000 at i=1
[06-20-2017 08:29:53] NPCD: WARN: MAX load reached: load 54.750000/10.000000 at i=1
[06-20-2017 08:30:19] NPCD: WARN: MAX load reached: load 56.080000/10.000000 at i=1
[06-20-2017 08:30:35] NPCD: WARN: MAX load reached: load 60.230000/10.000000 at i=1
[06-20-2017 08:30:58] NPCD: WARN: MAX load reached: load 61.880000/10.000000 at i=1
[06-20-2017 08:31:18] NPCD: WARN: MAX load reached: load 60.770000/10.000000 at i=1
[06-20-2017 08:31:47] NPCD: WARN: MAX load reached: load 62.730000/10.000000 at i=1
[06-20-2017 08:32:58] NPCD: npcd Daemon (0.4.14) started with PID=1442
[06-20-2017 08:32:58] NPCD: Please have a look at 'npcd -V' to get license information
[06-20-2017 08:32:58] NPCD: HINT: load_threshold is enabled - ('10.000000')
[06-20-2017 08:33:38] NPCD: ERROR: Executed command exits with return code '7'
Please can you explain what load_threshold ('10.00000') means?
I then checked the spool files like in this document: https://support.nagios.com/kb/article.php?id=9.
When running: ls /usr/local/nagios/var/spool/perfdata/ | wc -l, i get the following: '1'
When running: ls /usr/local/nagios/var/spool/xidpe/ | wc -l, i get the following: '0'.
Any help would be greatly appreciated.
Thanks,
NPCD: WARN: Max load reached
Re: NPCD: WARN: Max load reached
The load_threshold option is so NPCD will not start new threads if your system load is too high.
What this means is if the systems load it high, it will stop processing performance graphs which would add to the load.
This setting tries to keep the system running as smoothly as possible sacrificing some points for your graphs.
The setting of 10 is if the average load of the system is over 10, then it will stop processing the graph data.
To find out the processes that are generating the most load, run the following as root on the Nagios server.
It will show the top 20 processes.
What this means is if the systems load it high, it will stop processing performance graphs which would add to the load.
This setting tries to keep the system running as smoothly as possible sacrificing some points for your graphs.
The setting of 10 is if the average load of the system is over 10, then it will stop processing the graph data.
To find out the processes that are generating the most load, run the following as root on the Nagios server.
Code: Select all
top -b -n1 |head -n 27Be sure to check out our Knowledgebase for helpful articles and solutions!
-
michal.nastaly
- Posts: 59
- Joined: Tue Jun 02, 2015 9:24 am
Re: NPCD: WARN: Max load reached
Thank you for replying,
We've had to reboot our nagiosxi box because monitoring disappeared from our dashboard.
I've run this command and the following comes up:
top - 1[/code]2:05:04 up 1:10, 1 user, load average: 0.39, 0.26, 0.20
Tasks: 148 total, 4 running, 144 sleeping, 0 stopped, 0 zombie
Cpu(s): 21.5%us, 2.6%sy, 0.0%ni, 75.3%id, 0.6%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 1019168k total, 833808k used, 185360k free, 10484k buffers
Swap: 2064380k total, 39992k used, 2024388k free, 261956k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1362 mysql 20 0 713m 34m 3848 S 18.3 3.4 1:01.23 mysqld
1679 apache 20 0 443m 28m 4132 R 16.4 2.8 0:53.64 httpd
1541 apache 20 0 433m 18m 4380 S 11.0 1.9 0:59.58 httpd
1544 apache 20 0 443m 29m 4404 S 11.0 2.9 0:57.36 httpd
1700 apache 20 0 443m 28m 4240 R 9.1 2.8 0:53.34 httpd
1540 apache 20 0 433m 18m 4352 S 3.7 1.9 0:59.41 httpd
1542 apache 20 0 433m 18m 4480 R 3.7 1.9 0:57.46 httpd
24890 nagios 20 0 311m 21m 7684 S 1.8 2.2 0:00.09 php
1 root 20 0 19232 1212 960 S 0.0 0.1 0:00.89 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
4 root 20 0 0 0 0 S 0.0 0.0 0:00.06 ksoftirqd/0
5 root RT 0 0 0 0 S 0.0 0.0 0:00.00 stopper/0
6 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
7 root 20 0 0 0 0 S 0.0 0.0 0:02.01 events/0
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events/0
9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events_long/0
10 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events_power_ef
11 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cgroup
12 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper
Apologies for the poor formatting.
I've run the command a few times and it generates a different response every time.
We've had some more of the following errors occur this morning:
[06-21-2017 10:54:11] NPCD: WARN: MAX load reached: load 248.500000/10.000000 at i=1
[06-21-2017 10:54:28] NPCD: WARN: MAX load reached: load 249.430000/10.000000 at i=1
[06-21-2017 10:54:45] NPCD: WARN: MAX load reached: load 249.220000/10.000000 at i=1
[06-21-2017 10:55:13] NPCD: npcd Daemon (0.4.14) started with PID=1508
[06-21-2017 10:55:13] NPCD: Please have a look at 'npcd -V' to get license information
[06-21-2017 10:55:13] NPCD: HINT: load_threshold is enabled - ('10.000000')
Our perfdata.log doesn't seem to be keeping up to date either.
Please can you explain what this means and what we can do about it?
Thank you!
We've had to reboot our nagiosxi box because monitoring disappeared from our dashboard.
I've run this command and the following comes up:
top - 1[/code]2:05:04 up 1:10, 1 user, load average: 0.39, 0.26, 0.20
Tasks: 148 total, 4 running, 144 sleeping, 0 stopped, 0 zombie
Cpu(s): 21.5%us, 2.6%sy, 0.0%ni, 75.3%id, 0.6%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 1019168k total, 833808k used, 185360k free, 10484k buffers
Swap: 2064380k total, 39992k used, 2024388k free, 261956k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1362 mysql 20 0 713m 34m 3848 S 18.3 3.4 1:01.23 mysqld
1679 apache 20 0 443m 28m 4132 R 16.4 2.8 0:53.64 httpd
1541 apache 20 0 433m 18m 4380 S 11.0 1.9 0:59.58 httpd
1544 apache 20 0 443m 29m 4404 S 11.0 2.9 0:57.36 httpd
1700 apache 20 0 443m 28m 4240 R 9.1 2.8 0:53.34 httpd
1540 apache 20 0 433m 18m 4352 S 3.7 1.9 0:59.41 httpd
1542 apache 20 0 433m 18m 4480 R 3.7 1.9 0:57.46 httpd
24890 nagios 20 0 311m 21m 7684 S 1.8 2.2 0:00.09 php
1 root 20 0 19232 1212 960 S 0.0 0.1 0:00.89 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
4 root 20 0 0 0 0 S 0.0 0.0 0:00.06 ksoftirqd/0
5 root RT 0 0 0 0 S 0.0 0.0 0:00.00 stopper/0
6 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
7 root 20 0 0 0 0 S 0.0 0.0 0:02.01 events/0
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events/0
9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events_long/0
10 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events_power_ef
11 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cgroup
12 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper
Apologies for the poor formatting.
I've run the command a few times and it generates a different response every time.
We've had some more of the following errors occur this morning:
[06-21-2017 10:54:11] NPCD: WARN: MAX load reached: load 248.500000/10.000000 at i=1
[06-21-2017 10:54:28] NPCD: WARN: MAX load reached: load 249.430000/10.000000 at i=1
[06-21-2017 10:54:45] NPCD: WARN: MAX load reached: load 249.220000/10.000000 at i=1
[06-21-2017 10:55:13] NPCD: npcd Daemon (0.4.14) started with PID=1508
[06-21-2017 10:55:13] NPCD: Please have a look at 'npcd -V' to get license information
[06-21-2017 10:55:13] NPCD: HINT: load_threshold is enabled - ('10.000000')
Our perfdata.log doesn't seem to be keeping up to date either.
Please can you explain what this means and what we can do about it?
Thank you!
Re: NPCD: WARN: Max load reached
The output of the top command is showing you which processes are taking the most CPU time.
The mysql database and the Apache web server are using the most on your server.
One thing I see that may fix the issue is to add more memory to the system.
It is setup with 1 Gig of RAM but it is close to being all used and in the past, the system did use the swap and that is much slower and it is determined by the Hard Drive speed.
Increase the system to 4 Gigs of RAM and add a couple of CPU's to the system if it is running in a virtual environment.
Unless you turned on debugging, there will not be any new entries in the perfdata.log file.
By default, it will only show errors.
Try increasing the memory and CPU and let us know if that makes the system perform faster.
The mysql database and the Apache web server are using the most on your server.
One thing I see that may fix the issue is to add more memory to the system.
It is setup with 1 Gig of RAM but it is close to being all used and in the past, the system did use the swap and that is much slower and it is determined by the Hard Drive speed.
Increase the system to 4 Gigs of RAM and add a couple of CPU's to the system if it is running in a virtual environment.
Unless you turned on debugging, there will not be any new entries in the perfdata.log file.
By default, it will only show errors.
Try increasing the memory and CPU and let us know if that makes the system perform faster.
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
michal.nastaly
- Posts: 59
- Joined: Tue Jun 02, 2015 9:24 am
Re: NPCD: WARN: Max load reached
Hello,
Thanks for your input, but we are having the same problem on another box, which has 8GB RAM and 4 CPU's.
top - 08:34:25 up 18 min, 1 user, load average: 0.38, 0.37, 0.22
Tasks: 6230 total, 1 running, 6229 sleeping, 0 stopped, 0 zombie
Cpu(s): 8.4%us, 0.7%sy, 0.0%ni, 90.6%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 8060772k total, 2198340k used, 5862432k free, 25012k buffers
Swap: 2064376k total, 0k used, 2064376k free, 130248k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8733 root 20 0 19732 5928 880 R 16.5 0.1 0:00.19 top
1 root 20 0 19232 1560 1264 S 0.0 0.0 0:00.93 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
5 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
6 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
7 root RT 0 0 0 0 S 0.0 0.0 0:00.06 migration/1
8 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/1
9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/1
10 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/1
11 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/2
12 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/2
13 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/2
14 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/2
15 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/3
16 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/3
17 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/3
18 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/3
19 root 20 0 0 0 0 S 0.0 0.0 0:00.52 events/0
The boxes are still not happy and webpage that nagios is hosting was unavailable.
[06-21-2017 02:06:38] NPCD: ERROR: Executed command exits with return code '7'
[06-21-2017 02:06:38] NPCD: ERROR: Command line was '/usr/local/nagios/libexec/process_perfdata.pl -n -b /usr/local/nagios/var/spool/perfdata//1498007176.perfdata.service'
[06-21-2017 12:25:41] NPCD: Caught Termination Signal - Hasta la vista... baby
[06-21-2017 12:26:47] NPCD: npcd Daemon (0.4.14) started with PID=1625
[06-21-2017 12:26:47] NPCD: Please have a look at 'npcd -V' to get license information
[06-21-2017 12:26:47] NPCD: HINT: load_threshold is enabled - ('10.000000')
[06-21-2017 19:00:09] NPCD: npcd Daemon (0.4.14) started with PID=1667
[06-21-2017 19:00:09] NPCD: Please have a look at 'npcd -V' to get license information
[06-21-2017 19:00:09] NPCD: HINT: load_threshold is enabled - ('10.000000')
[06-22-2017 07:50:23] NPCD: npcd Daemon (0.4.14) started with PID=1715
[06-22-2017 07:50:23] NPCD: Please have a look at 'npcd -V' to get license information
[06-22-2017 07:50:23] NPCD: HINT: load_threshold is enabled - ('10.000000')
[06-22-2017 08:01:11] NPCD: npcd Daemon (0.4.14) started with PID=1724
[06-22-2017 08:01:11] NPCD: Please have a look at 'npcd -V' to get license information
[06-22-2017 08:01:11] NPCD: HINT: load_threshold is enabled - ('10.000000')
[06-22-2017 08:10:16] NPCD: Caught Termination Signal - Hasta la vista... baby
[06-22-2017 08:16:36] NPCD: npcd Daemon (0.4.14) started with PID=1675
[06-22-2017 08:16:36] NPCD: Please have a look at 'npcd -V' to get license information
[06-22-2017 08:16:36] NPCD: HINT: load_threshold is enabled - ('10.000000')
Thanks,
Thanks for your input, but we are having the same problem on another box, which has 8GB RAM and 4 CPU's.
top - 08:34:25 up 18 min, 1 user, load average: 0.38, 0.37, 0.22
Tasks: 6230 total, 1 running, 6229 sleeping, 0 stopped, 0 zombie
Cpu(s): 8.4%us, 0.7%sy, 0.0%ni, 90.6%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 8060772k total, 2198340k used, 5862432k free, 25012k buffers
Swap: 2064376k total, 0k used, 2064376k free, 130248k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8733 root 20 0 19732 5928 880 R 16.5 0.1 0:00.19 top
1 root 20 0 19232 1560 1264 S 0.0 0.0 0:00.93 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
5 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
6 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
7 root RT 0 0 0 0 S 0.0 0.0 0:00.06 migration/1
8 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/1
9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/1
10 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/1
11 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/2
12 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/2
13 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/2
14 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/2
15 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/3
16 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/3
17 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/3
18 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/3
19 root 20 0 0 0 0 S 0.0 0.0 0:00.52 events/0
The boxes are still not happy and webpage that nagios is hosting was unavailable.
[06-21-2017 02:06:38] NPCD: ERROR: Executed command exits with return code '7'
[06-21-2017 02:06:38] NPCD: ERROR: Command line was '/usr/local/nagios/libexec/process_perfdata.pl -n -b /usr/local/nagios/var/spool/perfdata//1498007176.perfdata.service'
[06-21-2017 12:25:41] NPCD: Caught Termination Signal - Hasta la vista... baby
[06-21-2017 12:26:47] NPCD: npcd Daemon (0.4.14) started with PID=1625
[06-21-2017 12:26:47] NPCD: Please have a look at 'npcd -V' to get license information
[06-21-2017 12:26:47] NPCD: HINT: load_threshold is enabled - ('10.000000')
[06-21-2017 19:00:09] NPCD: npcd Daemon (0.4.14) started with PID=1667
[06-21-2017 19:00:09] NPCD: Please have a look at 'npcd -V' to get license information
[06-21-2017 19:00:09] NPCD: HINT: load_threshold is enabled - ('10.000000')
[06-22-2017 07:50:23] NPCD: npcd Daemon (0.4.14) started with PID=1715
[06-22-2017 07:50:23] NPCD: Please have a look at 'npcd -V' to get license information
[06-22-2017 07:50:23] NPCD: HINT: load_threshold is enabled - ('10.000000')
[06-22-2017 08:01:11] NPCD: npcd Daemon (0.4.14) started with PID=1724
[06-22-2017 08:01:11] NPCD: Please have a look at 'npcd -V' to get license information
[06-22-2017 08:01:11] NPCD: HINT: load_threshold is enabled - ('10.000000')
[06-22-2017 08:10:16] NPCD: Caught Termination Signal - Hasta la vista... baby
[06-22-2017 08:16:36] NPCD: npcd Daemon (0.4.14) started with PID=1675
[06-22-2017 08:16:36] NPCD: Please have a look at 'npcd -V' to get license information
[06-22-2017 08:16:36] NPCD: HINT: load_threshold is enabled - ('10.000000')
Thanks,
Re: NPCD: WARN: Max load reached
There looks like there are not any processes causing high load in the previous post but the server has over 6200 processes running on it and with that many, that could cause the performance graphs to stop.
Take a look at the processes that are running and stop them if they are not needed and that should make the server perform better.
Also, there are not any MAX load reached messages in the NPCD log so they should be populating.
Take a look at the processes that are running and stop them if they are not needed and that should make the server perform better.
Also, there are not any MAX load reached messages in the NPCD log so they should be populating.
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
michal.nastaly
- Posts: 59
- Joined: Tue Jun 02, 2015 9:24 am
Re: NPCD: WARN: Max load reached
We're getting an insane amount of sleeping processes. It's up to 32500 now.
when i type in the command:
i get a huge list of sleeping processes and they are all the same line. some have been sleeping for hours.
Do you know how we can stop these processes from piling up?
when i type in the command:
Code: Select all
ps -eo pid,cmd,etimei have compared that .cfg file with our other nagios boxes and they have the exact same settings but the amount of sleeping processes on the others aren't going above 500.nsca -c /usr/local/nagios/etc/nsca.cfg --inetd
Do you know how we can stop these processes from piling up?
Re: NPCD: WARN: Max load reached
The NSCA processes that are piling up are probably coming from remote systems that are configured to send passive checks to the Nagios server.
If they try and send and the connection is dropped during the transfer of data or that the settings are incorrect, it could leave the NSCP process running.
Check a few of the remote hosts log files and see if you can find out why they are not sending.
The NSCA process is loaded on demand by the xinetd daemon and if you run the following and post the output, I can check the configuration file's settings.
If they try and send and the connection is dropped during the transfer of data or that the settings are incorrect, it could leave the NSCP process running.
Check a few of the remote hosts log files and see if you can find out why they are not sending.
The NSCA process is loaded on demand by the xinetd daemon and if you run the following and post the output, I can check the configuration file's settings.
Code: Select all
cat /etc/xinetd.d/nscaBe sure to check out our Knowledgebase for helpful articles and solutions!
-
michal.nastaly
- Posts: 59
- Joined: Tue Jun 02, 2015 9:24 am
Re: NPCD: WARN: Max load reached
The output of that command is :
# default: on
# description: NSCA (Nagios Service Check Acceptor)
service nsca
{
per_source = UNLIMITED
instances = UNLIMITED
flags = REUSE
socket_type = stream
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/nsca
server_args = -c /usr/local/nagios/etc/nsca.cfg --inetd
log_on_failure += USERID
disable = no
# only_from = 127.0.0.1
}
# default: on
# description: NSCA (Nagios Service Check Acceptor)
service nsca
{
per_source = UNLIMITED
instances = UNLIMITED
flags = REUSE
socket_type = stream
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/nsca
server_args = -c /usr/local/nagios/etc/nsca.cfg --inetd
log_on_failure += USERID
disable = no
# only_from = 127.0.0.1
}
-
michal.nastaly
- Posts: 59
- Joined: Tue Jun 02, 2015 9:24 am
Re: NPCD: WARN: Max load reached
Here is a log from a remote host:
2017-06-23 14:18:33: error:c:\source\master\modules\Scheduler\Scheduler.cpp:174: Failed to submit Drives: Error: Retry failed
2017-06-23 14:18:39: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:18:39: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:18:39: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:18:39: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:18:39: error:c:\source\master\modules\Scheduler\Scheduler.cpp:174: Failed to submit Drive C: Error: Retry failed
2017-06-23 14:19:52: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:19:52: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:19:52: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:19:52: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:19:52: error:c:\source\master\modules\Scheduler\Scheduler.cpp:174: Failed to submit Windows Services: Error: Retry failed
2017-06-23 14:20:31: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:31: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:31: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:31: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:31: error:c:\source\master\modules\Scheduler\Scheduler.cpp:174: Failed to submit Uptime: Error: Retry failed
2017-06-23 14:20:41: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:41: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:41: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:41: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:41: error:c:\source\master\modules\Scheduler\Scheduler.cpp:174: Failed to submit Memory RAM: Error: Retry failed
2017-06-23 14:18:33: error:c:\source\master\modules\Scheduler\Scheduler.cpp:174: Failed to submit Drives: Error: Retry failed
2017-06-23 14:18:39: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:18:39: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:18:39: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:18:39: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:18:39: error:c:\source\master\modules\Scheduler\Scheduler.cpp:174: Failed to submit Drive C: Error: Retry failed
2017-06-23 14:19:52: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:19:52: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:19:52: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:19:52: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:19:52: error:c:\source\master\modules\Scheduler\Scheduler.cpp:174: Failed to submit Windows Services: Error: Retry failed
2017-06-23 14:20:31: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:31: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:31: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:31: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:31: error:c:\source\master\modules\Scheduler\Scheduler.cpp:174: Failed to submit Uptime: Error: Retry failed
2017-06-23 14:20:41: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:41: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:41: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:41: error:c:\source\master\include\socket/client.hpp:145: Failed to read data: End of file
2017-06-23 14:20:41: error:c:\source\master\modules\Scheduler\Scheduler.cpp:174: Failed to submit Memory RAM: Error: Retry failed