We’ve found an issue with ClearNode where OpenVPN is installed and started as a daemon service via “systemctl” at boot. The RedNode API software service is starting before OpenVPN and establishing it’s messaging connection to the AWS Message Hub. Subsequently OpenVPN changes the network configuration and thus trashes the connection to AWS, preventing the ClearNode mobile app from controlling the node.

The temporary solution is to put a delay into the RedNode startup sequence. Edit the /lib/systemd/system/rednode.service file and add the delay as seen below

[Unit]
 Description=RedNode AWS client and node controller
 After=network.target
 

 [Service]
 Type=simple
 ExecStartPre=/bin/sleep 15
 ExecReload=/bin/kill -HUP $MAINPID
 KillMode=process
 Restart=always
 RestartSec=15
 User=root
 WorkingDirectory=/usr/local/rednode/
 ExecStart=/usr/bin/python /usr/local/rednode/nodeControl.py
 

 [Install]
 WantedBy=multi-user.target

We tried making rednode.service dependent on the OpenVPN service using the “After” section above, but that didn’t seem to work. You may need to adjust the value of “sleep 15” depending on your installation.

If you need help with taking care of this don’t hesitate to get in touch.

73 … Gerry.