Intel® Edge Software Hub
Get help on building Edge Software Hub solutions for edge compute node
Announcements
Welcome to the Intel Community! If you like the answer to your question, please mark it as 'Accepted Solution' to help others.

See our new article on Fidelity-first Ray Tracing in the Heterogeneous Compute Era.

The Edge Software Vision Package for Red Hat Enterprise Linux is now available here.

Learn more about developing on Intel® Hardware and Software here.
200 Discussions

Castle Server installation failing

Rajnish
Beginner
294 Views

 

I am facing following error.unable to find out the reason.Any help is appriciated.

dev@dev-NUC8i3BEH:~/edge_insights_industrial/Edge_Insights_for_Industrial_2.3.2/orchestrator/orchestrator/server-package$ /bin/bash server-bootstrap.sh
*** [Start] Bootstrap CSL Server Version 1.5.3483-a0f1d8e9 ***
{INFO}: Running on ubuntu 18.04
Docker daemon configuration is correctly set.
Network interfaces available:
============================================================
| ID | NAME | IP |
============================================================
| 1 | wlp0s20f3 | 192.168.1.9 |
| 2 | wlp0s20f3 | 192.168.1.13 |
| 3 | wlp0s20f3 | 192.168.1.99 |
| 4 | br-07787c332062 | 172.18.0.1 |
| 5 | docker0 | 172.17.0.1 |
============================================================
Please enter the network interface ID to be used for CSL: 1
{INFO}: Using Network Interface=wlp0s20f3, IP Address=192.168.1.9
Please enter the virtual IP to be used for load balancer: 192.168.66.66
Checking validity of 192.168.66.66 ...
{INFO}: IP address is valid
Enter the ingress port range to be used in kubernetes
Enter lower port limit [30000]:
Enter upper port limit [32767]:
{INFO}: 30000-32767 is a valid port range
{INFO}: Pre-Setup
{INFO}: Creating folder - /etc/opt/csl/csl-node
{INFO}: Creating folder - /etc/opt/csl/csl-node/parameters
{INFO}: Setting up ETCD Configuration file
{INFO}: Please enter desired path to Etcd data volume to be used by CSL Server or press ENTER to use default ['/var/opt/csl/csl-node/etcd']:
{INFO}: Starting Server bootstrapping

{INFO} Generating etcd peer transport cert and key ...Generating a RSA private key
....................................++++
........................................++++
writing new private key to 'etcd-peer-tr-key.pem'
-----
{INFO}: Sending request to CSL Manager for Signed Certificate ...
{INFO}: Sign Certificate success

{INFO} Generating etcd client transport cert and key ...Generating a RSA private key
...........................................................................................................................................................................++++
...........................................++++
writing new private key to 'etcd-client-tr-key.pem'
-----
{INFO}: Sending request to CSL Manager for Signed Certificate ...
{INFO}: Sign Certificate success

{INFO} Generating confd's etcd client cert and key ...Generating a RSA private key
.....................................++++
.................++++
writing new private key to 'confd-etcd-key.pem'
-----
{INFO}: Sending request to CSL Manager for Signed Certificate ...
{INFO}: Sign Certificate success
{INFO}: Get server config package ...
{INFO}: config-pkg.tar.gz received from CSL-manager
{INFO}: Unzipping the received package
{INFO}: Get server Package ...
{INFO}: Server package received from CSL-manager
{INFO}: untar server package
{INFO}: Folder exists! Can't create - /etc/opt/csl/csl-node
https://192.168.1.9:8443
{INFO}: Installing Certificates
{INFO}: Creating folder - /opt/csl/csl-node/certs/etcd/
{INFO}: Creating folder - /opt/csl/csl-node/certs/confd/
{INFO}: start install-config.sh ...
{INFO}: Reading configuration information
{INFO}: Generating necessary files from received information
{INFO}: Filling out template files to generate config files
{INFO}: Installing config package
{INFO}: Installing received cluster certs
{INFO}: changing directory to server-pkg ...
{INFO}: start install-server.sh ...
*** [Start] CSL Server Installation ***
{INFO} Using IP 192.168.1.9
{INFO}: Installing server components
{INFO}: Loading docker images
Loaded image: k8s.gcr.io/coredns:1.6.2
Loaded image: k8s.gcr.io/kube-apiserver:v1.16.0
Loaded image: k8s.gcr.io/kube-controller-manager:v1.16.0
Loaded image: k8s.gcr.io/kube-proxy:v1.16.0
Loaded image: k8s.gcr.io/kube-scheduler:v1.16.0
Loaded image: k8s.gcr.io/pause:3.1
Loaded image: weaveworks/weave-kube:2.6.5
Loaded image: weaveworks/weave-npc:2.6.5
Loaded image: nfvpe/multus:v3.2
Loaded image: busybox:1.30.1
Loaded image: cslscheduler:0.1
Loaded image: prom/prometheus:v2.12.0
{INFO}: Copying service files for etcd, confd, haproxy, keepalived, kubelet
{INFO}: Setting NodeIP Address = 192.168.1.9
{INFO}: Enable server component services
Created symlink /etc/systemd/system/default.target.wants/etcd.service → /lib/systemd/system/etcd.service.
Created symlink /etc/systemd/system/multi-user.target.wants/csl-keepalived.service → /lib/systemd/system/csl-keepalived.service.
Created symlink /etc/systemd/system/multi-user.target.wants/csl-haproxy.service → /lib/systemd/system/csl-haproxy.service.
Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service → /lib/systemd/system/kubelet.service.
{INFO}: Starting server component services
Job for etcd.service failed because the control process exited with error code.
See "systemctl status etcd.service" and "journalctl -xe" for details.
Operation (systemctl start etcd.service) Failed with error code : 1. Exiting install and cleaning environment
{ERR}: Static package installation failed
{INFO}: Start Cleanup.
{INFO}: Stopping services

Labels (1)
0 Kudos
6 Replies
Rajnish
Beginner
290 Views

{INFO}: Sending request to CSL Manager for Signed Certificate ...
{ERR}: Sign Certificate failed !! Http error :(401)
{INFO}: Start Cleanup.
{INFO}: Stopping services
{INFO}: Removing directories

 

Sometime i am getting this error message as well.

Johnbelley
Novice
285 Views

Which OS version you're using ?. I had the same problem until i change my OS from 16.07 with 20.04. Try to change it and tell if its work 

WengWai_C_Intel
Moderator
278 Views

Hi @Rajnish ,

Follow the setup documentation, can you first ensure the virtual IP that you use is under the same subnet with CSL manager? From your info provided, the subnet you are using is 192.168.1.xx in your setup. The virtual IP to be used should under this same subnet too.

thanks!

Rajnish
Beginner
258 Views

Hi Weng

i am still getting the same error can you look into it.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

dev@dev-NUC8i3BEH:~/edge_insights_industrial/Edge_Insights_for_Industrial_2.3.2/orchestrator/orchestrator/server-package$ sudo /bin/bash server-bootstrap.sh
*** [Start] Bootstrap CSL Server Version 1.5.3483-a0f1d8e9 ***
{INFO}: Running on ubuntu 18.04
Docker daemon configuration is correctly set.
Network interfaces available:
============================================================
| ID | NAME | IP |
============================================================
| 1 | wlp0s20f3 | 192.168.1.9 |
| 2 | wlp0s20f3 | 192.168.1.13 |
| 3 | wlp0s20f3 | 192.168.1.99 |
| 4 | br-07787c332062 | 172.18.0.1 |
| 5 | docker0 | 172.17.0.1 |
============================================================
Please enter the network interface ID to be used for CSL: 1
{INFO}: Using Network Interface=wlp0s20f3, IP Address=192.168.1.9
Please enter the virtual IP to be used for load balancer: 192.168.1.19
Checking validity of 192.168.1.19 ...
{INFO}: IP address is valid
Enter the ingress port range to be used in kubernetes
Enter lower port limit [30000]:
Enter upper port limit [32767]:
{INFO}: 30000-32767 is a valid port range
{INFO}: Pre-Setup
{INFO}: Creating folder - /etc/opt/csl/csl-node
{INFO}: Creating folder - /etc/opt/csl/csl-node/parameters
{INFO}: Setting up ETCD Configuration file
{INFO}: Please enter desired path to Etcd data volume to be used by CSL Server or press ENTER to use default ['/var/opt/csl/csl-node/etcd']:
{INFO}: Starting Server bootstrapping

{INFO} Generating etcd peer transport cert and key ...Generating a RSA private key
......................................................................................................................................................++++
....++++
writing new private key to 'etcd-peer-tr-key.pem'
-----
{INFO}: Sending request to CSL Manager for Signed Certificate ...
{INFO}: Sign Certificate success

{INFO} Generating etcd client transport cert and key ...Generating a RSA private key
..................++++
...........................................................................++++
writing new private key to 'etcd-client-tr-key.pem'
-----
{INFO}: Sending request to CSL Manager for Signed Certificate ...
{INFO}: Sign Certificate success

{INFO} Generating confd's etcd client cert and key ...Generating a RSA private key
.............++++
...........................................................++++
writing new private key to 'confd-etcd-key.pem'
-----
{INFO}: Sending request to CSL Manager for Signed Certificate ...
{INFO}: Sign Certificate success
{INFO}: Get server config package ...
{INFO}: config-pkg.tar.gz received from CSL-manager
{INFO}: Unzipping the received package
{INFO}: Get server Package ...
{INFO}: Server package received from CSL-manager
{INFO}: untar server package
{INFO}: Folder exists! Can't create - /etc/opt/csl/csl-node
https://192.168.1.9:8443
{INFO}: Installing Certificates
{INFO}: Creating folder - /opt/csl/csl-node/certs/etcd/
{INFO}: Creating folder - /opt/csl/csl-node/certs/confd/
{INFO}: start install-config.sh ...
{INFO}: Reading configuration information
{INFO}: Generating necessary files from received information
{INFO}: Filling out template files to generate config files
{INFO}: Installing config package
{INFO}: Installing received cluster certs
{INFO}: changing directory to server-pkg ...
{INFO}: start install-server.sh ...
*** [Start] CSL Server Installation ***
{INFO} Using IP 192.168.1.9
{INFO}: Installing server components
{INFO}: Loading docker images
Loaded image: k8s.gcr.io/coredns:1.6.2
Loaded image: k8s.gcr.io/kube-apiserver:v1.16.0
Loaded image: k8s.gcr.io/kube-controller-manager:v1.16.0
Loaded image: k8s.gcr.io/kube-proxy:v1.16.0
Loaded image: k8s.gcr.io/kube-scheduler:v1.16.0
Loaded image: k8s.gcr.io/pause:3.1
Loaded image: weaveworks/weave-kube:2.6.5
Loaded image: weaveworks/weave-npc:2.6.5
Loaded image: nfvpe/multus:v3.2
Loaded image: busybox:1.30.1
Loaded image: cslscheduler:0.1
Loaded image: prom/prometheus:v2.12.0
{INFO}: Copying service files for etcd, confd, haproxy, keepalived, kubelet
{INFO}: Setting NodeIP Address = 192.168.1.9
{INFO}: Enable server component services
Created symlink /etc/systemd/system/default.target.wants/etcd.service → /lib/systemd/system/etcd.service.
Created symlink /etc/systemd/system/multi-user.target.wants/csl-keepalived.service → /lib/systemd/system/csl-keepalived.service.
Created symlink /etc/systemd/system/multi-user.target.wants/csl-haproxy.service → /lib/systemd/system/csl-haproxy.service.
Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service → /lib/systemd/system/kubelet.service.
{INFO}: Starting server component services
Job for etcd.service failed because the control process exited with error code.
See "systemctl status etcd.service" and "journalctl -xe" for details.
Operation (systemctl start etcd.service) Failed with error code : 1. Exiting install and cleaning environment
{ERR}: Static package installation failed
{INFO}: Start Cleanup.
{INFO}: Stopping services
{INFO}: Removing directories

WengWai_C_Intel
Moderator
242 Views

Hi @Rajnish ,

Per setup documentation, please run the server-bootstrap.sh without sudo (root permission). It should be just as below:

/bin/bash server-bootstrap.sh
WengWai_C_Intel
Moderator
224 Views

Hi @Rajnish 

Just to close the loop here, that the failure from the log above was due to another ETCD instance running when you perform this setup. There should be no other ETCD instance running as the CSL server setup will create one. Therefore, stopping the ETCD instance before run the CSL server setup will address this issue.

thanks!

Reply