stdlog - how to disable logging some messages

[Jakub Kolacny]

Team,
We have some annoying messages in our stdlog files:

03/05 14:57:21.17 <server> web:local 6260 ERROR StringMut.c 270 String::upcase() failed at position 231 due to invalid character in string: _GA=GA1.2.574733321.1548766857; GUEST_LANGUAGE_ID=EN_US; COOKIE_SUPPORT=TRUE; _GID=GA1.2.2104280547.1551678692; YSOFTPP-ORGANIZATION-DATA='COUNTRY': 'US','REGION': 'YHQ01','PARTNER': 'TESTPARTNER.PP', 'USER': '', 'RSM': 'KOUDAR TOMáš', 'vendor': 'Canon', 'product': 'YSQ','ysoft_user': 'False','user_email': '','region_test': 'YHQ'

The problem is with the Czech characters in the string. The message itself seems to be connected with some kind of a cookie and it's only Chrome related (it does not occur in IE or Chrome in the incognito mode) and it's presented only for users on internal AD.

We don't care much about the message itself, but it heavily fills the stdlog files.

Any ideas on how to:

1. solve the issue with the issue itself
2. disable these annoying messages

Thank you so much for your help,
Jakub

[Brian Mathato]

Hi Jakub,

It is not possible to disable this message from showing up in the logs, considering it a basic level of logging (ERROR).

You will need to log a support case for Support to assist you to enable debugging and possibly work with the engineering team as to why this error message is constantly being generated on your environment. Hopefully, engineering can suggest or create a NX variable to suppress this specific message. 


------------------------------
Kind Regards,
Brian
------------------------------

[Kyle R]

Hello Jakub,

Brian is correct on both counts.

It is possible to disable "ERROR" level logging via pdm_logstat, BUT we don't recommend it, as it would disable ALL "ERROR" logging.

It should be logged as a Support issue to help you get to root cause.


I just wanted to add that we can't pre-empt the solution.  This type of issue has been seen before, and it can have a variety of causes, that you are unlikely to find out without specific troubleshooting. There have been both product defects and client customisation defects found in the past on different languages.

I can also recommend some troubleshooting that you can do on your own to get started:

* Note the product and version, customisations, patch levels. Basically, document at a high level the environment. Make sure that all combinations are certified. If the issue only happens on an uncertified browser version, then stop right there and move to a certified version.

* Identify - if possible - exactly HOW to reproduce the error. If you can find a particular form or series of steps that triggers the message, that would be ideal! If can reproduce this against a test environment - even better.

* Try and eliminate broad areas of the likely cause. The quickest and easiest is to remove all modifications by renaming the site/mods . . .  folder/s and restarting, and seeing if the issue goes away. If it does, then the likely source is a special character on one of your customised forms, which is a common cause of this issue. If not, then it is an interaction with the application/browser that needs to be locked down.


Thanks, Kyle_R.