SyslogCollector Status... missing Collector!

[Leonardo Roberto]

Hi folks!

I've RME 4.0.5 on LMS suite...

After done a stop/start of SyslogCollector and SyslogAnalyzer processes, the collector is vanished from the Collector Status window.

The processes are up and from the logs seems that they runs correctly but...

In the SyslogAnalyzerUI.log file I found the following error:

[ Mon Nov 26 16:53:45 MET 2007 ],ERROR,[Ajp13Processor[9009][2]],SA0015: Cannot contact SyslogAnalyzer service for up

dating Collector status information

com.cisco.nm.xms.ctm.common.CTMException: URN_NOT_FOUND : urn "SyslogAnalyzerService" : Not found !!

at com.cisco.nm.xms.ctm.client.CTMCall.establishIPC(CTMCall.java:201)

at com.cisco.nm.xms.ctm.client.CTMCall.<init>(CTMCall.java:181)

at com.cisco.nm.xms.ctm.client.CTMClient.invoke(CTMClient.java:253)

at com.cisco.nm.xms.ctm.client.CTMClient.invoke(CTMClient.java:123)

at com.cisco.nm.rmeng.sa.ui.helper.RmeSaCollectorStatus.getCollectorStatus(RmeSaCollectorStatus.java:35)

..............

etc..

So I cannot ADD a new Collector, and no errors give me during the ADD acticvity

Is not a peer server certificate problem, because it's setted correctly.

Another things:

The local DB was restored into another twin server. This twin server was affected with same problem.

Any helps would be appreciated!

Thanks

Leonardo

[Leonardo Roberto]

Thanks joe.

A last question about..

we have two DNS servers named, A and B.

This problem was occur when one of two DNS servers (B) has shutted down.

On the LMS solaris system, the first DNS choice was the running DNS (A).

Can this "shut" cause the problem on SyslogAnalyzer?

I would like to avoid again this problem.

Thanks in advance

Leonardo

[Joe Clarke]

A misconfigured DNS can also cause this problem. Assuming server A had all of the PTR entries, server B should never have been contacted. But, any missing entries would have caused RME to query server B which would lead to timeouts.

You can try removing server B, and see if the situation improves. Or you could upgrade to RME 4.0.6 which has the fix.

[Leonardo Roberto]

Hi joe.

I see that this problem is the bug CSCsh66475.

This bug is referer to windows machine.

Thus this behaviour is the same for solaris and the bug id is valid also for solaris.

Why the bug details doesn't write solaris also?

It has to be update?

We have solaris 8.

My customer would like to know if this bug is valid also for solaris.

He want to justify the update to RME 4.0.6.

Thanks in advance!

Leonardo

[Joe Clarke]

The bug can be valid for Solaris if the DNS is misconfigured. The bottom line is that RME resolves all of the interface IPs. If this takes a long time, then SyslogAnalyzer will take a long time to fully initialize. This typically only affects Windows as Windows name resolution is a bit more involved than Solaris.

In either case, this can be fixed by upgrading to Common Services 3.0.6 and RME 4.0.6.

[Leonardo Roberto]

Ok.

Thanks a lot for your support!

Leonardo