Don't store blank data if we fail to get anything from the shared state file
Don't store blank data if we fail to get anything from the shared state file

Occasionally on some systems, the data returned from the shared state file is
bad/blank, despite locking. Ideally we'd find the cause of this and fix it,
but various attempts haven't identified exactly why this happens (including
running fsync after writing and before unlocking). If the data returned is
blank, we should use the latest available data rather than returning blank
data to the user/monitoring system.

omniti-labs/resmon,omniti-labs/resmon