Articles in this section

See more

Troubleshooting checklist

Avatar
Johan
  • Updated
Follow

If you have problems to run deploy.sh this may be helpful to nail down the issues:

  • Check 's9s_deploy.log' (located in your HOME folder of the user you are install as, e.g. /home/<myusername>/s9s_deploy.log. It shows if e.g, an RPM has failed to install and why.
  • EC2:  Upload your keypair to $EC2_KEYPAIR on the clustercontrol server
  • Verify you have installed libaoi1 (ubuntu: apt-get install libaio1 redhat: yum install libaio )
  • Verify SELinux settings, firewalls, and /etc/hosts
  • 'hostname -i' must not resolve to 127.0.0.1, or 127.0.1.1. If it does you must write /etc/hosts file.
  • 'hostname' must not resolve to 'localhost'. If it does you must write /etc/hosts file.
  • Check that you have disk space
  • Verify you can ping the hosts
  • Verify that you have enough RAM
  • Verify that you have enough cores for the MySQL Servers and Data Nodes (setting the number of Cores to more than you have affects stability and can cause lockups).
  • Verify that you haven't installed a 64-bit version on 32-bit machines
  • Verify that you haven't got any conflicting RPMs installed. Run ./uninstall-rpm.sh. E.g, it may be needed to remove php-mysql (rpm -e php-mysql from the ClusterController
And you are of course welcome to create a ticket and we will help you get going.

Related articles

Comments

2 comments

Sort by Date Votes
  • Avatar
    Steve Diaz

    Hello

    If you encounter issues running deploy.sh, follow these troubleshooting steps:

    1. Check 's9s_deploy.log': Review the 's9s_deploy.log' in your user's home folder to diagnose installation errors, especially any RPM installation failures.

    2. EC2 Key Pair: If using Amazon EC2, ensure your keypair is uploaded to the $EC2_KEYPAIR location on the ClusterControl server.

    3. Install libaio1: On Ubuntu, run apt-get install libaio1, and on Red Hat, use yum install libaio to install libaio1.

    4. System Configuration: Verify SELinux settings, firewall rules, and the /etc/hosts file to ensure proper system configuration.

    5. Hostname Resolution: Ensure 'hostname -i' doesn't resolve to 127.0.0.1 or 127.0.1.1. If it does, update the /etc/hosts file.

    6. Hostname: Your hostname should not resolve to 'localhost.' Adjust the /etc/hosts file if needed.

    7. Disk Space: Check available disk space on your servers.

    8. Network Connectivity: Confirm that you can ping the hosts without issues.

    9. RAM: Verify you have sufficient RAM for MySQL Servers and Data Nodes.

    10. CPU Cores: Ensure you have enough CPU cores for the MySQL Servers and Data Nodes. Avoid setting the core count higher than available, as it can lead to instability.

    11. 32-bit vs. 64-bit: Ensure software architecture matches your machine's architecture.

    12. Conflicting RPMs: Remove conflicting RPM packages if necessary using './uninstall-rpm.sh.' For example, 'rpm -e php-mysql' from the ClusterController.

    If problems persist, consider creating a support ticket http://support.severalnines.com/tickets/new/

    Thank you.

    0
    Comment actions Permalink
  • Avatar
    Sacde Haser

    Great insights! I appreciate the effort here.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk