I looked at half of my masternodes, which I haven't restarted since upgrading to the latest version... they aren't really stuck, but are behind.
Running getinfo shows 259200 on all of the masternodes while my controller / wallet / staking node :-) is at 259279.
I'll let the masternodes chug along...
Hopefully, the only problem is what is being displayed, while the blockchain marches on.
What is interesting is that the peers, mostly show that they are on 259200 also.
Controller:
darknet-cli getpeerinfo |grep synced_headers
"synced_headers" : 258773,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
A masternode:
darknet-cli getpeerinfo |grep synced_headers
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259250,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : 259265,
"synced_headers" : 259200,
"synced_headers" : 259200,
"synced_headers" : -1,
Definitely, there are some issues to be addressed. I am optimistic that it is problem is mostly with what the cli reports.
Looking at the PoS reward schedule and current Masternode reward, I think investing in a few more masternodes is not a bad ides.