topic Re: Minemeld engine stopped - error starting engine in General Topics

Minemeld engine stopped - error starting engine

Sly_Cooper — Fri, 07 Apr 2017 17:22:10 GMT

I would like to create ipv4 output based on the aws ec2 and route 53 miners. I cloned miners, aggregator and output from prototypes. When I hit commit nothing happens. I can see the processes stopped under System. If I hit restart for the engine, I get Internal Server Error. I already tried by rebooting the server and tried the same. I have attached engine.log file.

Re: Minemeld engine stopped - error starting engine

lmori — Fri, 07 Apr 2017 17:47:44 GMT

Hi @Sly_Cooper,

looking at the engine logs everything looks good but I don't see the route53 and EC2 Miners. Would you mind uploading the API logs as well ? (minemeld-web.log)

Thanks,

luigi

Re: Minemeld engine stopped - error starting engine

Sly_Cooper — Fri, 07 Apr 2017 18:42:19 GMT

@lmori - Whenever I clone the nodes, I see them in the config. Nothing happens post hitting commit. If i hit reload, then it loads the previously commit config and remove thes newly added nodes. How do I make sure the commit is working? Also the services are stopped. If I hit restart then I get internal server error. How do I get the engine started?

API Logs attached.

Re: Minemeld engine stopped - error starting engine

lmori — Mon, 10 Apr 2017 15:05:23 GMT

Could you check if /var/run/minemeld/minemeld.sock exists ?

$ ls -la /var/run/minemeld/minemeld.sock

Re: Minemeld engine stopped - error starting engine

Sly_Cooper — Thu, 27 Apr 2017 19:02:19 GMT

@lmori - Sorry for the late response. Yes the file exists.

Re: Minemeld engine stopped - error starting engine

lmori — Thu, 27 Apr 2017 20:07:14 GMT

Hi @Sly_Cooper,

could you attache the output of the following commands ?

$ grep SUPERVISOR_URL /opt/minemeld/local/config/api/10-defaults.yml
$ ls -la /var/run/minemeld/minemeld.sock

Re: Minemeld engine stopped - error starting engine

Sly_Cooper — Thu, 27 Apr 2017 21:25:50 GMT

@lmori Here you go.

ubuntu@minemeld:~$ grep SUPERVISOR_URL /opt/minemeld/local/config/api/10-defaults.yml
SUPERVISOR_URL: "unix:///var/run/minemeld/minemeld.sock"
ubuntu@minemeld:~$ ls -la /var/run/minemeld/minemeld.sock
srwx------ 1 minemeld minemeld 0 Apr  7 08:51 /var/run/minemeld/minemeld.sock

Re: Minemeld engine stopped - error starting engine

lmori — Tue, 02 May 2017 23:01:58 GMT

Hi @Sly_Cooper,

sorry for the late reply. So it seems that the MineMeld API daemon is not able to open the unix socket that is use to communicate with the MineMeld service supervisord instance. Please, could you attach the config files from /opt/minemeld/local/config/api/* ?

Thanks,

luigi

Re: Minemeld engine stopped - error starting engine

Sly_Cooper — Thu, 04 May 2017 19:39:44 GMT

@lmori - Requested files attached.

Re: Minemeld engine stopped - error starting engine

lmori — Fri, 05 May 2017 15:45:12 GMT

Hi @Sly_Cooper,

found the problem, could you open /opt/minemeld/local/config/api/20-local.yml and remove the following line:

SUPERVISOR_URL: "unix:///opt/minemeld/local/supervisor/run/minemeld.sock"

Once done just do this:

sudo -u minemeld mm-supervisorctl restart minemeld-web