OS-SCO-KnownIssues

Index to SCO-specific observed issues, and, if known, related workarounds

See Also:> 

OS-SCO-OpenSource-BuildIssues

OS-SCO-Linux

OS-SCO

See OS-SCO-Linux for issues related to inherent system differences. This page documents observed operational issues and corrective actions.

Boot Issues

httpd does not autostart

/usr/lib/apache/logs/httpd.pid error

• If the httpd.pid file is present but not pointing to a valid, running instance of the httpd daemon, the /etc/rc2.d/P90apache script may fail to properly control the web server (i.e. restart, start, or stop). This can result in the web server not starting at system boot, but can also impact manual use of the P90apache script to correct operational issues.
• To correct the condition, it may be sufficient to reboot the system, but, manual removal of an invalid file may be more reliable.
• Background
  • The httpd.pid often seems to be incorrect on certain servers.
  • Apache server start failure is not particularly an uncommon occurrence at customer sites.
  • The server error log may contain the message "NoNe SuCh=: is not an identifier", though it is not clear if it is related.

    The text of the error message is found in various perl binaries, and likely would not occur if mod_perl and perl_module configuration was disabled in httpd.conf.

Command Errors

dynamic linker : vim : could not open /usr/local/lib/libncurses.so.4 Message not found!!

/usr/local/bin/vim is affected on one SCO system, but other binaries are not. This error occurs if the binary is called explicitly, or, when /usr/local/bin is listed in the PATH variable ahead of other system folders. The problem also occurs for other variants of the VI editor (i.e. vi, etc.).

Though not why /usr/local/bin copies of vim are broken, this error was found when a ${HOME}/.bash_profile was created to add more folders to the run PATH.

The workaround was to push the /usr/local paths farther down in the list of paths to search for executable files.

ssh/scp : PRNG is not seeded

/etc/prngd.lock was empty and did not contain a process ID.

The workaround was to delete the empty file.

Login Issues

ssh : no matching key exchange method found

After updating MSYS2 on or about March 27, 2020, it is no longer possible to SSH a SCO VM without special configuration.

$ ssh csdi@192.168.1.61 Unable to negotiate with 192.168.1.61 port 22: no matching key exchange method found. Their offer: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

Edit ~/.ssh/config' as follows to avoid downgrading other SSH connections to more up-to-date targets:

Host 192.168.8.49 192.168.1.61 KexAlgorithms +diffie-hellman-group-exchange-sha1 KexAlgorithms +diffie-hellman-group14-sha1 KexAlgorithms +diffie-hellman-group1-sha1 Match host 66.90.221.9 exec "test %p = 22" KexAlgorithms +diffie-hellman-group-exchange-sha1 KexAlgorithms +diffie-hellman-group14-sha1 KexAlgorithms +diffie-hellman-group1-sha1