Details

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

      Description

      Hello

      I'm representing SENTIO and having an issue with Perseo.
      I'm using docker compose (see attached file) to run Fiware components and I
      get the following log output:

      perseo-fe_1 | the server/replset/mongos options are deprecated, all
      their options are supported at the top level of the options object
      [poolSize,ssl,sslValidate,sslCA,sslCert,ciphers,ecdhCurve,sslKey,sslPass,sslCRL,autoReconnect,noDelay,keepAlive,connectTimeoutMS,family,socketTimeoutMS,reconnectTries,reconnectInterval,ha,haInterval,replicaSet,secondaryAcceptableLatencyMS,acceptableLatencyMS,connectWithNoPrimary,authSource,w,wtimeout,j,forceServerObjectId,serializeFunctions,ignoreUndefined,raw,bufferMaxEntries,readPreference,pkFactory,promiseLibrary,readConcern,maxStalenessSeconds,loggerLevel,logger,promoteValues,promoteBuffers,promoteLongs,domainsEnabled,keepAliveInitialDelay,checkServerIdentity,validateOptions,appname,auth]
      perseo-fe_1 | time=2018-07-04T12:57:59.981Z | lvl=INFO | corr=n/a |
      trans=n/a | op=initialRefresh | comp=perseo-fe | srv=n/a | subsrv=n/a |
      msg=rulesStore.FindAll []
      perseo-fe_1 | time=2018-07-04T12:57:59.981Z | lvl=INFO | corr=n/a |
      trans=n/a | op=initialRefresh | comp=perseo-fe | srv=n/a | subsrv=n/a |
      msg=making put to http://192.168.99.100:8080/perseo-core/rules
      perseo-fe_1 | time=2018-07-04T12:58:00.005Z | lvl=ERROR | corr=n/a |
      trans=n/a | op=initialRefresh | comp=perseo-fe | srv=n/a | subsrv=n/a |
      msg=error put to http://192.168.99.100:8080/perseo-core/rules socket hang up
      perseo-fe_1 | time=2018-07-04T12:58:00.005Z | lvl=ERROR | corr=n/a |
      trans=n/a | op=initialRefresh | comp=perseo-fe | srv=n/a | subsrv=n/a |
      msg=[object Object] socket hang up
      perseo-fe_1 | time=2018-07-04T12:58:00.010Z | lvl=INFO | corr=n/a |
      trans=n/a | op=perseo | comp=perseo-fe | srv=n/a | subsrv=n/a |
      msg=starting perseo
      perseo-fe_1 | time=2018-07-04T12:58:00.010Z | lvl=FATAL | corr=n/a |
      trans=n/a | op=perseo | comp=perseo-fe | srv=n/a | subsrv=n/a | msg=socket
      hang up
      fiware_perseo-fe_1 exited with code 255

      It seems that it doesn't depend on perseo-core properly as this runs before
      any log is shown from perseo-core.
      My docker compose file is based upon the following stackoverflow answer:
      https://stackoverflow.com/questions/50922739/error-installing-fiware-perseo

      Thanks in advance.

      Best regards
      Simon

      __________________________________________________________________________________________

      You can get more information about our cookies and privacy policies on the following links:

      Fiware-tech-help mailing list
      Fiware-tech-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-tech-help

      [Created via e-mail received from: Simon Bechmann <sb@seriousgames.net>]

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        4d 17h 44m 1 Rafael Fernández 09/Jul/18 9:13 AM
        In Progress In Progress Answered Answered
        3s 1 Rafael Fernández 09/Jul/18 9:13 AM
        Answered Answered Closed Closed
        4d 4h 8m 1 Rafael Fernández 13/Jul/18 1:21 PM

          People

          • Assignee:
            rfernandez Rafael Fernández
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: