Skip to main content
Question

Kubernetes Timeout during install main.ps1

  • September 6, 2023
  • 4 replies
  • 333 views
P
Sidekick (Customer)
Forum|alt.badge.img+8
  • PROAHAR
  • Sidekick (Customer)
  • 44 replies

Exact error:

C:\ifsroot-test\main.ps1 : Error found in Exception calling "EndExecute" with "1" argument(s): "Command '(bash
install-k8s.sh ifscloud.jfrog.io https docker )' has timed out.". Please
check logs for details.
At line:1 char:1
+ .\main.ps1
+ ~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,main.ps1

 

Tried a few different things to no effect. Does anyone have any suggestions?

4 replies

B
Superhero (Employee)
Forum|alt.badge.img+15
  • Ben Monroe
  • Superhero (Employee)
  • 182 replies
  • September 6, 2023

This looks like part of the 'KUBERNETES' step.
The error indicates that a timeout occurred while sending the following command to ifs-remote:

bash install-k8s.sh ifscloud.jfrog.io https docker

Please confirm that you can ping your ifs-remote server from your Windows Management server.
Also, please confirm that you can ping ifscloud.jfrog.io from within your ifs-remote server.

Best regards, Ben

P
Sidekick (Customer)
Forum|alt.badge.img+8
  • PROAHAR
  • Author
  • Sidekick (Customer)
  • 44 replies
  • September 7, 2023

Can ping both no problem. Running the command manually seems to point to this being the source of the timeout:

 

unable to recognize "/var/snap/microk8s/current/args/cni-network/cni.yaml": Get "https://127.0.0.1:16443/api?timeout=32s": net/http: TLS handshake timeout
unable to recognize "/var/snap/microk8s/current/args/cni-network/cni.yaml": Get "https://127.0.0.1:16443/api?timeout=32s": net/http: TLS handshake timeout
Unable to connect to the server: net/http: TLS handshake timeout
Unable to connect to the server: net/http: TLS handshake timeout
127.0.0.1       api.snapcraft.io already exists in /etc/hosts)

 

Many thanks,

Alex

durette
Superhero (Customer)
Forum|alt.badge.img+19
  • durette
  • Superhero (Customer)
  • 542 replies
  • May 15, 2024

Does it work if you run these first?

.\main.ps1 -resource 'DISABLEAPPARMORPROFILE'
.\main.ps1 -resource 'FIREWALL' -status 'DISABLE'

 

If you find this forum useful, please consider paying back to the community in your own areas of expertise. If you ask for help in a private message, please know that I will likely repost it as a forum question (with your personal details redacted) and answer it publicly. -- Kevin Durette - https://www.linkedin.com/in/kevindurette
Suraj_Kaushal
Do Gooder (Partner)
Forum|alt.badge.img+2
  • Suraj_Kaushal
  • Do Gooder (Partner)
  • 1 reply
  • June 15, 2024

Hi @durette 

Yes, I had the same issue and its fixed after disabling the firewall on the remote-server. Thank you for your help. 

 

.\main.ps1 -resource 'DISABLEAPPARMORPROFILE'

.\main.ps1 -resource 'FIREWALL' -status 'DISABLE'

 

Regards, 

Suraj 

Regards, Sk


Terms & ConditionsCookie settingsAccessibility statement