MineMeld engine failed to start.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

MineMeld engine failed to start.

L1 Bithead

I was attmepoting to configure Minemeld to pull AWS ip addresses, but nothing happened when I hit commit. I noticed the Supervisor had stopped, and came across this earlier article. I issued the commands:

sudo service minemeld stop
sudo service minemeld start
sudo -u minemeld /opt/minemeld/engine/current/bin/supervisorctl -c /opt/minemeld/local/supervisor/config/supervisord.conf status

 

and received the following:

ubuntu@minemeld:~$ sudo service minemeld stop
* Stopping: minemeld
minemeld-supervisord-listener: stopped
minemeld-traced: stopped
minemeld-web: stopped
...done.
ubuntu@minemeld:~$ sudo service minemeld start
* Starting: minemeld
...done.
ubuntu@minemeld:~$ sudo -u minemeld /opt/minemeld/engine/current/bin/supervisorctl -c /opt/minemeld/local/supervisor/config/supervisord.conf status
minemeld-engine BACKOFF Exited too quickly (process log may have details)
minemeld-supervisord-listener RUNNING pid 25983, uptime 0:00:08
minemeld-traced RUNNING pid 25985, uptime 0:00:08
minemeld-web RUNNING pid 26001, uptime 0:00:03
ubuntu@minemeld:~$ sudo -u minemeld /opt/minemeld/engine/current/bin/supervisorctl -c /opt/minemeld/local/supervisor/config/supervisord.conf status
minemeld-engine FATAL Exited too quickly (process log may have details)
minemeld-supervisord-listener RUNNING pid 25983, uptime 0:01:48
minemeld-traced RUNNING pid 25985, uptime 0:01:48
minemeld-web RUNNING pid 26096, uptime 0:00:03

 

I tried restarting the engine several times without success. Please assist. Engine logs attached. 

1 accepted solution

Accepted Solutions

L7 Applicator

Hi @cleediker,

the VM ran out of memory:

2017-10-25T18:57:06 (26288)launcher.main INFO: Number of chassis: 2
Traceback (most recent call last):
  File "/opt/minemeld/engine/current/bin/mm-run", line 11, in <module>
    sys.exit(main())
  File "/opt/minemeld/engine/0.9.42/local/lib/python2.7/site-packages/minemeld/run/launcher.py", line 267, in main
    p.start()
  File "/usr/lib/python2.7/multiprocessing/process.py", line 130, in start
    self._popen = Popen(self)
  File "/usr/lib/python2.7/multiprocessing/forking.py", line 121, in __init__
    self.pid = os.fork()
  File "/opt/minemeld/engine/0.9.42/local/lib/python2.7/site-packages/gevent/os.py", line 98, in fork
    result = _fork()
OSError: [Errno 12] Cannot allocate memory

View solution in original post

4 REPLIES 4

L7 Applicator

Hi @cleediker,

the VM ran out of memory:

2017-10-25T18:57:06 (26288)launcher.main INFO: Number of chassis: 2
Traceback (most recent call last):
  File "/opt/minemeld/engine/current/bin/mm-run", line 11, in <module>
    sys.exit(main())
  File "/opt/minemeld/engine/0.9.42/local/lib/python2.7/site-packages/minemeld/run/launcher.py", line 267, in main
    p.start()
  File "/usr/lib/python2.7/multiprocessing/process.py", line 130, in start
    self._popen = Popen(self)
  File "/usr/lib/python2.7/multiprocessing/forking.py", line 121, in __init__
    self.pid = os.fork()
  File "/opt/minemeld/engine/0.9.42/local/lib/python2.7/site-packages/gevent/os.py", line 98, in fork
    result = _fork()
OSError: [Errno 12] Cannot allocate memory

Thanks for the quick reply, Luigi.

I added more memory to the VM and rebooted, but noticed the error "* stopping Handle applying cloud-config". I then saw there was an update available, and ran the command:

41 packages can be updated.
12 updates are security updates.

New release '16.04.3 LTS' available.
Run 'do-release-upgrade' to upgrade to it.

 

once finished, I cant login to the UI, and see an "error checking credentials: timeout". I can log into the CLI and get this:

ubuntu@minemeld:~$ sudo -u minemeld /opt/minemeld/engine/current/bin/supervisorctl -c /opt/minemeld/local/supervisor/config/supervisord.conf status
Traceback (most recent call last):
File "/opt/minemeld/engine/current/bin/supervisorctl", line 7, in <module>
from supervisor.supervisorctl import main
File "/opt/minemeld/engine/0.9.42/local/lib/python2.7/site-packages/supervisor/supervisorctl.py", line 36, in <module>
from supervisor.options import ClientOptions
File "/opt/minemeld/engine/0.9.42/local/lib/python2.7/site-packages/supervisor/options.py", line 15, in <module>
import pkg_resources
File "/opt/minemeld/engine/0.9.42/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 35, in <module>
import plistlib
File "/usr/lib/python2.7/plistlib.py", line 62, in <module>
import datetime
ImportError: No module named datetime

 

Hi,

 

I also experinced same issue. Once the upgrade the ubuntu in to new version same error occured for me. Please help on this.

Hello,

 

Currently having the exact same issue.

What did solve the issue for you guys ?

 

Thanks

  • 1 accepted solution
  • 8974 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!