- 论坛徽章:
- 0
|
This message is displayed and the process stops:
ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs or a related file: /dsmerror.log. errno = 13, The file access permissions do not allow the specified action.
Beginning with TSM5.3, client applications will not run without a writable log. The system has denied write access to the log file named in the message. So the following (using dsmerror.log as an example, but all logs are treated equally) rules apply:
If the log does not exist, it will be created with default permissions
The name and the directory specified by the ERRORLOGNAME option will be used.
If the obtion is absent, the name dsmerror.log in the directory specified in the DSM_LOG environment variable, if present, will be used.
Otherwise, the name dsmerror.log in the current working directory will be used.
Because default permissions are used, a log created by the root user may not be writable by any other user. If this is the case, the root user must set the proper permissions or ACLs to allow free use of the TSM application by all users who need to use it.
If the log is successfully created, an error-free session will leave a zero-length (empty) log file.
The client does not attempt to create logs in the root directory. ANS1398E is displayed when the method in rule 1 directs the log file to be created in the root directory.
If a log file exists and can be located using the method in rule 1, it will be used (and it can be in the root directory if you choose). Furthermore, whatever permissions you give that log file will be preserved by TSM code.
Recommendation:
Create your log file in advance of first use, making sure all eligible users have write access to that log. Define the ERRORLOGNAME option or the DSM_DIR environment variable to designate your predefined log file.
Additional info:
Certain background TSM applications may fail to start due to errors writing to dsmerror.log. When these errors occur, a number of errors are recorded in the Windows system event log (System log on other platforms). One of which is an error indicating that dsmerror.log could not be written to.
For example:
C:\Program Files\Tivoli\Tsm\baclient>net start "TSM Sched"
The TSM sched service is starting.
The TSM Sched service could not be started.
A service specific error occurred: 12.
Additional setup steps are required for non-root users to run TSM applications or TSM for data protection applications. You will receive the ANS1398E error attempting to run TSM applications using an error log which has already been generated by root that is left with default permissions. For data protection clients, you may only receive a TSM API error <which one?>. Here is one method for setting up dsmerror.log for use by non-root users:
Set ERRORLOGNAME in dsm.sys. For example, errorLogName /var/msgs/tsm/dsmerror.log
Generate dsmerror.log. dsmc q sess
Modify the permissions on dsmerror.log to allow writing by all users. chmod 666 /var/msgs/tsm/dsmerror.log |
|
免费注册
发表于 2007-01-10 22:03
发表于 2007-01-10 22:52
