Technical article 110335

After unloading OSS601A, shell commands fail on my 5.0.2 system with "Killed".

OpenServer 5.0.2

Written · Last revised

Problem

I have both loaded and applied Support Level Supplement (SLS)
OSS601A, the Year 2000 Supplement for OpenServer 5.0.2 and 5.0.4,
on my OpenServer 5.0.2 system.  I now want to roll back OSS601A,
but I unload it before doing so.  After rollback, the system
seems severely crippled.  Some symptoms of this include:

- Not being able to run commands; attempting to execute commands such as ls(C), mv(C), cp(C), and so on, immediately results in the message "Killed" from the shell instead.

- The system panics upon boot, shortly after hardware
  initialization, with the message "cannot exec init (PID 1)
  status 9".  (See ta105032 for more information.)

Also, in the event that I have already unloaded the patch, but not attempted rollback yet, how can I safely roll back SLS OSS601A without crippling the system?

Cause

There is a problem with unloading SLS OSS601A before rolling it
back.  This causes the version of the shared standard C library
(/usr/lib/libc.so.1), which was present on the system before OSS601A
was installed, to be irretrievably lost.  As /usr/lib/libc.so.1
is crucial and necessary for running basic shell and system commands,
the above symptoms result when the rollback is carried out, and
the original 5.0.2 version of libc.so.1 fails to be restored.
The above problems may be avoided by rolling back the patch before
unloading it.  The solutions below assume that you have already
unloaded the patch, making the system vulnerable to these problems.
NOTE:     "Loading" a patch makes it available for installation over a network.
          "Applying" a patch installs it and makes it take effect on the
          local system.  (See the ScoHelp documentation for further
          information on "Loading" versus "Applying" patches.)  Loading a
          patch is not necessary _unless_ you want to install it from the
          local server onto another OpenServer 5 machine on your local area
          network.

Solution

The appropriate solution depends upon whether you have attempted rollback of SLS OSS601A.

---------------------------------------------------------------

If you have already attempted rollback, and have run into the crippling symptoms above, there are two possible solutions:

---------------------------------------------------------------
1. Restore a saved copy of /usr/lib/libc.so.1 while the system
is still up.  You will need the statically linked versions
of cp(C) and ln(C) in order to do this, as well as a copy
of libc.so.1 for OpenServer 5.0.2.  All of these essential
items are supplied by the Technical Library Supplement,
TLS704.

In order to perform the necessary steps, consult ta110334, "How to recover from a lost or corrupted /usr/lib/libc.so.1 on OpenServer 5", and follow the procedure under "What to do if the system has _not_ been shut down yet".

2. If you do not have TLS704 already installed (or the equivalent
necessary items), you can restore libc.so.1 by rebooting from a
set of emergency boot/root floppies or the installation media.
In order to perform the necessary steps, consult ta110334,
"How to recover from a lost or corrupted /usr/lib/libc.so.1
on OpenServer 5", and follow the procedure under "What to do if
the system has already been shut down".  After completing this
procedure, download and install TLS704 to ease recovery, should
a similar situation ever happen again.

If you do not have a set of emergency floppies, follow the procedure under "What to do if none of the proactive steps outlined above have been taken" in ta110034 instead.

-------------------------------------------------------------

If you have unloaded OSS601A but have not attempted rollback:

-------------------------------------------------------------

A. Download and install TLS704 if you have not done so already. Make a note of where the saved copies of libc.so.1 are kept for both the original 5.0.2 installation and for the SLS OSS601A environment.

B. Create the following directory:
mkdir -p /opt/K/SCO/Unix/oss601a.Unix502/patch_backup/usr/lib

C. Copy the original 5.0.2 version of libc.so.1 to this directory:

cd /opt/K/SCO/Unix/oss601a.Unix502/patch_backup/usr/lib
cp <5.0.2 libc save dir>/libc.so.1 .

where <5.0.2 libc save dir> is the directory where the 5.0.2 version of libc.so.1 (from TLS704) has been saved.

D. Start the Software Manager and choose to roll back the "SCO UNIX System V Operating System" component of OSS601A. You may encounter an error such as:

Cannot access /opt/K/SCO/Unix/oss601a.Unix502/patch_backup/.softmgmt/RTS.fl
This error can be safely ignored.
See the cover letter instructions for rollback of SLS OSS601A for
other details.  Rollback of other OSS601A components should
proceed without error.

See also

ta110077, "What is addressed by SLS OSS601A, the Year 2000 Supplement for SCO OpenServer 5.0.2 and 5.0.4?"

ta110091, "Special notes and recommendations before installing OSS601A, the Year 2000 Supplement for SCO OpenServer 5.0.2 and 5.0.4."

ta110334, "How to recover from a lost or corrupted /usr/lib/libc.so.1 on OpenServer 5."

ta105032, "My system panics with "PANIC: exit cannot exec /etc/init (PID 1) status 9."

ta110353, "TLS704 - Statically linked utilities and versions of libc.so.1 for OpenServer 5."

From the Xinuos technical article database, record 110335. Reproduced with permission. The original is at www.sco.com/ta/110335, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.