RSM Logs error

 
Joseph Pulicani
Occasional Advisor

RSM Logs error

Hi,

I configure RSM, when i click in Logs, i receive this message :

LogConfigurationModel refresh; nested exception is:
javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]

An idea ?

Thanks
12 REPLIES 12
Michel Oudt
New Member

Re: RSM Logs error

Same issue here!

Joseph, did you solve it yet?
Joseph Pulicani
Occasional Advisor

Re: RSM Logs error

Perhaps yes,

You must verify if you have many javaw.exe

I think, it's the problem ; the path of javaw.exe.

Joseph
Michel Oudt
New Member

Re: RSM Logs error

i have like 13 instances of javaw.exe!..which one should be used by RSM? and should i add it to the path statement?

thx!
Herman Sugeng_1
Frequent Advisor

Re: RSM Logs error

Hallo,
I have the same problem on een SMA III (dl360), but not in SMA II (dl380).
What excactly is you solution? I do not see the solution.
My CVE is v.6.0.2 and the RSM is v.2.1
Please advice, thanks
Herman
Joseph Pulicani
Occasional Advisor

Re: RSM Logs error

Hi Herman,

Have you install a java JRE ( 5 or more).

I think that it's the problem.

Joseph
Herman Sugeng_1
Frequent Advisor

Re: RSM Logs error

Hallo Joseph,
Thanks for your answer.
No, JRE is 1.4.2_03, this works in dl380 SMA II.
Best regards
Herman Sugeng_1
Frequent Advisor

Re: RSM Logs error

Hallo Joseph,
Thanks for your answer.
No, JRE is 1.4.2_03, this works in dl380 SMA II.
But since I have deinstall old ContinousAccess I have different error now: javax.naming.NameNotFoundExecption: LogConfig not bound in Log configuration and StorageLicenseRemote not bound in License.
Best regards, Herman
Michel O
New Member

Re: RSM Logs error

hi,

resolution to my problem was:
Stop ReplServer
Stop ReplicationDB
Start ReplicationDB
Start ReplServer

turned out DESTA (part of Webes) and RSM were trying to use the same socket.

wont hurt to try the same.

rgds,
Michel
Herman Sugeng_1
Frequent Advisor

Re: RSM Logs error

Hallo Michel,

I found several things:
1. The was still ContinousAccess active.
2. I install RSM on the SMA which CVE is not active.

Now I got the RMS detecting the EVA5000 and shows everything but all with "?".

Status now RSM stays in "Retriving Event, please wait"
in configuration: see attachment
1. "Licensing" "StorageLicenseRemote not bound".
2. Logs "nested exection is: javax.naming.NameNotFoundException: LogConfig not bound"

Tried your suggestion, no result.

Any idees where I have to look?
Best regards, Herman
Licensing in CVE is OK.