- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
04-07-2017 10:22 AM
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.
04-07-2017 10:47 AM
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
04-07-2017 11:39 AM - edited 04-07-2017 11:42 AM
@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.
04-10-2017 08:05 AM
Could you check if /var/run/minemeld/minemeld.sock exists ?
$ ls -la /var/run/minemeld/minemeld.sock
04-27-2017 12:02 PM
@lmori - Sorry for the late response. Yes the file exists.
04-27-2017 01:07 PM
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
04-27-2017 02:25 PM
@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
05-02-2017 04:01 PM
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
05-05-2017 08:45 AM
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
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!