[Backlogmanager] [FIWARE-JIRA] (HELP-15850) [fiware-stackoverflow] Fatal error when starting orion context broker

Ken Zangelin (JIRA) jira-help-desk at jira.fiware.org
Wed May 29 20:48:00 CEST 2019


     [ https://jira.fiware.org/browse/HELP-15850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ken Zangelin resolved HELP-15850.
---------------------------------
    Resolution: Done

> [fiware-stackoverflow] Fatal error when starting orion context broker
> ---------------------------------------------------------------------
>
>                 Key: HELP-15850
>                 URL: https://jira.fiware.org/browse/HELP-15850
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Ken Zangelin
>              Labels: fiware, fiware-orion
>
> Created question in FIWARE Q/A platform on 24-05-2019 at 13:05
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/56292091/fatal-error-when-starting-orion-context-broker
> +Question:+
> Fatal error when starting orion context broker
> +Description:+
> My orion context broker does not start and when I enter the command 
> /etc/init.d/contextBroker start I get this message
> [root at context-broker ~]# /etc/init.d/contextBroker start
> Starting contextBroker (via systemctl):  Job for contextBroker.service failed because the control process exited with error code. See "systemctl status contextBroker.service" and "journalctl -xe" for details.
>                                                            [FAILED]
> The systemctl status contextBroker.service commannd gives this message
> [root at context-broker ~]# systemctl status contextBroker.service
> ● contextBroker.service - LSB: run contextBroker
>    Loaded: loaded (/etc/rc.d/init.d/contextBroker; bad; vendor preset: disabled)
>    Active: failed (Result: exit-code) since Fri 2019-05-24 11:38:50 UTC; 1min 11s ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 9782 ExecStart=/etc/rc.d/init.d/contextBroker start (code=exited, status=1/FAILURE)
> May 24 11:38:47 context-broker.novalocal systemd[1]: Starting LSB: run contextBroker...
> May 24 11:38:48 context-broker.novalocal contextBroker[9782]: contextBroker is stopped
> May 24 11:38:48 context-broker.novalocal contextBroker[9782]: Starting...
> May 24 11:38:48 context-broker.novalocal su[9788]: (to orion) root on none
> May 24 11:38:50 context-broker.novalocal contextBroker[9782]: Starting contextBroker...                         cat: /var/run/contextBroker/contextBroker.pid...irectory
> May 24 11:38:50 context-broker.novalocal systemd[1]: contextBroker.service: control process exited, code=exited status=1
> May 24 11:38:50 context-broker.novalocal contextBroker[9782]: pidfile not found[FAILED]
> May 24 11:38:50 context-broker.novalocal systemd[1]: Failed to start LSB: run contextBroker.
> May 24 11:38:50 context-broker.novalocal systemd[1]: Unit contextBroker.service entered failed state.
> May 24 11:38:50 context-broker.novalocal systemd[1]: contextBroker.service failed.
> Hint: Some lines were ellipsized, use -l to show in full.
> Also the /tmp/contextBroker.log file looks like this
> time=2019-05-24T11:41:12.971Z | lvl=FATAL | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=rest.cpp[1753]:restStart | msg=Fatal Error (error starting REST interface)
> I checked if mongodb is running and it is running correctly.



--
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