Unable to disable logging of CACHE on 10.3

[ptc-4668818]

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.)

[jgorsline]

John,

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

[ptc-4668818]

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

Still have the problem.

[jgorsline]

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.

[KaelLizak]

Hi John,

I think the problem is that INFO logging is enabled. On 10.3, you should be able to see your current logging levels by running im diag --diag=loginfo from a workstation which has the Integrity client installed, and you should see a line which has something like:

message.includeCategory.INFO=10

If you disable INFO logging, that line should go away the next time you run the logInfo diag. Try disabling INFO logging and seeing what happens in your log.

Regards,

Kael

[ptc-4668818]

Still have the problem. I forced INFO logging off, but still see the entries in the log. Here is a dump of my loginfo:

message.includeCategory.DIAGNOSTIC=-1

message.includeCategory.EMAIL=20

message.includeCategory.REALMUSERCACHE=-1

message.includeCategory.DEBUG=-1

message.includeCategory.MKSALM=-1

message.includeCategory.ERROR=10

message.includeCategory.FATAL=20

message.includeCategory.TM=5

message.includeCategory.GENERAL=-1

message.includeCategory.CACHE=-1

message.includeCategory.SQL=-1

message.includeCategory.LDAP=-1

message.includeCategory.INFO=-1

message.includeCategory.API=-1

message.includeCategory.ApplicationState=5

message.includeCategory.SD=5

message.includeCategory.WARNING=10

message.includeCategory.MKSRQ=-1

message.includeCategory.ApplicationException=10

exception.includeCategory.DIAGNOSTIC=-1

exception.includeCategory.EMAIL=20

exception.includeCategory.REALMUSERCACHE=-1

exception.includeCategory.DEBUG=-1

exception.includeCategory.MKSALM=-1

exception.includeCategory.ERROR=10

exception.includeCategory.FATAL=20

exception.includeCategory.GENERAL=-1

exception.includeCategory.CACHE=-1

exception.includeCategory.SQL=-1

exception.includeCategory.LDAP=-1

exception.includeCategory.INFO=-1

exception.includeCategory.API=-1

exception.includeCategory.MKSRQ=-1

exception.includeCategory.WARNING=10

message.format.WARNING=* * * * {2} * * * * ({3}): {4}

message.format.ERROR=* * * * {2} * * * * ({3}): {4}

message.format.DIAGNOSTIC={2}({3}): {6}: {4}

exception.format.GENERAL={2}({3}): {4} -- {6}

exception.format.WARNING=* * * * {2} * * * * ({3}): {4} -- {6}

exception.format.ERROR=* * * * {2} * * * * ({3}): {4} -- {6}

exception.format.DIAGNOSTIC={2}({3}): {4} -- {6}

message.defaultFormat={2}({3}): {4}

exception.defaultFormat={2} {4}: {6}

[KaelLizak]

Looking at the original messages again, this makes sense.

John Stroebel wrote:

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)

The number in parentheses after "CACHE" is -1, which is the level that that message will be printed at.

Try running

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

Regards,
Kael

[ptc-4668818]

After running the command my log looks like this:

2014-09-26 13:50:56,245 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 13:52:43,667 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 13:54:58,919 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 13:55:01,087 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 13:55:03,068 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 13:57:22,532 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 13:58:24,511 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 13:58:25,197 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 13:58:25,962 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 13:58:26,851 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 13:58:28,021 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 13:58:28,754 INFO [mksis.IntegrityServer] CACHE(-1): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:43,335 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:45,207 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:45,987 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:47,469 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:50,293 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:50,870 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:51,775 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:52,399 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:53,039 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:53,865 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:54,443 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:55,004 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:55,597 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:56,174 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

2014-09-26 14:00:57,812 INFO [mksis.IntegrityServer] CACHE(-2): SWBuild: Client cache not disconnected. (soft disconnect)

[ptc-4668818]

Any other ideas?

[KaelLizak]

Hello John,

Please contact PTC Integrity Support to open a case to investigate this.

[ptc-4668818]

Bummer, I no longer have support. I was hoping to get an answer on the Community site.

Oh, well...

[ptc-4668818]

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.

[ptc-4668818]

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

[jgorsline · Accepted solution]

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.

[ptc-4668818]

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

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

[jgorsline]

Granted that it's not perfect, but that is at least it's a workaround.