Level upgrade of EdgeStreaming Runtime

Upgrade the level of EdgeStreaming Studio.

For details, refer to Level upgrade of EdgeStreaming Studio.

Disable the automatic execution setting of the script.

When the setting enables scripts to be automatically executed in the IoT gateway, disable that setting.

1. Stop the automatically executed script.

   #  systemctl stop es-agent.service 
   

2. Disable the setting that enables automatic execution of EdgeStreaming Runtime.

    #  systemctl disable es-agent.service
   

Back up the script of the old level.

Obtain the backup of the old-level script.

#  cd /opt
#  cp -r ./edge ~/backup/
#  rm -r ./edge/*

Transfer the script to the IoT gateway by using the new-level EdgeStreaming Studio.

Open the script in the new-level EdgeStreaming Studio to send it to the IoT gateway and configure the settings for automatic execution.

1. Use the new-level EdgeStreaming Studio to open the project that contains the script you want to operate.

2. Double-click the script that you want to operate in Project Explorer of Designer to open the script.

For an example on how to configure the settings, refer to Transfer of script to IoT gateway.

Restore the startup script.

Restore the startup script "run.sh" from the backup.

#  cd /opt/edge
#  cp ~/backup/edge/run.sh ./

Reactivate the automatic execution setting of the script.

Reactivate the automatic execution setting of the script.

#  systemctl enable es-agent.service

You have now replaced the script run in the old level with the new-level script.

Confirm once more that the settings have been configured correctly.

Start the service with "systemctl start <service name>" and confirm the status and content of standard output with "systemctl status <service name>".

If an error is not output at this time, the service has been created from the script correctly, and has been started.

# systemctl start es-agent.service

# systemctl status es-agent.service
● es-agent.service - es-agent
   Loaded: loaded (/etc/systemd/system/es-agent.service; enabled)
   Active: active (running) since Tue 2020-02-25 06:00:39 CET; 7s ago
  Process: 1577 ExecStop=/bin/kill -TERM ${MAINPID} (code=exited, status=0/SUCCESS)
 Main PID: 1661 (es-agent)
   CGroup: /system.slice/es-agent.service
           └─1661 /opt/edge/es-agent run -c /opt/edge/es-agent.yaml

Feb 25 06:00:39 debian run.sh[1661]: time="2020-02-25T05:00:39Z" level=info msg="no plugins to load" file=loade...script
Feb 25 06:00:39 debian run.sh[1661]: time="2020-02-25T05:00:39Z" level=info msg="Starting the server on :15601"
Feb 25 06:00:39 debian run.sh[1661]: {"cpu":99.99999999779732,"disk_avail":14.960063934326172}
Feb 25 06:00:40 debian run.sh[1661]: {"cpu":0,"disk_avail":14.960063934326172}
Feb 25 06:00:41 debian run.sh[1661]: {"cpu":0,"disk_avail":14.960063934326172}
Feb 25 06:00:42 debian run.sh[1661]: {"cpu":0.9900990099009309,"disk_avail":14.960063934326172}
Feb 25 06:00:43 debian run.sh[1661]: {"cpu":0,"disk_avail":14.960063934326172}
Feb 25 06:00:44 debian run.sh[1661]: {"cpu":0,"disk_avail":14.960063934326172}
Feb 25 06:00:45 debian run.sh[1661]: {"cpu":0,"disk_avail":14.960063934326172}
Feb 25 06:00:46 debian run.sh[1661]: {"cpu":0,"disk_avail":14.960063934326172}