F

Errors From the Authentication Manager

This appendix lists the errors you can receive from the Authentication Manager and their meaning.

This appendix covers the following Authentication Manager topics:

Message Format

The general format of the log messages is:

timestamp thread_name message_class message
For example:
1999.04.15 21:46:33.909 PDT Client6 NOTICE: SESSION_OK user.924231680-8477
In this example, a session was successfully initialized for the authentication token "user.924231680-8477".

Message components are defined as follows:

`1999.04.15 21:46:33.909 PDT Client6 NOTICE: SESSION_OK user.924231680-8477`

timestamp is of the form:

year.month.day hours:minutes:seconds.milliseconds timezone
thread_name

There are several different types of threads. The most common is the thread that handles appliance authentication, access control and session monitoring. These threads are named "Client" plus number. The Client# thread names are reused when a connection terminates. Other threads are:
- SessionManager#--Communicate with utsessiond on behalf of a Client# thread.
- AdminJobQ--Used in the implementation to wrap a library that would not otherwise be thread safe.
- CallBack#--Communicate with applications such as utload.
- Control--Listens for connections from utsessiond as well as the initial communications with applications such as utload.

Note - Messages with the same thread name are related. The exception to this is when a Client# thread disconnects an appliance and then purges the connection information from memory. After a Client# DESTROY message, the next use of that Client# thread name will have no relation to previous uses of the thread name (in other words the thread names are reused).

message_class
- CLIENT_ERROR--Indicates unexpected behavior from an appliance. These messages can be generated during normal operation if an appliance is rebooted.
- CONFIG_ERROR--Indicates a system configuration error. The Authentication Manager generally exits after one of these errors is detected.
- NOTICE--Logs normal events.
- UNEXPECTED--Logs events or conditions that were not anticipated for normal operation but are generally not fatal. Some of these errors should be brought to the attention of the Sun Ray product development team.
- DEBUG--Beneficial to developers and only occur if they are explicitly enabled. Debug messages can reveal session IDs, which must be kept secret to ensure proper security.

Error Messages

TABLE F-1 Possible Errors
Error class
Message
Description

`CLIENT_ERROR`

`...Exception ... : cannot send keepAliveInf`

Error encountered while attempting to send a keep alive message to an appliance.

`...keepAlive timeout`

An appliance has failed to respond within the allotted time. The session is being disconnected.

`duplicate key:`

Appliance does not properly implement the authentication protocol.

`invalid key:`

Appliance does not properly implement the authentication protocol.

`CONFIG_ERROR`

`attempt to instantiate CallBack 2nd time.`

Program error.

`AuthModule.load`

Problem encountered while loading configuration module.

`Cannot find module`

Program or installation error.

`Cannot get AdminImpl methods:`

Installation error.

`Cannot open call back socket on port ...`

Runtime error. Is `cbport` busy?

`Cannot read properties file: ...`

Installation or configuration error.

`cannot read properties file: ...`

Installation or configuration error, check file.

`Cannot read session types`

Check file, usually
`/etc/opt/SUNWut/sessionTypes.props`

`during status:`

Program error or Java VM error.

`Error while reading policy file ...`

Installation or configuration error.

`Invalid configuration. Exiting`

Check value of `auth.props:policy` and the contents of the file indicated by the policy property.

`Invalid option`

Program error in the
`/opt/SUNWut/lib/utauthd` script`.`

`CONFIG_ERROR`

`No policy specified`

A policy must be specified using the `utpolicy` command. Check the "policy" keyword in the
`/etc/opt/SUNWut/auth.props` file.

`Policy file does not exist: ...`

Installation or configuration error.

`refreshProperties: file non-existent: ...`

Installation or configuration error, check file name.

`refreshProperties: no filename`

Configuration error, check the
`/etc/opt/SUNWut/auth.props` file.

`SessionManager.initiateCallback: ... claims to be already connected`

Possible configuration error.

`sessionTypesFile not specified`

The required parameter "sessionTypesFile" is missing from `/etc/opt/SUNWut/auth.props` file.

`UNCONFIGUED MODULE`

An authentication module is not configured and will not be offered a token. This can be a serious problem and should probably be a fatal error. However, none of the currently implemented authentication modules should ever fail this test.

`utjadmin.so or configuration error in ...`

Check installation.

`XXX CANNOT instantiate module instance=`

Program, configuration, or installation error.

`NOTICE`

`"discarding response: " + param`

No controlling application is present to receive appliance response.

`"NOT_CLAIMED PARAMETERS: " + param`

A token was not claimed by any authentication module.

`...authentication module(s) loaded.`

Notification that authentication modules have loaded.

`...DISCONNECT ...`

Normal notification of disconnection.

`...finalize lifetime=`

An authentication record has been garbage collected by the Java Virtual Machine.

`...null session in redirect`

Not seen in normal operation.

`CLAIMED by`

A token has been claimed by an authentication module.

`CONNECT ...`

Normal indication of session connection.

`NOTICE`

`Control established on ...`

Normal notification that a program has been granted control over a session.

`DESTROY ... lifetime= ...`

Normal cleanup of disconnected session.

`DISCONNECT ...`

Normal notification of disconnection.

`Invalid call back attempt: ...`

Bad call back attempt from a `utsessiond`.

`Loaded module`

Notification of authentication module loading.

`SESSION_OK`

Normal startup of a new session or verification of an existing session.

`SessionManager.getSessionManager: Initiate callback to utsessiond at ...`

Normal.

`SessionManager.initiateCallback... established communication`

Normal.

`TERMINATE ...`

Normal notification of session termination.

`TERMINATE: empty session cleanup is disabled`

The `auth.props:terminateEnable` feature is not fully functional in this release and is not enabled by default. This message indicates that `utsessiond` notified `utauthd` that a session has no members. Future releases may use this information to cleanup empty sessions. It is normal to receive this message when a user exits their X session. `Dtlogin` normally will restart the session and present a login screen.

`TERMINATE: inactive session`

Terminate message received from `utsessiond` on a session that has already been purged from `utauthd`.

`TIMEOUT connection dropped ...`

An appliance is not responding.

`UNEXPECTED`

`"CallBack: malformed command"`

Bad syntax from a user application such as `utload` or `utidle.`

`.../ ... read/0:" + ie`

Possible program error.

`.../ ... read/1: ... Exception ...`

Error encountered while reading messages from appliance.

`.../... protocolError: ...`

Various protocol violations are reported with this message. This is also a way for `utauthd` to force the appliance to reset.

`UNEXPECTED`

`cannot send connInf, disconnecting session`

Session was disconnected during connection due to a problem in communicating with the appliance.

`Cannot set socket timeout: ... Exception ...`

Program error.

`connect failed: ...`

Problem encountered while attempting to connect appliance to a session.

`Error while closing socket: ... Exception ...`

Possible program error.

`Error while processing protocolError: ...`

An error was encountered while attempting to send a `protocolError` message to an appliance.

`Exception ... on ... / ...`

Error while trying to read input from appliance.

`null session in disconnect`

Possible program error.

`adminEvent strange event=`

Program error.

`attempt to instantiate CallBack()`

Program error.

`AuthReader: "`

Java runtime error or normal IO error due to appliance reboot.

`AuthRecord.connect: ... already connected"`

Possible program error.

`AuthRecord.disconnect: Null Client`

Possible program error.

`AuthRecord.send: no connection.`

Possible program error.

`CallBack.attach: cookie NOT consumed`

Bad call back attempt from a `utsessiond`.

`Callback.control: cannot begin: ...`

Possible program error while trying to start a thread to handle a program such as `utload`.

`CallBack.print: ...`

IO error while trying to send an appliance response back to the controlling application.

`CallBack.run init in: ...`

IO error.

`Callback: malformed command`

Syntax error from program attempting to control a session.

`Callback: malformed session id`

Syntax error from program attempting to control a session.

`Cannot accept on socket: ...`

Runtime error. Is `cbport` busy?

`UNEXPECTED`

`Cannot accept on socket: ... Exception ...`

Possible program error.

`Cannot connect on port change`

Check `utsessiond` log file.

`Cannot derive BufferedOutputStream: ... Exception ...`

Program error.

`Cannot derive BufferedReader: ... Exception ...`

Program error.

`cannot get socket inputStream from ... / ...`

Error while trying to read input from appliance.

`Cannot open socket: ... Exception ...`

Cannot open the socket specified by `auth.props:port`. Is there another `utauthd` running? `utauthd` should only be started by running `/etc/init.d/utsvc.`

`cannot pushback`

Possible program error.

`Cannot send protocolError to terminal on failed port change`

IO problem encountered while trying to reset appliance.

`Cannot set socket timeout: ... Exception ...`

Program error.

`Control.annotate: bad key: ...`

Annotations are not allowed in the
`/etc/opt/SUNWut/auth.props` file.

`Control.annotate: bad value: ...`

Only true or false are allowed as values for this parameter.

`Control.destroy: unable to clear controller: " + e`

Session has already disconnected.

`Control.load: extraneous parameters: ...`

Syntax error from controlling application.

`Control.load: invalid file param ...`

File might not be present and readable in
`/tftpboot`.

`Control.load: invalid flash param`

Syntax error from controlling application.

`Control.parse: invalid parameter`

Syntax error from controlling application.

`Control.response: out=null"`

No controlling application is present to receive appliance response.

`UNEXPECTED`

`Control.run: ar: " + arex`

Only one controlling application allowed or session not connected.

`Control.setParam failed: ...`

Only one controller allowed or session is not connected.

`Control.setParam null ar`

Possible program error.

`Control.setParam null in/out`

Possible program error or early exit of controlling command.

`Control: ...`

Possible program error or early exit of controlling command.

`Control: input error: ...`

Syntax or IO error from controlling application.

`Control: recv`

Error while reading input from controlling application.

`Control: unknown command: ...`

Syntax error from controlling application.

`Control: unknown command: ...`

Syntax error from controlling application.

`createClient:`

Program, installation or runtime error.

`desktopExists`

Likely program error.

`destroy error: " + e`

Error while trying to tell `utsessiond` to destroy a session.

`during send to:`

Loss of connection to appliance.

`Error ...\n while instantiating module. instance=`

Program, configuration, or installation error.

`exception in async job:`

Program error.

`Impossible error in putCanonical`

Possible program error.

`JobQueue.run:`

Program or installation error.

`JobQueue.submit:`

If `auth.props:terminateEnable` is true then this can occur in normal operation, otherwise it may occur due to a program error.

`logicalTokenExists`

Likely program error.

`No controller available to handle message:`

Normal if controlling application (`utload`, etc.) exited before results were received.

`rawTokenExists`

Likely program error.

`UNEXPECTED`

`Resolve error on`

Program or installation error.

`revoke error: ... Exception ...`

Error while trying to disconnect an appliance from a session.

`SESSION_ERROR`

Possible program error.

`SESSION_ERROR ... exitCode=`

It was not possible to start the first program in a session. The `exitCode` is helpful in determining the exact cause.

`SessionManager.confirmation: ... Exception ...`

If `auth.props:terminateEnable` is true then this can occur in normal operation, otherwise it may occur due to a program error or a problem in `utsessiond`.

`SessionManager.getSessionManager: ... InterruptedException`

Possibly normal message.

`SessionManager.initiateCallback: ... is not configured to talk to this utauthd`

The configuration file
`/etc/opt/SUNWut/auth.permit` does allow this `utauthd` to talk to the `utsessiond`.

`SessionManager.initiateCallback: ... unknown response: ...`

Program error.

`SessionManager.initiateCallback: ... was not able to talk to this utauthd`

Possible configuration error.

`SessionManager.initiateCallback: during send: ...`

Error while communicating to `utsessiond`.

`SessionManager.permit: ... Exception ...`

Error while attempting to connect an appliance to a session.

`SessionManager.permit: line="..."`

`utsessiond` did not allow the appliance to session connection.

`SessionManager.run: ... Exception ...`

Error while reading input from `utsessiond`.

`SessionManager.run: No job to match with "..." ... Exception ...`

Program error.

`SessionManager.run: readLine returns null`

Error while reading input from `utsessiond`.

`SessionManager.sessionFactory: ... Exception ...`

Possible program error.

`UNEXPECTED`

`SessionManager.sessionFactory: Cannot send create: ... Exception ...`

Communication problem with `utsessiond`.

`SessionManager.sessionFactory: Empty file: ...`

Possible program error.

`SessionManager.sessionFactory: unable to create new session: ...`

`utsessiond` did not create a new session ID as requested.

`SessionManager.sessionFactory:invalid SID from utsessiond: ...`

Program error in `utsession`.

`SessionManager.terminate: bad argument: "..."`

Could not parse message from `utsessiond`. Possible program error.

`SessionManager.terminate: invalid SessionId`

Possible program error.

`socket + "Handleclient, AuthRecord: ... Exception ...`

Possible program error.

`Terminal sent "..." as first message after TcpOpen, reports connected`

Appliance and `utauthd` are out of sync. This situation should correct itself.

`userExists`

Likely program error.

`utauthd: ... Exception ...`

Error encountered while listening for appliances.

`Worker: ... Exception ...`

Possible program error.

Error class	Message	Description
`CLIENT_ERROR`	`...Exception ... : cannot send keepAliveInf`	Error encountered while attempting to send a keep alive message to an appliance.
	`...keepAlive timeout`	An appliance has failed to respond within the allotted time. The session is being disconnected.
	`duplicate key:`	Appliance does not properly implement the authentication protocol.
	`invalid key:`	Appliance does not properly implement the authentication protocol.
`CONFIG_ERROR`	`attempt to instantiate CallBack 2nd time.`	Program error.
	`AuthModule.load`	Problem encountered while loading configuration module.
	`Cannot find module`	Program or installation error.
	`Cannot get AdminImpl methods:`	Installation error.
	`Cannot open call back socket on port ...`	Runtime error. Is `cbport` busy?
	`Cannot read properties file: ...`	Installation or configuration error.
	`cannot read properties file: ...`	Installation or configuration error, check file.
	`Cannot read session types`	Check file, usually `/etc/opt/SUNWut/sessionTypes.props`
	`during status:`	Program error or Java VM error.
	`Error while reading policy file ...`	Installation or configuration error.
	`Invalid configuration. Exiting`	Check value of `auth.props:policy` and the contents of the file indicated by the policy property.
	`Invalid option`	Program error in the `/opt/SUNWut/lib/utauthd` script`.`
`CONFIG_ERROR`	`No policy specified`	A policy must be specified using the `utpolicy` command. Check the "policy" keyword in the `/etc/opt/SUNWut/auth.props` file.
	`Policy file does not exist: ...`	Installation or configuration error.
	`refreshProperties: file non-existent: ...`	Installation or configuration error, check file name.
	`refreshProperties: no filename`	Configuration error, check the `/etc/opt/SUNWut/auth.props` file.
	`SessionManager.initiateCallback: ... claims to be already connected`	Possible configuration error.
	`sessionTypesFile not specified`	The required parameter "sessionTypesFile" is missing from `/etc/opt/SUNWut/auth.props` file.
	`UNCONFIGUED MODULE`	An authentication module is not configured and will not be offered a token. This can be a serious problem and should probably be a fatal error. However, none of the currently implemented authentication modules should ever fail this test.
	`utjadmin.so or configuration error in ...`	Check installation.
	`XXX CANNOT instantiate module instance=`	Program, configuration, or installation error.
`NOTICE`	`"discarding response: " + param`	No controlling application is present to receive appliance response.
	`"NOT_CLAIMED PARAMETERS: " + param`	A token was not claimed by any authentication module.
	`...authentication module(s) loaded.`	Notification that authentication modules have loaded.
	`...DISCONNECT ...`	Normal notification of disconnection.
	`...finalize lifetime=`	An authentication record has been garbage collected by the Java Virtual Machine.
	`...null session in redirect`	Not seen in normal operation.
	`CLAIMED by`	A token has been claimed by an authentication module.
	`CONNECT ...`	Normal indication of session connection.
`NOTICE`	`Control established on ...`	Normal notification that a program has been granted control over a session.
	`DESTROY ... lifetime= ...`	Normal cleanup of disconnected session.
	`DISCONNECT ...`	Normal notification of disconnection.
	`Invalid call back attempt: ...`	Bad call back attempt from a `utsessiond`.
	`Loaded module`	Notification of authentication module loading.
	`SESSION_OK`	Normal startup of a new session or verification of an existing session.
	`SessionManager.getSessionManager: Initiate callback to utsessiond at ...`	Normal.
	`SessionManager.initiateCallback... established communication`	Normal.
	`TERMINATE ...`	Normal notification of session termination.
	`TERMINATE: empty session cleanup is disabled`	The `auth.props:terminateEnable` feature is not fully functional in this release and is not enabled by default. This message indicates that `utsessiond` notified `utauthd` that a session has no members. Future releases may use this information to cleanup empty sessions. It is normal to receive this message when a user exits their X session. `Dtlogin` normally will restart the session and present a login screen.
	`TERMINATE: inactive session`	Terminate message received from `utsessiond` on a session that has already been purged from `utauthd`.
	`TIMEOUT connection dropped ...`	An appliance is not responding.
`UNEXPECTED`	`"CallBack: malformed command"`	Bad syntax from a user application such as `utload` or `utidle.`
	`.../ ... read/0:" + ie`	Possible program error.
	`.../ ... read/1: ... Exception ...`	Error encountered while reading messages from appliance.
	`.../... protocolError: ...`	Various protocol violations are reported with this message. This is also a way for `utauthd` to force the appliance to reset.
`UNEXPECTED`	`cannot send connInf, disconnecting session`	Session was disconnected during connection due to a problem in communicating with the appliance.
	`Cannot set socket timeout: ... Exception ...`	Program error.
	`connect failed: ...`	Problem encountered while attempting to connect appliance to a session.
	`Error while closing socket: ... Exception ...`	Possible program error.
	`Error while processing protocolError: ...`	An error was encountered while attempting to send a `protocolError` message to an appliance.
	`Exception ... on ... / ...`	Error while trying to read input from appliance.
	`null session in disconnect`	Possible program error.
	`adminEvent strange event=`	Program error.
	`attempt to instantiate CallBack()`	Program error.
	`AuthReader: "`	Java runtime error or normal IO error due to appliance reboot.
	`AuthRecord.connect: ... already connected"`	Possible program error.
	`AuthRecord.disconnect: Null Client`	Possible program error.
	`AuthRecord.send: no connection.`	Possible program error.
	`CallBack.attach: cookie NOT consumed`	Bad call back attempt from a `utsessiond`.
	`Callback.control: cannot begin: ...`	Possible program error while trying to start a thread to handle a program such as `utload`.
	`CallBack.print: ...`	IO error while trying to send an appliance response back to the controlling application.
	`CallBack.run init in: ...`	IO error.
	`Callback: malformed command`	Syntax error from program attempting to control a session.
	`Callback: malformed session id`	Syntax error from program attempting to control a session.
	`Cannot accept on socket: ...`	Runtime error. Is `cbport` busy?
`UNEXPECTED`	`Cannot accept on socket: ... Exception ...`	Possible program error.
	`Cannot connect on port change`	Check `utsessiond` log file.
	`Cannot derive BufferedOutputStream: ... Exception ...`	Program error.
	`Cannot derive BufferedReader: ... Exception ...`	Program error.
	`cannot get socket inputStream from ... / ...`	Error while trying to read input from appliance.
	`Cannot open socket: ... Exception ...`	Cannot open the socket specified by `auth.props:port`. Is there another `utauthd` running? `utauthd` should only be started by running `/etc/init.d/utsvc.`
	`cannot pushback`	Possible program error.
	`Cannot send protocolError to terminal on failed port change`	IO problem encountered while trying to reset appliance.
	`Cannot set socket timeout: ... Exception ...`	Program error.
	`Control.annotate: bad key: ...`	Annotations are not allowed in the `/etc/opt/SUNWut/auth.props` file.
	`Control.annotate: bad value: ...`	Only true or false are allowed as values for this parameter.
	`Control.destroy: unable to clear controller: " + e`	Session has already disconnected.
	`Control.load: extraneous parameters: ...`	Syntax error from controlling application.
	`Control.load: invalid file param ...`	File might not be present and readable in `/tftpboot`.
	`Control.load: invalid flash param`	Syntax error from controlling application.
	`Control.parse: invalid parameter`	Syntax error from controlling application.
	`Control.response: out=null"`	No controlling application is present to receive appliance response.
`UNEXPECTED`	`Control.run: ar: " + arex`	Only one controlling application allowed or session not connected.
	`Control.setParam failed: ...`	Only one controller allowed or session is not connected.
	`Control.setParam null ar`	Possible program error.
	`Control.setParam null in/out`	Possible program error or early exit of controlling command.
	`Control: ...`	Possible program error or early exit of controlling command.
	`Control: input error: ...`	Syntax or IO error from controlling application.
	`Control: recv`	Error while reading input from controlling application.
	`Control: unknown command: ...`	Syntax error from controlling application.
	`Control: unknown command: ...`	Syntax error from controlling application.
	`createClient:`	Program, installation or runtime error.
	`desktopExists`	Likely program error.
	`destroy error: " + e`	Error while trying to tell `utsessiond` to destroy a session.
	`during send to:`	Loss of connection to appliance.
	`Error ...\n while instantiating module. instance=`	Program, configuration, or installation error.
	`exception in async job:`	Program error.
	`Impossible error in putCanonical`	Possible program error.
	`JobQueue.run:`	Program or installation error.
	`JobQueue.submit:`	If `auth.props:terminateEnable` is true then this can occur in normal operation, otherwise it may occur due to a program error.
	`logicalTokenExists`	Likely program error.
	`No controller available to handle message:`	Normal if controlling application (`utload`, etc.) exited before results were received.
	`rawTokenExists`	Likely program error.
`UNEXPECTED`	`Resolve error on`	Program or installation error.
	`revoke error: ... Exception ...`	Error while trying to disconnect an appliance from a session.
	`SESSION_ERROR`	Possible program error.
	`SESSION_ERROR ... exitCode=`	It was not possible to start the first program in a session. The `exitCode` is helpful in determining the exact cause.
	`SessionManager.confirmation: ... Exception ...`	If `auth.props:terminateEnable` is true then this can occur in normal operation, otherwise it may occur due to a program error or a problem in `utsessiond`.
	`SessionManager.getSessionManager: ... InterruptedException`	Possibly normal message.
	`SessionManager.initiateCallback: ... is not configured to talk to this utauthd`	The configuration file `/etc/opt/SUNWut/auth.permit` does allow this `utauthd` to talk to the `utsessiond`.
	`SessionManager.initiateCallback: ... unknown response: ...`	Program error.
	`SessionManager.initiateCallback: ... was not able to talk to this utauthd`	Possible configuration error.
	`SessionManager.initiateCallback: during send: ...`	Error while communicating to `utsessiond`.
	`SessionManager.permit: ... Exception ...`	Error while attempting to connect an appliance to a session.
	`SessionManager.permit: line="..."`	`utsessiond` did not allow the appliance to session connection.
	`SessionManager.run: ... Exception ...`	Error while reading input from `utsessiond`.
	`SessionManager.run: No job to match with "..." ... Exception ...`	Program error.
	`SessionManager.run: readLine returns null`	Error while reading input from `utsessiond`.
	`SessionManager.sessionFactory: ... Exception ...`	Possible program error.
`UNEXPECTED`	`SessionManager.sessionFactory: Cannot send create: ... Exception ...`	Communication problem with `utsessiond`.
	`SessionManager.sessionFactory: Empty file: ...`	Possible program error.
	`SessionManager.sessionFactory: unable to create new session: ...`	`utsessiond` did not create a new session ID as requested.
	`SessionManager.sessionFactory:invalid SID from utsessiond: ...`	Program error in `utsession`.
	`SessionManager.terminate: bad argument: "..."`	Could not parse message from `utsessiond`. Possible program error.
	`SessionManager.terminate: invalid SessionId`	Possible program error.
	`socket + "Handleclient, AuthRecord: ... Exception ...`	Possible program error.
	`Terminal sent "..." as first message after TcpOpen, reports connected`	Appliance and `utauthd` are out of sync. This situation should correct itself.
	`userExists`	Likely program error.
	`utauthd: ... Exception ...`	Error encountered while listening for appliances.
	`Worker: ... Exception ...`	Possible program error.