This section provides a list of messages that you may encounter with the use of the LifeKeeper Samba Recovery Kit. Where appropriate, it provides an additional explanation of the cause of an error and necessary action to resolve the error condition.
Because the Samba Recovery Kit relies on other LifeKeeper components to drive the creation and extension of hierarchies, messages from these other components are also possible. In these cases, please refer to the Message Catalog (located on our Technical Documentation site under Search for an Error Code) which provides a listing of all error codes, including operational, administrative and GUI, that may be encountered while using LifeKeeper for Linux and, where appropriate, provides additional explanation of the cause of the error code and necessary action to resolve the issue. This full listing may be searched for any error code received, or you may go directly to one of the individual Message Catalogs for the appropriate LifeKeeper component.
Common Error Messages
|Error Number||Error Message||Description|
|109009||Error getting netbios name from the instance information field for tag “Samba- smb.conf” on server “ServerA”.||Extracting the NetBIOS name from the instance info failed. Check that the info field contains the configuration file and NetBIOS name.|
|109015||The Samba utility testparm failed. Unable to parse Samba configuration file.||The Samba utility testparm that is used to parse the configuration file failed. Run testparm from the command line specifying the configuration file used for the hierarchy to determine the failure.|
|109019||Failed to initialize for reading of the Configuration File “/tmp/smb.ini.1234”.||Attempts to read the generated output of the configuration file failed. The utility testparm generated a bad file.|
|109022||Error getting configuration name from the instance information field for tag “Samba- smb.conf” on server “ServerA”.||Extracting the NetBIOS name from the instance info failed. Check that the info field contains the configuration file and NetBIOS name.|
|109030||Failure opening “/var/lock/samba/smbd.pid” on server “ServerA”: “File Not Found”||The attempted open of the daemon process ID file failed for the listed reason. Correct the problem based on the listed error code.|
|109050||Open of the testparm output file failed.||The open of output file created by running testparm failed because the file does not exist or does not contain any data. Run testparm from the command line specifying the configuration file used for the hierarchy to determine the failure.|
Post your comment on this topic.