CentOS 6.9的AWS EC2实例执行/usr/bin/curator报无法识别可执行文件错误求助

Let's work through this error step by step—here are the most likely causes and fixes:

1. Verify the Curator executable exists and has proper permissions #

First, confirm if the /usr/bin/curator file actually exists and has executable rights:

ls -l /usr/bin/curator

• If the file doesn’t appear at all, your Curator installation didn’t complete successfully. Reinstall using your preferred method (yum/pip) and watch for errors during the process.
• If the file exists but lacks the executable permission (no x in the permission string, e.g., -rw-r--r--), fix it with:

  chmod +x /usr/bin/curator
  

2. Check Python compatibility and shebang line #

CentOS 6.9 ships with Python 2.6 by default, but newer Curator versions (5.x+) require Python 3. Let’s check the script’s Python dependency:

head -1 /usr/bin/curator

• If the output is #!/usr/bin/python3 and you don’t have Python 3 installed, you have two options:
  1. Install Python 3 on your CentOS 6 system, then reinstall Curator for Python 3.
  2. Downgrade to a Curator version compatible with Python 2.6 (e.g., 4.3.1):

     pip uninstall elasticsearch-curator
     pip install elasticsearch-curator==4.3.1
     

• If the shebang points to a non-existent Python path (e.g., #!/usr/local/bin/python which doesn’t exist), update it to point to your system’s valid Python binary (e.g., #!/usr/bin/python).

3. Rule out SELinux restrictions #

CentOS 6 enables SELinux in enforcing mode by default, which can block executable files unexpectedly:

getenforce

• If the output is Enforcing, temporarily disable SELinux to test:

  setenforce 0
  

  Run /usr/bin/curator again. If it works, fix the SELinux context for the Curator file to make the change permanent:

  chcon -t bin_t /usr/bin/curator
  

4. Check root volume mount options #

Since your root volume is EBS, double-check that it wasn’t mounted with the noexec flag (which prevents executing files on the filesystem):

mount | grep '/ '

• Look for noexec in the mount options (e.g., rw,noexec,relatime). If present, remount the root volume without the flag:

  mount -o remount,rw /
  

  Then edit /etc/fstab to remove noexec from the root volume’s mount line so the fix persists after reboot.

5. Reinstall Curator to fix corrupted files #

If none of the above works, a corrupted installation might be the issue. Uninstall and reinstall properly:

• For yum installations:

  yum remove elasticsearch-curator
  yum install elasticsearch-curator
  

• For pip installations (ensure you’re using the correct Python pip):

  pip uninstall elasticsearch-curator
  pip install elasticsearch-curator==4.3.1  # For Python 2.6 compatibility
  

内容的提问来源于stack exchange，提问作者Satish Lokhande