Unable to access ECN-viewer


(Jingyang Chen) #1

Hi, I’m new to ioFog and was trying to use ioFog-SDK downloaded from http://www.edgeworx.io/downloads/eap/edgeworx-iofog-sdk_1.2.0.tar.gz to deply io-Fog and trying to deply HealthcareWearables microservice.

Here is what I got when I run $iofogctl get all

NAMESPACE
default

CONTROLLER STATUS AGE UPTIME IP PORT
test-enc online - 12m31s 0.0.0.0 51121

AGENT STATUS AGE UPTIME IP VERSION
ioFog Agent RUNNING 12m5s 11m39s 103.117.102.16 1.3.0-rc1

APPLICATION STATUS MICROSERVICES
HealthcareWearableFlow Running heart-rate-monitor, heart-rate-viewer

MICROSERVICE STATUS CONFIG ROUTES VOLUMES PORTS
heart-rate-monitor - {“test_mode”: true, “data_label”: “Anonymous Person”} heart-rate-viewer
heart-rate-viewer - {} 5000:80

Both microservice status are missing and never changed, ECN-viwer could not be accessed, following is the yaml file to deploy my app.

user:
email: jingyangchen@gmail.com
password: jingyang
flow: HealthcareWearableFlow
controller:

HTTP(S) endpoint to reach the controller

address: http://192.168.12.157:51121
microservices:

Custom micro service that will connect to Scosche heart rate monitor via Bluetooth

heart-rate:
agent-name: ioFog Agent
agent-config:
bluetoothEnabled: true # this will install the iofog/restblue microservice
abstractedHardwareEnabled: false
images:
arm: edgeworx/healthcare-heart-rate:arm-v1
x86: edgeworx/healthcare-heart-rate:x86-v1
microservice:
name: heart-rate-monitor # If you are happy with the default name, you don’t need to edit.
root-host: false
ports: []
config:
test_mode: true
data_label: Anonymous Person

Simple JSON viewer for the heart rate output

viewer:
agent-name: ioFog Agent
images:
arm: edgeworx/healthcare-heart-rate-ui:arm
x86: edgeworx/healthcare-heart-rate:x86-nano
x86: edgeworx/healthcare-heart-rate-ui:x86
microservice:
name: heart-rate-viewer # If you are happy with the default name, you don’t need to edit.
root-host: false
ports:
# The ui will be listening on port 80 (internal).
- external: 5000 # You will be able to access the ui on <AGENT_IP>:5000
internal: 80 # The ui is listening on port 80. Do not edit this.
publicMode: false # Do not edit this.
volumes: []
env:
- key: BASE_URL
value: http://192.168.12.157:8080/data
routes:

Use this section to configure route between microservices

Use microservice name

  • from: heart-rate-monitor
    to: heart-rate-viewer

Any help and instructions are appreciated, thanks a lot in advance.

Thanks,
Jingyang


#2

Hi,

ECN viewer is not part of the 1.2.0 release. You need the new 1.3.0 beta. You can get that from here:

http://www.edgeworx.io/downloads/demo-sdk/edgeworx-iofog-sdk_1.3.0-beta.tar.gz

Please let us know if you have any more issues. You can also join the ioFog Slack channel to message the ioFog community in real time.


(Jingyang Chen) #3

Hi, thank you so much for the quick respond! Could you please share me with a link to Slack? The link on ioFog website could not be accessed currently.

Thanks,
Jingyang


(Jingyang Chen) #5

Hi, thank you so much for the help! I was able to access ECN-viewer following this quick start guide https://iofog.org/docs/1.3.0/getting-started/quick-start.html
although when I was using bootstrap in the SDK, I could not get agent running as shown below.

ubuntu@kurento:~$ sudo iofogctl get all
NAMESPACE
default

CONTROLLER STATUS AGE UPTIME IP PORT
jing-controller2online 1h32m 1h32m 0.0.0.0 51121

CONNECTOR STATUS AGE UPTIME IP
local-connector online 1h32m 1h32m 0.0.0.0

AGENT STATUS AGE UPTIME IP VERSION
local-agent UNKNOWN 1h32m 0s 0.0.0.0:54321

APPLICATION STATUS MICROSERVICES
HealthcareWearableFlow RUNNING heart-rate-monitor, heart-rate-viewer

MICROSERVICE STATUS AGENT CONFIG ROUTES VOLUMES PORTS
heart-rate-monitor QUEUED local-agent {“data_label”:“Anonymous Person”,“test_mode”:true} heart-rate-viewer
heart-rate-viewer QUEUED local-agent {} 5000:80

Thank you for your help!


(Serge Radinovich) #6

iofog.slack.com is our Slack.

It looks like your local-agent is in a bad state based on the UNKNOWN status. We can debug this with you if you jump on Slack.

In the meantime, check that your version of iofogctl is 1.3.0-beta by running iofogctl version. Try run iofogctl delete all and repeat the steps.


(Pixcell) #7

Hi,

Thank you for your message.

Could you give us the output of “docker exec -it iofog-agent iofog-agent status” and “docker exec -it iofog-agent iofog-agent info” in order for us to control it has been properly provisioned with the controller.

Thank you,


(Jingyang Chen) #8

Hi, thank you so much for the reply! I tried to run iofogctl delete all and delete the whole SDK folder then repeat: ./bootstrap.sh, ./install.sh HealthcareWearables/config.yml, then waited couple mins now the local-agent is up and running!! :wink: Also I can access ECN-viewer after microservice is running. Still not sure where I was wrong but everything is fine now. Thank you again for the help.


(Pixcell) #9

Hi,

That’s great to hear ! Glad to know all is fine.
Please join us on Slack (the website link has been updated) or create a new issue here if you encounter any problem