Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS


Legato stops responding after Brisque reboots and deletes system file links from “/”


Product

  Brisque™ Serve 4.0

Platform

 
  • 44P-170—Hammerhead
  • F50—Wildcat (2 and 4 CPUs)
  • 6F1— Condor (2,4, and 6 CPUs)

Operating system

 

IBM® AIX 4.3.3


Symptoms

  The Legato application stops responding after Brisque reboots, and deletes links to Brisque system files from the root (/) directory.

Cause

 

After a reboot, Legato creates a default configuration because it is unable to load the Creo configuration file located in the directory /nsr/res/. All links to system files are removed from the root (/) directory, but directories are not removed.

To verify that the default Legato configuration was created instead of the Creo configuration:

From the command line, type ls -la /.
Files such as smit.log are missing from the displayed output, for example:
root@timna1:/ 33 % ls -la / |grep lr
lrwxrwxrwx 1 root system 40 Jul 24 06:16 .xinitrc -> /scitex/version/scripts/.xinitrc.manager
lrwxrwxrwx 1 bin bin 8 Jul 24 03:55 bin -> /usr/bin
lrwxrwxrwx 1 bin bin 8 Jul 24 03:55 lib -> /usr/lib


Normally, the following links to system files are displayed:
root@timna1:/ 33 % ls -la / |grep lr
lrwxrwxrwx 1 root system 40 Jul 24 06:16 .xinitrc -> /scitex/version/scripts/.xinitrc.manager
lrwxrwxrwx 1 bin bin 8 Jul 24 03:55 bin -> /usr/bin
lrwxrwxrwx 1 bin bin 8 Jul 24 03:55 lib -> /usr/lib
lrwxrwxrwx 1 root scitex 11 Jul 25 16:02 nsr -> /backup/nsr
lrwxrwxrwx 1 bin bin 5 Jul 24 03:55 u -> /home
lrwxrwxrwx 1 root system 21 Jul 24 04:03 unix -> /usr/lib/boot/unix_mp


Solution

 

There are two possible sources from which this problem originates:

cust_main.sh script

The cust_main.sh script runs from crontab using the -| (auto logout) option. In this case, the script activates the stop.ScitexServers script, which contains the following type of commands:
su sciroot -c "rm -f $SCI_TEMP/*

Scripts that run from crontab do not have the correct environmental settings. Therefore su sciroot -c "rm -f $SCI_TEMP/* may receive a null value. Thus, when the stop.ScitexServers script is activated by cust_maint.sh, it may delete every file/link under /

Workaround

Replace or reinstall all your existing cust_maint.sh script versions with the cust_maint.tar.Z script.

UPS shutdown script

The second source is the UPS shutdown script. This script also does not have the correct environmental settings.

Workaround

  1. Add lines in the UPS shutdown script using vi /usr/ls3/ls3.shutdown, as shown:

    #!/bin/sh
    :
    # Modified by William Jungheit Oct 98.
    # Scitex Ripro Server Archiver product.
    #======================================
    # LanSafe III shutdown script.
    # This script is executed to shutdown the system.
    # Run this script by hand to verify that the system will shutdown correctly.
    # When executed by the ls3 (LanSafe Power Server daemon)
    # no arguments are passed to this script.

    # Set Scitex Environment
    . /scitex/version/scripts/set.ScitexEnv
    umask 000

  2. In case the links are deleted, recreate the links by running the following commands:
    ln -s /usr/lib/boot/unix_mp /unix
    ln -s /home /u
    ln -s /backup/nsr /nrs

 


Technical contact(s)
 

Lev Weissman

Submitted by
 

Lev Weissman

Date submitted
 

02 Oct 2002


    Copyright © 2005 Creo Inc. All rights reserved. Confidential. Back to top.