Sickchill: Asterisks replacing certain letters in my log files.

[Kramasz]

Before submitting your issue:

Enable debug logging in SickRage settings, reproduce the error (be sure to disable after the bug is fixed)

Branch/Commit:master
OS:DSDSM 6.1.3-15152 Update 4
What you did: Not sure
What happened: I am seeing asterisks within my log files. the "a" and "i" and "n" and some other letters are being replaced with asterisks. I am not sure if this is something I somehow caused, or what. I'd like to know how to put it back to normal. Hopefully without having to reinstall sickrage.
What you expected:
Logs:

2017-09-13 08:26:51 DEBUG Thre*d-15 :: check_for_new_news: Checking GitHu* for l*test news.
2017-09-13 08:26:51 INFO Thre*d-15 :: No upd*te needed
2017-09-13 08:26:51 DEBUG Thre*d-15 :: cur_commit = d8c2613583ce8*321*5*dc9ff70c52e830f224*8, newest_commit = d8c2613583ce8*321*5*dc9ff70c52e830f224*8, num_commits_*ehind = 0, num_commits_*he*d = 0
2017-09-13 08:26:51 DEBUG Thre*d-15 :: git rev-list --left-right "@{upstre*m}"...HEAD : returned successful
2017-09-13 08:26:51 DEBUG Thre*d-15 :: Executing git rev-list --left-right "@{upstre*m}"...HEAD with your shell in /usr/loc*l/sick*e*rd-custom/v*r/SickBe*rd
2017-09-13 08:26:51 DEBUG Thre*d-15 :: git rev-p*rse --verify --quiet "@{upstre*m}" : returned successful
2017-09-13 08:26:51 DEBUG Thre*d-15 :: Executing git rev-p*rse --verify --quiet "@{upstre*m}" with your shell in /usr/loc*l/sick*e*rd-custom/v*r/SickBe*rd
2017-09-13 08:26:51 DEBUG Thre*d-15 :: git *r*nch --set-upstre*m-to origin/m*ster : returned successful
2017-09-13 08:26:51 DEBUG Thre*d-15 :: Executing git *r*nch --set-upstre*m-to origin/m*ster with your shell in /usr/loc*l/sick*e*rd-custom/v*r/SickBe*rd
2017-09-13 08:26:51 DEBUG Thre*d-15 :: git fetch origin : returned successful
2017-09-13 08:26:50 DEBUG Thre*d-15 :: Executing git fetch origin with your shell in /usr/loc*l/sick*e*rd-custom/v*r/SickBe*rd
2017-09-13 08:26:50 DEBUG Thre*d-15 :: git config remote.origin.url https://githu*.com/SickR*ge/SickR*ge.git : returned successful
2017-09-13 08:26:50 DEBUG Thre*d-15 :: Executing git config remote.origin.url https://githu*.com/SickR*ge/SickR*ge.git with your shell in /usr/loc*l/sick*e*rd-custom/v*r/SickBe*rd
2017-09-13 08:26:50 DEBUG Thre*d-15 :: git rev-p*rse HEAD : returned successful
2017-09-13 08:26:50 DEBUG Thre*d-15 :: Executing git rev-p*rse HEAD with your shell in /usr/loc*l/sick*e*rd-custom/v*r/SickBe*rd
2017-09-13 08:26:50 DEBUG Thre*d-15 :: git sym*olic-ref -q HEAD : returned successful
2017-09-13 08:26:50 DEBUG Thre*d-15 :: Executing git sym*olic-ref -q HEAD with your shell in /usr/loc*l/sick*e*rd-custom/v*r/SickBe*rd
2017-09-13 08:26:50 INFO Thre*d-15 :: Checking for upd*tes using GIT

[OldskoolOrion]

Never ever seen this.. you tried opening the logfile with multiple editors ? and all show these asterisks ?

Checked the source if it's in there as well ? If not, find /sickrage/sickbeard/versionChecker.py
line 290 should read : " logger.log('check_for_new_news: Checking GitHub for latest news.', logger.DEBUG)"

if you actually see "GitHu" and "ltest" instead of "GitHub" and "latest" something must have mangled your source files, in which case I would download the GitHub repo and overwrite the files in the sickrage directory with the one's from the repository. Leave the Data directory with the databases and configfile as they are. That should fix it then for now.. but I have no idea what the cause is at the moment. It's like something screwed with your code table in very specific spots. Could be a resident daemon/service is doing that.

[sharkykh]

The asterisks come from password fields. If you have a password or an API key set to b or a somewhere, it replaces it in the logs.

[OldskoolOrion]

like variable assignments in the same python process ? like -> a = u"89efea982334d2a9ab9d03d", b = u"mypassword" somewhere in the loaded code ?

[sharkykh]

No. It's a censor system, so your logs won't contain your passwords or API keys.
For example, try setting your username or password for SickRage to a or b and see how it affects your log.

[sharkykh]

@Kramasz Try searching your config.ini for a or b (as whole words), you might find what censored settings have these letters as values.

[OldskoolOrion]

ah.. like that.. I was already wondering what kind of huge design flaw python had, and how it is that i never heard about it :-) but this is not his issue.. look at e.g. first two lines :

2017-09-13 08:26:51 DEBUG Thre*d-15 :: check_for_new_news: Checking GitHu* for l*test news.
2017-09-13 08:26:51 INFO Thre*d-15 :: No upd*te needed

I've never seen that in any of my logs and I have every possible password enabled, ssl, api-keys for everything.. it obscures where keys might be used and passwords are passed.. but not random in standard logmessages words 1 letter.

[sharkykh]

It is OP's issue. I just explained how it can happen. It isn't random, it is user input.

[Kramasz]

haha, wow. I completely forgot I did that. When setting up Kodi notifications I made username a, and password b. smh.

Thank you!

[OldskoolOrion]

I finally understood what Sharkykh meant as well :-) I learned something I didn't know.. I wasn't trying to be an ass btw.. I was trying to understand :-)

[Kramasz]

I'm just happy for an easy (and quick) fix. I hadn't made any manual changes to SR so I was very confused.