I used to run standalone MM 0.9.50 with CentOS 7, perfectly. Last week I updated MM to 0.9.52 with the help of @lmori and the proccess was completed with success. See ( https://live.paloaltonetworks.com/t5/MineMeld-Discussions/Updating-MineMeld-from-0-9-50-to-the-lates... ).
However since the upload my MM doesn't work the same way. On my Dashboard is visible that my miner works fine, more than 90K indicators, but almost none of them ara available, less than 1K in the outputs (see figure below).
If we detailed the proccess, we see that the status of many nodes is "stopped". The number of indicators forwarded by the miners is high.
The number of indicators forwarded by the aggregators is almost the same.
But the number of indicators available by the outputs is extrmely low.
Has anybody experienced something similar? How you dealed with the problem?
Solved! Go to Solution.
That's what I said in previous posts. I already asked @lmori , but I got no answer.
That's where I'm stucked, and probably you too.
How can I work around a problem related with "Error reading last checkpoint"? I'm getting the following in my "minemeld-engine.log"
My MM engine is restarting continously. I even changed the config to the default one (few nodes - spamhaus etc.) but I'm getting the same behaviour. Should I delete all ".chpk" files in "/opt/minemeld/local/data/" and restart the engine?
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!