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; } } }

unable to connect open deploy daemon

gayathri

When i put the iwodcmd command i get this message

iwodcmd serverstatus
Unable to Connect to OpenDeploy daemon
Reason: Failed to create Socket
Reason: sockErr=10057, Socket is not connected
Check that the OpenDeploy server on host localhost is listening on port 3434.

Environment :Teamsite 6.7.1,OD6.1,Win2k.
i tried Deploy cltProxyAuthCheck set to no in deploy.cfg.
restarted iwod60 still it is not working.

Any help, greatly appreciated.

thanks and regards
gayathri

Find more posts tagged with

Comments

nipper

view your OpenDeploy logs, in either OpenDeployNG or OpenDeployNG /logs. Post anything that has been updated recently. Also, check your event viewer.

gayathri

in snmp log i get
OpenDeploy server unavailable:
Reason = Connection refused to host nested exception is:
java.net.ConnectException: Connection refused: connect
Server can not be reached, server might be down

in odbase log i get
Bring up of OpenDeploy server FAILED.

nipper

Look in OpenDeployNG for od.log and od.err

See if they have anything meaningful. Ignore the snmp log

Adam Stoller

Look in OpenDeployNG for od.log and od.err

See if they have anything meaningful. Ignore the snmp log

Also - try running the following commands from the Command Prompt:

C:\> net stop iwod60
You'll probably see an error about it not running
C:\> net start iwod60

Then see if you can run iwodcmd serverstatus after a minute or two (it takes a bit of time for it to fully start up.

Antharix

Also check the od config files and ensure that correct references are made to the Base server and receiver respectively.

Erroneous definitions may cause the receiver not to startup, as desired.

neeraj_forever

When i put the iwodcmd command i get this message

iwodcmd serverstatus
Unable to Connect to OpenDeploy daemon
Reason: Failed to create Socket
Reason: sockErr=10057, Socket is not connected
Check that the OpenDeploy server on host localhost is listening on port 3434.

Environment :Teamsite 6.7.1,OD6.1,Win2k.
i tried Deploy cltProxyAuthCheck set to no in deploy.cfg.
restarted iwod60 still it is not working.

Any help, greatly appreciated.

thanks and regards
gayathri

Hi Friends,
Actually I m getting the same error when I m trying to run the iwodcmd serverstatus .so do u have any idea how to resolve it.

Thanking you
Neeraj

nakumar

Restart your opendeploy service. On which platform you are running into issue?

neeraj_forever

Restart your opendeploy service. On which platform you are running into issue?

I have restarted the services through clt and through services,but still I m getting the same error,inspite of iwOD 60 services up.

and also iwOD 60 services getting down automatically twice in a week without any indication of error in the log files.

thanks
Neeraj

nakumar

Can you post OD-HOME\od.log and od.err? and also hostname_odbase.log?

Adam Stoller

I have restarted the services through clt and through services,but still I m getting the same error,inspite of iwOD 60 services up.

and also iwOD 60 services getting down automatically twice in a week without any indication of error in the log files.

thanks
Neeraj

Do you have something else running on that server which may be utilizing the same port(s) and thus disrupting the OD service?

yogesh_agrawal

please check "Deploy.cltProxyEnable:" value in deploy.cfg . it should be "y".
i.e Deploy.cltProxyEnable: y

tivinelvis

Try restarting your interwoven webdaemon service. The issue will be resolved.

Adam Stoller

Try restarting your interwoven webdaemon service. The issue will be resolved.

Try reading the information in the thread (including the last date it was active) and consider your response before posting it - since this is the third OpenDeploy thread you've responded to saying the exact same thing, and all three times your response has nothing to do with the problem that was being discussed in the thread.