Tres, I verified that all production/staging app servers:
- Have ~/bin/doctotext
- The appropriate user account has ~/bin in the PATH as the first hop
- When logged in as the appropriate user, 'cd /tmp; which doctotext' finds the one in ~/bin
- ~/bin/doctotext --help executes
I do worry that, despite all this, there were errors in the error monitor for production yesterday about the path to 'doctotext'. There is a slim chance it was whining "No such file or directory" on the file being provided to doctotext, not doctotext itself. Perhaps we can make a change that better captures the error.
I'd like us to re-evaluate this after today's production update:
- When fixing the cron jobs to do digest, let's also do the step Theune suggested about BASH_ENV=/etc/bash/bashr
- We try uploading a .docx file and see if there's an error
Tres, I verified that all production/staging app servers:
- Have ~/bin/doctotext
- The appropriate user account has ~/bin in the PATH as the first hop
- When logged in as the appropriate user, 'cd /tmp; which doctotext' finds the one in ~/bin
- ~/bin/doctotext --help executes
I do worry that, despite all this, there were errors in the error monitor for production yesterday about the path to 'doctotext'. There is a slim chance it was whining "No such file or directory" on the file being provided to doctotext, not doctotext itself. Perhaps we can make a change that better captures the error.
I'd like us to re-evaluate this after today's production update:
- When fixing the cron jobs to do digest, let's also do the step Theune suggested about BASH_ENV= /etc/bash/ bashr
- We try uploading a .docx file and see if there's an error
- If not, we close this ticket and call it a day