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

        Hide
        fw.ext.user FW External User added a comment -

        Hi Simon,

        I'm testing your docker compose file and if I use docker's internal
        references instead of those hardcoded IP addresses, it works fine.

        I mean:

        perseo-core:
        image: fiware/perseo-core
        ports:

        perseo-fe:
        image: fiware/perseo
        ports:

        Hope it helps!

        Best regards
        Rafael

        [image: FICODES] FUTURE INTERNET CONSULTING & DEVELOPMENT SOLUTIONS S.L
        <http://www.ficodes.com>
        Rafael Fernández Gallego <rfernandez@ficodes.com>

        Chief Operating Officer <http://ficodes.com>

        rfernandez@ficodes.com

        +34 687 47 77 29

        www.ficodes.com

        El mié., 4 jul. 2018 a las 15:28, Simon Bechmann (<sb@seriousgames.net>)

        __________________________________________________________________________________________

        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

        Show
        fw.ext.user FW External User added a comment - Hi Simon, I'm testing your docker compose file and if I use docker's internal references instead of those hardcoded IP addresses, it works fine. I mean: perseo-core: image: fiware/perseo-core ports: "8080:8080" environment: PERSEO_FE_URL= http://*perseo-fe*:9090 depends_on: mongo perseo-fe: image: fiware/perseo ports: "9090:9090" depends_on: perseo-core environment: PERSEO_MONGO_ENDPOINT=mongo PERSEO_CORE_URL= http://*perseo-core*:8080 PERSEO_LOG_LEVEL=info PERSEO_ORION_URL= http://*orion*:1026/ Hope it helps! Best regards Rafael [image: FICODES] FUTURE INTERNET CONSULTING & DEVELOPMENT SOLUTIONS S.L < http://www.ficodes.com > Rafael Fernández Gallego <rfernandez@ficodes.com> Chief Operating Officer < http://ficodes.com > rfernandez@ficodes.com +34 687 47 77 29 www.ficodes.com El mié., 4 jul. 2018 a las 15:28, Simon Bechmann (<sb@seriousgames.net>) __________________________________________________________________________________________ You can get more information about our cookies and privacy policies on the following links: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE Fiware-tech-help mailing list Fiware-tech-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-tech-help

          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: