06-12-2018 11:17 PM
Every time Minemeld auto-update ( I don't know why this is automatic and if it is recommended). We have a custom miner with a prototype created manually and every time Minemeld updates seems to generate a new folder like "0.9.48" on /opt/minemeld/prototypes/ with only the originals .yml not the custom one so obviously is missing.
My solution is to copy the custom.yml from last version for example "0.9.46" to "0.9.48" and after engine restart it works again.
So the question is: Is this normal to "auto-update" and recommended? And why is not copying my custom.yml? It is not productive every time it is updated that stops working and I have to make the copy of the file.
Email received: SYSTEM ALERT : medium : EDL(ITSA_IPblocklist) Unable to fetch external dynamic list. HTTP response code said error Using old copy for refresh.:
minemeld-engine log: 2018-06-13T07:25:12 (23000)config.resolve_prototypes ERROR: Error loading prototype itsa.IP: Unable to load prototype itsa.IP: not found
Solved! Go to Solution.
06-13-2018 02:06 AM
auto-update is recommended. The right way to add local custom prototypes is placing them inside the /opt/minemeld/local/prototypes directory. Contents of the /opt/minemeld/local subdirectories are preserved across updates.
Just copy your custom.yml in that directory and restart the engine. It will survive updates.
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 Live Community as a whole!
The Live Community thanks you for your participation!