Sodium: Device Check in
-
-
@gjacobse said in Sodium: Device Check in:
Just about ever device we have connected has not checked in since 9:20
Waiting on a response from IT so that I can get logs and look into what is going on.
-
There has only been one cycle since then, likely a run was missed. They are every twenty minutes, so the next one is in six minutes from now.
-
@scottalanmiller said in Sodium: Device Check in:
There has only been one cycle since then, likely a run was missed. They are every twenty minutes, so the next one is in six minutes from now.
except I typically see times of:
- 9:20
- 9:40
- etc...
-
@gjacobse said in Sodium: Device Check in:
@scottalanmiller said in Sodium: Device Check in:
There has only been one cycle since then, likely a run was missed. They are every twenty minutes, so the next one is in six minutes from now.
except I typically see times of:
- 9:20
- 9:40
- etc...
Right, every twenty minutes. It's 9:56 here now.
-
@scottalanmiller said in Sodium: Device Check in:
@gjacobse said in Sodium: Device Check in:
@scottalanmiller said in Sodium: Device Check in:
There has only been one cycle since then, likely a run was missed. They are every twenty minutes, so the next one is in six minutes from now.
except I typically see times of:
- 9:20
- 9:40
- etc...
Right, every twenty minutes. It's 9:56 here now.
Gotta think my time... It's 10:57
It's been over an hour since it check in. -
@scottalanmiller
And it's been nearly 45 minutes since I posted this... -
@gjacobse said in Sodium: Device Check in:
@scottalanmiller
And it's been nearly 45 minutes since I posted this...Looks like you're good now.
-
@quixoticjeremy said in Sodium: Device Check in:
@gjacobse said in Sodium: Device Check in:
@scottalanmiller
And it's been nearly 45 minutes since I posted this...Looks like you're good now.
Awesome - thanks.
I have one that has failed for a few days now. I've uninstalled it, deleted the
c:\saltdirectory, then reinstalled. but won't check in.I'm trying another cycle, making sure the service is also gone.. to see if that will address the issue.
-
We think that the issue was tied to performance. We saw the system being driven really hard, there is a lot going on behind the scenes. Our infrastructure upgrade this morning seems to have addressed the issue well.
