- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
04-12-2017 10:51 AM
I'm getting an error when committing on an instance I had spun down for a year and then upgraded yesterday when spinning back up. Looking in logs it looks like it's having problems resolving one of the miners but I'm not positive.
Any thoughts on how to troubleshoot this?
04-13-2017 02:32 PM
Hi @chirss,
could you share the error message you get ? Have you checked the minemeld-engine.log file ? You can get it from SYSTEM > DASHBOARD > ENGINE > LOGS
Thanks,
luigi
04-13-2017 02:32 PM
Hi @chirss,
could you share the error message you get ? Have you checked the minemeld-engine.log file ? You can get it from SYSTEM > DASHBOARD > ENGINE > LOGS
Thanks,
luigi
04-17-2017 08:21 AM
I ended up blowing the installation away (I know, awful). It was over a year old and I remember doing things I shouldn't have been doing with the feeds file on disk. It made more sense to just start over.
In the logs you mentioned there was not anything useful. However what would be handy is if there was a way to check a box or click a tab to show just the system logs versus the logs for feed pulling (20 records added, I don't have an install up right now to quote it exactly).
04-18-2017 02:57 AM
Hi @chirss,
once you download the mineneld-engine.log you can search for ERROR (all uppercase) to find error logs inside the file, this will filter out all the logs from the Miners.
04-18-2017 09:26 AM
I was thinking more in the interface so we can avoid shell access.
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!