some /usr/bin commands like find do not work properly, hoy to rebuild them?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Alright. Atleast we now have some direction. Either there is something wrong with /usr/bin/find itself because updatedb command require /usr/bin/find or something wrong with PATH variable. I am assuming you are logged in as root and if you are doing su then you are doing that by typing: su - root
Are both cluster servers are on same version? If yes, then try this rename find on the problematic server as follows:
Code:
mv /usr/bin/find /usr/bin/find.old
Once done copy over the find from other server to this server under /usr/bin
If it still does not work then it is not find binary issue rather an issue with your profile or with PATH variable.
Last edited by T3RM1NVT0R; 01-05-2012 at 12:33 PM.
Edit perms/ownerships on new find to match orig and/or the other (working) server.
You may also need to fix the SELinux settings if you have that. Try 'ls -lZ' to see.
cluster2:/ # updatedb
/usr/bin/find: /: No such file or directory
cluster2:/ # ls -lZ
/bin/ls: invalid option -- Z
Try `/bin/ls --help' for more information.
Well, permissiones where different, but now are equal on both servers (755). But as you can see above, updatedb continues with problems.
Your version of ls apparently doesn't support the -Z option. When you see an error message, try to heed it. In this case reissue the command with "ls -l" instead.
find binary permissions look ok. But here is something unusual that I see in your previous post:
Code:
cluster2:~ # updatedb
/usr/bin/updatedb: line 203: /usr/bin/find: Permission denied
Try this:
1. Rename existing /usr/bin/updatedb /usr/bin/updatedb.old
2. I have attached updatedb.txt file with this post. So rename it from updatedb.txt updatedb
3. Copy it to /usr/bin/
4. Run the command updatedb.
4. And then execute locate command as mentioned in previous posts.
If that does not work then paste the output of the following commands:
Code:
cat /usr/bin/updatedb
Run the above on problematic server and paste the output. Then run the same on working server and paste the output.
Alright we have tried everything so far and now it appears that the incident that took place on 22nd November really messed up the things. If possible could you reboot the server and paste the output of the following command:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.