Rebooted vm that hosted elasticsearch and not nothing is working

So I rebooted my elasticsearch vm and now I can't seem to get anything working again. I REALLY need to restore this. Anyone able to help me work through this?

> [root@elasticsearch etc]# curl -k -u elastic -XGET 'https://localhost/_cluster/health?pretty'
> Enter host password for user 'elastic':
> {
>   "cluster_name" : "logging",
>   "status" : "red",
>   "timed_out" : false,
>   "number_of_nodes" : 1,
>   "number_of_data_nodes" : 1,
>   "active_primary_shards" : 737,
>   "active_shards" : 737,
>   "relocating_shards" : 0,
>   "initializing_shards" : 4,
>   "unassigned_shards" : 721,
>   "delayed_unassigned_shards" : 0,
>   "number_of_pending_tasks" : 3,
>   "number_of_in_flight_fetch" : 0,
>   "task_max_waiting_in_queue_millis" : 2706,
>   "active_shards_percent_as_number" : 50.41039671682627
> }

Here is an error I see in the log for elasticsearch.

2019-11-27T16:04:08.581405405Z [2019-11-27T16:04:08,574][ERROR][o.e.x.m.c.c.ClusterStatsCollector] [05w2lDl] collector [cluster_stats] failed to collect data
2019-11-27T16:04:08.581434005Z org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];
2019-11-27T16:04:08.581440405Z  at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedException(ClusterBlocks.java:166) ~[elasticsearch-6.6.1.jar:6.6.1]
2019-11-27T16:04:08.581446405Z  at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedRaiseException(ClusterBlocks.java:152) ~[elasticsearch-6.6.1.jar:6.6.1]
2019-11-27T16:04:08.581451805Z  at org.elasticsearch.action.search.TransportSearchAction.executeSearch(TransportSearchAction.java:297) ~[elasticsearch-6.6.1.jar:6.6.1]
2019-11-27T16:04:08.581457205Z  at org.elasticsearch.action.search.TransportSearchAction.lambda$doExecute$4(TransportSearchAction.java:193) ~[elasticsearch-6.6.1.jar:6.6.1]
2019-11-27T16:04:08.581462705Z  at org.elasticsearch.action.ActionListener$1.onResponse(ActionListener.java:60) ~[elasticsearch-6.6.1.jar:6.6.1]

It's okay now! I guess it just needed time to fix itself... I thought I was about to have a really bad holiday weekend....