Loads of problems after upgrading to LMS3.2

Unanswered Question
Oct 1st, 2009

After the upgrade from lms3.1 to 3.2, recommended by Cisco because of some bugs we ran into on lms3.1 we have several big problems:

- Every day or other day all devices are gone in RME, not in CS (see attachment).

After restarting the deamon manager the devices are visible again.

- When starting device manager it takes at least 15min. before the selected device shows up. It's just telling its opening (see attachment red arrows) but nothing happends untill 15min. later.

- User tracking doesn't seem to work at all, only historical before upgrade data is available.

At this moment not all the functionalities are tested, because of these basic problems but I can imagine that more issues may arise.

Can someone please help?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Thu, 10/01/2009 - 08:19

I haven't seen any of these problems. I'll focus on the RME devices problem in this thread. I recommend you start new threads for the other issues. Really, I recommend you open some TAC service requests as these problems may require some remote access so they can be analyzed in real time.

As for the missing devices issue, please post the rme_ctm.log, and RMEDeviceSelector.log after reproducing the problem.

orsonjoon Thu, 10/01/2009 - 22:10

Thanks for the quick response, I havn't posted the rme_ctm.log, because of the size limit, but below is a piece of it, hope this helps:

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,589,Trying to find matching method, using our own methodMatcher method

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[TP-Processor7],com.cisco.nm.xms.ctm.client.CTMCall,219,Establish IPC

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,170,Just created a new ID:1254399051501

[ Thu Oct 01 14:10:51 CEST 2009 ],INFO ,[Thread-9],com.cisco.nm.xms.ctm.common.CTMRequestProcessor,210,Added cliententry, requestID:1254399051501 hashtable size:16

Joe Clarke Fri, 10/02/2009 - 09:43

Post the EssentialsDM*.log and NMSROOT/MDC/tomcat/stdout.log and stderr.log files after reproducing the problem.

Joe Clarke Sat, 10/03/2009 - 08:02

You did not include the stderr.log, but I'm doubtful I'll see anything. It doesn't appear that you ever went back to RME Devices to reproduce the problem. Exactly when did you see this problem with the devices missing from the RME Devices device selector last?

orsonjoon Mon, 10/05/2009 - 23:09

Strange thing is I broke the multiserver trust and the problem is gone.

We are not planning to set it up again, so this won't be an issue for us anymore.

Thanks for all the help anyway.

Actions

This Discussion