CloudatCost CentOS 7 Failing to boot
-
One of my C@C servers was down. Couldn't ping or ssh into it. I went to the console and this is all it shows, is my only option to re-image it?
-
Well that is different. If you power cycle it (virtually) do you see anything else happen? How far does it make it?
-
Have I mentioned that I hate systemd? Fragility everywhere.
-
It does the same thing if I reboot it, takes about 10 min to get to this point though.
-
I haven't tried, but is there a way to see GRUB as it boots up?
-
@scottalanmiller said:
I haven't tried, but is there a way to see GRUB as it boots up?
Doesn't look like you can.
-
I opened a ticket with them, I'm not hopeful about it though.
-
@thecreativeone91 said:
@scottalanmiller said:
I haven't tried, but is there a way to see GRUB as it boots up?
Doesn't look like you can.
That sucks, might have fixed things.
-
They are looking into it now.
-
That's good.
-
They said there is on way to fix this. They also stated that that SELINUX must be in a permissive state at cloudatcost as any other setting is not supported any may casue it to fail to boot (both enforcing and disabled)
-
@thecreativeone91 said:
They said there is on way to fix this. They also stated that that SELINUX must be in a permissive state at cloudatcost as any other setting is not supported any may casue it to fail to boot (both enforcing and disabled)
Wait... WHAT?!??!?
-
@scottalanmiller said:
@thecreativeone91 said:
They said there is on way to fix this. They also stated that that SELINUX must be in a permissive state at cloudatcost as any other setting is not supported any may casue it to fail to boot (both enforcing and disabled)
Wait... WHAT?!??!?
Yeah I don't get why either would cause it to fail to boot, maybe it's something to do with the image they use.
-
This is pretty bad.
