ITEM: U9858L

sbclient: setup of install server failed : connect failed

Question:

Env:
  AIX 3.2.5
  sysback ver 3.2.1.6

Desc:  
  Customer is trying to set up a network server using sysback
  and is getting this error message:

  sbclient: setup of install server failed

 
Action:
  /usr/lpp/sysback/inst/sbclient \ check
  sbclient: unable to connect to socket


Response:

Act:    Sysback is failing in the netsopen function in sbclient.
        sbclient is attempting to make a connect call to the
        server, in this case sbserver on port 1235.  It is
        this connect call that is failing:

   /* Got the socket, try to connect with the remote host */
   if (connect(rc,(struct sockaddr *)&ssin,sizeof(ssin)) \< 0) {
      close(rc);                /* the connect system call failed */
      fprintf(stderr, "sbclient: unable to connect to socket\\n");
      return(-1);
   }

        The connect system call attempts to take an already
        created socket, in this case the socket referenced by
        "rc", and connect it to a socket on a remote server
        process.  The structure "ssin" specifies the hostname   
        and port of the remote client we're trying to connect
        to.  The hostname is specified on the command line, and
        the correct port is looked up in the /etc/services file.

        The connect call expects that there is going to be something
        at the remote end of the socket connection for it to
        connect to.  There should be either a process already 
        bound to the port on that server and in the LISTEN state,
        ( use 'netstat -an | grep \' to find out ) or
        inetd should be configured to monitor requests to that
        port.  In this case, sysback is using inetd.

        The script /usr/sbin/cfginstsvr performs the proper
        steps to configure inetd to monitor for requests to 
        this service (sbserver).  An entry must be placed in
        /etc/services specifying the service name, the port,
        and the protocol that inetd should be looking for.  
        /etc/inetd.conf must also be updated to include information
        on what process to start when a request is made to the
        port:

sbinst  stream  tcp     nowait  sbnet   /usr/lpp/sysback/netinst/bin/sbserver sb
server /usr/lpp/sysback/netinst/scripts

        After these changes have been made, the inetd daemon
        needs to be refreshed.  If inetd was started via 
        SRC control, ( lssrc -s inetd ) then the InetServ database
        needs to be updated ( inetimp ) before inetd is refreshed.
        ( refresh -s inetd ).  If inetd was started from the
        command line, then after modifying the files send
        SIGHUP to inetd.  ( kill -1 \ )

        What probably happened here, was that for some reason
        either inetd didn't get refreshed, or the changes were
        not imported into the InetServ database when the refresh
        was run.  ( The changes actually were in the files. )

        Manually running:

        inetimp
        refresh -s inetd
        /usr/lpp/sysback/inst/sbclient \ check 

        forced the inetd to get refreshed with our changes
        and then sbclient ran without a hitch.

Next:   CC.




Support Line: sbclient: setup of install server failed : connect failed ITEM: U9858L

Dated: May 1995 Category: N/A

This HTML file was generated 99/06/24~13:30:34

Comments or suggestions?
Contact us