9 FAQ AND TROUBLESHOOTING

9.1 STARTUP AND SHUTDOWN

9.1.1 Some of the common errors encountered during start-up

1. A problem in the OLDB. In this case, check the database with utility lccdb. E.g.:

cd $VLTDATA/ENVIRONMENTS/lxxics1

lccdb -r DB

2. The OLDB backup file is missing. Check that the file exists, e.g.:

ls -l $VLTDATA/config/lxxics1.dbcfg

If it is missing, then run the following command:

icbConfigSet XXXX

3. The LCU OLDB configuration is not correct.

If the configuration is located in the LCU OLDB backup file, then check if the file really contains the correct value(s). If not, then update the configuration and use the icbConfigSet utility to update the LCU OLDB backup file.

If the configuration was updated in a dbl file, then check that the new configuration is not overridden by an entry in the LCU OLDB backup file.

4. No logs are received from the LCU. Check file $VLTDATA/ENVIRONMENTS/wxxxx/logLCU.config and restart the logManager with utility logConfig.

9.2 STANDARD DEVICES

9.2.1 How do I retrieve the status of an individual FITS keyword ?

Retrieving the status of a individual FITS keywords of a device is in general not supported by the STATUS command. Individual status values are available in the OLDB. See sections 7.4.4 and 8.13.1.4.

9.3 SPECIAL DEVICES

9.3.1 May I base a special device on modules ic0* ?

No. Special devices should be based in the template software module xxidev. Running e.g. two servers similar to ic0devServer in one LCU is not supported.

Quadralay Corporation http://www.webworks.com Voice: (512) 719-3399 Fax: (512) 719-3606 sales@webworks.com