Technical article 105498

Installing OSS451A followed by OSS449A on OpenServer 5.0.2 causes problems.

OpenServer 5.0.2

Written · Last revised

Problem

After installing Support Level Supplement (SLS) OSS451A on my system, the subsequent installation of SLS OSS449A will fail to complete. The relink of UNIX will fail with errors similar to:

dynamic linker: chown: cannot open /usr/lib/libsocket.so.1 ./opt/K/SCO/tcp/2.0.0Dp/cntl/cpcs.OSS449A.tcp.200.1: 138 killed dynamic linker: chgrp: cannot open /usr/lib/libsocket.so.1 ./opt/K/SCO/tcp/2.0.0Dp/cntl/cpcs.OSS449A.tcp.200.1: 139 killed dynamic linker: chown: cannot open /usr/lib/libsocket.so.1 ./opt/K/SCO/tcp/2.0.0Dp/cntl/cpcs.OSS449A.tcp.200.1: 141 killed

Commands such as ls(C) that rely on /usr/lib/libsocket.so.1 will fail with errors:

dynamic linker: ls: cannot open /usr/lib/libsocket.so.1
Killed

A system reboot will give the following error and hang:

Warning: exit /etc/init (pid 1) died, status 0x000008b

Cause

The installation of OSS449A will set the links for
/usr/lib/libsocket.so and /usr/lib/libsocket.so.1 to point to the
directory /opt/K/SCO/Unix/5.0.0Cl instead of /opt/K/SCO/Unix/5.0.2Dp.
This is only a problem if OSS449A is installed after OSS451A, as the
latter saves copies of /etc/badtrk in both of the above mentioned
directories as part of its installation procedure. This causes the
creation of directory /opt/K/SCO/Unix/5.0.0Cl and OSS449A will then
set its links incorrectly.

This is not a problem on SCO OpenServer Release 5.0.0.

Solution

Subsequent releases of SLS OSS451 and SLS OSS449 will both independently correct this installation problem. In the meantime, the problem may be avoided by renaming the directory 5.0.0Cl before installing SLS OSS449A. The directory name can be restored after the installation is complete.

If the supplement has been installed incorrectly as described above, the system can be recovered by restoring the link to the correct location. To do this, use the following commands:

%cd /usr/lib
%rm libsocket.so
%rm libsocket.so.1
%ln -s /opt/K/SCO/Unix/5.0.2Dp/usr/lib/libsocket.so.1 libsocket.so.1
%ln -s /opt/K/SCO/Unix/5.0.2Dp/usr/lib/libsocket.so libsocket.so
%cd /etc/conf/cf.d
%./link_unix

This should complete the installation of SLS OSS449A and recover the system.

See also

TA107704, "What is the SLS OSS449F Network Maintenance Supplement?"

From the Xinuos technical article database, record 105498. Reproduced with permission. The original is at www.sco.com/ta/105498, 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.