Tips and Troubleshooting

Changes made by HP-UX Bastille might cause other software to stop working.

To troubleshoot, enter:

The user asked for the X interface, but the $DISPLAY environment variable was not set. Set the environment variable to the desired display to correct the problem.

The user attempted to revert changes that HP-UX Bastille made using the -r option, but there were no changes to revert.

HP-UX Bastille must be run as the root user since the changes it makes affect system files.

Problems opening, copying, or reading files

Error messages citing problems performing these operations are usually related to NFS file systems that do not trust the root user on the local machine. Consult the options section in the fstab manpage for details.

Errors related to individual configuration files

Errors complaining about individual configuration files indicate that a system has been too heavily modified for HP-UX Bastille to make effective changes, or the files, locations, or permissions of the HP-UX Bastille installation directories have been changed.

If HP Secure Shell locks you out of your system immediately when passwords expire, you may need a PAM patch: PHCO_24839 (HP-UX 11.11) available at the HP IT Resource Center:

https://www2.itrc.hp.com/service/patch/mainPage.do

HP-UX Bastille configures a firewall using IPFilter

The most common conflicts are with firewalls. When a network service is not working that HP-UX Bastille did not turn off explicitly, you should make sure the firewall rules will pass the ports you need.

See ipfstat(8) and ipmon(8) for more information.