How to Troubleshoot commands that fails

[Ricky B. Nino]

Hi,

Just recently have experienced issuing a command in my system that works before and now it fails. The error message is ... NOT FOUND!

for example...
# make_tape_recovery -Av

After a system reboot it works again.

Anyways I can find the root cause and fix the problem without system reboot?

regards...

[S.K. Chan · Accepted solution]

Most of the time it's due to the $PATH environment var that does not have the directory path of where "make_tape_recovery" command is located .. hence the error NOT FOUND. For instance in this example, make_tape_recovery is in /opt/ignite/bin, check $PATH and see if /opt/ignite/bin is included in the path.
# env|grep PATH
Look for something like ..
..
PATH=/bin:/usr/bin:..
....
If it's not there (the path), you got to include it in root's profile. Another possibility is if you are already in the directory /opt/ignite/bin then it should be run like so ..
# ./make_tape_recovery
that is with a "./" in front of it.

[Michael Tully]

You will find that the command is not in your path and most likely not in the default system path i.e. /etc/PATH

To check:
# echo $PATH

You can use the 'whereis' command to find programs etc.

Add it to the default system path or you can add it as you need it.
# PATH=$PATH:/opt/ignite/bin ; export PATH

[Manju Kampli]

command not found error is due to the fact that the system could not find the command with in the search PATH .. there are two ways you can solve it .. use the full path when running command
i.e. /opt/ignite/bin/make_recovery ... OR
in your home dir edit .profile and add the /opt/ignite/bin to the PATH variable

The second option is preferred as it will keep this permanent and you don't have to type the full path again and again.
HTH
Manju

[Ricky B. Nino]

Guys,

1. Aside from intentionally/ accidentally changing the PATH variable any possible reason/s why PATH have changed?

Have not changed the PATH when I encountered the problem. Just rebooted the system then everything goes well.

2. Is the man pages related to this kind of problem?

thanks...

[RAC_1]

you can define path from /etc/profile or in /etc/PATH file. now check if have some issues with that.

do not know if both are present and varies then which one takes precedence?.

[Manju Kampli]

Hello Ricky,

If you haven't changed any thing and command worked after the reboot does not make sense..

did you update the PATH in .profile and run the command with out logout and login .. The reboot would have done this ..
Once you change the .profile you need to logout and login again to take the effect OR execute it using ". ./.profile" from your home directory

- Manju

[Ricky B. Nino]

Hi Manju,

As I have mentioned I really never did anything prior and after my system reboot to the PATH variable.

Anyways, many thanks for the ideas...

[John Meissner]

if you type:
#command
and it doesn't work... try:
#./command
if it works that time then you need to enter the "." (pwd) into your path statement. Wheather or not you did something to your .profile doesn't mean that someone else didn't .

[Jean-Louis Phelix]

Hi,

In fact I agree with you, if nothing has changed on your system, the "static" configuration defined in /etc/PATH, /etc/profile or $HOME/.profile should be good. So, first try should have been to logout and login to see if a script which could modify you $PATH had been sourced using a '.' command.

Regards.