Skip to main content
1-Visitor
September 11, 2014
Solved

Unable to disable logging of CACHE on 10.3

  • September 11, 2014
  • 3 replies
  • 4688 views

I adjusted logging levels of several categories as I was tracking down an issue that was causing Integrity to log errors on a regular basis. I found the problem (a rogue client) and fixed the problem. However, I am unable to stop the CACHE logger from logging. I even tried setting the logging level to -100. It continues to create log entries like this:

2014-09-11 09:18:02,563 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-11 09:18:03,203 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-11 09:18:04,061 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-11 09:18:04,779 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-11 09:18:05,902 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-11 09:18:07,899 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

Does anyone know how to stop the CACHE logger? (I feel a bit like George Jetson on the treadmill.)

    Best answer by jgorsline

    John,

    Have you tried any of the steps from above since the restart?

    I'm afraid that we might have run out of options for what can be done from our end in the forum.

    3 replies

    1-Visitor
    September 11, 2014

    John,

    Did you make the changes to the logging level from the command line or from the properties file? Have you restarted the server?

    1-Visitor
    September 11, 2014

    Changes were made from the CLI, the UI, and the properties file with a server restart.

    Still have the problem.

    1-Visitor
    September 19, 2014

    John,

    After working on this for a bit, I realized that the example you sent is actually being logging by the INFO logger, and the information is just cache related. Your CACHE logging is off.

    1-Visitor
    October 15, 2014

    It appears that the offending CACHE logging has stopped. The last one in my log was:

    2014-10-02 16:14:42,023 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

    I'm not sure what caused this to stop because I didn't do anything after running Kael's "im logging" command from the September 26th post.

    1-Visitor
    November 11, 2014

    And, after a server restart, it has re-appeared...

    jgorsline1-VisitorAnswer
    1-Visitor
    November 12, 2014

    John,

    Have you tried any of the steps from above since the restart?

    I'm afraid that we might have run out of options for what can be done from our end in the forum.

    1-Visitor
    November 12, 2014

    It seems that I need to run this command after every restart to fix the problem:

    im logging --category=CACHE --level=-2 --server=<serverName>