starting masternode on a protocol increase needs restart of daemon 2 times

[ciripel]

possible reason
you start node... it does an internal check but order of check may not be correct and as such new protocol number is applied after masternode start message is processed
or something like that
so second starts with correct protocol number and activates node
I guess wallet version is loaded on start and saved on shutdown
so first start loads old one and thus it does not start node
after shutdown it is saved with proper version

Restart forces mn db to resync
So it is likely something related to mn sync
Not sure why it wont sync without restart