Uploaded image for project: 'Service Design and Creation'
  1. Service Design and Creation
  2. SDC-12

SDC service fails, SDC BE container is not coming up

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • None
    • None

      In our environment SDC BE is in fail state and log showing following error. Issue remains same even after removing all containers (sdc-BE   sdc-cs   sdc-es   sdc-FE   sdc-kbn ) and restarting service

       service asdc_serv start

       

      Error in file asdc_serv.sh.log

       

      FE health-Check:
      {
      "sdcVersion": "UNKNOWN",
      "siteMode": "UNKNOWN",
      "componentsInfo": [
      {
      "healthCheckComponent": "FE",
      "healthCheckStatus": "UP",
      "version": "1.0.0",
      "description": "OK"
      },
      {
      "healthCheckComponent": "BE",
      "healthCheckStatus": "DOWN"
      },
      {
      "healthCheckComponent": "ES",
      "healthCheckStatus": "UNKNOWN"
      },
      {
      "healthCheckComponent": "TITAN",
      "healthCheckStatus": "UNKNOWN"
      },
      {
      "healthCheckComponent": "DE",
      "healthCheckStatus": "UNKNOWN"
      }
      ]
      }

      Error [12] while user existance check

       

      Error in /root/chef-solo/cache/chef-stacktrace.out  (attached)

      Generated at 2017-04-14 18:37:31 +0000
      Mixlib::ShellOut::ShellCommandFailed: bash[upgrade-normatives] (sdc-normatives::upgrade_Normatives line 7) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
      ---- Begin output of "bash" "/tmp/jetty/chef-script20170414-514-1jpzctp" ----

            surajbisht surajbisht
            surajbisht surajbisht
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: