[Backlogmanager] [FIWARE-JIRA] (HELP-8484) [fiware-stackoverflow] How to make Orion Context Broker works with HTTPS notification?

Fermín Galán (JIRA) jira-help-desk at jira.fiware.org
Mon May 8 09:19:00 CEST 2017


    [ https://jira.fiware.org/browse/HELP-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=73143#comment-73143 ] 

Fermín Galán commented on HELP-8484:
------------------------------------

Assigning back to backlog manager in order to avoid reminder emails. Once the system gets adapted to avoid them (see https://github.com/flopezag/fiware-management-scripts/pull/17) you can assign me it back if you want

> [fiware-stackoverflow] How to make Orion Context Broker works with HTTPS notification?
> --------------------------------------------------------------------------------------
>
>                 Key: HELP-8484
>                 URL: https://jira.fiware.org/browse/HELP-8484
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Backlog Manager
>              Labels: fiware, fiware-orion, https, ssl
>
> Created question in FIWARE Q/A platform on 04-04-2017 at 18:04
> {color: red}Please, ANSWER this question AT{color} http://stackoverflow.com/questions/43212442/how-to-make-orion-context-broker-works-with-https-notification
> +Question:+
> How to make Orion Context Broker works with HTTPS notification?
> +Description:+
> I want to enable https for notifications. The Orion Context Broker version 1.7.0 is installed in Ubuntu 16.04. To start, the following command is being used:
> sudo /etc/init.d/contextBroker start -logAppend -https -key /path/to/orion.key -cert /path/to/orion.crt
> The answer is:
> [ ok ] Starting contextBroker (via systemctl): contextBroker.service.
> The status is:
> sudo systemctl status contextBroker.service
> contextBroker.service - LSB: Example initscript
> Loaded: loaded (/etc/init.d/contextBroker; bad; vendor preset: enabled)
> Active: active (exited) since Tue 2017-04-04 12:56:13 BRT; 14s ago
> Docs: man:systemd-sysv-generator(8)
> Process: 8312 ExecStart=/etc/init.d/contextBroker start (code=exited, status=0/SUCCESS)
> Apr 04 12:56:13 fiware-ubuntu systemd[1]: Starting LSB:  Example initscript...
> Apr 04 12:56:13 fiware-ubuntu contextBroker[8312]: contextBroker
> Apr 04 12:56:13 fiware-ubuntu contextBroker[8312]: /path/bin/contextBroker
> Apr 04 12:56:13 fiware-ubuntu systemd[1]: Started LSB: Example initscript.
> Another approach is running Orion as:
> sudo /path/bin/contextBroker -logLevel DEBUG -localIp x.y.z.t -https -key /path/to/orion.key -cert /path/to/orion.crt
> The log follows:
> time=2017-04-04T18:37:58.881Z | lvl=INFO | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=contextBroker.cpp[1705]:main | msg=Orion Context Broker is running
> time=2017-04-04T18:37:58.887Z | lvl=INFO | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=mongoConnectionPool.cpp[205]:mongoConnect | msg=Successful connection to database
> time=2017-04-04T18:37:58.887Z | lvl=INFO | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=connectionOperations.cpp[681]:setWriteConcern | msg=Database Operation Successful (setWriteConcern: 1)
> time=2017-04-04T18:37:58.887Z | lvl=INFO | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=connectionOperations.cpp[724]:getWriteConcern | msg=Database Operation Successful (getWriteConcern)
> time=2017-04-04T18:37:58.888Z | lvl=INFO | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=connectionOperations.cpp[626]:runCollectionCommand | msg=Database Operation Successful (command: { buildinfo: 1 })
> ...
> time=2017-04-04T18:37:58.897Z | lvl=FATAL | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=rest.cpp[1720]:restStart | msg=Fatal Error (error starting REST interface)
> It is not working...



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)


More information about the Backlogmanager mailing list

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