Troubleshooting ASET Problems

This section documents the error messages that are generated by ASET.

ASET Error Messages

ASET failed: no mail program found.

Cause: ASET is directed to send the execution log to a user, but no mail program can be found.

Solution: Install a mail program.

Usage: aset [-n user[@host]] in /bin/mail or /usr/ucb/mail.

Cannot decide current and previous security levels.

Cause: ASET cannot determine what the security levels are for the current and previous invocations.

Solution: Ensure the current security level is set either through the command-line option or the ASETSECLEVEL environment variable. Also, ensure that the last line of ASETDIR/archives/asetseclevel.arch correctly reflects the previous security level. If these values are not set or are incorrect, correct them.

ASET working directory undefined.

To specify, set ASETDIR environment variable or use command line

option -d.

ASET startup unsuccessful.

Cause: The ASET working (operating) directory is not defined, or it is defined incorrectly.

Solution: Use the ASETDIR environment variable or the -d command-line option to correct it, and restart ASET.

ASET working directory $ASETDIR missing.

ASET startup unsuccessful.

Cause: The ASET working (operating) directory is not defined, or it is defined incorrectly. This problem might be because the ASETDIR variable or the -d command-line option refers to a nonexistent directory.

Solution: Ensure that the correct directory, that is, the directory that contains the ASET directory hierarchy, is referred to correctly.

Cannot expand $ASETDIR to full pathname.

Cause: ASET cannot expand the directory name that is given by the ASETDIR variable or the -d command-line option to a full path name.

Solution: Ensure that the directory name is correct, and that it refers to an existing directory to which the user has access.

aset: invalid/undefined security level.

To specify, set ASETSECLEVEL environment variable or use command

line option -l, with argument= low/med/high.

Cause: The security level is not defined, or it is defined incorrectly. Only the values low, med, or high are acceptable.

Solution: Use the ASETSECLEVEL variable or the -l command-line option to specify one of the three values.

ASET environment file asetenv not found in $ASETDIR.

ASET startup unsuccessful.

Cause: ASET cannot locate an asetenv file in its working directory.

Solution: Ensure there is an asetenv file in ASET's working directory. See asetenv(4) for the details about this file.

filename doesn't exist or is not readable.

Cause: The file that is referred to by filename doesn't exist or is not readable. This problem can occur when you are using the -u option, where you can specify a file that contains a list of users whom you want to check.

Solution: Ensure that the argument to the -u option exists and is readable.

ASET task list TASKLIST undefined.

Cause: The ASET task list, which should be defined in the asetenv file, is not defined. This message can mean that your asetenv file is bad.

Solution: Examine your asetenv file. Ensure that the task list is defined in the User Configurable section. Also check other parts of the file to ensure that the file is intact. See asetenv(4) for the content of a valid asetenv file.

ASET task list $TASKLIST missing.

ASET startup unsuccessful.

Cause: The ASET task list, which should be defined in the asetenv file, is not defined. This message can mean that your asetenv file is bad.

Solution: Examine your asetenv file. Ensure that the task list is defined in the User Configurable section. Also check other parts of the file to ensure that the file is intact. See asetenv(4) for the content of a valid asetenv file.

Schedule undefined for periodic invocation.

No tasks executed or scheduled. Check asetenv file.

Cause: ASET scheduling is requested by using the -p option, but the environment variable PERIODIC_SCHEDULE is undefined in the asetenv file.

Solution: Check the User Configurable section of the asetenv file to ensure that the variable is defined and is in proper format.

Warning! Duplicate ASET execution scheduled.

Check crontab file.

Cause: ASET is scheduled to run more than once. In other words, ASET scheduling is requested while a schedule is already in effect. This message does not necessarily indicate an error if more than one schedule is indeed desired. In this instance, the messages servers only as a warning. If you want more than one schedule, you should use the proper scheduling format with the crontab command. For more information, see the crontab(1) man page.

Solution: Verify, through the crontab command, that the correct schedule is in effect. Ensure that no unnecessary crontab entries for ASET are in place.


20. Using the Automated Security Enhancement Tool (Tasks) Running ASET How to Collect ASET Reports on a Server


	Troubleshooting ASET Problems This section documents the error messages that are generated by ASET. ASET Error Messages `ASET failed: no mail program found.` Cause: ASET is directed to send the execution log to a user, but no mail program can be found. Solution: Install a mail program. `Usage: aset [-n user[@host]] in /bin/mail or /usr/ucb/mail.` `Cannot decide current and previous security levels.` Cause: ASET cannot determine what the security levels are for the current and previous invocations. Solution: Ensure the current security level is set either through the command-line option or the `ASETSECLEVEL` environment variable. Also, ensure that the last line of `ASETDIR/archives/asetseclevel.arch` correctly reflects the previous security level. If these values are not set or are incorrect, correct them. `ASET working directory undefined.` `To specify, set ASETDIR environment variable or use command line` `option -d.` `ASET startup unsuccessful.` Cause: The ASET working (operating) directory is not defined, or it is defined incorrectly. Solution: Use the `ASETDIR` environment variable or the `-d` command-line option to correct it, and restart ASET. `ASET working directory $ASETDIR missing.` `ASET startup unsuccessful.` Cause: The ASET working (operating) directory is not defined, or it is defined incorrectly. This problem might be because the `ASETDIR` variable or the `-d` command-line option refers to a nonexistent directory. Solution: Ensure that the correct directory, that is, the directory that contains the ASET directory hierarchy, is referred to correctly. `Cannot expand $ASETDIR to full pathname.` Cause: ASET cannot expand the directory name that is given by the `ASETDIR` variable or the `-d` command-line option to a full path name. Solution: Ensure that the directory name is correct, and that it refers to an existing directory to which the user has access. `aset: invalid/undefined security level.` `To specify, set ASETSECLEVEL environment variable or use command` `line option -l, with argument= low/med/high.` Cause: The security level is not defined, or it is defined incorrectly. Only the values `low`, `med`, or `high` are acceptable. Solution: Use the `ASETSECLEVEL` variable or the `-l` command-line option to specify one of the three values. `ASET environment file asetenv not found in $ASETDIR.` `ASET startup unsuccessful.` Cause: ASET cannot locate an `asetenv` file in its working directory. Solution: Ensure there is an `asetenv` file in ASET's working directory. See `asetenv`(4) for the details about this file. `filename doesn't exist or is not readable.` Cause: The file that is referred to by filename doesn't exist or is not readable. This problem can occur when you are using the `-u` option, where you can specify a file that contains a list of users whom you want to check. Solution: Ensure that the argument to the `-u` option exists and is readable. `ASET task list TASKLIST undefined.` Cause: The ASET task list, which should be defined in the `asetenv` file, is not defined. This message can mean that your `asetenv` file is bad. Solution: Examine your `asetenv` file. Ensure that the task list is defined in the `User Configurable` section. Also check other parts of the file to ensure that the file is intact. See `asetenv`(4) for the content of a valid `asetenv` file. `ASET task list $TASKLIST missing.` `ASET startup unsuccessful.` Cause: The ASET task list, which should be defined in the `asetenv` file, is not defined. This message can mean that your `asetenv` file is bad. Solution: Examine your `asetenv` file. Ensure that the task list is defined in the `User Configurable` section. Also check other parts of the file to ensure that the file is intact. See `asetenv`(4) for the content of a valid `asetenv` file. `Schedule undefined for periodic invocation.` `No tasks executed or scheduled. Check asetenv file.` Cause: ASET scheduling is requested by using the `-p` option, but the environment variable `PERIODIC_SCHEDULE` is undefined in the `asetenv` file. Solution: Check the `User Configurable` section of the `asetenv` file to ensure that the variable is defined and is in proper format. `Warning! Duplicate ASET execution scheduled.` `Check crontab file.` Cause: ASET is scheduled to run more than once. In other words, ASET scheduling is requested while a schedule is already in effect. This message does not necessarily indicate an error if more than one schedule is indeed desired. In this instance, the messages servers only as a warning. If you want more than one schedule, you should use the proper scheduling format with the `crontab` command. For more information, see the `crontab`(1) man page. Solution: Verify, through the `crontab` command, that the correct schedule is in effect. Ensure that no unnecessary `crontab` entries for ASET are in place.