Dump stacktrace from failed custom transport script

jgillmanjr

• March 30, 2015 08:34

Hello! I'm working on a custom transport script to facilitate the storage of backups on Liquid Web's Object Storage. When backup time comes around, something seems to not like the 13G backup that's generated for one of the accounts. Manual execution of the script seems to work with the file in question. Short of me building logging into the script itself, Is there a way to have any of the backup logs snag any stack traces? /usr/local/cpanel/logs/cpbackup_transporter.log and the individual logs in cpbackup_transporter/ don't seem to have any useful information. The backup script is in python, and the script itself is on github: github.com/liquidweb/cPanelToObjectStore Thanks in advance! -Jason

• 

  jgillmanjr

  • April 01, 2015 13:20

  Well, ended up just building in logging anyways. Looks like the timeout is just getting hit and is restarting the process. So it appears it's just a timeout issue.

  0
• 

  cPanelMichael

  • April 08, 2015 13:12

  Hello, I am happy to see you were able to determine the cause of the problem. Were you able to address the timeout issue? Thank you.

  0

Please sign in to leave a comment.