Bug ID 842193: Scriptd coring while running f5.automated_backup script

Last Modified: Jan 11, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2, 16.0.0,, 16.0.1

Opened: Oct 23, 2019
Severity: 3-Major


When the iApp, f5.automated_backup, script is terminated due to the max-script-run-time, the script still continues and finishes, sometimes with scriptd coring and posting error messages in /var/log/ltm: -- info logger[17173]: f5.automated_backup iApp autobackup: STARTED -- info logger[17175]: f5.automated_backup iApp autobackup: pem.f5lab.com_20191004.ucs GENERATING -- err scriptd[13532]: 014f0004:3: script has exceeded its time to live, terminating the script <------ after 20 secs, it continues even after the scriptd core. -- notice sod[3235]: 01140041:5: Killing /usr/bin/scriptd pid 13532. -- warning sod[3235]: 01140029:4: high availability (HA) daemon_heartbeat scriptd fails action is restart. -- info logger[19370]: f5.automated_backup iApp autobackup: pem.f5lab.com_20191004.ucs SAVED LOCALLY (/var/local/ucs) -- info logger[19372]: f5.automated_backup iApp autobackup: FINISHED


Scriptd core.


Configure the iApp application with f5.automated_backup template to do auto-backup at regular intervals.


Increasing the sys scriptd max-script-run-time higher then the default of 300 seconds might be helpful if the higher timeout allows the script to complete. For example, if the script is saving a UCS and the save takes 400 seconds, then increasing the max-script-run-time to 430 seconds would allow the script to finish and would work around this issue.

Fix Information


Behavior Change