Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-1619

FIWARE.Request.Tech.Data.BigData-Analysis.CannotInstallCosmosMasterNodeWithoutErrors

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None
    • HD-Chapter:
      Data
    • HD-Enabler:
      Cosmos

      Description

      Responsible: fiware@ulpgc.es

      Tested GE(s): BigData Analysis - Cosmos GE

      Environment:

      • Local (Virtualized machines)
        Host Operating System: Ubuntu Server 14.04.1 (64 bits)
        Virtualization software: Kernel-based Virtual Machine 3.13.0-32-generic
        Virtual Machines Operating System: CentOS 6.5 (64 bits)

      Links:
      http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/BigData_Analysis_-_Installation_and_Administration_Guide

      Description:
      While following the installation instructions in the Installation and
      Administration Guide we found that we cannot install the master node
      without installation errors. We execute the command indicated in “Step 7:
      Applying puppet” from root user as you can see below:

      $puppet apply --debug --verbose --modulepath
      puppet/modules/:puppet/modules_third_party/:rpms/ --environment cosmos
      --hiera_config puppet/modules/cosmos/manifests/hiera.yaml --manifestdir
      puppet/modules/cosmos/manifests/ puppet/modules/cosmos/manifests/site.pp >
      puppet.out 2> puppet.err

      The error that appears is

      Error: /Stage[main]/Cosmos::Setup/Exec[cosmos-setup]: Failed to call
      refresh: /opt/pdi-cosmos/cosmos-admin/cosmos-admin setup returned 255
      instead of one of [0]
      Error: /Stage[main]/Cosmos::Setup/Exec[cosmos-setup]:
      /opt/pdi-cosmos/cosmos-admin/cosmos-admin setup returned 255 instead of one
      of [0]

      When we run /opt/pdi-cosmos/cosmos-admin/cosmos-admin setup we receive the
      following ouput:

      1. /opt/pdi-cosmos/cosmos-admin/cosmos-admin setup
        SLF4J: Class path contains multiple SLF4J bindings.
        SLF4J: Found binding in
        [jar:file:/opt/pdi-cosmos/cosmos-admin/lib/logback-classic-1.0.13.jar!/org/slf4j/impl/StaticLoggerBinder.class]
        SLF4J: Found binding in
        [jar:file:/opt/pdi-cosmos/cosmos-api/lib/ch.qos.logback.logback-classic-1.0.13.jar!/org/slf4j/impl/StaticLoggerBinder.class]
        SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
        explanation.
        10:44:10,522 |-INFO in ch.qos.logback.classic.LoggerContext[default] -
        Could NOT find resource [logback.groovy]
        10:44:10,522 |-INFO in ch.qos.logback.classic.LoggerContext[default] -
        Could NOT find resource [logback-test.xml]
        10:44:10,522 |-INFO in ch.qos.logback.classic.LoggerContext[default] -
        Found resource [logback.xml] at
        [jar:file:/opt/pdi-cosmos/cosmos-admin/lib/play_2.10-2.2.2-RC2.jar!/logback.xml]
        10:44:10,522 |-WARN in ch.qos.logback.classic.LoggerContext[default] -
        Resource [logback.xml] occurs multiple times on the classpath.
        10:44:10,522 |-WARN in ch.qos.logback.classic.LoggerContext[default] -
        Resource [logback.xml] occurs at
        [jar:file:/opt/pdi-cosmos/cosmos-admin/lib/play_2.10-2.2.2-RC2.jar!/logback.xml]
        10:44:10,522 |-WARN in ch.qos.logback.classic.LoggerContext[default] -
        Resource [logback.xml] occurs at
        [jar:file:/opt/pdi-cosmos/cosmos-api/lib/com.typesafe.play.play_2.10-2.2.2-RC2.jar!/logback.xml]
        10:44:10,539 |-INFO in
        ch.qos.logback.core.joran.spi.ConfigurationWatchList@5ed4dbe8 - URL
        [jar:file:/opt/pdi-cosmos/cosmos-admin/lib/play_2.10-2.2.2-RC2.jar!/logback.xml]
        is not of type file
        10:44:10,669 |-INFO in
        ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute
        not set
        10:44:10,678 |-INFO in ch.qos.logback.core.joran.action.AppenderAction -
        About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
        10:44:10,683 |-INFO in ch.qos.logback.core.joran.action.AppenderAction -
        Naming appender as [STDOUT]
        10:44:10,735 |-INFO in
        ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default
        type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder]
        property
        10:44:10,796 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction
      • Setting level of ROOT logger to ERROR
        10:44:10,796 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction -
        Attaching appender named [STDOUT] to Logger[ROOT]
        10:44:10,796 |-INFO in
        ch.qos.logback.classic.joran.action.ConfigurationAction - End of
        configuration.
        10:44:10,798 |-INFO in
        ch.qos.logback.classic.joran.JoranConfigurator@68b18cfb - Registering
        current configuration as safe fallback point

      SLF4J: Actual binding is of type
      [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
      [info] play - database [default] connected at
      jdbc:mysql://localhost:3306/cosmos
      [info] play - Application started (Prod)
      Persistent Storage Terminated. Not changing anything...

      The previous output does not lead us to where could be the issue. We will
      copy below both puppet.out and puppet.err logs content for further
      reference.

      Logs content:
      puppet.err
      Warning: The use of 'import' is deprecated at
      /home/root/cosmos/puppet/modules/cosmos/manifests/site.pp:13. See
      http://links.puppetlabs.com/puppet-import-deprecation

      (at /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser_support.rb:110:in
      `import')

      Warning: The package type's allow_virtual parameter will be changing its
      default value from false to true in a future release. If you do not want to
      allow virtual packages, please explicitly set allow_virtual to false.

      (at /usr/lib/ruby/site_ruby/1.8/puppet/type/package.rb:430:in `default')

      Error: /Stage[main]/Cosmos::Setup/Exec[cosmos-setup]: Failed to call
      refresh: /opt/pdi-cosmos/cosmos-admin/cosmos-admin setup returned 255
      instead of one of [0]

      Error: /Stage[main]/Cosmos::Setup/Exec[cosmos-setup]:
      /opt/pdi-cosmos/cosmos-admin/cosmos-admin setup returned 255 instead of one
      of [0]

      puppet.out
      Attached in the ticket as it has more than 2500 lines.

      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-lab-help

      1. puppet.out
        265 kB
        Pablo Fernandez Moniz

        Activity

        Hide
        frb Francisco Romero added a comment -

        Cosmos implementation is no longer supported for new installations since the Big Data GE implementation is going to move to Openstack's Sahara (https://wiki.openstack.org/wiki/Sahara).

        Show
        frb Francisco Romero added a comment - Cosmos implementation is no longer supported for new installations since the Big Data GE implementation is going to move to Openstack's Sahara ( https://wiki.openstack.org/wiki/Sahara ).

          People

          • Assignee:
            frb Francisco Romero
            Reporter:
            pablo.fernandez Pablo Fernandez Moniz
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: