I see one of the two recommended priority nodes for monerod has been changed from node.supportxmr.com to p2pmd.xmrvsbeast.com. It seems that when a priority node is down, monerod doesn't start, which can be fixed by temporarily removing the offending --add-priority-node parameter (correct me if I'm wrong).
Your monerod should have it's own node list, especially if it has been on the network for some time. A priority node being offline should not affect your node.
I mean, when I try to start monerod, monerod fails to start if sample.net in --add-priority-node=sample.net is down. I experienced that a few times, though it's just me.
I see. Disregard it then, it might have been something accidental. Actually I didn't check if the node was up or down, so it was just a guess. (If someone happens to experience a weird error where the daemon refuses to start, tweaking --add-priority-node wouldn't hurt, I guess.)
Anyway one of the two priority nodes, in a recommended command in README.md, has changed.