store-volume stuck in start-pre/auto-restart loop on deisctl start platform
#2317
Comments
@EvanK It looks like the monitors are crashing due to not having enough disk space available:
|
The logs are cut off, but it seems like one of the monitors are crashing due to limited disk space. edit: jinx |
Huh, that does look a likely culprit:
These machines were provisioned with 8G disk each, should I be aiming for 16/32? |
Yep, I think each OSD will provision 5GB. |
@EvanK I'm going to close this as I don't think this is an issue with store. If you have trouble once you remedy the disk space issue, let us know. Thanks! |
I'm seeing this same issue with the deis-store-metadata.service unable to start for some reason:
Right now I'm just providing the same information that EvanK provided. I'm (very) new to Deis/CoreOS/etc, so let me know if you need any more information.
Where would more logs be stored? -Cody |
Oh, also this is 1.1.0 on ec2 using the contrib/ec2 provisioner setup. codyaray@mbpro:bin$ deisctl --version |
@codyaray Your cluster is perfectly healthy. Can you get the logs from |
Here they are
So it sounds like some components are running an old version then? I installed this a long time ago and thought I had updated it. -Cody |
Yep, sounds like it. I'm guessing you used a more recent deisctl to |
@codyaray You may want to try following the upgrade documentation again, because it sounds like you missed a step. If you run into trouble, please open a fresh ticket. Thanks! |
I built a fresh 0.15.0 cluster from bare-metal docs, locally using the
deisctl
binary provided by @carmstrong (per our conversation in #2300).Upon
deisctl start platform
, it hangs and loops on starting store-volume:Following are commands run within the first node of the cluster:
The text was updated successfully, but these errors were encountered: