Solved

Cannot start local server with docker support in IFS Cloud 22R1

  • 16 October 2022
  • 7 replies
  • 213 views

Badge +2

Hi, 

 

I try to set up the local server in developer studio for IFS Cloud 22R1 with docker support according to https://docs.ifs.com/techdocs/22r2/060_development/050_development_tools/002_developer_studio/030_reference/600_java_debugger/.

But when I try to start the serve,r it gives the following error.

 

ifsapp-odata              | cat: can't open '/etc/podinfo/labels': No such file or directory
ifsapp-odata              | cat: can't open '/etc/podinfo/labels': No such file or directory
ifsapp-odata              | Using API to fetch certificates
ifsapp-odata              | cat: can't open '/run/secrets/kubernetes.io/serviceaccount/token': No such file or directory
ifsapp-odata              | cat: can't open '/run/secrets/kubernetes.io/serviceaccount/namespace': No such file or directory
ifsapp-odata              | curl: (6) Could not resolve host: kubernetes.default.svc
ifsapp-client-services    | curl: (6) Could not resolve host: kubernetes.default.svc
ifsapp-odata              | curl: (6) Could not resolve host: kubernetes.default.svc
ifs-file-storage          | curl: (6) Could not resolve host: kubernetes.default.svc

 

Also, then later it gives another error as below:

 

ifs-file-storage          | 09:24:54.766 [Timer-0] ERROR com.ifsworld.storage.service.scanner.ScanProcessor - Error occurred while checking Scanner Status.
ifs-file-storage          | java.net.UnknownHostException: ifs-virus-scanner
ifs-file-storage          |     at java.net.AbstractPlainSocketImpl.connect(Unknown Source) ~[?:?]
ifs-file-storage          |     at java.net.Socket.connect(Unknown Source) ~[?:?]
ifs-file-storage          |     at java.net.Socket.connect(Unknown Source) ~[?:?]
ifs-file-storage          |     at sun.net.NetworkClient.doConnect(Unknown Source) ~[?:?]
ifs-file-storage          |     at sun.net.www.http.HttpClient.openServer(Unknown Source) ~[?:?]
ifs-file-storage          |     at sun.net.www.http.HttpClient.openServer(Unknown Source) ~[?:?]
ifs-file-storage          |     at sun.net.www.http.HttpClient.<init>(Unknown Source) ~[?:?]
ifs-file-storage          |     at sun.net.www.http.HttpClient.New(Unknown Source) ~[?:?]

 

Is there any workaround for the above errors?

 

Best Regards,

/Methshika

icon

Best answer by chanaka-shanil 17 October 2022, 08:36

View original

7 replies

Userlevel 5
Badge +13

Hi @EntMethAb 

 

Hope you performed the steps carefully and performed  “Synchronize Libraries” step as well and all the jar files got synced into your local workspace without any issue.

 

Hope you selected the “Docker” option from technologies but nor Kubernetes. 

https://docs.ifs.com/techdocs/22r2/060_development/050_development_tools/002_developer_studio/030_reference/600_java_debugger/

https://docs.ifs.com/techdocs/22r2/060_development/050_development_tools/002_developer_studio/020_project_setup/080_technologies/

 

/Harshini

Badge +2

Hi @hamalk ,

I have set the docker in the project properties and also followed the steps correctly mentioned in the documentation. 

I can see the containers are running in the docker desktop but when starting the application it gives some loading errors we shown below.

Could this be due to any setting in the docker desktop?

I have attached the server stat up log and docker-compose.yml and services_vars.

it mainly gives the following error:

ifsapp-odata            | cat: can't open '/run/secrets/kubernetes.io/serviceaccount/token': No such file or directory
ifsapp-odata            | cat: can't open '/run/secrets/kubernetes.io/serviceaccount/namespace': No such file or directory
ifsapp-odata            | curl: (6) Could not resolve host: kubernetes.default.svc
ifsapp-client-services  | curl: (6) Could not resolve host: kubernetes.default.svc
ifs-file-storage        | curl: (6) Could not resolve host: kubernetes.default.svc
ifsapp-odata            | curl: (6) Could not resolve host: kubernetes.default.svc

 

 

 

Best Regards,

/Methshika

Userlevel 5
Badge +13

Hi @EntMethAb 

 

It’s not nice to get those errors, but you can ignore the errors it seems, the functionality works works fine even with these errors.

May be OData team can give us the reason for these errors thrown by OData and FSS. tagging @chanaka-shanil  and @kosaladesilva 

 

/Harshini

Userlevel 6
Badge +15

The curl: (6) Could not resolve host: kubernetes.default.svc error is there because the way secrets are trying to be fetched at startup, since running via docker, there is no Kubernetes involved you get this error. Eventhough the error is there you can ignore and continue.

Badge +2

Hi @chanaka-shanil ,

I get another error saying:

ifs-file-storage        | 04:29:12.973 [Timer-0] ERROR com.ifsworld.storage.service.scanner.ScanProcessor - Error occurred while checking Scanner Status.
ifs-file-storage        | java.net.UnknownHostException: ifs-virus-scanner
ifs-file-storage        |     at java.net.AbstractPlainSocketImpl.connect(Unknown Source) ~[?:?]
ifs-file-storage        |     at java.net.Socket.connect(Unknown Source) ~[?:?]
ifs-file-storage        |     at java.net.Socket.connect(Unknown Source) ~[?:?]
ifs-file-storage        |     at sun.net.NetworkClient.doConnect(Unknown Source) ~[?:?]
ifs-file-storage        |     at sun.net.www.http.HttpClient.openServer(Unknown Source) ~[?:?]
ifs-file-storage        |     at sun.net.www.http.HttpClient.openServer(Unknown Source) ~[?:?]
ifs-file-storage        |     at sun.net.www.http.HttpClient.<init>(Unknown Source) ~[?:?]

 

may be this too can be ignored?

However, I cannot load the application. Could this be due to that it tried to load the application using ifssys user?.. it gives the error as below as well when loading:

 

 

Best Regards,

/Methshika

Userlevel 6
Badge +15

You need to login as a enduser. IFSSYS is not a enduser.

As for the error “ifs-file-storage | java.net.UnknownHostException: ifs-virus-scanner. You can ignore this also. This can be an issue if you are specifically developing File Storage functionality. But again, there is a workaround for it. 
 

Badge +2

 Hi @chanaka-shanil ,

Thanks for your inputs!..

It seems when using the user ifsapp instead ifssys, the application loaded without any issue.

Best Regards,

/Methshika

 

Reply