This post is more than 5 years old
10 Posts
0
736
September 30th, 2015 16:00
MDM on W2K12R2 crashing
Hello,
I installed ScaleIO 1.3.2 on 3 Windows Server 2012 R2 systems. The Primary and Secondary MDMs keep crashing, causing me to lose connectivity through the GUI and CLI. This is my first attempt at installing and using ScaleIO and could use some help figuring out what is going on here.
To add a little bit more info, even when the MDM is running, it doesn't appear to be listening on port 6611 as checked with netstat when things have gone south.
Thanks!
Jason
No Events found!
gc_emc
45 Posts
0
October 1st, 2015 00:00
Hi Jason,
Sounds like a networking issue -ensure there is network connectivity between all components.
Did you use the installation wizard ( Installation Manager) to install SIO?
When you say "The Primary and Secondary MDMs keep crashing" - do you mean they keep switching between each other?
If so, then it is very likely a networking issue.
Rdgs
jasonpnnl
10 Posts
0
October 1st, 2015 09:00
Hi Rdgs,
Thanks for your response. I am trying to find indication that there are networking issues, but so far can't confirm that this is the case. Pings between the Primary and Secondary MDM and the tie-breaker continue uninterrupted. What seems to happen is that the service on the Primary MDM starts, opens port 6611 for a little bit and then either stops listening on ports 6611 or the MDM service stops completely.
I did you the Installation Wizard to install.
This morning I have tried turning off the host based firewalls completely even though the rules seemed like they should be correct. This didn't change anything.
Currently my Primary MDM has the MDM service running but is not listening on port 6611 and my Secondary MDM has the MDM service stopped and will not start. When I try to start the MDM service on the Secondary MDM it starts several times and then gives up in the stopped state.
Is there someplace where I can look at logs?
jasonpnnl
10 Posts
0
October 1st, 2015 10:00
My test boxes are VMware virtual machines, I created a DRS rule that keeps them all on the same physical ESX host and the issues seem to have gone away. I'm not sure why that would be the case, but I guess it doesn't really matter as I wouldn't be doing this in production anyway. Thanks for your help.