- 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.
06-26-2018 06:57 AM - edited 06-26-2018 06:58 AM
Hello team!
I hope you are doing alright !
It looks like that since the last update (0.9.48), I am no longer able to setup new nodes with the prototypes:
OR
Moreover, a couple of my miners/nodes now have an "unknown" type.
Any idea of what could be the cause of that ?
Thanks in advance for your help.
06-28-2018 02:24 AM
Hi @camsad,
no, you should place it in /opt/minemeld/local/prototypes. This way it won't be overwritten on upgrades.
06-28-2018 12:55 AM
Hi Luigi,
ls -l /opt/minemeld/prototypes/
drwxr-xr-x 2 minemeld minemeld 4096 Apr 3 2017 0.9.16
drwxr-xr-x 2 minemeld minemeld 4096 Aug 2 2017 0.9.40
drwxr-xr-x 2 minemeld minemeld 4096 Sep 6 2017 0.9.42
drwxr-xr-x 2 minemeld minemeld 4096 Oct 27 2017 0.9.44
drwxr-xr-x 2 minemeld minemeld 4096 May 11 06:26 0.9.46
drwxr-xr-x 2 minemeld minemeld 4096 Jun 18 07:33 0.9.48
lrwxrwxrwx 1 root root 31 Jun 13 06:36 current -> /opt/minemeld/prototypes/0.9.48
Thanks !
06-28-2018 01:16 AM
Luigi,
Pretty much everything starting with stdlib
06-28-2018 01:53 AM
Could you try this command?
ls -la /opt/minemeld/prototypes/0.9.48/stdlib.yml
06-28-2018 01:55 AM - edited 06-28-2018 01:57 AM
ls -la /opt/minemeld/prototypes/0.9.48/stdlib.yml -rw-r--r-- 1 minemeld minemeld 32243 Jun 13 06:36 /opt/minemeld/prototypes/0.9.48/stdlib.yml
diff between 0.9.46/stdlib.yml and 0.9.48/stlib.yml indicates no difference
06-28-2018 01:58 AM
Ok, prototypes looks good.
Could you go in System > API and click on restart?
06-28-2018 02:01 AM
Done. Did not solve the issue.
06-28-2018 02:03 AM
Did you also do a hard refresh of the browser after restarting the API? Prototypes are cached both in the browser and in the API process.
If that doesn't solve, could you share your minemeld-web.log file?
06-28-2018 02:23 AM
Hi Luigi,
A stated by the minemeld-web.log file, it was a permission issue:
Traceback (most recent call last): File "/opt/minemeld/engine/0.9.48.post1/local/lib/python2.7/site-packages/minemeld/flask/prototypeapi.py", line 128, in list_prototypes with open(os.path.join(p, plibrary), 'r') as f: IOError: [Errno 13] Permission denied: '/opt/minemeld/prototypes/current/minemeldlocal.yml'
Then, setting "minemeld" as the owner of
/opt/minemeld/prototypes/current/minemeldlocal.yml
solved the issue.
Thanks a lot for your help !
P.S. : Do I need minemeldlocal.yml in /opt/minemeld/prototypes/current ?
06-28-2018 02:24 AM
Hi @camsad,
no, you should place it in /opt/minemeld/local/prototypes. This way it won't be overwritten on upgrades.
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!