SunScreen 3.1 Reference Manual

Error Messages From the ssadm edit Component

Error messages can arise while editing the address, rule, and service configurations (and from the corresponding GUIs).

The expression, [ARGUMENTS], used in the following error messages means that the same set of arguments passed into ssadm* is echoed back.

For example, if you type: "add address a b junk x y z" the error message is: "add address a b junk x y z: error_message".

The ssadm edit component's error messages follow.

Return code: 1

The user invoked the edit program incorrectly.

Return code: 1

The user specified an illegal policy name while invoking the editor.

Return code:

The user chose to QUIT even though there are unsaved changes.

Return code:

The user asked for their lock_status, and they currently hold the write lock.

Return code:

The user asked for their lock_status, and they currently hold the read lock.

Return code: 0

The user asked for the version currently being edited.

Return code: 251

The user tried to delete a NAT Rule using the old ssadm nat or ssadm access command.

Return code: 231

The user attempted to quit without saving unsaved changes.

Return code: 232

The user attempted to save the policy as lock, which is a reserved word.

Return code: 233

The user attempted to save the policy as version, which is a reserved word.

Return code: 234

The user attempted to save the policy as registry, which is a reserved word.

Return code: 235

The user attempted to save a versioned policy with a new name.

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: 240

The policy given to be read did not exist.

Return code: 241

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

Return code: 242

The configuration editor could not acquire a read lock. Likely the lock file is corrupt or some process is hanging. ss_lock -c policy is likely to be needed.

Return code: 243

A request to gain the write lock failed. Likely some other process currently holds the write lock.

Return code: 244

An attempt was made to save changes, but something has happened so that this process no longer holds the write lock. Perhaps someone else has issued an ss_lock -c policy and invalidated the lock.

Return code: 247

An attempt was made to modify the Address or Screen object *. This is a reserved name and cannot be modified.

Return code: 248

An attempt was made to modify the Address localhost. This is a reserved name and cannot be modified.

Return code: 249

Indicates that something happened to the lock files. ss_lock -c policy is likely needed to fix the situation.

Return code: 250

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

Return code: 251

A request was not well-formed.

Return code: 252

A request was issued for an invalid data type.

Return code: 253

A request used an invalid operation.

Return code: 255

No longer used.

Return code : nonzero : nonzero

Indicates you added an ADMIN interface to a routing machine. You probably want this to be a routing type interface.

Appears as a result of an "add Interface" request

Appears as a result of an "add Interface" request

Appears as a result of an "add Interface" request