SunScreen 3.2 Administrator's Overview

Error Messages From ssadm activate

Return code : nonzero

You provided an invalid output directory name with ssadm activate.

Return code: 236

The policy being compiled and activated refers to more than 31 distinct time objects.

Return code:

An entry in the registry (on disk) has more than one definition. All definitions after the first are lost upon the next save.

Return code: 239

The -S passed to ssadm activate is a nonexistent Screen object.

Return code: 240

The policy to be read did not exist.

Return code: 241

The policy or registry file on disk is corrupt and cannot be read. Be sure you have a backup or a recent version saved.

Return code: 245

No longer used.

Return code: 250

A reference is made to a named object in the global registry that does not exist in the registry.

Return code : nonzero

Return code : nonzero

Return code : nonzero

Return code : nonzero

Return code : nonzero

The Screen object must define the SMTP Address if the SMTP proxy is to be used.

Return code : nonzero

The indicated service is needed by the system, but the definition has either been deleted or renamed in the global registry.

Return code : nonzero

The Screen object is not fully defined. Remote administration is indicated but the Screen is lacking a Certificate.

Return code: nonzero

An Ethernet-based Rule is specified (that is, a service that includes the "ether" state engine) and it also indicates SKIP is to be used.

Return code: nonzero

Only 16 of a given type of interface are supported.

Return code: nonzero

HA is indicated but the services "HA administration" and "HA heartbeat" have been either removed or renamed.

Return code: nonzero

The Screen objects participating in the current HA cluster lack HA_IP addresses.

Return code: nonzero

The HA IP address specified is not part of the HA interface.

Return code: nonzero

A service has contradictory information, such as the same port but different state engines, or different parameters.

Return code: nonzero

Two (or more) interfaces' addresses intersect.

Return code: nonzero

The reverse rule swaps the certificates, and groups are not supported in the encrypting case.

Return code: nonzero

The reverse rule swaps the certificates, and groups are not supported in the encrypting case.

Return code: nonzero

The service is needed internally but has been either renamed or deleted.

Return code: nonzero

The service is needed internally but has been either renamed or deleted.

Return code: nonzero

The service is needed internally but has been either renamed or deleted.

Return code: nonzero

The service is needed internally but has been either renamed or deleted.

Return code: nonzero

The service is needed internally but has been either renamed or deleted.

Return code: nonzero

The service is needed internally but has been either renamed or deleted.

Return code: nonzero

The service is needed internally but has been either renamed or deleted.

Return code: nonzero

Return code: nonzero

Return code: nonzero

Return code: nonzero

Return code: nonzero

Return code: nonzero

HA is indicated, but no primary Screen is specified.

Return code: nonzero

One of the following is missing given that HA_Secondary is indicated: certificate, key, data, mac, or compression algorithm.

Return code: nonzero

Return code: nonzero

Return code: nonzero

The data compiler could not write the output file owing to a failed fseek.

A certificate name1 that is not local to this Screen is used in at least two SKIP_VERSION_1 rules, but the local certificate is not the same. SunScreen supports only using a one local certificate for any given remote certificate in SKIP_VERSION_1 compatibility mode. You must either use skip_version_2 or change one of name2 and name3 to the other.

There are more than 65535 pairs of certificates for either manual keying or support SKIP_V1 nodes. There is a limit of 65535.

There are more than 65535 pairs of certificates for either Manual Keying or support SKIP_V1 nodes. There is a limit of 65535.

Return code: 1

Return code: 0

A problem determining how to implement the rule occurred and is being discarded.

TYPE is address, action, service, state engine. This means that the name is defined multiple times. One of the definitions must be removed. Using the ssadm* command removes the first such definition. To remove the second, and keep the first intact, you must use a text editor on the file on the Screen.

Indicates an unresolved reference, where name2 refers to name1 but name1 is not defined. You need to define name1 or remove the reference by modifying name2.

A circular reference in an address list definition, such that list A includes list B as a member and list B includes list A as a member. You must break the cycle for the compilation to be successful.

A circular reference in a service list definition, such that list A includes list B as a member and list B includes list A as a member. You must break the cycle for the compilation to be successful.

The service is internally inconsistent. Either the service defines two state engines in the same class and subclass for the same port, or the same port and the same state engine are used twice but with different parameters. You must redefine this service for the compilation to be successful.

You are referring to an object (address, service) that has not yet been defined.

You have entered a domain name that has illegal characters, such as /. Use the default domain name "default."

You have entered a nonexistent domain name. Use the default domain name "default.

You have requested an operation that is not recognized.

You have entered an unsupported character.

Too many concurrent processes are running.

Too many concurrent processes are running.

You entered something incorrectly. Refer to the relevant man page to verify you have the correct command syntax.

You requested an operation on an unknown data type.

The first certificate specified is supposed to be the Administration Station's certificate. If the certificate is local to the Screen, then it cannot be the Administration Station's certificate.

The first certificate could not be found in the Certificate registry, as maintained by ssadm certificate. Be sure the entry is entered correctly.

The second certificate must belong to the Screen. Try again and verify that the second certificate is the Screen's certificate.

The second certificate could not be found in the Certificate registry, as maintained by ssadm certificate. Be sure the entry is entered correctly.

You attempted to modify *, which is not user-editable.

You attempted to modify localhost, which is not user-editable.

The user-indicated service is missing.

A SKIP-based rule must include one local and one nonlocal certificate. If both are local, or both are nonlocal, then the rule is invalid and will be ignored. If you believe the rule is necessary for this Screen, verify that one of the certificates is local and one is nonlocal, and reactivate.

You specified proxy definition cannot be found and a proxy rule was specified. The rule necessary to support the proxy cannot be generated. Be sure the appropriate proxy server is defined.

The configuration does not exist.

The NAT entry is invalid if its public and private addresses intersect with each other or any other address in the NAT table. Be sure that no two NAT entries intersect.

The service "HA Service" could not be found.

The specified service is not well defined. For example, it may specify the same port for multiple state engines that conflict, like UDP and UDP-datagram.

le0 is the name of the nonexistent interface. This happens if the global common registry being activated contains an interface that the machine that is doing the compile and activate does not have.

You added an interface and it could not be verified on the Screen.

The syntax entered was incorrect. See the man page for correct syntax.

The syntax entered was incorrect. See the man page for correct syntax.

The syntax entered was incorrect. See the man page for correct syntax.

You entered a range where the end value was less than the start value.

You specified service is not well-defined. For example, it may specify the same port for conflicting state engines, such as UDP and UDP-datagram.