Domino startup fails with message "Unable to bind to port 2050 on host machine"

25 January, 2011 10:17:00 AM Miguel Calvo  Domino  |  Comentarios (6)

Last week I detected the same problem than the published in this Technote, Domino startup fails with message "Unable to bind to port 2050 on host machine", on a Windows 2003 server on a VMware virtual environtment. My server was Domino 8.5.2 FP1. I was unable to start the Domino server with the -jc switch. The server controller always throwed the error  "Unable to bind to port 2050 on host machine 192.168.0.100"

I turned off the firewall, checked that the 2050 port was not being used by any other software, verified the host name in the server document, and tried to find out where 192.168.0.100 IP came from. I was unable. That IP was not assigned to any network card.

Any clue ?

Gravatar Image
1) Domino startup fails with message Unable to bind to port 2050 on host machine
René Winkelmeyer 1/25/2011 11:24:48 AM http://blog.winkelmeyer.com

Hi!

Have you checked the settings in the server document (Ports => Internet Ports => Server Controller) and the content of the dcontroller.ini in the domino data path?

-- René

Gravatar Image
2) Domino startup fails with message Unable to bind to port 2050 on host machine
Mark 1/25/2011 11:24:54 AM

If you don't have the IP then it would have trouble binding to it!

Have you checked the contents of dcontroller.ini ? Maybe that got a bad IP somehow?

Gravatar Image
3) Domino startup fails with message Unable to bind to port 2050 on host machine
Miguel Calvo 1/25/2011 11:42:30 AM

Thanks and

SOLVED: It was my fault

Ports => Internet Ports => Server Controller had the wrong IP.

But why was 192.168.1.100 in that field ? Where it came from ? Did it read it from the Host machine virtual network ?

Gravatar Image
4) Domino startup fails with message Unable to bind to port 2050 on host machine
Harald Gärttner 1/25/2011 12:02:11 PM http://twitter.com/ShadowBJ21

We had a similar problem once and found out that it came from a file called admin.xml (hope I got the name correctly).

In this file there's stored a lot of startup information that is used BEFORE the server reads the adressbook and the serverdocuments.

In our case a migration from one machine to another (wit a change of IP adresses) caused that we had a wron IP in here and the machine wasn't able to start.

Gravatar Image
5) Domino startup fails with message Unable to bind to port 2050 on host machine
Miguel Angel Calvo 1/25/2011 1:31:22 PM

@Harald,

Thank you, the name is admindata.xml but I think it gets created after the server is started with the Server Controller. So the information is read from the names.nsf innitially. But I'm not completely sure though.

I still don't know where the initial IP went to the Server doc in the names.nsf :-)

Gravatar Image
6) Domino startup fails with message Unable to bind to port 2050 on host machine
Harald Gärttner 1/25/2011 2:37:49 PM http://twitter.com/ShadowBJ21

Yes, exactly admindata.xml ... and yes, the information there is read from the names.nsf initially. But upon the start of the server it's the first information pulled before the server can reach the names.nsf.

So there might be cases were this information is wrong while the names.nsf is still correct. In that case the correct infomation won't be update the admindata.xml as the server never opens the names.nsf during the failing start. That's what happened to us.

But unless you made something tricky like a sever switch or stuff like getting an older names.nsf from another server etc. you most probably can't counterfeit the admindata.xml.

Deja una respuesta


Nota:  (No HTML - Los enlaces serán convertidos si están precedidos por http://)

¿ Recuérdame?