MongoDB Install Simple Test Ops Manager java.lang.OutOfMemoryError on startup

Question

I just installed a test evaluation of MongoDB Ops Manager and get an error on startup of the Backup HTTP server:

Migrate MMS data
   Running migrations...[  OK  ]
Start MMS server
   Instance 0 starting..........[  OK  ]
Start Backup HTTP Server
   Instance 0 starting.......[FAILED]

2015-05-07T14:00:32.107+0000 [main] gid  ERROR ServerMain:199 - Cannot start bslurp server [FATAL-EXITING] - instance: 0  - msg: unable to create new native thread
java.lang.OutOfMemoryError: unable to create new native thread

I appear to have plenty of memory

[root@krh60621 ~]# free -m
             total       used       free     shared    buffers     cached
Mem:         15951       4588      11362          0        364       2021

and I upped the max processes to unlimited to see if that would help....

[root@krh60621 ~]# ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 127421
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 94000
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 10240
cpu time               (seconds, -t) unlimited
max user processes              (-u) unlimited
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

[root@krh60621 ~]# ps -eLF| grep -c java
593

[root@krh60621 ~]# ps -eLF| wc -l
1031

Any thoughts???

Did you install this using an rpm, deb, or tar.gz package? — Pete Garafano
– Pete Garafano, Commented May 13, 2015 at 15:01

Bruce · Accepted Answer · 2015-07-16 04:28:18Z

0

I encountered a similar issue in our Test Ops Manager deployment when we upgraded to Ops Manager 1.8.0. I ultimately opened up a ticket with MongoDB Support and this was the resolution for our issue:

The Ops Manager components are launched using the default username "mongodb-mms". Please adjust the ulimit settings for this user to match those of the "mongodb" user, currently defined in /etc/security/limits.d/99-mongodb-mms-automation-agent.conf.

You may wish to add a separate file under /etc/security/limits.d/ for the mongodb-mms user.

More information can be found here.

edited Jul 16, 2015 at 4:28

Bruce

1,6694 gold badges20 silver badges22 bronze badges

answered Jul 16, 2015 at 4:17

Mike Grayson

11 silver badge2 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

MongoDB Install Simple Test Ops Manager java.lang.OutOfMemoryError on startup

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related