nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OpenDeploy

lokesh

Hi All,

Does any one had any idea about this...

SVR: 2003-01-07 11:48:30 CST GMT-06:00 *** OpenDeploy engine component started. ***

SVR: 2003-01-07 11:48:30 CST GMT-06:00 Get any RMI connection ports specified in the deploy.cfg file
SVR: 2003-01-07 11:48:30 CST GMT-06:00 No RMI connection ports specified in the deploy.cfg file
SVR: 2003-01-07 11:48:30 CST GMT-06:00 Using default RMI connection port numbers: 24071 to 24077
SVR: 2003-01-07 11:48:30 CST GMT-06:00 Initialize OpenDeploy API component.
API: 2003-01-07 11:48:31 CST GMT-06:00 Register OpenDeploy service with RMI registry.
SVR: 2003-01-07 11:48:31 CST GMT-06:00 OpenDeploy server host: localhost, RMI registry port: 9173

SVR: 2003-01-07 11:48:34 CST GMT-06:00 *** OpenDeploy API component started. ***

SVR: 2003-01-07 11:48:34 CST GMT-06:00 *** OPENDEPLOY SERVER FINISHED STARTUP. ***
ENG: 2003-01-07 12:20:42 CST GMT-06:00 ***ERROR - Listener accept failed. IOException: java.io.IOException

ENG: 2003-01-07 12:20:42 CST GMT-06:00 ***ERROR - Listener accept failure

ENG: 2003-01-07 12:20:48 CST GMT-06:00 ***ERROR - Listener accept failed. IOException: java.io.IOException

ENG: 2003-01-07 12:20:48 CST GMT-06:00 ***ERROR - Listener accept failure

ENG: 2003-01-07 12:20:55 CST GMT-06:00 ***ERROR - Listener accept failed. IOException: java.io.IOException

ENG: 2003-01-07 12:20:55 CST GMT-06:00 ***ERROR - Listener accept failure

ENG: 2003-01-07 12:21:01 CST GMT-06:00 ***ERROR - Listener accept failed. IOException: java.io.IOException

ENG: 2003-01-07 12:21:01 CST GMT-06:00 ***ERROR - Listener accept failure

ENG: 2003-01-07 12:21:07 CST GMT-06:00 ***ERROR - Listener accept failed. IOException: java.io.IOException

ENG: 2003-01-07 12:21:07 CST GMT-06:00 ***ERROR - Listener accept failure
I am getting this error in the log file:

ENG: 2003-01-07 16:19:36 CST GMT-06:00 Thread-8 ***ERROR - Job ID=m1Deployment=xyz
Base: failed creating socket, got null.

Thank you,
lokesh.

Find more posts tagged with

Comments

Migrateduser

Are you attempting to run your deployment with SSL enabled?

Make sure that both ends (sender and rcvr) both have SSL configured correctly if you are using SSL. The settings must match on both ends (cyphers and such) and the paths to all the keys must be correct.

you also might want to try disabling SSL and making sure that the deployment works without the keys first. You also might want to think about attaching both sender and rcvr configurations to this forum if you want more help.

Migrateduser

R u deploying using SSL?

lokesh

ssl enabled

lokesh

yes

Migrateduser

Telling us that SSL is enabled does not help us without copies of your config files. Most commonly when you see the cannot connect socket errors with a deployment with SSL enabled it has to do with problems with the config files or invalid SSL cert/key pairs.

If you want help you need to provide a little more info.

lokesh

Hi Nacks,

Thank you for your help.

nodes config of source

Edited by lokesh on 01/08/03 10:10 AM (server time).

lokesh

deployment conig of source.

KeepTogetherSusbst.ssd.zip

Output.pdf

lokesh

receiver config file.

articles.ssd.zip

output.pdf

lokesh

nodes config of receiver

Migrateduser

Hi Lokesh,
Did the deployment run with the SSL specification??

Test.pdf

KeepTogetherSusbst - b.zip

Migrateduser

oops...sorry without the ssl Smiley Wink

Migrateduser

is this from the od.log from the rcvr or odbase (or is this from some other log)?

One other thing to try, for whatever server you are seeing this error on, try shutting down OD and check the process table listing to make sure there is nothing still hanging around and then restart.

I still think that the issue has to do with either one of the keys not being in the correct format or maybe one of the paths being incorrect. you should verify each of the paths you have to the SSL related files from the command line.

lokesh

I was sure that this is happinig due to the keys,i have to check this out. The log info which i had sent you is from the receiver's log file

Thank you.

KeepTogetherSusbst - c.ssd.zip

Output.pdf

lokesh

Hi Nacks,

I got this working i had regenerated the client certificates.

Thank you,
lokesh.

lokesh

Hi Alfred,

I got this working i had regenerated client certificates.

Thank you,
lokesh.

Bryan_K

Lokesh, Im having the same problem.

What do you mean when you say you had regenerated client certificates. Does that mean that you had regenerated them, and that caused the problem, or does it mean that you regenerated them to fix the problem?