Troubleshooting a Custom Script Error

Updated on 2024-01-24 GMT+08:00

View PDF

Application-consistent backup may fail due to custom script defects. In such conditions, open the /home/rdadmin/Agent/log/thirdparty.log file and view logs to locate the fault.

Figure 1 provides a log example recording a MySQL database freezing failure

Figure 1 Log example
Click to enlarge

18-09-13--22:30:10 in the first column records the logging time.

[30243] in the second column is the script PID.

[root] in the third column is the user who executes the script.

[INFO] or [ERROR] in the fourth column indicates the log level.

When a script invocation failure occurs, you can view the ERROR logs generated around the failure occurrence time to locate the fault. In Figure 1, the freezing fails because the MySQL database is in the frozen state and cannot be frozen again.

Parent topic: Using a Custom Script to Implement Application-Consistent Backup

Previous topic: Compiling an Unfreezing Script

Next topic: Verifying the Application-Consistent Backup Result (Linux)