ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Bin log Script Error
Article ID: 76791
Updated On:
Products
CA Rapid App Security
CA API Gateway
Issue/Introduction
Binlog script fails with similar error
Gateway#sh manage_binlogs.sh -f
: command not foundline 127:
: command not foundline 129:
: command not foundline 138:
: command not foundline 144:
: command not foundline 147:
: command not foundline 153:
: command not foundline 161:
: command not foundline 165:
: command not foundline 170:
: command not foundline 174:
: command not foundline 176:
'anage_binlogs.sh: line 177: syntax error near unexpected token `{
'anage_binlogs.sh: line 177: `clean_up() {
Gateway#sh manage_binlogs.sh -f
: command not foundline 127:
: command not foundline 129:
: command not foundline 138:
: command not foundline 144:
: command not foundline 147:
: command not foundline 153:
: command not foundline 161:
: command not foundline 165:
: command not foundline 170:
: command not foundline 174:
: command not foundline 176:
'anage_binlogs.sh: line 177: syntax error near unexpected token `{
'anage_binlogs.sh: line 177: `clean_up() {
Cause
These errors are usually due to incorrect line terminators in a script i.e. DOS CR/LF versus Unix LF.
Environment
All versions of Gateway
Resolution
It is possible to convert the file to use correct UNIX terminators by using the Dos2Unix command (either d2u or dos2unix). The line terminator problem is usually caused by saving the script in a Windows file editor.
Feedback
Yes
No
Powered by
