Created question in FIWARE Q/A platform on 01-06-2018 at 16:06
Please, ANSWER this question AT https://stackoverflow.com/questions/50645999/perseo-fe-docker-instance-fail-to-start

Question:
Perseo fe docker instance fail to start

Description:
I am facing with the following issue:
I am trying to deploy FIWARE-Perseo to my Centos 7 server as docker instances. Although the perseocore instance runs without a problem, it doesn't happen the same with the perseo front end. It is created but fails to start. From the logs it is clear that the problem is associated to the mongodb:

Changing PERSEO_CORE_URL to environment value: http://localhost:8080
Changing PERSEO_ORION_URL to environment value:
http://myip:1026/v1/updateContext Changing PERSEO_LOG_LEVEL to
environment value: debug time=2018-06-01T14:36:02.691Z | lvl=INFO |
corr=n/a | trans=n/a | op=start | comp=perseo-fe | msg=starting perseo
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,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]
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,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]
time=2018-06-01T14:36:02.789Z | lvl=ERROR | corr=n/a | trans=n/a |
op=checkDB | comp=perseo-fe | msg=connect failed to connect to server
[localhost:27017] on first connect [MongoError: connect ECONNREFUSED
127.0.0.1:27017] time=2018-06-01T14:36:02.790Z | lvl=ERROR | corr=n/a | trans=n/a | op=start | comp=perseo-fe | msg=failed to connect to
server [localhost:27017] on first connect [MongoError: connect
ECONNREFUSED 127.0.0.1:27017] time=2018-06-01T14:36:02.792Z | lvl=INFO

trans=n/a | op=perseo | comp=perseo-fe | msg=failed to connect to
server [localhost:27017] on first connect [MongoError: connect
ECONNREFUSED 127.0.0.1:27017]

I have used the instructions from the following link, in a system where Orion and MongoDB were already running as docker instances:
Running together with Perseo Core and Orion Context Broker
Thank you very much in advance for any help you can provide me.