Hi @lmori,
Is there any support for Ubuntu 16.04 or later? Or is Minemeld still only supported on 14.04?
Thanks!
Regards,
Bo
Solved! Go to Solution.
@borising : You can give the MineMeld Ansible Playbook a try. It's been reported to succesfully deploy MineMeld in Ubuntu 16.04.
Xavi
@borising : You can give the MineMeld Ansible Playbook a try. It's been reported to succesfully deploy MineMeld in Ubuntu 16.04.
Xavi
I found some issue when installed mindmeld on Ubuntu.
Could you recommend me?
@xhoms wrote:
@borising : You can give the MineMeld Ansible Playbook a try. It's been reported to succesfully deploy MineMeld in Ubuntu 16.04.
Xavi
This suggestion might come a little too late, but, I have decided to post it anyway.
I ran into a problem with nginx during the ansible-notebook install. Please see below:
TASK [infrastructure : install packages] *************************************************** changed: [127.0.0.1] => (item=rabbitmq-server) changed: [127.0.0.1] => (item=redis-server) changed: [127.0.0.1] => (item=collectd-core) failed: [127.0.0.1] (item=nginx)
In order to solve this issue, I followed the instructions from this askubuntu post:
https://askubuntu.com/questions/764222/nginx-installation-error-in-ubuntu-16-04/805283#805283
I also followed this advice from a hurricanelabs pdf. I personally did not experienced the issue before editing the webui.yml, but I think it's worth a look:
https://www.hurricanelabs.com/docs/minemeld_user_guide.pdf#page=8&zoom=90,-354,680
I ran the following command to do the install:
ansible-playbook -K -e "minemeld_version=master" -i 127.0.0.1, local.yml
Everything went smoothly after that, and did not notice any other errors during the install, which takes a while.
sudo -u minemeld /opt/minemeld/engine/current/bin/supervisorctl -c /opt/minemeld/supervisor/config/supervisord.conf status minemeld-engine RUNNING pid 1443, uptime 0:00:31 minemeld-supervisord-listener RUNNING pid 1442, uptime 0:00:31 minemeld-traced RUNNING pid 1444, uptime 0:00:31 minemeld-web RUNNING pid 1445, uptime 0:00:31
Hope this helps!
Cheers,
Fer
Keep getting this error when running the ansible playbook
TASK [minemeld : requirements] *************************************************************************************************************************************************
fatal: [127.0.0.1]: FAILED! => {"changed": false, "cmd": "/opt/minemeld/engine/current/bin/pip2 freeze", "msg": "\n:stderr: Traceback (most recent call last):\n File \"/opt/minemeld/engine/current/bin/pip2\", line 7, in <module>\n from pip._internal import main\n File \"/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/pip/_internal/__init__.py\", line 19, in <module>\n from pip._vendor.urllib3.exceptions import DependencyWarning\n File \"/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/pip/_vendor/urllib3/__init__.py\", line 8, in <module>\n from .connectionpool import (\n File \"/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/pip/_vendor/urllib3/connectionpool.py\", line 29, in <module>\n from .connection import (\n File \"/opt/minemeld/engine/0.9.52.post1/local/lib/python2.7/site-packages/pip/_vendor/urllib3/connection.py\", line 2, in <module>\n import datetime\nImportError: No module named datetime\n"}
to retry, use: --limit @/home/ubuntu/minemeld-ansible/local.retry
PLAY RECAP *********************************************************************************************************************************************************************
127.0.0.1 : ok=33 changed=2 unreachable=0 failed=1
Me too:
ASK [minemeld : gulp build] *******************************************************************************************************************
fatal: [127.0.0.1]: FAILED! => {"changed": true, "cmd": ["gulp", "build"], "delta": "0:00:14.231891", "end": "2019-02-26 21:45:23.642662", "msg": "non-zero return code", "rc": 1, "start": "2019-02-26 21:45:09.410771", "stderr": "", "stderr_lines": [], "stdout": "[21:45:10] Using gulpfile /opt/minemeld/www/webui/gulpfile.js\n[21:45:10] Starting 'scripts'...\n[21:45:10] Starting 'styles'...\n[21:45:10] 'styles' errored after 40 ms\n[21:45:10] Error: ENOENT: no such file or directory, scandir '/opt/minemeld/www/webui/node_modules/node-sass/vendor'\n at Error (native)\n at Object.fs.readdirSync (fs.js:961:18)\n at Object.getInstalledBinaries (/opt/minemeld/www/webui/node_modules/node-sass/lib/extensions.js:121:13)\n at foundBinariesList (/opt/minemeld/www/webui/node_modules/node-sass/lib/errors.js:20:15)\n at foundBinaries (/opt/minemeld/www/webui/node_modules/node-sass/lib/errors.js:15:5)\n at Object.module.exports.missingBinary (/opt/minemeld/www/webui/node_modules/node-sass/lib/errors.js:45:5)\n at module.exports (/opt/minemeld/www/webui/node_modules/node-sass/lib/binding.js:15:30)\n at Object.<anonymous> ./src/app/dashboard/dashboard.controller.ts", "[173, 19]: comment must start with lowercase letter", "", "", "WARNING in ./src/app/system/system.controller.ts", "[105, 34]: == should be ===", "[125, 34]: == should be ===", "[150, 34]: == should be ===", "[199, 34]: == should be ===", "", "", "WARNING in ./src/app/system/extensions.controller.ts", "[528, 15]: comment must start with lowercase letter", "[416, 56]: == should be ===", "[509, 30]: == should be ===", "", "", "WARNING in ./src/app/config/config.controller.ts", "[205, 34]: == should be ===", "[205, 68]: == should be ===", "[610, 37]: == should be ===", "[633, 28]: == should be ===", "[726, 32]: == should be ===", "", "", "WARNING in ./src/app/config/configimport.controller.ts", "[403, 9]: for (... in ...) statements must be filtered with an if statement", "", "", "WARNING in ./src/app/config/configadd.controller.ts", "[111, 59]: == should be ===", "[157, 24]: == should be ===", "[187, 25]: == should be ===", "[194, 31]: == should be ===", "", "", "WARNING in ./src/app/admin/admin.users.controller.ts", "[59, 13]: unused variable: 'lastUser'", "[68, 31]: == should be ===", "", "", "WARNING in ./src/app/indicatoradd/indicatoradd.controller.ts", "[188, 29]: forbidden bitwise operation", "", "", "WARNING in ./src/app/services/minemeldapi.ts", "[197, 20]: == should be ===", "", "", "WARNING in ./src/app/services/status.ts", "[320, 12]: trailing whitespace", "", "", "WARNING in ./src/app/services/prototype.ts", "[16, 28]: comment must start with lowercase letter", "", "", "WARNING in ./src/app/services/events.ts", "[110, 63]: == should be ===", "", "", "WARNING in ./src/app/services/traced.ts", "[224, 21]: forbidden bitwise operation", "[226, 38]: forbidden bitwise operation", "[226, 38]: forbidden bitwise operation", "", "", "WARNING in ./src/app/services/enginestatus.ts", "[85, 50]: != should be !==", "[111, 30]: != should be !==", "", "", "WARNING in ./src/app/services/jobs.ts", "[122, 35]: != should be !==", "[126, 39]: != should be !==", "", "", "WARNING in ./src/app/services/currentuser.ts", "[51, 30]: == should be ===", "", "", "WARNING in ./src/app/components/navbar/navbar.directive.ts", "[79, 28]: != should be !==", "[84, 45]: != should be !==", "", "", "WARNING in ./src/app/components/suggestion/suggestion.directive.ts", "[31, 9]: 'toastr' cannot be declared in the constructor", "[32, 9]: '$modal' cannot be declared in the constructor", "[93, 17]: '$modalInstance' cannot be declared in the constructor", "[58, 19]: expected parameter: 'result' to have a typedef", "[60, 28]: expected parameter: 'success' to have a typedef", "[63, 26]: expected parameter: 'error' to have a typedef", "[75, 19]: expected parameter: 'result' to have a typedef", "", "[21:45:23] Finished 'scripts' after 13 s"]}
to retry, use: --limit @/home/ubuntu/minemeld-ansible/local.retry
PLAY RECAP *************************************************************************************************************************************
127.0.0.1 : ok=58 changed=11 unreachable=0 failed=1
What command in particular were you running?
ansible-playbook -K -i 127.0.0.1, local.yml
or
ansible-playbook -K -e "minemeld_version=master" -i 127.0.0.1, local.yml
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!