Windows Socket Create Error Under Git Bash

Tagged: , ,

This topic has 1 reply, 1 voice, and was last updated 6 years, 4 months ago by Gregory Wright.

  • Author
    Posts
  • #10427
     Gregory Wright
    Participant

    I have not had a fruitful day of tracking down an answer to this via Google, so I am turning to you all to see if someone else has run into this issue or something similar. Any help would be greatly appreciated.

    I am running into the following error when trying to run the LDAP utility commands and the control-panel application for OpenDJ (2.7 and 3.0) using Java 8 update 91 / 92 under Git Bash 2.8.1 with Windows 7 and Windows 10:
    `
    [10/05/2016:18:11:18 -0400] category=TOOLS seq=0 severity=FINEST msg=Unrecognized Windows Sockets error: 10106: create exception=SocketException: Unrecognized Windows Sockets error: 10106: create (null:-1 null:-1 null:-1 LDAPConnection.java:510 LDAPConnection.java:621 LDAPConnection.java:249 LDAPModify.java:1113 LDAPModify.java:510)
    [10/05/2016:18:11:18 -0400] category=TOOLS seq=1 severity=FINEST msg=Unrecognized Windows Sockets error: 10106: create exception=LDAPConnectionException: Unrecognized Windows Sockets error: 10106: create (LDAPConnection.java:532 LDAPConnection.java:621 LDAPConnection.java:249 LDAPModify.java:1113 LDAPModify.java:510)
    Unrecognized Windows Sockets error: 10106: create
    `
    If I run the control-panel via control-panel.bat from the Windows shell, everything works fine. However, all of our load scripts are written to run under Bash. They were working fine under a previous version of Git Bash and Java 8 update 71, but at the moment I’m not sure which version of Git Bash to try backing out to.

    #10761
     Gregory Wright
    Participant

    I can only assume that sometime prior to upgrading the versions of Git and Java, things worked more by accident than design (e.g., the Windows Java environment got picked up by the version Bash provided by the prior version of Git). Once I defined the OPENDJ_JAVA_HOME environment variable for my Windows user as described in the installation manual, things started behaving properly.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

©2022 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?