-bash: export: not a valid identifier [duplicate]
This question already has an answer here:
How to fix “not a valid identifier” error after setting environment variables?
3 answers
Whenever I open a terminal, I always end up with this same error.
-bash: export: `/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/usr/local/hadoop/bin': not a valid identifier
And when I run command lines, I get errors like this:
-bash: sudo: No such file or directory
I can't even edit ~/.bashrc through gedit ~/.bashrc which I think could be the problem. echo $PATH gives me an empty line.
All this stuff happens under my personal account. There's a dedicated hadoop user account, which I created specifically for running hadoop and that works fine without a glitch.
In the process of hadoop setup, which involves editing environment variables, I edited ~/.bashrc as instructed by some tutorials.
What could be the problem, and how might I fix it?
bash environment-variables bashrc hadoop
edited Dec 19 '18 at 21:10
Zanna
50.3k13133241
asked Jun 13 '16 at 8:20
James WongJames Wong
148119
marked as duplicate by wjandrea, Eric Carvalho, karel, Zanna, Charles Green Dec 20 '18 at 14:13
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
How to fix “not a valid identifier” error after setting environment variables?
3 answers
Whenever I open a terminal, I always end up with this same error.
-bash: export: `/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/usr/local/hadoop/bin': not a valid identifier
And when I run command lines, I get errors like this:
-bash: sudo: No such file or directory
I can't even edit ~/.bashrc through gedit ~/.bashrc which I think could be the problem. echo $PATH gives me an empty line.
All this stuff happens under my personal account. There's a dedicated hadoop user account, which I created specifically for running hadoop and that works fine without a glitch.
In the process of hadoop setup, which involves editing environment variables, I edited ~/.bashrc as instructed by some tutorials.
What could be the problem, and how might I fix it?
bash environment-variables bashrc hadoop
edited Dec 19 '18 at 21:10
Zanna
50.3k13133241
asked Jun 13 '16 at 8:20
James WongJames Wong
148119
marked as duplicate by wjandrea, Eric Carvalho, karel, Zanna, Charles Green Dec 20 '18 at 14:13
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
looks like you have a different tick at the start than at the end. can yousudo gedit ~/.bashrc?
– TmTron
Jun 13 '16 at 8:31
Ye just change your ` to a normal ' and it should work fine.
– Ziazis
Jun 13 '16 at 8:31
Did you try to edit your~/.bashrcand~/.profileby another user with enough privileges?
– gwarah
Jun 13 '16 at 8:32
1
Btw. since your $PATH isn't working you have to tell the shell exactly where which command is. That means you would need to write something like /usr/bin/sudo /bin/vi /home/user/.bashrc or .profile and correct the issues
– Ziazis
Jun 13 '16 at 8:36
add a comment |
This question already has an answer here:
How to fix “not a valid identifier” error after setting environment variables?
3 answers
Whenever I open a terminal, I always end up with this same error.
-bash: export: `/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/usr/local/hadoop/bin': not a valid identifier
And when I run command lines, I get errors like this:
-bash: sudo: No such file or directory
I can't even edit ~/.bashrc through gedit ~/.bashrc which I think could be the problem. echo $PATH gives me an empty line.
All this stuff happens under my personal account. There's a dedicated hadoop user account, which I created specifically for running hadoop and that works fine without a glitch.
In the process of hadoop setup, which involves editing environment variables, I edited ~/.bashrc as instructed by some tutorials.
What could be the problem, and how might I fix it?
bash environment-variables bashrc hadoop
edited Dec 19 '18 at 21:10
Zanna
50.3k13133241
asked Jun 13 '16 at 8:20
James WongJames Wong
148119
This question already has an answer here:
How to fix “not a valid identifier” error after setting environment variables?
3 answers
Whenever I open a terminal, I always end up with this same error.
-bash: export: `/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/usr/local/hadoop/bin': not a valid identifier
And when I run command lines, I get errors like this:
-bash: sudo: No such file or directory
I can't even edit ~/.bashrc through gedit ~/.bashrc which I think could be the problem. echo $PATH gives me an empty line.
All this stuff happens under my personal account. There's a dedicated hadoop user account, which I created specifically for running hadoop and that works fine without a glitch.
In the process of hadoop setup, which involves editing environment variables, I edited ~/.bashrc as instructed by some tutorials.
What could be the problem, and how might I fix it?
This question already has an answer here:
How to fix “not a valid identifier” error after setting environment variables?
3 answers
bash environment-variables bashrc hadoop
bash environment-variables bashrc hadoop
edited Dec 19 '18 at 21:10
Zanna
50.3k13133241
asked Jun 13 '16 at 8:20
James WongJames Wong
148119
edited Dec 19 '18 at 21:10
Zanna
50.3k13133241
asked Jun 13 '16 at 8:20
James WongJames Wong
148119
edited Dec 19 '18 at 21:10
Zanna
50.3k13133241
edited Dec 19 '18 at 21:10
Zanna
50.3k13133241
edited Dec 19 '18 at 21:10
Zanna
50.3k13133241
50.3k13133241
asked Jun 13 '16 at 8:20
James WongJames Wong
148119
asked Jun 13 '16 at 8:20
James WongJames Wong
148119
asked Jun 13 '16 at 8:20
James WongJames Wong
148119
148119
marked as duplicate by wjandrea, Eric Carvalho, karel, Zanna, Charles Green Dec 20 '18 at 14:13
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by wjandrea, Eric Carvalho, karel, Zanna, Charles Green Dec 20 '18 at 14:13
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
looks like you have a different tick at the start than at the end. can yousudo gedit ~/.bashrc?
– TmTron
Jun 13 '16 at 8:31
Ye just change your ` to a normal ' and it should work fine.
– Ziazis
Jun 13 '16 at 8:31
Did you try to edit your~/.bashrcand~/.profileby another user with enough privileges?
– gwarah
Jun 13 '16 at 8:32
1
Btw. since your $PATH isn't working you have to tell the shell exactly where which command is. That means you would need to write something like /usr/bin/sudo /bin/vi /home/user/.bashrc or .profile and correct the issues
– Ziazis
Jun 13 '16 at 8:36
add a comment |
looks like you have a different tick at the start than at the end. can yousudo gedit ~/.bashrc?
– TmTron
Jun 13 '16 at 8:31
Ye just change your ` to a normal ' and it should work fine.
– Ziazis
Jun 13 '16 at 8:31
Did you try to edit your~/.bashrcand~/.profileby another user with enough privileges?
– gwarah
Jun 13 '16 at 8:32
1
Btw. since your $PATH isn't working you have to tell the shell exactly where which command is. That means you would need to write something like /usr/bin/sudo /bin/vi /home/user/.bashrc or .profile and correct the issues
– Ziazis
Jun 13 '16 at 8:36
looks like you have a different tick at the start than at the end. can you
sudo gedit ~/.bashrc?– TmTron
Jun 13 '16 at 8:31
looks like you have a different tick at the start than at the end. can you
sudo gedit ~/.bashrc?– TmTron
Jun 13 '16 at 8:31
Ye just change your ` to a normal ' and it should work fine.
– Ziazis
Jun 13 '16 at 8:31
Ye just change your ` to a normal ' and it should work fine.
– Ziazis
Jun 13 '16 at 8:31
Did you try to edit your
~/.bashrc and ~/.profile by another user with enough privileges?– gwarah
Jun 13 '16 at 8:32
Did you try to edit your
~/.bashrc and ~/.profile by another user with enough privileges?– gwarah
Jun 13 '16 at 8:32
1
1
Btw. since your $PATH isn't working you have to tell the shell exactly where which command is. That means you would need to write something like /usr/bin/sudo /bin/vi /home/user/.bashrc or .profile and correct the issues
– Ziazis
Jun 13 '16 at 8:36
Btw. since your $PATH isn't working you have to tell the shell exactly where which command is. That means you would need to write something like /usr/bin/sudo /bin/vi /home/user/.bashrc or .profile and correct the issues
– Ziazis
Jun 13 '16 at 8:36
add a comment |
1 Answer
1
active
oldest
votes
Probably your .bashrc or .profile is messedup.
Your gedit will not start if it is not in path and since your path is empty it is not in the path.
You should first establish a good enough path.
export PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
And then you should be able to start gedit. Alternativelly you could just run gedit with its whole path. Like:
/usr/bin/gedit
answered Jun 13 '16 at 8:35
E. TimoteiE. Timotei
1166
Thank you very much indeed. At least I can start to debug by running command lines.
– James Wong
Jun 13 '16 at 10:50
@JamesWong the error message suggests it's runningexport $PATHinstead ofexport PATH, so look for that in particular.
– geirha
Jun 15 '16 at 11:00
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Probably your .bashrc or .profile is messedup.
Your gedit will not start if it is not in path and since your path is empty it is not in the path.
You should first establish a good enough path.
export PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
And then you should be able to start gedit. Alternativelly you could just run gedit with its whole path. Like:
/usr/bin/gedit
answered Jun 13 '16 at 8:35
E. TimoteiE. Timotei
1166
Thank you very much indeed. At least I can start to debug by running command lines.
– James Wong
Jun 13 '16 at 10:50
@JamesWong the error message suggests it's runningexport $PATHinstead ofexport PATH, so look for that in particular.
– geirha
Jun 15 '16 at 11:00
add a comment |
Probably your .bashrc or .profile is messedup.
Your gedit will not start if it is not in path and since your path is empty it is not in the path.
You should first establish a good enough path.
export PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
And then you should be able to start gedit. Alternativelly you could just run gedit with its whole path. Like:
/usr/bin/gedit
answered Jun 13 '16 at 8:35
E. TimoteiE. Timotei
1166
Thank you very much indeed. At least I can start to debug by running command lines.
– James Wong
Jun 13 '16 at 10:50
@JamesWong the error message suggests it's runningexport $PATHinstead ofexport PATH, so look for that in particular.
– geirha
Jun 15 '16 at 11:00
add a comment |
Probably your .bashrc or .profile is messedup.
Your gedit will not start if it is not in path and since your path is empty it is not in the path.
You should first establish a good enough path.
export PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
And then you should be able to start gedit. Alternativelly you could just run gedit with its whole path. Like:
/usr/bin/gedit
answered Jun 13 '16 at 8:35
E. TimoteiE. Timotei
1166
Probably your .bashrc or .profile is messedup.
Your gedit will not start if it is not in path and since your path is empty it is not in the path.
You should first establish a good enough path.
export PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
And then you should be able to start gedit. Alternativelly you could just run gedit with its whole path. Like:
/usr/bin/gedit
answered Jun 13 '16 at 8:35
E. TimoteiE. Timotei
1166
answered Jun 13 '16 at 8:35
E. TimoteiE. Timotei
1166
answered Jun 13 '16 at 8:35
E. TimoteiE. Timotei
1166
answered Jun 13 '16 at 8:35
E. TimoteiE. Timotei
1166
1166
Thank you very much indeed. At least I can start to debug by running command lines.
– James Wong
Jun 13 '16 at 10:50
@JamesWong the error message suggests it's runningexport $PATHinstead ofexport PATH, so look for that in particular.
– geirha
Jun 15 '16 at 11:00
add a comment |
Thank you very much indeed. At least I can start to debug by running command lines.
– James Wong
Jun 13 '16 at 10:50
@JamesWong the error message suggests it's runningexport $PATHinstead ofexport PATH, so look for that in particular.
– geirha
Jun 15 '16 at 11:00
Thank you very much indeed. At least I can start to debug by running command lines.
– James Wong
Jun 13 '16 at 10:50
Thank you very much indeed. At least I can start to debug by running command lines.
– James Wong
Jun 13 '16 at 10:50
@JamesWong the error message suggests it's running
export $PATH instead of export PATH, so look for that in particular.– geirha
Jun 15 '16 at 11:00
@JamesWong the error message suggests it's running
export $PATH instead of export PATH, so look for that in particular.– geirha
Jun 15 '16 at 11:00
add a comment |
looks like you have a different tick at the start than at the end. can you
sudo gedit ~/.bashrc?– TmTron
Jun 13 '16 at 8:31
Ye just change your ` to a normal ' and it should work fine.
– Ziazis
Jun 13 '16 at 8:31
Did you try to edit your
~/.bashrcand~/.profileby another user with enough privileges?– gwarah
Jun 13 '16 at 8:32
1
Btw. since your $PATH isn't working you have to tell the shell exactly where which command is. That means you would need to write something like /usr/bin/sudo /bin/vi /home/user/.bashrc or .profile and correct the issues
– Ziazis
Jun 13 '16 at 8:36