ITEM: S2835L

Errors trying to create a network install server with sysback/6000

Question:

Question:

Env
AIX 3.2.5
sysback 3.1.0.34

Customer is getting a error when trying to setup the
system as a sysback network install server.

Using this method:
smitty installp
  Remote Backup Services
    Configure this Host as a Network Install Server

The command being call is the 
  /usr/sbin/cfginstsvr 

The command will add lines in the inetd.conf, and 
services

It adds this line in inetd.conf:
sbinst  stream  tcp     nowait  sbnet   /usr/lpp/sysback/netinst/bin/sbserver s
bserver /usr/lpp/sysback/netinst/scripts
It adds this line to services:

sbinst          1235/tcp            \# Sysback Network Installs

It also creates a sbnet user

Refresh the daemon
refresh -s inetd

Then check the socket with this command:
/usr/lpp/sysback/inst/sbclient $host check
it fails on this line.  The sbclient cannot open
the socket at all.

This command just checks if the socket can be used

I have check all the settings and everything seems to be correct.
No other process is using socket 1235

I am not sure what else to check on this system.

Told the customer that after he makes changes to the inetd.conf file,
he needs to run the command 'inetimp' BEFORE running 'refresh -s inetd'.
This causes any changes made to the inetd.conf file to be reflected in
the ODM.

'refresh -s inetd' without any extra paramters gets its information 
from the ODM.  If 'inetimp' is not run, changes made to inetd.conf will
not be picked up when inetd is refreshed.


Response:

ACT:  Spoke with the user, the system he is running on also supports
      oracle.  Suggested that he reboot and do the installation prior
      to doing the install of sysback to insure that the port is not
      used.

NEXT: wocb

Response:

vi /etc/syslog.conf
  change this line:
\#  *.debug         /dev/console
    to
*.debug         /dev/console

refresh -s syslogd
smit -C inetd
  inetd Subsystem
    Change / Show Restart Characteristics of inetd Subsystem
    Change this line:
    Start the inetd subsystem with DEBUGGING on?        no
       to
    Start the inetd subsystem with DEBUGGING on?        yes

smit inetd
   inetd Subsystem
     Start Using the inetd Subsystem

At this point any socket conection should display debug information
on the screen.


Response:

ACT:  John called back, he tried the trace that leem had suggested
      and was unable to get any entries.  Left vm for tonyj to see
      if he had a debug version of sbclient so we could see what is
      happening.

Response:

ACT:  The user has used this tape to install the product on 32h and 
      970.  It is failing on a 590.

      Have left vm with drew to develop a plan to get some debug 
      code to the user.

NEXT: wocb

Response:

Spoke with Tony Johnson, he said that when sbclient runs on the 
server it is simply testing whether or not the server is configured
and responding to client requests.  Left message for Richard, do
netstat -i and let me know if any interface has a * by it, parti-
cularly lo0 loopback.  Also do an lslpp -h bosnet.tcpip.obj and 
let me know the list of ptfs installed on TCP/IP.

Response:

Contacted customer to check status.  Customer said that he
was able to correct the problem by copying the /etc/services
and /etc/inetd.conf files from another system and rebooting.
Which seems to indicate that either inetd.conf or some
process (which is not in inittab) was holding the socket open.




Support Line: Errors trying to create a network install server with sysback/6000 ITEM: S2835L

Dated: March 1995 Category: N/A

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

Comments or suggestions?
Contact us