Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-3797

Mariadb Galera Cluster stack_bottom = 0x0 thread_stack 0x30000

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 5.5.25-galera
    • None
    • None
    • Debian Squeeze amd64 on a qemu VM.

    Description

      I attached the complete terminal steps and the small tutorial I made. In /var/lib/mysql/kooka1h.err :

      121005 15:18:22 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
      121005 15:18:22 [ERROR] An old style --language value with language specific part detected: /usr/share/mysql/english/
      121005 15:18:22 [ERROR] Use --lc-messages-dir without language specific part instead.
      121005 15:18:22 [ERROR] mysqld got signal 11 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.

      To report this bug, see http://kb.askmonty.org/en/reporting-bugs

      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed,
      something is definitely wrong and this may fail.

      Server version: 5.5.25-MariaDB
      key_buffer_size=0
      read_buffer_size=131072
      max_used_connections=0
      max_threads=153
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 335099 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0x0
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x0 thread_stack 0x30000

      Attachments

        Activity

          That works very well except for the init script. It doesn't accept the start command. I have that line in my error log:

          /usr/local/mysql/bin/mysqld: Too many arguments (first extra is 'start').
          121122 18:26:07 [ERROR] Aborting

          '/usr/local/mysql/bin/mysqld' alone works but '/usr/local/mysql/bin/mysqld start' not.
          The problem is I call the init script like that:
          /etc/init.d/mysql start

          Thanks.

          michee.lengronne Michée Lengronne added a comment - That works very well except for the init script. It doesn't accept the start command. I have that line in my error log: /usr/local/mysql/bin/mysqld: Too many arguments (first extra is 'start'). 121122 18:26:07 [ERROR] Aborting '/usr/local/mysql/bin/mysqld' alone works but '/usr/local/mysql/bin/mysqld start' not. The problem is I call the init script like that: /etc/init.d/mysql start Thanks.

          I made my own init script which works but I have another problem:

          121122 19:21:44 [Note] WSREP: Running: 'wsrep_sst_rsync_wan 'joiner' '10.111.200.9' '' '/usr/local/mysql/data/' '/etc/mysql/my.cnf' '1329''
          sh: wsrep_sst_rsync_wan: not found
          121122 19:21:44 [ERROR] WSREP: Failed to read 'ready <addr>' from: wsrep_sst_rsync_wan 'joiner' '10.111.200.9' '' '/usr/local/mysql/data/' '/etc/mysql/my.cnf' '1329'
          Read: '(null)'

          when I try to connect a server to the first server.

          Can you help me ?

          Thanks again.

          michee.lengronne Michée Lengronne added a comment - I made my own init script which works but I have another problem: 121122 19:21:44 [Note] WSREP: Running: 'wsrep_sst_rsync_wan 'joiner' '10.111.200.9' '' '/usr/local/mysql/data/' '/etc/mysql/my.cnf' '1329'' sh: wsrep_sst_rsync_wan: not found 121122 19:21:44 [ERROR] WSREP: Failed to read 'ready <addr>' from: wsrep_sst_rsync_wan 'joiner' '10.111.200.9' '' '/usr/local/mysql/data/' '/etc/mysql/my.cnf' '1329' Read: '(null)' when I try to connect a server to the first server. Can you help me ? Thanks again.
          elenst Elena Stepanova added a comment - - edited

          Regarding the script, if I remember correctly (I don't have that installation currently) your algorithm causes /etc/init.d/mysql to be a link to mysqld_safe, which of course doesn't have 'start' command.

          For the error above, it's just what it says: there is no wsrep_sst_rsync_wan script in the current package. Try to use wsrep_sst_method=rsync instead of wsrep_sst_method=rsync_wan

          elenst Elena Stepanova added a comment - - edited Regarding the script, if I remember correctly (I don't have that installation currently) your algorithm causes /etc/init.d/mysql to be a link to mysqld_safe, which of course doesn't have 'start' command. For the error above, it's just what it says: there is no wsrep_sst_rsync_wan script in the current package. Try to use wsrep_sst_method=rsync instead of wsrep_sst_method=rsync_wan

          It works !!!! Thanks a lot.

          michee.lengronne Michée Lengronne added a comment - It works !!!! Thanks a lot.

          I will close the report then, please open a new one if you observe further problems

          elenst Elena Stepanova added a comment - I will close the report then, please open a new one if you observe further problems

          People

            elenst Elena Stepanova
            michee.lengronne Michée Lengronne
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.