Installing A Web, Email And MySQL Database Cluster (Mirror) On Ubuntu 14.04 With ISPConfig 3

Discussion in 'Installation/Configuration' started by MQuintana, Apr 7, 2016.

  1. MQuintana

    MQuintana New Member

    I am using this site https://www.howtoforge.com/installi...tabase-cluster-on-debian-5.0-with-ispconfig-3 how to a guide, but I have problems with the settings when configure mysql database in both servers. Receive the followings Errors:
    ==> mysql/error.log <==
    InnoDB: using the same InnoDB data or log files.
    InnoDB: Unable to lock ./ibdata1, error: 11
    InnoDB: Check that you do not already have another mysqld process
    InnoDB: using the same InnoDB data or log files.
    160407 18:41:30 InnoDB: Unable to open the first data file
    InnoDB: Error in opening ./ibdata1
    160407 18:41:30 InnoDB: Operating system error number 11 in a file operation.

    InnoDB: Error number 11 means 'Resource temporarily unavailable'.
    InnoDB: Some operating system error numbers are described at
    InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
    160407 18:41:30 InnoDB: Could not open or create data files.
    160407 18:41:30 InnoDB: If you tried to add new data files, and it failed here,
    160407 18:41:30 InnoDB: you should now edit innodb_data_file_path in my.cnf back
    160407 18:41:30 InnoDB: to what it was, and remove the new ibdata files InnoDB created
    160407 18:41:30 InnoDB: in this failed attempt. InnoDB only wrote those files full of
    160407 18:41:30 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
    160407 18:41:30 InnoDB: remove old data files which contain your precious data!
    160407 18:41:30 [ERROR] Plugin 'InnoDB' init function returned error.
    160407 18:41:30 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

    160407 18:41:30 [ERROR] Unknown/unsupported storage engine: InnoDB
    160407 18:41:30 [ERROR] Aborting
    160407 18:41:30 [Note] /usr/sbin/mysqld: Shutdown complete
    ==> /etc/mysql/my.cnf <== "Configuration file" ======>
    The #skip-innodb is commented because if is uncommented the mysql process fail.
    #
    # The MySQL database server configuration file.
    #
    # You can copy this to one of:
    # - "/etc/mysql/my.cnf" to set global options,
    # - "~/.my.cnf" to set user-specific options.
    #
    # One can use all long options that the program supports.
    # Run program with --help to get a list of available options and with
    # --print-defaults to see which it would actually understand and use.
    #
    # For explanations see
    # http://dev.mysql.com/doc/mysql/en/server-system-variables.html

    # This will be passed to all mysql clients
    # It has been reported that passwords should be enclosed with ticks/quotes
    # escpecially if they contain "#" chars...
    # Remember to edit /etc/mysql/debian.cnf when changing the socket location.
    [client]
    port = 3306
    socket = /var/run/mysqld/mysqld.sock

    # Here is entries for some specific programs
    # The following values assume you have at least 32M ram

    # This was formally known as [safe_mysqld]. Both versions are currently parsed.
    [mysqld_safe]
    socket = /var/run/mysqld/mysqld.sock
    nice = 0

    [mysqld]
    #
    # * Basic Settings
    #
    user = mysql
    pid-file = /var/run/mysqld/mysqld.pid
    socket = /var/run/mysqld/mysqld.sock
    port = 3306
    basedir = /usr
    datadir = /var/lib/mysql
    tmpdir = /tmp
    lc-messages-dir = /usr/share/mysql
    skip-external-locking
    #skip-innodb
    innodb_file_per_table


    #
    # Instead of skip-networking the default is now to listen only on
    # localhost which is more compatible and is not less secure.
    #bind-address = 127.0.0.1
    #
    # * Fine Tuning
    #
    key_buffer = 16M
    max_allowed_packet = 16M
    thread_stack = 192K
    thread_cache_size = 8
    # This replaces the startup script and checks MyISAM tables if needed
    # the first time they are touched
    myisam-recover = BACKUP
    #max_connections = 100
    #table_cache = 64
    #thread_concurrency = 10
    #
    # * Query Cache Configuration
    #
    query_cache_limit = 1M
    query_cache_size = 16M
    #
    # * Logging and Replication
    #
    # Both location gets rotated by the cronjob.
    # Be aware that this log type is a performance killer.
    # As of 5.1 you can enable the log at runtime!
    #general_log_file = /var/log/mysql/mysql.log
    #general_log = 1
    #
    # Error log - should be very few entries.
    #
    log_error = /var/log/mysql/error.log
    #
    # Here you can see queries with especially long duration
    #log_slow_queries = /var/log/mysql/mysql-slow.log
    #long_query_time = 2
    #log-queries-not-using-indexes
    #
    # The following can be used as easy to replay backup logs or for replication.
    # note: if you are setting up a replication slave, see README.Debian about
    # other settings you may need to change.
    #server-id = 1
    #log_bin = /var/log/mysql/mysql-bin.log
    expire_logs_days = 10
    max_binlog_size = 100M
    #binlog_do_db = include_database_name
    #binlog_ignore_db = include_database_name
    #
    # * InnoDB
    #
    # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
    # Read the manual for more InnoDB related options. There are many!
    #
    # * Security Features
    #
    # Read the manual, too, if you want chroot!
    # chroot = /var/lib/mysql/
    #
    # For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
    #
    # ssl-ca=/etc/mysql/cacert.pem
    # ssl-cert=/etc/mysql/server-cert.pem
    # ssl-key=/etc/mysql/server-key.pem



    [mysqldump]
    quick
    quote-names
    max_allowed_packet = 16M

    [mysql]
    #no-auto-rehash # faster start of mysql but no tab completition

    [isamchk]
    key_buffer = 16M

    #
    # * IMPORTANT: Additional settings that can override those from this file!
    # The files must end with '.cnf', otherwise they'll be ignored.
    #
     
  2. danhansen@denmark

    danhansen@denmark Member HowtoForge Supporter

    Hi,

    Had a similar issue using ubuntu 12.04/14.04 and mysql. Did you ever find a solution?
     

Share This Page