Automated install scheme fails with stty: no such

Question

Hello,
Can someone please help me out with my crafty scheme? I want to do a mass deployment
of SunMC agents using both Jumpstart and web based deployment via N1SPS.
I have gone so far as to have read the install guide for Sun MC 4 and it is already out of date!
I haved used es-makeclient to create an install client with pkg response and config files
for es-setup and es-inst.
Then I roll the above into a Solaris pkg with a postinstall script. This worked up to a
point until I got a conclusion where the es-inst commands run out of the postinstall
script were waiting for the pkgadd of the "makeclient" process to complete. Does this
make sense so far?
So, to stop the above condition where 2 pkgadds concurrent were waiting for the
first to finish (held open by the postinstall script running the second pkgadd), I
changed postinstall to just be a bourne shell exec /var/tmp/sunmc_agent/finish,
with a modified version of the finish script described in the SunMC install guide.
But my finish script fails with spurious errors and I can't seem to resolve it.
Here is the procedure and the error message will be obvious when you
see "finish script begins now"
pkgadd -d . -G sunmcagent
Processing package instance <sunmcagent> from </tmp>
sunmcagent(sparc) 1.0
rachel@snoz
Using </var/tmp> as the package base directory.
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <sunmcagent> [y,n,?]
Do you want to continue with the installation of <sunmcagent> [y,n,?] y
Using </var/tmp> as the package base directory.
## Processing package information.
## Processing system information.
3278 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <sunmcagent> [y,n,?] y
Installing sunmcagent as <sunmcagent>
## Installing part 1 of 1.
/var/tmp/sunmc_agent/disk1/image/SunOS/sparc/Addons/TNG/Common/Basic/SUNWfrcam/pkginfo
/var/tmp/sunmc_agent/disk1/image/SunOS/sparc/Addons/TNG/Common/Basic/SUNWfrcam/pkgmap
/var/tmp/sunmc_agent/disk1/image/SunOS/sparc/Addons/TNG/Common/Basic/SUNWhcam/pkginfo
/var/tmp/sunmc_agent/disk2/image/SunOS/sparc/Addons/X86ConfigReader/Solaris_9/installation.info
/var/tmp/sunmc_agent/disk2/image/SunOS/sparc/Addons/X86ConfigReader/Solaris_9/installation.properties
/var/tmp/sunmc_agent/finish
/var/tmp/sunmc_agent/response_files/install_cfg
/var/tmp/sunmc_agent/response_files/setup.cfg
/var/tmp/sunmc_agent/response_files/sunmc_install.cfg
/var/tmp/sunmc_agent/response_files/sunmc_setup.cfg
[ verifying class <none> ]
## Executing postinstall script.
sleeping for cleanup
Installation of <sunmcagent> was successful.
Installation of <sunmcagent> was successful.
server:/tmp 128# finish script begins now
This script installs Sun (TM) Sun Management Center 4.0
Installation files source directory: /var/tmp/sunmc_agent/disk1/image/SunOS/sparc
stty: : No such device or address
Enter the directory in which you want to install: [ /opt ] : /opt
Installation destination directory: /opt
Selecting : Agent
mkdir: Failed to make directory "/var/tmp/installCJaGg5/patchadd-1610629752"; No such file or directory
/usr/lib/patch/patchadd[18]: /var/tmp//installCJaGg5: not found
Reading Add-On products from image. Please wait...
This can take approximately 2 minutes to complete.
Found: Sun Enterprise 6500-3500 Servers/sun4d DR
Found: Sun Fire Entry-Level Midrange System
Found: PltAdmin SPARC Enterprise Mx000
The es-inst process runs through but the stty error and the pkgadd install dir errors
make the install failure and no SunMC packages are installed. My response files
are correct and I will post everything here, sans passwds:
This is the postinstall that calls the finish script. The postinstall runs after the
client package is installed in /var/tmp to be run by es-inst:
#!/bin/sh
# Program type      : Unix bourne shell script
# Description       : Standard finish script for installing and
#                     setting up Sun Management Center core agent
# THIS VERSION FOR SOLARIS 10 ONLY
exec sh /var/tmp/sunmc_agent/finish &
exit 0This is the finish script, without secrets:
!/bin/sh
# Program type      : Unix bourne shell script
# Description       : Standard finish script for installing and
#                     setting up Sun Management Center core agent
# THIS VERSION FOR SOLARIS 10 ONLY
LOGDIR=/var/tmp/sunmcfinish
SI_CONFIG_DIR=/var/tmp/sunmc_agent
INSTALL_RESP=${SI_CONFIG_DIR}/response_files/sunmc_install.cfg
SETUP_RESP=${SI_CONFIG_DIR}/response_files/sunmc_setup.cfg
echo "sleeping for cleanup"
sleep 15
echo "finish script begins now"
# Begin Main Program
umask 022
mkdir -p $LOGDIR
# Copy the install and setup response file to target system
cp ${INSTALL_RESP} $LOGDIR
cp ${SETUP_RESP} $LOGDIR
# run es-inst with -a -R -T and -A options
# skip the next line for Flash Archive based deployment
# Do not use the -T option if you have specified the TARGET_DIRECTORY
# tag in install.cfg
${SI_CONFIG_DIR}/disk1/sbin/es-inst -a -A ${LOGDIR}/sunmc_install.cfg
# Clean up any rc script with the same name if present
test -f /etc/rc3.d/S80SunMCJumpStart && rm -f /etc/rc3.d/S80SunMCJumpStart
rm -f /etc/init.d/SunMCJumpStart
# Place rc script in rc3.d and init.d to do setup
# Remember to access es-setup based on the target directory location
echo "Creating rc script..."
cat > /etc/rc3.d/S80SunMCJumpStart << EOF
#!/sbin/sh
rm /etc/rc3.d/S80SunMCJumpStart /etc/init.d/SunMCJumpStart
SECURITY_SEED=selfsown
SNMPV1_STRING=harhar!
export SECURITY_SEED SNMPV1_STRING
/opt/SUNWsymon/sbin/es-setup -e -A /var/tmp/sunmcfinish/sunmc_setup.cfg
EOF
cp /etc/rc3.d/S80SunMCJumpStart /etc/init.d/SunMCJumpStart
chmod 755 /etc/rc3.d/S80SunMCJumpStart /etc/init.d/SunMCJumpStart
exit 0And so as you can see, "postinstall" runs 'finish" which is the boilerplate
from the SunMC4 install guide jumpstart section. Now the crazy thing is,
if I do the first pkgadd of my makeclient tarball and then run the "finish" script
from the CLI, then the install goes 100% perfect, so I know my responses files
are ok and my scripts are ok, but perhaps it is because I have spawned a subshell
and have no tty? The pkgadd started by es-inst fails because of a dir entry,
but it should just create it's own. Is there someway to get the subshell what it
needs to run my "finish" script correctly?
rachel

Answer 1

OK,
I fixed the stty problem by using #!/bin/sh -i
to give the impression of an interactive shell.
Bu I still get:
mkdir: Failed to make directory "/var/tmp/installnZa4GW/patchadd-3145325386"; No such file or directory
/usr/lib/patch/patchadd[18]: /var/tmp//installnZa4GW: not found
When es-inst is run. There is a person on here with a similar problem, unanswered.
I wonder if they found a solution, although it was 3.6.1?
rachel