On NLS client rsyslog/python/httpd processing stopped
-
GhostRider2110
- Posts: 193
- Joined: Thu Oct 30, 2014 8:04 am
- Location: Indiana
- Contact:
Re: On NLS client rsyslog/python/httpd processing stopped
Interesting, open files limit is showing 1024.
Re: On NLS client rsyslog/python/httpd processing stopped
Might not be a bad idea to at least double that.
How many open files does the nagios user have?
How many open files does the nagios user have?
Code: Select all
lsof -u nagios | wc -lFormer Nagios employee
-
GhostRider2110
- Posts: 193
- Joined: Thu Oct 30, 2014 8:04 am
- Location: Indiana
- Contact:
Re: On NLS client rsyslog/python/httpd processing stopped
On the Nagios server? or the NLS? It's the clients that are hanging.
See-ya
Mitch
See-ya
Mitch
Re: On NLS client rsyslog/python/httpd processing stopped
Right, sorry. I've got my mind stuck on Logserver. I believe your rsyslog should be running on the clients as root, so:
And to display the actual hard limit to compare against (as opposed to just the soft limit) run:
as root as well.
Code: Select all
lsof -u root | wc -lCode: Select all
ulimit -aHFormer Nagios employee
-
GhostRider2110
- Posts: 193
- Joined: Thu Oct 30, 2014 8:04 am
- Location: Indiana
- Contact:
Re: On NLS client rsyslog/python/httpd processing stopped
Code: Select all
[root@igapubrep01 lsaadmin]# lsof -u root | wc -l
1436
[root@igapubrep01 lsaadmin]# ulimit -aH
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 30460
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 4096
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 30460
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Re: On NLS client rsyslog/python/httpd processing stopped
Anything in the elasticsearch logs?I restarted electicsearch and everything started working again.
Code: Select all
cat /var/log/elasticsearch/*.logIt sounds to me like logstash was having trouble with outputting logs to elasticsearch. This could be caused by a host of things - but since restarting logstash did not help, we have to look at elasticsearch.
Regarding your client machines that are getting bogged down - let us know if upping the file limit helps prevent the slowdown at all.
-
GhostRider2110
- Posts: 193
- Joined: Thu Oct 30, 2014 8:04 am
- Location: Indiana
- Contact:
Re: On NLS client rsyslog/python/httpd processing stopped
Looking through them.... I did figure out why my snapshots were not processing as I had mentioned a while back, getting permission denied. I must have not changed the ownership of the datastore to nagios when I created it. Will keep looking through the logs and see if I see anything out of place...
Re: On NLS client rsyslog/python/httpd processing stopped
Let us know what you find out - thanks Mitch.