Technical article 125188

I get the error "custom+ backend process has died", or "Unable to start the Software Manager, possibly because it is already running"

OpenServer 6.0.0OpenServer 5.0.5OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

The Software Manager (custom) reports errors and won't show the list of installed software. Some errors seen by this problem include:

"the custom+ backend process has died"

"Unable to start software manager. Possibly because it is already in use"

"Assertion failed: StrEqual (sectionSuffix, componentPtr->name ()), file "componentIO.C", line 1287"

"Error reading Component Contents Database"
"Syntax error in stanza file on line XXX"

Cause

One cause for these errors is corruption in one or more of the shared.db and/or client.db stanza files.

It has been reported that this problem has been caused by shutting the system off while the Software Manager was running.

Solution

Use the following program to create a list of stanza files on your system, then restore these files from a backup.

    -------------------cut here--------------------
# find /opt/K/ -type f -print|grep -e "shared.db$" >/tmp/filelist
# find /var/opt/K/ -type f -print|grep -e "client.db$" >>/tmp/filelist
    -------------------cut here--------------------

This program will create the file /tmp/filelist, which will contain all of the stanza files from your system. Restoring this list of files from a backup made before the problem happened should restore the Component Contents Database and fix the problem with the Software Manager.

NOTES:    If you don't have a backup, it is possible to restore this list of
          files from another OpenServer system that is running the same version
          and has the same set of software and patches installed.
NOTES:    Another possible cause for these errors could be that the packages
          in /opt/K/ do not match what is in /var/opt/K/, possibly because
          custom was interrupted in the middle of installing.  This problem
          can be found by checking the lists created above, and carefully
          removing the extra new directories.  For this type of problem it is
          often best to check the timestamps of these extra directories and be
          sure that they are from a recent installation interruption. As always
          make copies of files you remove so that if you make a mistake you can
          put them back.
NOTES:    To diagnose 'custom' further:
# touch /tmp/custom.trace.log
# CUSTOM_TRACE_LOG=1 export CUSTOM_TRACE_LOG
# custom

See also

TA113181: I get "The custom+ binary (backend) process has died." error message while trying to install SCO Sendmail (ver 8.11.0).

TA110684: The custom+ binary (backend) process has died before showing the installation source devices.

TA110567: I get the error "The custom+ binary (backend) process has died" while trying to install SLS OSS601A.

From the Xinuos technical article database, record 125188. Reproduced with permission. The original is at www.sco.com/ta/125188, which is reachable but blocked from search engines.

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.