After upgrading ISC - error: WD_108 :: Could not connect to the name server

[gaborjuhasz]

Hi Experts,

I've got the task to do the upgrade from ISC 4.1.2 to ISC 4.2 on our server, however, I've run into the following problem:

- I've installed ISC 4.2 without any issue.

- I've used the ISC42_UpgradeTool to upgrade the 4.1.2 repository to 4.2 and it was successful.

- I've issued the command ". /opt/isc-4.2/bin/vpnenv.sh".

- However, when I tried to issue "startwd" I got the following error message:

==== Invoked Startup ====

com.cisco.vpnsc.watchdog.WDRuntimeException: WD_108 :: Could not connect to the name server

com.cisco.vpnsc.dist.ConnectException: Error connecting to the name server while creating the initial context.

javax.naming.CommunicationException: Cannot connect to ORB [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No]

at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:362)

at com.sun.jndi.cosnaming.CNCtx.initUsingIiopUrl(CNCtx.java:289)

at com.sun.jndi.cosnaming.CNCtx.initUsingUrl(CNCtx.java:245)

at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:209)

at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:69)

at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:32)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)

at javax.naming.InitialContext.init(InitialContext.java:219)

at javax.naming.InitialContext.<init>(InitialContext.java:195)

at com.cisco.vpnsc.dist.RmiIiopUtil.getContext(RmiIiopUtil.java:173)

at com.cisco.vpnsc.dist.RemoteUtil.getContext(RemoteUtil.java:108)

at com.cisco.vpnsc.watchdog.Main.checkNameServer(Main.java:233)

at com.cisco.vpnsc.watchdog.Main.<init>(Main.java:96)

at com.cisco.vpnsc.watchdog.Main.main(Main.java:77)

Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No

at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:148)

at com.sun.corba.se.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:65)

at com.sun.corba.se.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:67)

at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:652)

at com.sun.corba.se.internal.corba.ClientDelegate.createRequest(ClientDelegate.java:594)

at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1105)

at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)

at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)

at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)

at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)

at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:340)

... 14 more

So, watchdog is not able to run. This error message also appears after a server reboot.

I've also tried to start the previous version (4.1.2) but I got the same result.

Could you please help me to find out what is the root cause of the above error message?

Thanks in advance and have a nice day!

Regards,

Gabor

[David Stanford]

Are DNS and name resolution fully configured?

Try the following:

log in as iscadm (or the user you installed isc under) and do:

(make sure you source the vpnenv.sh)

./stopwd -all

./stopns -y

./stopdb -y

Then restart with

./startwd -all

What messages are returned?

[gaborjuhasz]

Hi David,

Yes, DNS is configured correctly.

I've tried the commands you suggested, however, I got the same error message. :(

You can have a look at it in the attachment (WD_108_error.txt). It contains the full output.

Do you have any other idea?

Thanks in advance for your help and have a nice day!

Regards,

Gabor

[gaborjuhasz]

Hi David,

One more thing...

The version 3.2 works fine on the same machine. However, I'm not able to find out the diffrences between v3.2 and v4.1.2 and v4.2.

Do you have any other idea what should I look for?

Regards,

Gabor

[gaborjuhasz]

FYI:

I've compared the following files of v3.2 and v4.2:

etc/boot.properties

etc/vpnsc.properties

bin/vpnenv.sh

and changed the hostname to the correct one in v4.2 files. I had to use HOSTNAME in most cases, however,

there were some places where I had to use FQDN instead.

Now, it is working fine. :)

[David Stanford]

Thanks...the error indicated that either DNS or hostname resolution was not fully working