2 Replies Latest reply on Mar 7, 2016 9:33 AM by Yanick Girouard

    RSCD Agent Logs: session_thread: caught exception. Command did not complete.

    Yanick Girouard

      We're getting a ton of these errors in a lot of our RSCD agent logs. What are they and how can we get rid of them? This is with RSCD 8.5.01.304 on Windows 2003 and 2008. It's making the logs much bigger than they should be !

       

      192.168.1.10 10/02/15 08:53:34.820 1068 SYSTEM (Not_available): (Not_available): session_thread: caught exception. Command did not complete.

      192.168.1.10 10/02/15 08:54:44.225 7848 SYSTEM (Not_available): (Not_available): session_thread: caught exception. Command did not complete.

      192.168.1.10 10/02/15 08:55:53.474 12964 SYSTEM (Not_available): (Not_available): session_thread: caught exception. Command did not complete.

      192.168.1.10 10/02/15 08:57:01.537 5444 SYSTEM (Not_available): (Not_available): session_thread: caught exception. Command did not complete.

      192.168.1.10 10/02/15 08:58:09.616 4988 SYSTEM (Not_available): (Not_available): session_thread: caught exception. Command did not complete.

      192.168.1.10 10/02/15 08:59:15.292 16284 SYSTEM (Not_available): (Not_available): session_thread: caught exception. Command did not complete.

      192.168.1.10 10/02/15 09:00:24.900 11836 SYSTEM (Not_available): (Not_available): session_thread: caught exception. Command did not complete.

      192.168.1.10 10/02/15 09:01:33.088 7012 SYSTEM (Not_available): (Not_available): session_thread: caught exception. Command did not complete.