A scenario might exist where jobs no longer run successfully in the current configuration. Perform the following procedure to determine whether the Appliance Backup Utility server has stopped responding to job requests and to correct the situation.
- To test Appliance Backup Utility server responsiveness, at the command line type /opt/teradata/abu_service/gui/bin/abujobquery -u administrator -p <password> -L. If successful, a list of current and previous jobs that have been launched through the Appliance Backup Utility is returned.
-
To verify that there is no filesize statement in the defaults file that exceeds 2 GB, type: grep filesize /etc/opt/teradata/abu_service/defaults
If there is no return from the grep command, there is no filesize parameter in the defaults file.
-
[Optional] To adjust the logfile maximum length to a value less than 2 GB:
- Add an entry within the [Defaults] stanza of the /etc/opt/teradata/abu_service/defaults file: filesize=numofbytes. For example, to set the log file size to 500 MB (500 * 1024): filesize=524288000 The default size of the Appliance Backup Utility server logfile is 2 GB. When this limit is reached, the server saves the existing log as logfile.prev and creates a new logfile before writing more log entries.
- [Optional] If you want to keep the logfile information, rename the file so that the information is not overwritten when a new logfile and logfile.prev are created.
- At the command line, type /etc/init.d/tdabusrv start to start the server.
-
Add ulimit -c 131072 to the /etc/init.d/tdabusrv script to create core files for debugging
case "$1" in start) echo -n 'Starting abusrv ' ulimit -c 131072 if [ $KTYPE -eq 0 ]; then
Core files are located in /var/opt/teradata/abu_service/service/config. - Type /etc/init.d/tdabusrv start to start the Appliance Backup Utility server.