Did you check your masternode tab on the new qt wallet where you have your masternode.conf?
Heh - I checked it a day or two back, marveled at its elegance, and then forgot all about it. Looking at it again now I saw it reporting "status ENABLED" while the wallet was syncing, then "WATCHDOG EXPIRED" once it synced. I pressed the "Start Alias" button (hey, this is way easier than doing it with console commands) and got a message that the MN had started. My earlier attempts through the console had all reported failure to start. The "WATCHDOG EXPIRED" status is still on (needs a mouseover explanation?) and the masternode.me stats still say don't say 12.1 a few minutes and refreshes later, but I think things may be OK. I'll keep an eye on it. Now to do my other 100 MNs (I wish).
Thanks for the suggestion!
may be this can help
https://www.dash.org/forum/threads/what-is-the-mean-watchdog_expired.13014/Thanks, oly1. Some of that is what I'd hope to see in a popup, so people don't have to chase down a link. A question that doesn't have to be asked doesn't have to be answered, kind of thing.

I think some of the specific content (re Sentinel) doesn't seem to apply to people who use moocowmoo's remote MN hosting service though - I may be wrong - that's my central issue, actually.
In any case, I'll wait a while (Sunday?) then check my status with moocowmoo if it doesn't sort itself out before then.
a few things to remember when starting your masternode from local (cold) wallet :
* local wallet will need a re-index too
* masternode.conf will need to have an externalip address (for example externalip=123.123.123.123)
* issue masternode
start-alias yrmasternodelabelfromyourmasternode.conf passwordphrase
(appearently masternode start-missing is for version updates, when your masternode is still payment-ranked on the network and masternode start-alias is for protocol updates or when you are totally kicked off the network)