Closed akijuh closed 7 years ago
Not exactly a fix, but on first launch it at least fills the rpcuser and password without using special chars. https://github.com/SilkNetwork/DarkSilk-Core/commit/e0b9eb358119383a64405dde1d8e21190bfad1c1
I doubt it's a Dash Core issue, filled an issue in Sentinel's repo https://github.com/dashpay/sentinel/issues/4
Yep, its probably a sentinel bug, because this was not problem before 12.1.
It is a sentinel issue with how it reads the config file, i just added the conf file generation for DarkSilk and thought of this a quick fix/circumvention of the issue, for now ;)
@akijuh Can you specify the exact character(s) that you had to remove in order to get it to work?
@nmarley Here is one of my masternode info (old) which was ok before 12.1 but not with it.
rpcuser=nOtSD*=l[F(mQFJJJ rpcpassword=Q'O'ecCcmUkRv-,Gt4%#OL[&
sentinel issue, closing here
V12.1.0 If in dash.conf rpcuser and/or rpcpassword include any special character, like !"#¤%&/, sentinel wont work like it should be, and masternode status become to watchdog_expired, only normal chars are working ok.
I did have this problem, after fixed/removed all special characters, no problem any more.