Guest User

Untitled

a guest
Mar 28th, 2016
189
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.54 KB | None | 0 0
  1. TASK: [mariadb | Running MariaDB bootstrap container] *************************
  2. <localhost> REMOTE_MODULE kolla_docker image=localhost:4000/kollaglue/ubuntu-source-mariadb:2.0.0 action=start_cont ainer restart_policy=never name=bootstrap_mariadb
  3. <localhost> EXEC ['/bin/sh', '-c', 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1459181030.46-249137949565922 && echo $ HOME/.ansible/tmp/ansible-tmp-1459181030.46-249137949565922']
  4. <localhost> PUT /tmp/tmpxRotmU TO /root/.ansible/tmp/ansible-tmp-1459181030.46-249137949565922/kolla_docker
  5. <localhost> EXEC ['/bin/sh', '-c', u'LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 /usr/bin/python /root/.ansible/tmp/ansib le-tmp-1459181030.46-249137949565922/kolla_docker; rm -rf /root/.ansible/tmp/ansible-tmp-1459181030.46-249137949565 922/ >/dev/null 2>&1']
  6. failed: [localhost] => {"changed": true, "failed": true}
  7. msg: Container exited with non-zero return code
  8.  
  9. FATAL: all hosts have already failed -- aborting
  10.  
  11. root@ubuntu:~/kolla# docker logs bootstrap_mariadb
  12. INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
  13. INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
  14. INFO:__main__:Validating config file
  15. INFO:__main__:Copying service configuration files
  16. INFO:__main__:Removing existing destination: /etc/mysql/my.cnf
  17. INFO:__main__:Copying /var/lib/kolla/config_files/galera.cnf to /etc/mysql/my.cnf
  18. INFO:__main__:Setting permissions for /etc/mysql/my.cnf
  19. INFO:__main__:Writing out command to execute
  20. Installing MariaDB/MySQL system tables in '/var/lib/mysql/' ...
  21. 160328 16:03:51 [Note] /usr/sbin/mysqld (mysqld 10.0.24-MariaDB-1~trusty-wsrep) starting as process 33 ...
  22. OK
  23. Filling help tables...
  24. 160328 16:03:55 [Note] /usr/sbin/mysqld (mysqld 10.0.24-MariaDB-1~trusty-wsrep) starting as process 60 ...
  25. OK
  26.  
  27. To start mysqld at boot time you have to copy
  28. support-files/mysql.server to the right place for your system
  29.  
  30. PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
  31. To do so, start the server, then issue the following commands:
  32.  
  33. '/usr/bin/mysqladmin' -u root password 'new-password'
  34. '/usr/bin/mysqladmin' -u root -h ubuntu password 'new-password'
  35.  
  36. Alternatively you can run:
  37. '/usr/bin/mysql_secure_installation'
  38.  
  39. which will also give you the option of removing the test
  40. databases and anonymous user created by default. This is
  41. strongly recommended for production servers.
  42.  
  43. See the MariaDB Knowledgebase at http://mariadb.com/kb or the
  44. MySQL manual for more instructions.
  45.  
  46. You can start the MariaDB daemon with:
  47. cd '/usr' ; /usr/bin/mysqld_safe --datadir='/var/lib/mysql/'
  48.  
  49. You can test the MariaDB daemon with mysql-test-run.pl
  50. cd '/usr/mysql-test' ; perl mysql-test-run.pl
  51.  
  52. Please report any problems at http://mariadb.org/jira
  53.  
  54. The latest information about MariaDB is available at http://mariadb.org/.
  55. You can find additional information about the MySQL part at:
  56. http://dev.mysql.com
  57. Support MariaDB development by buying support/new features from MariaDB
  58. Corporation Ab. You can contact us about this at [email protected].
  59. Alternatively consider joining our community based development effort:
  60. http://mariadb.com/kb/en/contributing-to-the-mariadb-project/
  61.  
  62. 160328 16:03:59 mysqld_safe Logging to '/var/log/kolla/mariadb/mariadb.log'.
  63. 160328 16:03:59 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
  64. 160328 16:03:59 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql//wsrep_recovery.ac9FAa' --pid-file='/var/lib/mysql//ubuntu-recover.pid'
  65. 160328 16:04:01 mysqld_safe WSREP: Failed to recover position: '160328 16:03:59 [Note] InnoDB: Using mutexes to ref count buffer pool pages
  66. 160328 16:03:59 [Note] InnoDB: The InnoDB memory heap is disabled
  67. 160328 16:03:59 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  68. 160328 16:03:59 [Note] InnoDB: Memory barrier is not used
  69. 160328 16:03:59 [Note] InnoDB: Compressed tables use zlib 1.2.8
  70. 160328 16:03:59 [Note] InnoDB: Using Linux native AIO
  71. 160328 16:03:59 [Note] InnoDB: Using CPU crc32 instructions
  72. 160328 16:03:59 [Note] InnoDB: Initializing buffer pool, size = 128.0M
  73. 160328 16:03:59 [Note] InnoDB: Completed initialization of buffer pool
  74. 160328 16:03:59 [Note] InnoDB: Highest supported file format is Barracuda.
  75. 160328 16:03:59 [Note] InnoDB: 128 rollback segment(s) are active.
  76. 160328 16:03:59 [Note] InnoDB: Waiting for purge to start
  77. 160328 16:03:59 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 1616707
  78. 160328 16:03:59 [Warning] InnoDB: Skipping buffer pool dump/restore during wsrep recovery.
  79. 160328 16:03:59 [Note] Plugin 'FEEDBACK' is disabled.
  80. 160328 16:03:59 [Note] Server socket created on IP: '10.102.22.89'.
  81. 160328 16:03:59 [ERROR] Can't start server: listen() on TCP/IP port: Address already in use
  82. 160328 16:03:59 [ERROR] listen() on TCP/IP failed with error 98
  83. 160328 16:03:59 [ERROR] Aborting
  84.  
  85. 160328 16:03:59 [Note] InnoDB: FTS optimize thread exiting.
  86. 160328 16:03:59 [Note] InnoDB: Starting shutdown...
  87. 160328 16:04:01 [Note] InnoDB: Shutdown completed; log sequence number 1616717
  88. 160328 16:04:01 [Note] /usr/sbin/mysqld: Shutdown complete'
Advertisement
Add Comment
Please, Sign In to add comment