Bash Syntax Error Near Unexpected Token: How to Fix It

Have you ever seen the message “syntax error near unexpected token” while running one of your Bash scripts?

In this guide, I will show you why this error occurs and how to fix it.

“Error Near Unexpected Token” is a Bash syntax error that reports bad syntax in your script or command. Many things can go wrong in a Bash script and cause this error. Some common causes are missing spaces next to commands and a lack of escaping for characters that have a special meaning for the Bash shell.

Finding the syntax error reported when you execute your script is not always easy. This process often requires you to change and retest your script multiple times.

To make your life easier I have analyzed different scenarios in which this syntax error can occur. For every scenario, I will show you the script or command with the error and the fix you need to apply to solve the problem.

One Approach to Fix This Error in Multiple Scenarios

By going through the examples below you will learn how to identify what’s causing this error and know how to fix it.

In some of the examples, I will show you how to fix this error if it happens while executing a single command in a Bash shell.

In other examples, we will look at Bash scripts that when executed fail with the “unexpected token” error.

To fix the error in a single command it’s usually enough to add or remove some incorrect characters that cause the syntax error in the command.

Knowing how to fix the error in a script can take a bit more time, and for that, I will use the following 5-step process:

  1. Run the script that contains the syntax error.
  2. Take note of the line mentioned by the Bash error.
  3. Execute the line with the error in a Bash shell to find the error fast (without having to change the script and rerun it multiple times).
  4. Update your script with the correct line of code.
  5. Confirm the script works.

Let’s go through the first scenario.

Syntax Error Near Unexpected Token ‘(‘

Let’s say I have the following file on my Linux system:

-rw-r--r--  1 ec2-user ec2-user   28 Jun 28 22:29 report(july).csv

And I want to rename it to report_july.csv.

I can use the following command, right?

mv report(july).csv report_july.csv

When I run it I get the following error:

-bash: syntax error near unexpected token `('

But, why?

Because parentheses () are used in Bash to create a subshell. In other words, they are special characters.

And Bash special characters need to be escaped if used as normal characters in a command. The backslash is used to escape characters.

I will update the command to include the backslash before both parentheses:

mv report\(july\).csv report_july.csv

No errors this time:

-rw-r--r--   1 ec2-user ec2-user   28 Jun 28 22:29 report_july.csv
Lesson 1: Remember to escape Bash special characters when you use them as normal characters (literals) in a filename or string in general.

We have fixed the first error!

Syntax Error Near Unexpected Token Then (Example 1)

And here is the second scenario.

When I run the following script:



if[ $DAY == "Monday" ]; then
  echo "Today is Monday"
  echo "Today is not Monday"

I get back the error below:

(localhost)$ ./
./ line 5: syntax error near unexpected token `then'
./ line 5: `if[ $DAY == "Monday" ]; then'

Can you see why?

The error is caused by the missing space between if and the open square bracket ( [ ).

The reason is the following:

if is a shell built-in command and you might be thinking you are using if here. But in reality, the shell sees if[ that is not a known command to the shell.

The shell doesn’t know how to handle then given that it hasn’t found if before, and it stops the script with the error above.

The correct script is:



if [ $DAY == "Monday" ]; then
  echo "Today is Monday"
  echo "Today is not Monday"

I have just added a space between if and [ so the shell can see the if command.

The output of the script is correct:

(localhost)$ ./
Today is Monday
Lesson 2: Spaces are important in Bash to help the shell identify every command.

Syntax Error Near Unexpected Token Then (Example 2)

While writing Bash scripts, especially at the beginning, it’s common to make errors like the one below:

(localhost)$ for i in {0..10} ; do echo $i ; then echo "Printing next number" ; done

When you run this one-liner here’s what you get:

-bash: syntax error near unexpected token `then'

Let’s find out why.

The syntax of a for loop in Bash is:

for VARIABLE in {0..10}
  echo command1
  echo command2
  echo commandN

And using a single line:

for VARIABLE in {0..10}; do echo command1; echo command2; echo commandN; done

So, as you can see the semicolon is used in Bash to separate commands when you want to write them on a single line.

The reason why the semicolons were not required in the first version of the script is that the newline is a command separator too.

Now, let’s go back to our error…

The one-liner that was failing with an error contains the then statement that as you can see is not part of the structure of a for loop.

The error is telling us:

  • There is a syntax error.
  • The token ‘then‘ is unexpected.

Let’s confirm the one-liner runs well after removing then:

(localhost)$ for i in {0..10} ; do echo $i ; echo "Printing next number" ; done
Printing next number
Printing next number
Printing next number
Printing next number
Printing next number
Printing next number
Printing next number
Printing next number
Printing next number
Printing next number
Printing next number

It’s working!

Lesson 3: When you see a syntax error verify that you are using Bash loops or conditional constructs in the right way and you are not adding any statements that shouldn't be there.

Syntax Error Near Unexpected Token Done

I have created a simple script in which an if statement is nested inside a while loop. This is very common in Bash.


while true 
  if [ $COUNTER -eq 0 ]; then
    echo "Stopping the script..."
    exit 1

This script might seem ok, but when I run it I get the following:

./ line 8: syntax error near unexpected token `done'
./ line 8: `  done'


The done and fi statements are correctly used to close the while loop and the if conditional statement. But they are used in the wrong order!

The if statement is nested into the while loop so we should be closing the if statement first, using fi. And after that, we can close the while loop using done.

Let’s try the script:

(localhost)$ ./ 
Stopping the script...

All good now.

Lesson 4: Nested loops and conditional statements need to be closed in the same order in which they are opened.

Syntax Error Near Unexpected Token fi

Let’s look at another scenario in which this syntax error can occur with the fi token:

for NAME in 'John' 'Mark' 'Kate'
    if [ "$NAME" == 'Mark' ] then
        echo 'Hello Mark!'

And this is what you get when you run it:

./ line 7: syntax error near unexpected token `fi'
./ line 7: `    fi'

In this case, the Bash shell identifies the if statement and because of that, it expects then after it.

As you can see then is there, so what’s the problem?

There is no command separator between the [ ] command (yes….it’s a command) and the then statement.

So, what’s the fix?

Add a command separator immediately after the closing square bracket. We will use the semicolon ( ; ) as a command separator.

Our script becomes:

for NAME in 'John' 'Mark' 'Kate'
    if [ "$NAME" == 'Mark' ]; then
        echo 'Hello Mark!'

And if I run it I get the correct output:

(localhost)$ ./ 
Hello Mark!
Lesson 5: Remember to specify command separators in your Bash scripts. Either the semicolon or the newline.


You now have what you need to understand what causes this syntax error in your scripts. You can apply the 5 lessons I have explained in this guide to find a fix.

If you have any questions please leave a comment below.

Now, let’s say you have saved your Bash script using Windows.

And when you run it in Linux you are seeing a syntax error that you can’t explain because the script looks correct to you.

You might be having the problem explained in this article.

Related FREE Course: Decipher Bash Scripting

Leave a Comment