[Backlogmanager] [FIWARE-JIRA] (HELP-13301) [fiware-stackoverflow] Orion Context Broker doesn' t start

[Fernando Lopez (JIRA)]

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

Fernando Lopez resolved HELP-13301.
-----------------------------------
    Resolution: Done

> [fiware-stackoverflow] Orion Context Broker doesn't start
> -------------------------------------------------------------
>
>                 Key: HELP-13301
>                 URL: https://jira.fiware.org/browse/HELP-13301
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Jose Manuel Cantera
>              Labels: contextmanager, fiware, fiware-orion
>
> Created question in FIWARE Q/A platform on 01-01-2018 at 19:01
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/48052288/orion-context-broker-doesnt-start
> +Question:+
> Orion Context Broker doesn't start
> +Description:+
> I've been working with FIWARE for a school project, I had previously installed Orion and was able to post data to the Context Broker. I rebooted the system since I made some other changes to my set up and Orion has stopped working ever since.
> I was trying to start the Context Broker from my command line and its starts. However it doesn't start the Context Broker. The netstat -tupln command doesn't display that the port 1026 is in use and the JSON file which had previously posted the data to FIWARE isn't displayed anymore.
> [ec2-user at ip-172-31-31-236 config]$ /etc/init.d/contextBroker status
> ● contextBroker.service - LSB: run contextBroker
>    Loaded: loaded (/etc/rc.d/init.d/contextBroker; bad; vendor preset: disabled)
>    Active: active (exited) since mån 2018-01-01 15:38:39 UTC; 42min ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 1829 ExecStart=/etc/rc.d/init.d/contextBroker start (code=exited, status=0/SUCCESS)
>    Memory: 0B
> jan 01 15:38:37 ip-172-31-31-236.ap-south-1.compute.internal systemd[1]: Starting LSB: run contextBroker...
> jan 01 15:38:37 ip-172-31-31-236.ap-south-1.compute.internal contextBroker[1829]: Starting...
> jan 01 15:38:37 ip-172-31-31-236.ap-south-1.compute.internal contextBroker[1829]: contextBroker is stopped
> jan 01 15:38:37 ip-172-31-31-236.ap-south-1.compute.internal su[1834]: (to orion) root on none
> jan 01 15:38:37 ip-172-31-31-236.ap-south-1.compute.internal su[1837]: (to orion) root on none
> jan 01 15:38:39 ip-172-31-31-236.ap-south-1.compute.internal contextBroker[1829]: Starting contextBroker...                         [  OK  ]
> jan 01 15:38:39 ip-172-31-31-236.ap-south-1.compute.internal systemd[1]: Started LSB: run contextBroker.
> [ec2-user at ip-172-31-31-236 config]$ sudo netstat -tupln
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
> tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      900/sshd            
> tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      864/master          
> tcp6       0      0 :::22                   :::*                    LISTEN      900/sshd            
> tcp6       0      0 ::1:25                  :::*                    LISTEN      864/master          
> tcp6       0      0 :::8000                 :::*                    LISTEN      2353/docker-proxy   
> tcp6       0      0 :::5000                 :::*                    LISTEN      2363/docker-proxy   
> udp        0      0 0.0.0.0:68              0.0.0.0:*                           546/dhclient        
> udp        0      0 0.0.0.0:44244           0.0.0.0:*                           546/dhclient        
> udp        0      0 127.0.0.1:323           0.0.0.0:*                           511/chronyd         
> udp6       0      0 :::24106                :::*                                546/dhclient        
> udp6       0      0 ::1:323                 :::*                                511/chronyd         
> [ec2-user at ip-172-31-31-236 config]$ 
> [ec2-user at ip-172-31-31-236 config]$ curl localhost:1026/version
> curl: (7) Failed connect to localhost:1026; Connection refused



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