OBSOLETE Patch-ID# 101391-04 Keywords: SNA p2p appc strip startp2p state abend zombie defunct accept inet core Synopsis: OBSOLETED by 102146 Date: Jul/06/94 Solaris Release: 2.1, 2.2, 2.3 SunOS Release: 5.1, 5.2, 5.3 Unbundled Product: Sunlink SNA P2P Unbundled Release: 8.0 Relevant Architectures: sparc BugId's fixed with this patch: 1140624 1146414 1152835 1154016 1154477 1154478 1156769 1158264 1160741 1162043 1162844 1163002 1163152 1164465 1165133 1167805 1168444 1169799 1169800 Changes incorporated in this version: 1140624 1146414 1154477 1154478 1156769 1160741 1163002 1164465 1165133 1167805 1168444 1169799 1169800 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: 102146 on Jan/03/95 Files included with this patch: SUNWconn/snap2p/p2p_etc/bin/appc SUNWconn/snap2p/p2p_etc/bin/startp2p SUNWconn/snap2p/p2p_lib/lib/libcpic.a SUNWconn/snap2p/p2p_lib/lib/libcpic_db.a SUNWconn/snap2p/p2p_etc/bin/APING/aping SUNWconn/snap2p/p2p_etc/bin/APING/apingd SUNWconn/snap2p/p2p_etc/bin/AREXEC/arexec SUNWconn/snap2p/p2p_etc/bin/AREXEC/arexecd SUNWconn/snap2p/p2p_etc/bin/ATELL/atell SUNWconn/snap2p/p2p_etc/bin/ATELL/atelld SUNWconn/snap2p/p2p_etc/src/tp_parent.c SUNWconn/snap2p/p2p_lib/include/cpic.h SUNWconn/snap2p/p2p_lib/include/cpic_proto.h /kernel/drv/sdlc Problem Description: (Rev 01) SUNWsnp2p package File tp_parent.c was revised to close the gateway file descriptor after the fork/exec of the child TP process. Changed snap2p/arexec/Makefile to strip executable modules. Changed snap2p/atell/Makefile to strip executable modules. Changed snap2p/snalu62_tp/startp2p.sh script to increase sleep time from 5 to 8 seconds. SUNWrup2p package Changed snap2p/aping/Makefile to strip executable modules. Corrected dlc_name in L_GETTUNE trace message. Changed appc version to 8.0.1 for log file. (Rev 02) 1152835: TP gets STATE_CHECK_BAD_STATE return code When generating an "allocate", the security fields are copied to the "rcb" only if present. CPI-C will check for UNSUCESSFUL returned from verb appc_test(), and will not generate an error condition. 1154016: TP gets DEALLOCATE_ABEND return code In cpic_lib.c, cmrcv() was calling [mc_]receive_immediate() when it should have been calling [mc_]receive_immediate_proc(). 1158264: TP forked by p2p becomes a zombie (defunct) SNAp2p creates a transaction program (TP) as a child process when it receives an incoming allocate. When the TP terminates, SunOS turns the child process into a zombie until the parent process (appc) issues a waitpid() system call to retrieve the child's termination status. But snap2p does not really care about the termination status. So the fix was to issue a signal() system call to set the disposition of the SIGCHLD signal to be ignored. This tells SunOS to not create the zombies. 1162043: appc does not recognize TP name with trailing blanks in attach When appc tries to match the TP name in an Attach, it does not recognize the trailing blanks. In the IBM world, it's a common practice to pad an EBCDIC string with blanks to 8 characters. 1162844: appc sends negative response when tp_accept issued appc uses waitpid() to check if the child process it just forked is up and running. Since there are multiple reasons waitpid() could return a non-zero value, appc should check the status of the child process, and should only send a negative response to the host if the status indicates the child has died. (Rev 03) 1163152: TP gets INET_READ_FAIL return code on allocate An incorrect length message was being sent from the gateway to the appc library routines when an allocate with PIP data failed. This was causing an INET_READ_FAIL return code. 1164465: appc crashes on tp_accept with core file If the link is down when tp_accept() is issued, the scb has been freed. Added a check to see if scb exists on tp_accept. (Rev 04) 1140624: snap2p bind problem with unique session id 1146414: timing problems with XID and SABME with AS/400 1154477: syntax errors in include file cpic_proto.h; missing semicolons 1154478: missing end of comment causes annoying warning message at compile time 1156769: sdlc link was disconnected after it was up for several hours 1160741: appc rejects deallocate when no data sent on session pc_biu2ru_type() was rejecting any DFC requests with oaf = 0. Apparently in p2p v7, a check was added by JDA for bugid 1077079 to reject any DFC requests or responses with oaf = 0 because it was assumed that this meant it was an sscp-lu session. In 8.0, it was changed to reject only requests by an unknown person (possibly Wei-Nan Kao). However, apparently the oaf can be 0 on an independent LU session. In sid_init() in sid.c, the next_sid field is initialized to zero, except for local LU #1. The comment says "only addr 0x01 will start from 1". 1163002: system panic caused by sdlc Set sd_timeouton flag when resetting npr timer in sdlc_input(). Check sl_timeouton flag before calling timeout() in start_pause_idle_timer() and start_nprtimer(). Reset sl_timeouton in sdlc_untimeout(). Reset sd_timeouton in sdlc_npruntimeout(). 1164465: appc core dump If link is down when tp_accept is issued, scb has been freed. Added a check to see if scb exists on tp_accept. 1165133: fail to start daemon on both sdlc/zsh & sdlc/hsi during snap2p testing on OS2.4 1167805: appc 8.0 coredumps if CICS application initiates lu6.2 data xfer followed byh a reset 1168444: delete() api function also deletes mode name, pu name and lu local address If user specifies delete_tp option on delete() verb, then after processing the option, return. 1169799: appc fails to start after installing patch 101391-03 1169800: CPI-C returns unexpected error code on deallocate SUNWsnp2p package Changed snap2p/p2p_lib/cpic_lib.c: CM_PREP_TO_RECEIVE_SYNC_LEVEL, CM_DEALLOCATE_SYNC_LEVEL will go to CM_RECEIVE_STATE. The next cpic call will not get CPIC_IMPOSSIBLE return code. Call mc_receive_immediate_proc() instead of mc_receieve_immediate() in CMRCV(). SUNWrup2p package Changed snap2p/snalu62_server/lns.c: When no lu defined, snap2p will restart link after link is down. Using local_lu_address and scb address as a unique pcid in bind. Changed snap2p/snalu62_server/pc.c: Accept unbind when pu is not active, allocate will not wait forever. Changed snap2p/snalu62_server/ps_conv.c: After receives negative response, only send CD if we are in send state. Changed snap2p/snalu62_server/ps_mc.c: INET_READ_FAIL from mc_send_data. Changed snap2p/snalu62_server/cnos.c: Problem in CNOS negotiation. SUNWsdlc package Changed sys/netmsdlc/sdlc_in.c: Start poll timer only after link is up. Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- After installation of this patch, all APPC application programs based upon the tp_parent.c source module should be updated with the new module, compiled and linked. All applications using CPI-C must be re-linked with the new CPI-C library. See also the following patches: 101407: Only if using Solaris 2.3 and SDLC over ZSH serial ports. 101410: Only if using Solaris 2.3 - snacommd patch. 101263: Only if using Solaris 2.1 or 2.2 and LLC2. The SUNWllc2a patches should be installed from this X.25 Jumbo patch. 101272: Only if using Solaris 2.3 and LLC2. The SUNWllc2a patches should be installed from this X.25 Jumbo patch. 101357: Only if using TRI/S version 3.0. Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing: //installpatch / where is the directory containing the patch and is the patch number. must be a full path name. Example: # /tmp/123456-01/installpatch /tmp/123456-01 3. If any errors are reported, see "Patch Installation Errors" in the Command Descriptions section below. Rebooting the system or restarting the application after a successful patch installation is usually necessary to utilize patch. NOTE: On client server machines the patch package is NOT applied to existing clients or to the client root template space. Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH METHOD ON THE CLIENT. See the next section for instructions for installing a patch on a client. Instructions for installing a patch on a diskless or dataless client -------------------------------------------------------------------- 1. Before applying the patch, the following command must be executed on the server to give the client read-only, root access to the exported /usr file system so that the client can execute the pkgadd command: share -F nfs -o ro,anon=0 /export/exec//usr The command: share -F nfs -o ro,root= \ /export/exec//usr accomplishes the same goal, but only gives root access to the client specified in the command. 2. Login to the client system and become super-user. 3. Continue with step 2 in the "Instructions to install patch using installpatch" section above. Instructions for backing out patch using "backoutpatch" ------------------------------------------------------- 1. Become super-user. 2. Change directory to /var/sadm/patch: cd /var/sadm/patch 3. Backout patch by typing: /backoutpatch where is the patch number. Example: # 123456-01/backoutpatch 123456-01 4. If any errors are reported, see "Patch Backout Errors" in the Command Descriptions section below. Instructions for identifying patches installed on system: ---------------------------------------------------------- Patch packets that have been installed can be identified by using the showrev command with the "-p" option: showrev -p Also note that installpatch has a similar "-p" option which will also just identify patches already installed. Command Descriptions -------------------- NAME installpatch - apply patch package to Solaris 2.x system backoutpatch - remove patch package, restore previously saved files SYNOPSIS installpatch [-udpV] [-S ] backoutpatch [-fV] [-S ] DESCRIPTION These installation and backout utilities apply only to Solaris 2.x associated patches. They do not apply to Solaris 1.x associated patches. These utilities are currently only provided with each patch package and are not included with the standard Solaris 2.x release software. OPTIONS installpatch: -u unconditional install, turns off file validation. Allows the patch to be applied even if some of the files to be patched have been modified since original installation. -d Don't back up the files to be patched. This means that the patch can't be backed out. -p Print a list of the patches currently applied -V Print script version number -S Specify an alternate service (e.g. Solaris_2.3) for patch package processing references. backoutpatch: -f force the backout regardless of whether the patch was superseded -V print version number only -S Specify an alternate service (e.g. Solaris_2.3) for patch package processing references. DIAGNOSTICS Patch Installation Errors: -------------------------- Error message: Patch has already been applied. Explanation and recommended action: This patch has already been applied to the system. If the patch has to be reapplied for some reason, backout the patch and then reapply it. Error message: This patch is obsoleted by patch which has already been applied to this system. Patch installation is aborted. Explanation and recommended action: Occasionally, a patch is replaced by a new patch which incorporates the bug fixes in the old patch and supplies additional fixes also. At this time, the earlier patch is no longer made available to users. The second patch is said to "obsolete" the first patch. However, it is possible that some users may still have the earlier patch and try to apply it to a system on which the later patch is already applied. If the obsoleted patch were allowed to be applied, the additional fixes supplied by the later patch would no longer be available, and the system would be left in an inconsistent state. This error message indicates that the user attempted to install an obsoleted patch. There is no need to apply this patch because the later patch has already supplied the fix. Error Message: None of the packages to patch are installed on this system. Explanation and recommended action: The original packages for this patch have not been installed and therefore the patch cannot be applied. The original packages need to be installed before applying the patch. Error message: This patch is not applicable to client systems. Explanation and recommended action: The patch is only applicable to servers and standalone machines. Attempting to apply this patch to a client system will have no effect on the system. Error message: The /usr/sbin/pkgadd command is not executable. Explanation and recommended action: The /usr/sbin/pkgadd command cannot be executed. The most likely cause of this is that installpatch is being run on a diskless or dataless client and the /usr file system was not exported with root access to the client. See the section above on "Instructions for installing a patch on a diskless or dataless client". Error message: packages are not proper patch packages. Explanation and recommended action: The patch directory supplied as an argument to installpatch did not contain the expected package format. Verify that the argument supplied to installpatch is correct. Error message: The following validation error was found: Explanation and recommended action: Before applying the patch, the patch application script verifies that the current versions of the files to be patched have the expected fcs checksums and attributes. If a file to be patched has been modified by the user, the user is notified of this fact. The user then has the opportunity to save the file and make a similar change to the patched version. For example, if the user has modified /etc/inet/inetd.conf and /etc/inet/inetd.conf is to be replaced by the patch, the user can save the locally modified /etc/inet/inetd.conf file and make the same modification to the new file after the patch is applied. After the user has noted all validation errors and taken the appropriate action for each one, the user should re-run installpatch using the "-u" (for "unconditional") option. This time, the patch installation will ignore validation errors and install the patch anyway. Error message: Insufficient space in /var/sadm/patch to save old files. Explanation and recommended action: There is insufficient space in the /var/sadm/patch directory to save old files. The user has two options for handling this problem: (1) generate additional disk space by deleting unneeded files, or (2) override the saving of the old files by using the "-d" (do not save) option when running installpatch. However if the user elects not to save the old versions of the files to be patched, backoutpatch CANNOT be used. One way to regain space on a system is to remove the save area for previously applied patches. Once the user has decided that it is unlikely that a patch will be backed out, the user can remove the files that were saved by installpatch. The following commands should be executed to remove the saved files for patch xxxxxx-yy: cd /var/sadm/patch/xxxxxx-yy rm -r save/* rm .oldfilessaved After these commands have been executed, patch xxxxxx-yy can no longer be backed out. Error message: Save of old files failed. Explanation and recommended action: Before applying the patch, the patch installation script uses cpio to save the old versions of the files to be patched. This error message means that the cpio failed. The output of the cpio would have been preceded this message. The user should take the appropriate action to correct the cpio failure. A common reason for failure will be insufficient disk space to save the old versions of the files. The user has two options for handling insufficient disk space: (1) generate additional disk space by deleting unneeded files, or (2) override the saving of the old files by using the "-d" option when running installpatch. However if the user elects not to save the old versions of the files to be patched, the patch CANNOT be backed out. Error message: Pkgadd of package failed with error code . See /tmp/log. for reason for failure. Explanation and recommended action: The installation of one of patch packages failed. Any previously installed packages in the patch should have been removed. See the log file for the reason for failure. Correct the problem and re-apply the patch. Patch Installation Messages: --------------------------- Note: the messages listed below are not necessarily considered errors as indicated in the explanations given. These messages are, however, recorded in the patch installation log for diagnostic reference. Message: Package not patched: PKG=SUNxxxx Original package not installed Explanation: One of the components of the patch would have patched a package that is not installed on your system. This is not necessarily an error. A Patch may fix a related bug for several packages. Example: suppose a patch fixes a bug in both the online-backup and fddi packages. If you had online-backup installed but didn't have fddi installed, you would get the message Package not patched: PKG=SUNWbf Original package not installed This message only indicates an error if you thought the package was installed on your system. If this is the case, take the necessary action to install the package, backout the patch (if it installed other packages) and re-install the patch. Message: Package not patched: PKG=SUNxxx ARCH=xxxxxxx VERSION=xxxxxxx Architecture mismatch Explanation: One of the components of the patch would have patched a package for an architecture different from your system. This is not necessarily an error. Any patch to one of the architecture specific packages may contain one element for each of the possible architectures. For example, Assume you are running on a sun4m. If you were to install a patch to package SUNWcar, you would see the following (or similar) messages: Package not patched: PKG=SUNWcar ARCH=sparc.sun4c VERSION=11.5.0,REV=2.0.18 Architecture mismatch Package not patched: PKG=SUNWcar ARCH=sparc.sun4d VERSION=11.5.0,REV=2.0.18 Architecture mismatch Package not patched: PKG=SUNWcar ARCH=sparc.sun4e VERSION=11.5.0,REV=2.0.18 Architecture mismatch Package not patched: PKG=SUNWcar ARCH=sparc.sun4 VERSION=11.5.0,REV=2.0.18 Architecture mismatch The only time these messages indicate an error condition is if installpatch does not correctly recognize your architecture. Message: Package not patched: PKG=SUNxxxx ARCH=xxxx VERSION=xxxxxxx Version mismatch Explanation: The version of software to which the patch is applied is not installed on your system. For example, if you were running Solaris 5.3, and you tried to install a patch against Solaris 5.2, you would see the following (or similar) message: Package not patched: PKG=SUNWcsu ARCH=sparc VERSION=10.0.2 Version mismatch This message does not necessarily indicate an error. If the version mismatch was for a package you needed patched, either get the correct patch version or install the correct package version. Then backout the patch (if necessary) and re-apply. Patch Backout Errors: --------------------- Error message: Patch has not been successfully applied to this system. Explanation and recommended action: The user has attempted to back out a patch that was never applied to this system. It is possible that the patch was applied, but that the patch directory /var/sadm/patch/ was deleted somehow. If this is the case, the patch cannot be backed out. The user may have to restore the original files from the initial installation CD. Error message: This patch was obsoleted by patch $1. Patches must be backed out in the order in which they were installed. Patch backout aborted. Explanation and recommended action: The obsoleted contents of an older patch rev that apparently still exists under /var/sadm/patch should never be restored out of sequence. This could undermine the integrity of the more current patch rev installed and the restoration of the files it has saved. Error message: Patch was installed without backing up the original files. It cannot be backed out. Explanation and recommended action: Either the -d option of installpatch was set when the patch was applied, or the save area of the patch was deleted to regain space. As a result, the original files are not saved and backoutpatch cannot be used. The original files can only be recovered from the original installation CD. Error message: pkgrm of package failed return code . See /var/sadm/patch//log for reason for failure. Explanation and recommended action: The removal of one of patch packages failed. See the log file for the reason for failure. Correct the problem and run the backout script again. Error message: Restore of old files failed. Explanation and recommended action: The backout script uses the cpio command to restore the previous versions of the files that were patched. The output of the cpio command should have preceded this message. The user should take the appropriate action to correct the cpio failure. KNOWN PROBLEMS: On client server machines the patch package is NOT applied to existing clients or to the client root template space. Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH METHOD ON THE CLIENT. See instructions above for applying patches to a client. A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk) could affect the reliability of installpatch or backoutpatch which uses package utilities to install and backout the patch package. It is recommended that any patch that fixes package utility problems be reviewed and, if necessary, applied before other patches are applied. Such existing patches are: 100901 Solaris 2.1 101122 Solaris 2.2 101331 Solaris 2.3 SEE ALSO pkgadd, pkgchk, pkgrm, pkginfo, showrev