fiware orion - Context broker is not started: parameter header not recogined -


I am deploying contextual broker and when I use "-multi service" as the context-Broker_extra_ops option If I do, the reference broker does not start and there is no further information found. Can you give me a hand?

I am using Reference Broker version 0.15.0

  contextbroker -port 9999-logdir / var / log / contextbroker -pidpath / var / log / contextbroker / Contextbroker.pid -dbhost 127.0.0.17017 -db testdb1- Maximum service header log directory: '/ var / log / contextbroker' DEBUG @ 12: 59: 56 PA Config CPP [8 9]: Trace for '0-255 Setting Level 'DEBUG @ 12: 59: 56 PA Config CPP [8 9]: Skiping the function paConfig parameter' header 'is not recognized  

/etc/init.d/contextBroker I got a failure using

  /etc/init.d/contextBroker Start Starting up ... ReferencesBlock is closed Bringing Reference ... Cat: /var/log/contextBroker/contextBroker.pid: No such file or directory foundPidfile [FAILED]  

-Multiserve CLI parameter has been changed between version 0.14.1 and 0.15. 0 0.15.0 Changelog:

  # rpm -q --changelog Reference Broker * miƩ oct 01 2014 Fermin Galan & lt; Fermin@tid.es> 0.15.0-1 (FIWARE-3.5.3-1) ... - Fix: Broker no longer supported URL-based multi-service (tenants) (Issue # 522) - Fix: URL-related to tenants Code removed (number # 522) ...  

simply replace - the maximum service service by changing the -multiheader to fix the problem needed.


Comments

Popular posts from this blog

java - Can't add JTree to JPanel of a JInternalFrame -

javascript - data.match(var) not working it seems -

javascript - How can I pause a jQuery .each() loop, while waiting for user input? -