Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-1965

1um2pm stack failed to start after being shut down

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 1.2.2
    • None
    • ?
    • None

    Description

      Build tested: 2018-11.25 nightly build, Lentos 7 RPM

      1. Installed 1um2pm stack
      2. create and loaded 1g DBT3 database
      3. ran select count on lineitem
      4. Shutdownsystem on pm1
      5. startsystem <password> on pm1

      mcsadmin> shutdownsystem
      shutdownsystem Mon Nov 26 14:57:58 2018

      This command stops the processing of applications on all Modules within the MariaDB ColumnStore System

      Checking for active transactions
      Do you want to proceed: (y or n) [n]: y

      Stopping System...
      Successful stop of System

      Shutting Down System...
      Successful shutdown of System

      mcsadmin> startsystem vagrant
      startsystem Mon Nov 26 14:58:59 2018

      startSystem command, 'columnstore' service is down, sending command to
      start the 'columnstore' service on all modules

      System being started, please wait........

      TIMEOUT: ProcMon not responding to getSystemStatus

            • startSystem Failed : check log files
              mcsadmin> getprocessstatus
              getprocessstatus Mon Nov 26 15:02:40 2018

      MariaDB ColumnStore Process statuses

      Process Module Status Last Status Change Process ID
      ------------------ ------ --------------- ------------------------ ----------
      ProcessMonitor um1 ACTIVE Mon Nov 26 14:59:33 2018 12948
      ServerMonitor um1 ACTIVE Mon Nov 26 14:59:52 2018 13396
      DBRMWorkerNode um1 FAILED Mon Nov 26 14:59:50 2018
      ExeMgr um1 INITIAL
      DDLProc um1 INITIAL
      DMLProc um1 INITIAL
      mysqld um1 ACTIVE Mon Nov 26 14:59:53 2018 13352

      ProcessMonitor pm1 ACTIVE Mon Nov 26 14:59:16 2018 2889
      ProcessManager pm1 ACTIVE Mon Nov 26 14:59:22 2018 3056
      DBRMControllerNode pm1 ACTIVE Mon Nov 26 14:59:47 2018 3684
      ServerMonitor pm1 ACTIVE Mon Nov 26 14:59:49 2018 3704
      DBRMWorkerNode pm1 ACTIVE Mon Nov 26 14:59:49 2018 3743
      PrimProc pm1 ACTIVE Mon Nov 26 14:59:53 2018 3877
      WriteEngineServer pm1 ACTIVE Mon Nov 26 14:59:54 2018 3921

      ProcessMonitor pm2 ACTIVE Mon Nov 26 14:59:40 2018 4373
      ProcessManager pm2 HOT_STANDBY Mon Nov 26 14:59:41 2018 4419
      DBRMControllerNode pm2 INITIAL
      ServerMonitor pm2 INITIAL
      DBRMWorkerNode pm2 INITIAL
      PrimProc pm2 INITIAL
      WriteEngineServer pm2 INITIAL
      mcsadmin> quit

      logs on pm1:

      [root@localhost columnstore]# cat crit.log
      Nov 26 14:59:57 localhost ProcessManager[3056]: 57.902720 |0|0|0| C 17 CAL0000: startMgrProcessThread Exit with a failure, error returned from startSystemThread
      [root@localhost columnstore]# cat err.log
      Nov 26 14:58:19 localhost controllernode[3278]: 19.063429 |0|0|0| E 29 CAL0000: DBRM: error: SessionManager::setSystemState() failed (network)
      Nov 26 14:58:19 localhost controllernode[3278]: 19.064352 |0|0|0| E 29 CAL0000: DBRM: error: SessionManager::setSystemState() failed (network)
      Nov 26 14:58:19 localhost controllernode[3278]: 19.971126 |0|0|0| E 29 CAL0000: DBRM: error: SessionManager::getSystemState() failed (network)
      Nov 26 14:59:57 localhost ProcessManager[3056]: 57.902720 |0|0|0| C 17 CAL0000: startMgrProcessThread Exit with a failure, error returned from startSystemThread

      Attachments

        Activity

          People

            dleeyh Daniel Lee (Inactive)
            dleeyh Daniel Lee (Inactive)
            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.