3.5 Troubleshooting the Text File Policy

The Text File policy is not enforced

Source: ZENworks Linux Management; Policy Handlers; Text File Policy
Possible Cause: Policy Enforcement might have failed.
Action: Ensure that the policy has been enforced correctly by checking the Event Log of the policy or of the managed device.
Possible Cause: The search string was not found in the file.
Action: Verify that the Additional Info field in a log message contains a list of changes that were not performed. Ensure that the search string specified in the changes which were not done is found in the file.
Possible Cause: The pre-change action that is specified in the policy failed and the Action When the Execution Fails field was set to Do Not Modify the Text File.
Action: Ensure that the pre-change action does not fail.

Unable to find the backup file after the Text File policy has modified the file

Source: ZENworks Linux Management; Policy Handlers; Text File Policy
Possible Cause: There was an error while creating the backup of the modified file.
Action: Perform the following:
  1. Verify the value of the backup exit code in the message that is logged after policy was enforced.

  2. If the exit code is 1, it indicates that there was an error while taking the backup. Check the Additional Information field of the message to get more information on the error that is occurred.

Possible Cause: You might not be looking at the correct location of the backup.
Action: Perform the following:
  1. Verify the value of the backup exit code in the message that is logged after policy was enforced.

  2. If the exit code is 0, it indicates that the backup was taken successfully. Check to see if the backup file is in the same directory as the modified file.

Text File policy enforcement failed because of an error, but the file still appears modified or some unknown files appear in the same directory as the file

Source: ZENworks Linux Management; Policy Handlers; Text File Policy
Possible Cause: When the text file enforcement failed, there was also an error while rolling back the changes in the files being modified.
Action: Perform the following:
  1. Verify the value of the rollback exit code in the logged error message.

  2. If the exit code is 1, it indicates that there was an error while rolling back the changes. Check the Additional Information field of the message to get more information the error that occurred during rollback.

Possible Cause: There might be another Text File policy that modifies the same file.
Action: Perform the following:
  1. Verify the value of rollback exit code in the logged error message.

  2. If the exit code is 0, it indicates that the rollback was done successfully. Check to see if there is another Text File policy that modifies the same file.

  3. If the exit code is -1, it indicates that the rollback operation was not done because the file was not modified. Check to see if there is another Text File policy that modifies the same file.

How to ensure that the post-change action has been successful when the Text File policy was enforced

Source: ZENworks Linux Management; Policy Handlers; Text File Policy
Action: Verify the value of the post-change action exit code in the message that was logged after policy was enforced. This value is the exit code, which was returned by the program or script launched in the post-change action.