Error Message Reference ---Tivoli Access Manager WebSEAL Messages

今天通过查阅这个文档解决了一个集成中的问题,希望也会帮你提供关于webseal中集成的方案;

引用:http://publib.boulder.ibm.com/tividd/td/ITAMOS/SC32-1144-00/en_US/HTML/am41_error_ref06.htm

This chapter describes the messages provided by Tivoli Access Manager WebSEAL.

0x38983135 (949498165) The WebSEAL administration service has not been initalized.
Explanation: The WebSEAL administration service plug-in failed to initialize properly.

Action: Check for other initialization errors and/or configuration problems that may have previously occurred.

Name: admin_svc_uninitialized

Severity: Error

Component: wad / admin_s_general

0x38983137 (949498167) Invalid object name.
Explanation: An object name was presented which is not considered valid.

Action: Check the value of the object name being used to make sure it is valid.

Name: admin_svc_bad_object_name

Severity: Notice

Component: wad / admin_s_general

0x38983138 (949498168) Object list failed: %s


Explanation: The object list command failed to complete correctly.

Action: This is a generic error which will contain further details when output.

Name: admin_svc_object_list_failed

Severity: Error

Component: wad / admin_s_general

0x38983141 (949498177) Invalid command.


Explanation: The command had a syntax error.

Action: Check the command name or the arguments supplied to the command are correct.

Name: admin_invalid_command

Severity: Notice

Component: wad / admin_s_general

0x38983148 (949498184) The junction import command recieved invalid data


Explanation: An error occurred when trying to extract one or more of the junction attributes sent in the admin command.

Action: Check that the data being passed into the junction import command is valid.

Name: junc_imp_attrlist_extract_failed

Severity: Error

Component: wad / admin_s_general

0x38983149 (949498185) The junction import command recieved an invalid version


Explanation: The version in the junction definition is not supported by this version of WebSEAL

Action: Check the version of the junction in the XML definition

Name: junc_imp_attrlist_extract_version_failed

Severity: Error

Component: wad / admin_s_general

0x3898314a (949498186) The junction import could not create the junction file


Explanation: WebSEAL can not create the junction file.

Action: Check the filesystem to make sure there is space available, or that the WebSEAL server has permissions to create/write the file.

Name: junc_imp_cannot_create_jct

Severity: Error

Component: wad / admin_s_general

0x3898314b (949498187) The junction import could not write the junction file


Explanation: An error occurred writing the junction definition.

Action: Check the filesystem to make sure there is space available, or that the WebSEAL server has permissions to create/write the file.

Name: junc_imp_cannot_write_jct

Severity: Error

Component: wad / admin_s_general

0x3898314c (949498188) The junction export could not read the junction directory


Explanation: An error occurred while trying to read the contents of the junction database directory.

Action: Check to make sure that WebSEAL is able to read the contents of the directory which is configured to contain the junction definitions.

Name: junc_exp_cannot_read_db

Severity: Error

Component: wad / admin_s_general

0x3898314d (949498189) azn_attrlist_add_entry failed for some reason


Explanation: An error occurred returning the junction data to the client

Action: This is an internal error which occurs when WebSEAL is marshalling the junction data to the export command. Check for other errors occurring previously.

Name: junc_exp_attrlist_add_entry_failed

Severity: Error

Component: wad / admin_s_general

0x3898314e (949498190) An invalid junction point was specified.


Explanation: WebSEAL was unable to build the junction filename.

Action: An internal error occurred in WebSEAL when trying to build the encoded filename. Check for previous errors.

Name: junc_bad_jct_point

Severity: Error

Component: wad / admin_s_general

0x3898314f (949498191) Error reading junction point %s.


Explanation: The file name representing the junction could not constructed.

Action: An internal error occurred in WebSEAL when trying to build the encoded filename. Check for previous errors.

Name: junc_point_read_failed

Severity: Error

Component: wad / admin_s_general

0x38983150 (949498192) Error reading junction file %s.


Explanation: There was an error opening or parsing the junction definition file.

Action: Verify the .xml file exists, is readable, and has valid data.

Name: junc_file_read_failed

Severity: Error

Component: wad / admin_s_general

0x38983156 (949498198) Error reading input user session id.


Explanation: There was an error parsing the user session id.

Action: Verify that the input is being passed correctly.

Name: termsess_invalid_user_session_id

Severity: Error

Component: wad / admin_s_general

0x38983157 (949498199) Error reading input user id.


Explanation: There was an error parsing the user ID.

Action: Verify that user ID is being input correctly.

Name: termallsess_invalid_user_id

Severity: Error

Component: wad / admin_s_general

0x38983158 (949498200) User not logged in.


Explanation: Bad input, or User's sessions were already terminated.

Action: Verify validity of input, or assume sessions were already terminated.

Name: termallsess_nonexistent_userid

Severity: Notice

Component: wad / admin_s_general

0x38983159 (949498201) No matching User Session found.


Explanation: Bad input, or User session was already terminated.

Action: Verify validity of input, or assume session was already terminated.

Name: termsess_nonexistent_user_session_id

Severity: Error

Component: wad / admin_s_general

0x3898316a (949498218) The dynurl configuration file %s cannot be opened for reading.


Explanation: An attempt to open the dynurl configuration file for reading failed

Action: Ensure that the file exists on the WebSEAL server and is readable

Name: dynurl_read_no_file

Severity: Error

Component: wad / admin_s_general

0x3898316b (949498219) The jmt configuration file %s cannot be opened for reading.


Explanation: An attempt to open the jmt configuration file for reading failed

Action: Ensure that the file exists on the WebSEAL server and is readable

Name: jmt_read_no_file

Severity: Error

Component: wad / admin_s_general

0x3898316c (949498220) You must specify a junction point to read or write an fsso configuration file.


Explanation: A junction point is necessary to determine which fsso configuration file to read or write

Action: Add the junction point to the junction attribute of the indata attribute list

Name: fsso_conf_mgmt_no_junction

Severity: Error

Component: wad / admin_s_general

0x3898316d (949498221) The junction: %s is not a valid junction on this WebSEAL server.


Explanation: An invalid junction point was provided.

Action: Ensure that the junction attribute in indata is a valid junction

Name: fsso_conf_mgmt_invalid_jct

Severity: Error

Component: wad / admin_s_general

0x3898316e (949498222) The junction: %s is not an fsso junction on this WebSEAL server.


Explanation: The junction specified is not an FSSO junction.

Action: Ensure that the junction specified is an FSSO junction.

Name: fsso_conf_mgmt_not_fsso_jct

Severity: Error

Component: wad / admin_s_general

0x3898316f (949498223) The fsso configuration file: %s could not be opened for reading.


Explanation: The junction specified could not be opened.

Action: Ensure that the fsso configuration file for the junction specified exists and is readable.

Name: fsso_conf_mgmt_no_file

Severity: Error

Component: wad / admin_s_general

0x38983170 (949498224) Could not create dynurl configuration file: %s


Explanation: WebSEAL was unable to create the dynurl conf file.

Action: Ensure that ivmgr has filesystem permissions to create a file in the directory where the dynurl configuration file will be stored

Name: dynurl_write_file_create_failed

Severity: Error

Component: wad / admin_s_general

0x38983171 (949498225) Reloading the in memory dynurl table failed


Explanation: An error occurred while trying to read the dynurl configuration file.

Action: Ensure that the new file specified is in the proper format

Name: dynurl_write_reload_failed

Severity: Error

Component: wad / admin_s_general

0x38983172 (949498226) Could not create jmt configuration file: %s


Explanation: An error occured while trying to open the jmt configuration file.

Action: Ensure that ivmgr has filesystem permissions to create a file in the directory where the jmt configuration file will be stored

Name: jmt_write_file_create_failed

Severity: Error

Component: wad / admin_s_general

0x38983173 (949498227) Reloading the in memory jmt table failed


Explanation: An error occurred while trying to read in the new jmt configuration file.

Action: Ensure that the new file specified is in the proper format.

Name: jmt_write_reload_failed

Severity: Error

Component: wad / admin_s_general

0x38983174 (949498228) The junction specified does not exist. The configuration file: %s was created.


Explanation: An fsso junction may not be created without the configuration file being inplace. This allows the file to be created before the junction

Action: The junction may now be created using this new configuration file

Name: fsso_write_no_such_junction

Severity: Warning

Component: wad / admin_s_general

0x38983175 (949498229) Could not create fsso configuration file: %s


Explanation: An error occurred while trying to read in the new fsso configuration file.

Action: Ensure that ivmgr has filesystem permissions to create a file in the directory where the fsso configuration file will be stored

Name: fsso_write_file_create_failed

Severity: Error

Component: wad / admin_s_general

0x38983176 (949498230) The backup operation failed for %s


Explanation: An error occurred while attempting to create a backup copy of the original configuration file.

Action: Ensure that ivmgr has filesystem permissions to create a file in the directory where the configuration file resides.

Name: cfg_file_mgmt_backup_failed

Severity: Error

Component: wad / admin_s_general

0x38983177 (949498231) Reloading junction: %s failed


Explanation: An error occurred while trying to load the fsso configuration file.

Action: Ensure that the new file specified is in the proper format.

Name: fsso_write_reload_failed

Severity: Error

Component: wad / admin_s_general

0x389d0096 (949813398) Invalid UNIX user name (%s)


Explanation: See message.

Action: Use a valid user name

Name: cdas_s_unknown_unix_user

Severity: Error

Component: wca / cdas_s_general

0x389d0097 (949813399) Invalid UNIX group name (%s)


Explanation: See message

Action: Put user in a valid group.

Name: cdas_s_unknown_unix_group

Severity: Error

Component: wca / cdas_s_general

0x389d0098 (949813400) Could not change process GID (%s)


Explanation: See message.

Action: Contact support.

Name: cdas_s_change_unix_group

Severity: Error

Component: wca / cdas_s_general

0x389d0099 (949813401) Could not change process UID (%s)


Explanation: See message.

Action: Contact support.

Name: cdas_s_change_unix_user

Severity: Error

Component: wca / cdas_s_general

0x389d009a (949813402) Could not become background process (%d)


Explanation: See message.

Action: Contact support.

Name: cdas_s_cant_background

Severity: Error

Component: wca / cdas_s_general

0x389d009b (949813403) Could not start background process


Explanation: See message.

Action: Contact support.

Name: cdas_s_failed_child_startup

Severity: Warning

Component: wca / cdas_s_general

0x389d009c (949813404) Could not use RPC protocol sequence (%s,%s,0x%8.8lx)


Explanation: See message.

Action: Contact support.

Name: cdas_s_use_protseq_ep

Severity: Error

Component: wca / cdas_s_general

0x389d009d (949813405) Could not fetch RPC bindings (0x%8.8lx)


Explanation: See message.

Action: Contact support.

Name: cdas_s_fetch_bindings

Severity: Error

Component: wca / cdas_s_general

0x389d009e (949813406) Could not release RPC bindings (0x%8.8lx)


Explanation: See message.

Action: Contact Support.

Name: cdas_s_release_bindings

Severity: Error

Component: wca / cdas_s_general

0x389d009f (949813407) Caught signal (%d)


Explanation: See message.

Action: Contact Support.

Name: cdas_s_signal_caught

Severity: Fatal

Component: wca / cdas_s_general

0x389d00a0 (949813408) Could not create new thread (%d)


Explanation: See message.

Action: Contact support.

Name: cdas_s_failed_pthread_create

Severity: Error

Component: wca / cdas_s_general

0x389d00a1 (949813409) Could not cancel thread (%d)


Explanation: See message.

Action: Contact support.

Name: cdas_s_failed_pthread_cancel

Severity: Error

Component: wca / cdas_s_general

0x389d00a2 (949813410) Could not join thread (%d)


Explanation: See message.

Action: Contact Support.

Name: cdas_s_failed_pthread_join

Severity: Error

Component: wca / cdas_s_general

0x389d00a3 (949813411) Could not set RPC authorization function (0x%8.8lx)


Explanation: See message.

Action: Contact support.

Name: cdas_s_set_auth_func

Severity: Error

Component: wca / cdas_s_general

0x389d00a4 (949813412) Could not setup authentication info (0x%8.8lx)


Explanation: Unable to perform login.

Action: Check login parameters.

Name: cdas_s_register_auth_info

Severity: Error

Component: wca / cdas_s_general

0x389d00a5 (949813413) Could not set server login context (0x%8.8lx)


Explanation: Unable to set the network credentials to those specified by login context.

Action: Check that network credentials are correct.

Name: cdas_s_set_login_context

Severity: Error

Component: wca / cdas_s_general

0x389d00a6 (949813414) Could not perform network login (%s,%s,0x%8.8lx)


Explanation: See message.

Action: Verify that user/password is correct.

Name: cdas_s_cant_validate_ident

Severity: Error

Component: wca / cdas_s_general

0x389d00a7 (949813415) Could not fetch key from keytab file (%s,%s,0x%8.8lx)


Explanation: See message.

Action: Check that the keyfile is set up correctly, and the user information is valid.

Name: cdas_s_get_key

Severity: Error

Component: wca / cdas_s_general

0x389d00a8 (949813416) Could not refresh login context (0x%8.8lx)


Explanation: WebSEAL was unable to refresh the login based on existing login information.

Action: Check validity of login information

Name: cdas_s_cant_refresh_identity

Severity: Error

Component: wca / cdas_s_general

0x389d00a9 (949813417) Could not determine login context expiration (0x%8.8lx)


Explanation: See message.

Action: Check validity of login information.

Name: cdas_s_no_login_expiration

Severity: Error

Component: wca / cdas_s_general

0x389d00aa (949813418) Could not set RPC interface (0x%8.8lx)


Explanation: See message.

Action: Check interfaces.

Name: cdas_s_register_if

Severity: Error

Component: wca / cdas_s_general

0x389d00ab (949813419) Could not register RPC endpoints (%s,0x%8.8lx)


Explanation: See message.

Action: Check endpoints.

Name: cdas_s_register_ep

Severity: Error

Component: wca / cdas_s_general

0x389d00ac (949813420) Could not unregister RPC interface (0x%8.8lx)


Explanation: See message.

Action: Check validity and status of interfaces.

Name: cdas_s_unregister_if

Severity: Error

Component: wca / cdas_s_general

0x389d00ad (949813421) Could not export bindings to name service (%s,%s,0x%8.8lx)


Explanation: See message.

Action: Check status of name service.

Name: cdas_s_ns_export

Severity: Error

Component: wca / cdas_s_general

0x389d00ae (949813422) Could not unregister RPC endpoints (0x%8.8lx)


Explanation: See message.

Action: Check validity and status of endpoints.

Name: cdas_s_unregister_ep

Severity: Error

Component: wca / cdas_s_general

0x389d00af (949813423) Could not unexport bindings from name service (%s,0x%8.8lx)


Explanation: See message.

Action: Check validity of interfaces and name service.

Name: cdas_s_ns_unexport

Severity: Error

Component: wca / cdas_s_general

0x389d00b0 (949813424) Malloc failure (0x%8.8lx)


Explanation: See message.

Action: Check status of memory on the system.

Name: cdas_s_malloc_fail

Severity: Error

Component: wca / cdas_s_general

0x389d00b1 (949813425) This CDAS does not support this authentication style: (%d)


Explanation: See message.

Action: Check validity of authentication style

Name: cdas_s_invalid_auth_style

Severity: Error

Component: wca / cdas_s_general

0x389d00b2 (949813426) General CDAS (Cross Domain Authentication Service) failure (%s, 0x%8.8lx)


Explanation: See message.

Action: See message.

Name: cdas_s_general_fail

Severity: Error

Component: wca / cdas_s_general

0x389d00b3 (949813427) Pthread error occurred: %d


Explanation: See message.

Action: Check system resources.

Name: cdas_s_general_pthread_error

Severity: Error

Component: wca / cdas_s_general

0x389d012c (949813548) API internal error: (%s, %d)


Explanation: See message.

Action: See message.

Name: cdas_s_api_internal_error

Severity: Error

Component: wca / cdas_s_token

0x389d01ca (949813706) malloc() failure


Explanation: The application was unable to allocate the required memory.

Action: Ensure that there is enough system memory.

Name: cdas_s_malloc_failure

Severity: Fatal

Component: wca / cdas_s_cert

0x389d02ee (949813998) Shutting down the CDAS


Explanation: Message showing CDAS is shutting down

Action: No action is required.

Name: xkms_s_shut_down_cdas

Severity: Notice

Component: wca / cdas_s_xkms

0x389d02ef (949813999) There is NO user authentication information available.


Explanation: The user does not provide their information for authentication

Action: Check user information for Authentication

Name: xkms_s_no_user_auth_info

Severity: Error

Component: wca / cdas_s_xkms

0x389d02f0 (949814000) CDAS called - xauthn_dn: %s