Page 4 of 8
Re: Configure Exim MailServer Logs With NLS
Posted: Tue Feb 02, 2016 10:41 am
by rkennedy
Hm, java can't start and this may be the issue. What is the result of top|head -5 and free -m?
Re: Configure Exim MailServer Logs With NLS
Posted: Tue Feb 02, 2016 12:46 pm
by rlinux57
Code: Select all
[root@logs ~]# top|head -5
top - 22:45:47 up 15 days, 6:07, 1 user, load average: 0.01, 0.02, 0.00
Tasks: 37 total, 1 running, 36 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.2%us, 0.1%sy, 0.0%ni, 99.7%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 2097152k total, 1716980k used, 380172k free, 0k buffers
Swap: 0k total, 0k used, 0k free, 57808k cached
Code: Select all
[root@logs ~]# free -m
total used free shared buffers cached
Mem: 2048 1676 371 3 0 56
-/+ buffers/cache: 1619 428
Swap: 0 0 0
Re: Configure Exim MailServer Logs With NLS
Posted: Tue Feb 02, 2016 1:03 pm
by jolson
Could not reserve enough space for object heap
This is the concerning error to me, and it's why we checked your available memory. Is there any chance you could bump the server up to 4GB of memory temporarily to see if that helps resolve the issue?
Logstash will want at least 256MB of RAM to start up properly, and java appears to be unable to allocate any memory to itself. Let me know if the above helps, thanks!
Re: Configure Exim MailServer Logs With NLS
Posted: Tue Feb 09, 2016 2:59 am
by rlinux57
I have upgraded the ram 2GB to 4GB, its working but after a couple of second service again dead.
Code: Select all
service logstash restart
Restarting Logstash Daemon: [ OK ]
WARNING: Default JAVA_OPTS will be overridden by the JAVA_OPTS defined in the environment. Environment JAVA_OPTS are -Djava.io.tmpdir=/usr/local/nagioslogserver/tmp
[ OK ]
Code: Select all
[root@logs ~]# service logstash status
Logstash Daemon dead but pid file exists
Re: Configure Exim MailServer Logs With NLS
Posted: Tue Feb 09, 2016 4:33 am
by rlinux57
Now i have upgraded ram upto 8GB but after sometime service got stuck.
Code: Select all
[root@logs ~]# service logstash start
Starting Logstash Daemon: WARNING: Default JAVA_OPTS will be overridden by the JAVA_OPTS defined in the environment. Environment JAVA_OPTS are -Djava.io.tmpdir=/usr/local/nagioslogserver/tmp
[ OK ]
[root@logs ~]# service logstash status
Logstash Daemon (pid 3894) is running...
[root@logs ~]# service logstash status
Logstash Daemon (pid 3894) is running...
[root@logs ~]# service logstash status
Logstash Daemon dead but pid file exists
Re: Configure Exim MailServer Logs With NLS
Posted: Tue Feb 09, 2016 10:50 am
by rkennedy
What is the result of a top|head -5 now?
Also, please post the output for this too. grep -i 'out of memory' /var/log/messages
Re: Configure Exim MailServer Logs With NLS
Posted: Wed Feb 10, 2016 2:39 am
by rlinux57
Code: Select all
root@logs ~]# top | head -5
top - 12:37:38 up 22:32, 1 user, load average: 0.01, 0.05, 0.09
Tasks: 39 total, 1 running, 38 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.2%us, 0.1%sy, 0.0%ni, 99.7%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 8290304k total, 1132944k used, 7157360k free, 0k buffers
Swap: 0k total, 0k used, 0k free, 67008k cached
Code: Select all
[root@logs ~]# grep -i 'out of memory' /var/log/messages
Feb 9 14:03:46 logs kernel: [1975726.697697] Out of memory in UB 147: OOM killed process 618 (java) score 0 vm:4718000kB, rss:2615528kB, swap:0kB
Re: Configure Exim MailServer Logs With NLS
Posted: Wed Feb 10, 2016 10:45 am
by rkennedy
Can you verify a few things?
- A screenshot of your Backup & Maintenance page.
- A screenshot of your Index Status page.
It looks like your memory is getting consumed over time, so I have a feeling the retention is storing too much data to cache (on your ram), and then causing NLS to crash.
Re: Configure Exim MailServer Logs With NLS
Posted: Thu Feb 11, 2016 2:14 pm
by rlinux57
How can i provide this information please let me know.
Re: Configure Exim MailServer Logs With NLS
Posted: Thu Feb 11, 2016 2:17 pm
by hsmith
You take a screenshot, and can attach it here using either the tags or the 'Upload attachment' button on the bottom of the screen when writing a new post.