fission: getting error while running a function

Hello When I run a function, I will get the error message like this:

fission fn list
NAME  UID                                  ENV    EXECUTORTYPE MINSCALE MAXSCALE TARGETCPU
hello 6a0159b0-4202-11e8-9901-ce0dcdd7b986 nodejs poolmgr

#fission function test --name hello
Failed to execute HTTP request: Get http://[my ip]:31314/fission-function/hello: dial tcp [my ip]:31314: getsockopt: connection refused

fission version:

Client Version: {"GitCommit":"0247ea488e7e2f4b23b46ec9757d7b381caccf81","BuildDate":"2018-04-02T22:54:21Z","Version":"0.7.0"}
Server Version: {"GitCommit":"0247ea488e7e2f4b23b46ec9757d7b381caccf81","BuildDate":"2018-04-02T22:54:21Z","Version":"0.7.0"}

helm version:

Client: &version.Version{SemVer:"v2.7.0", GitCommit:"08c1144f5eb3e3b636d9775617287cc26e53dba4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.7.0", GitCommit:"08c1144f5eb3e3b636d9775617287cc26e53dba4", GitTreeState:"clean"}

OS: Linux srv 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64 GNU/Linux

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 16 (8 by maintainers)

Most upvoted comments

IMHO in the installation documentation for Minikube, we should pass --set routerServiceType=NodePort. If it’s ok for you I can open a pull request

chinmay5 on Apr 24, 2018

Good to hear it works now! And sorry for the confusion. I will update a section to explain how to set FISSION_ROUTER properly.

For questions:

If fission is installed with helm variable routerServiceType=NodePort , then port will be 31314. Otherwise, k8s will assign a port for router service. So, I recommend following way to get router port

$ kubectl -n fission get svc router -o jsonpath='{...nodePort}'
32471

2: No, it’s not necessary to set FISSION_URL from 0.6.0. The CLI will try to get controller service information automatically.

life1347 on Apr 24, 2018