The Dgraph cannot start if its process cannot bind to a socket and its port cannot initialize. This error tends to occur when you upgrade the MDEX Engine and attempt to use a port that is already occupied by another process on your server.
The baseline update script from the Deployment Template completes, but the MDEX Engine does not start. The following errors appear in the Dgraph log:
ERROR (date and time)
DGRAPH {dgraph,baseline}: Unable to bind
to socket [err=`Result too large',errno=34]
FATAL (date and time)
DGRAPH {dgraph,baseline}: Unable to initialize the
main server port: 8000
The
"Unable to bind to socket" errors usually indicate
that the port in question is already in use by another process.
The Windows command-line utility
netstat -ano lists all ports in use along with the
process ID of the process using them. Use this utility to identify the process
ID occupying port 8000, and locate that process in the Windows Task Manager to
confirm that it is used by another process. This prevents the Dgraph from
starting.
To identify ports in use on your Windows system:
This command lists ports and process IDs of all processes that are running.
Examine which process occupies the port that the Dgraph is trying to use. In this example, it is port 8000.
Run the Dgraph on another port, or ensure that the previously occupied port can be freed to be used by the MDEX Engine.
