When firing up Enterprise Server Administration via the web the startup failed, showing the message NET_BIND failed with return code of 226.
Problem:
When starting Enterprise Server Administration via the web, the startup failed with the following messages:
02/22/05 14:21:19 CCITCP (tcpnet.c $Revision: 4.75.1.1 $:0064) 20000 E bind (), called in NET_BIND, failed with return code 226.
050222 14211536 CASCD1020I JCP service process created for region ESDEMO, process-id = 00544 14:21:15
050222 14211537 CASCD0127I SEP 0001 created for ES ESDEMO, process-id = 00545 14:21:15
050222 14211554 544 ESDEMO CASJC0001I Journal control initialized 14:21:15
050222 14211598 545 ESDEMO CASSI1500I SEP initialization started 14:21:15
050222 14211604 CASCD0127I SEP 0002 created for ES ESDEMO, process-id = 00612 14:21:16
050222 14211628 612 ESDEMO CASSI1500I SEP initialization started 14:21:16
050222 14211634 CASCD1038I ES Communications Server created, ES ESDEMO, process-id = 00631 14:21:16
050222 14211634 106 ESDEMO CASKC1000I ES concurrent request limit: 0000 000003 14:21:16
050222 14211634 106 ESDEMO CASSI1000I Server Manager initialization completed successfully 14:21:16
050222 14211645 545 ESDEMO CASSI1600I SEP initialization completed successfully 14:21:16
050222 14211747 612 ESDEMO CASSI1600I SEP initialization completed successfully 14:21:17
050222 14211896 631 ESDEMO CASCS5001I Communications interface 01 initialization started 14:21:18
050222 14211901 631 ESDEMO CASCS5003I Communications interface 01 initialization complete 14:21:19
050222 14212101 CASCD1039I ES Communications Server for ES ESDEMO has terminated normally 14:21:21
050222 14212112 1249 ESDEMO CASSP0002I Server manager informed of process termination, pinfo = H,0000000631 14:21:21
Resolution:
The error message means the "bind()" function failed and set errno to 226. The meaning of specific errno values depends on the platform, where "bind()" is the socket's function that associates a TCP server socket with a port.
For example, if you are using HPUX 11i, 226 is EADDRINUSE: bind failed because another socket is already bound to that port. You are trying to start an Enterprise Server that is configured to use a port which something else is using. This is a standard Unix system administration issue which your administrator should have no problem identifying and correcting it. The MFCS log should show what the conflicting port number is; a utility like lsof will show what is already bound to it. The actual fix will depend on what the conflict is and how the system should be arranged. An easy fix is to change the Enterprise Server configuration to use a different port or use a system-assigned one.
#MFDS
#EnterpriseDeveloper