You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openserverless.apache.org by "sgallizia (via GitHub)" <gi...@apache.org> on 2025/05/19 10:51:19 UTC
[I] infinite loop "waiting for APIHOST ready" [openserverless]
sgallizia opened a new issue, #128:
URL: https://github.com/apache/openserverless/issues/128
- [x ] I have searched the [issues](https://github.com/apache/openserverless/issues) of this repository and believe that this is not a duplicate.
### Ⅰ. Issue Description
I'm installing OpenServerless on a Ubuntu server within my home intranet. I followed the instructions on this page: https://openserverless.apache.org/docs/installation/install/server/.
After meeting all the prerequisites, I ran the following command:
`ops setup server 192.168.1.171 <ssh user>` (also tried with the hostname)
However, the process doesn't complete—it gets stuck in an infinite loop with the following output:
0... waiting for APIHOST ready
1... waiting for APIHOST ready
2... waiting for APIHOST ready
3... waiting for APIHOST ready
...
ops cli is installed on ubuntu (wsl)
### Ⅱ. Describe what happened
-
### Ⅲ. Describe what you expected to happen
The installation must complete
### Ⅳ. How to reproduce it (as minimally and precisely as possible)
-
### Ⅴ. Anything else we need to know?
### Ⅵ. Environment:
cli version: 0.1.0-2409121919.dev
k3s version: v1.27.7-rc1+k3s2
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] infinite loop "waiting for APIHOST ready" [openserverless]
Posted by "d4rkstar (via GitHub)" <gi...@apache.org>.
d4rkstar commented on issue #128:
URL: https://github.com/apache/openserverless/issues/128#issuecomment-2890742070
Hello,
probably you didn't configure DNS: https://openserverless.apache.org/docs/installation/configure/dns/
Try to do this:
`ops config reset`
`ops config minimal`
`ops config apihost 192.168.1.171.traefik.me --protocol=auto`
`ops setup server 192.168.1.171 <ssh user>`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] infinite loop "waiting for APIHOST ready" [openserverless]
Posted by "sgallizia (via GitHub)" <gi...@apache.org>.
sgallizia commented on issue #128:
URL: https://github.com/apache/openserverless/issues/128#issuecomment-2891290051
Thank you very much for you answer, the installation now completes without errors. However, I'm encountering a new issue: when I try to deploy a simple golang function, I get the following error:
"required S3_API_URL environment variable is not set!"
ops ide deploy
bun install v1.2.5 (013fdddc)
+ @types/bun@1.2.2
+ chokidar@4.0.3
+ commander@13.1.0
+ dotenv@16.4.7
+ glob@11.0.1
43 packages installed [165.00ms]
/home/<user>/.ops/tmp/deploy.pid
PID 657609
> Scan:
>> Action: packages/test/test.go
> Deploying:
>> Package: test
$ $OPS package update test
ok: updated package test
>>> Action: packages/test/test.go
$ $OPS action update test/test packages/test/test.go
ok: updated action test/test
build process exited with code 0
UPLOAD ASSETS FROM web
**required S3_API_URL environment variable is not set!**
ops: Failed to run task "upload": exit status 1
task execution error: ops: Failed to run task "upload": exit status 1
ops: Failed to run task "deploy": exit status 1
task execution error: ops: Failed to run task "deploy": exit status 1
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] infinite loop "waiting for APIHOST ready" [openserverless]
Posted by "d4rkstar (via GitHub)" <gi...@apache.org>.
d4rkstar commented on issue #128:
URL: https://github.com/apache/openserverless/issues/128#issuecomment-2898970128
@sgallizia: please open a specific issue for S3_API_URL: i'll be glad to help.
If you want, try to reach us on our live channels
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] infinite loop "waiting for APIHOST ready" [openserverless]
Posted by "d4rkstar (via GitHub)" <gi...@apache.org>.
d4rkstar commented on issue #128:
URL: https://github.com/apache/openserverless/issues/128#issuecomment-2892011389
Try to enable minio: https://openserverless.apache.org/docs/installation/configure/services/#minio
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] infinite loop "waiting for APIHOST ready" [openserverless]
Posted by "sgallizia (via GitHub)" <gi...@apache.org>.
sgallizia commented on issue #128:
URL: https://github.com/apache/openserverless/issues/128#issuecomment-2894806521
I think I've solved it. I ran the command on the server:
```
:~$ kubectl get svc -n nuvolaris
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
couchdb ClusterIP 10.43.128.118 <none> 5984/TCP 25h
couchdb-np NodePort 10.43.252.24 <none> 5984:30984/TCP 25h
redis NodePort 10.43.163.123 <none> 6379:30379/TCP 25h
nuvolaris-minio NodePort 10.43.43.80 <none> 9000:32090/TCP,9090:32091/TCP 25h
nuvolaris-static-svc ClusterIP 10.43.170.115 <none> 8080/TCP 25h
kubegres-controller-manager-metrics-service ClusterIP 10.43.68.82 <none> 8443/TCP 25h
nuvolaris-postgres ClusterIP None <none> 5432/TCP 25h
nuvolaris-mongodb-svc ClusterIP None <none> 27017/TCP 25h
zookeeper ClusterIP None <none> 2181/TCP,2888/TCP,3888/TCP 25h
nuvolaris-postgres-replica ClusterIP None <none> 5432/TCP 25h
kafka ClusterIP None <none> 9092/TCP,9071/TCP,9888/TCP 25h
invoker ClusterIP 10.43.183.238 <none> 8080/TCP 25h
controller NodePort 10.43.183.175 <none> 3233:30233/TCP 25h
```
I took the cluster ip of the nuvolaris-minio and I ran:
```
export S3_API_URL=http://10.43.43.80:9000
ops ide deploy
/home/user/.ops/tmp/deploy.pid
PID 719534
> Scan:
>> Action: packages/test/test.go
> Deploying:
>> Package: test
$ $OPS package update test
ok: updated package test
>>> Action: packages/test/test.go
$ $OPS action update test/test packages/test/test.go
ok: updated action test/test
build process exited with code 0
UPLOAD ASSETS FROM web
ERROR: /home/user/path/packages/data/test/web is not a directory
URL: http://testuser.192.168.1.171.traefik.me
```
So I created the web directory and then it worked.
It's not clear to me why S3_API_URL is missing and why the web directory is mandatory.
Now I can finally start using openserverless (I hope :) )
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] infinite loop "waiting for APIHOST ready" [openserverless]
Posted by "sgallizia (via GitHub)" <gi...@apache.org>.
sgallizia closed issue #128: infinite loop "waiting for APIHOST ready"
URL: https://github.com/apache/openserverless/issues/128
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] infinite loop "waiting for APIHOST ready" [openserverless]
Posted by "sgallizia (via GitHub)" <gi...@apache.org>.
sgallizia commented on issue #128:
URL: https://github.com/apache/openserverless/issues/128#issuecomment-2893701622
Yes, but I did again all the steps and I'm still facing the same error:
```
ops admin adduser testuser test@test.it testuser --all
Generated TESTUSER user secrets.
Creating user testuser...
whiskuser.nuvolaris.org/testuser created
```
```
ops ide login testuser http://192.168.1.171.traefik.me
*** Configuring Access to OpenServerless ***
apihost=http://192.168.1.171.traefik.me username=testuser
Logging in http://192.168.1.171.traefik.me as testuser
Enter Password:
Successfully logged in as testuser.
ok: whisk auth set. Run 'wsk property get --auth' to see the new value.
ok: whisk API host set to http://192.168.1.171.traefik.me
OpenServerless host and auth set successfully. You are now ready to use ops!
```
```
ops ide deploy
/home/user/.ops/tmp/deploy.pid
PID 702587
> Scan:
>> Action: packages/test/test.go
> Deploying:
>> Package: test
$ $OPS package update test
ok: updated package test
>>> Action: packages/test/test.go
$ $OPS action update test/test packages/test/test.go
ok: updated action test/test
build process exited with code 0
UPLOAD ASSETS FROM web
required S3_API_URL environment variable is not set!
ops: Failed to run task "upload": exit status 1
task execution error: ops: Failed to run task "upload": exit status 1
ops: Failed to run task "deploy": exit status 1
task execution error: ops: Failed to run task "deploy": exit status 1
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] infinite loop "waiting for APIHOST ready" [openserverless]
Posted by "d4rkstar (via GitHub)" <gi...@apache.org>.
d4rkstar commented on issue #128:
URL: https://github.com/apache/openserverless/issues/128#issuecomment-2893643881
When you created the user, did you enable it for all services?
`ops admin adduser <user> <email> <password> --all`
If, not, try to create an additional user and check if that works.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] infinite loop "waiting for APIHOST ready" [openserverless]
Posted by "sgallizia (via GitHub)" <gi...@apache.org>.
sgallizia commented on issue #128:
URL: https://github.com/apache/openserverless/issues/128#issuecomment-2893347313
I'm still getting the error.
I believe minio was already running, as it's part of the minimal configuration. I ran the two commands, and I can see the following output:
NAME READY STATUS RESTARTS AGE
minio-deployment-59d9b8c4dd-4bhvl 1/1 Running 0 18h
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] infinite loop "waiting for APIHOST ready" [openserverless]
Posted by "sgallizia (via GitHub)" <gi...@apache.org>.
sgallizia commented on issue #128:
URL: https://github.com/apache/openserverless/issues/128#issuecomment-2898363119
> > I think I've solved it. I ran the command on the server:
> > ```
> > :~$ kubectl get svc -n nuvolaris
> > NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
> > couchdb ClusterIP 10.43.128.118 <none> 5984/TCP 25h
> > couchdb-np NodePort 10.43.252.24 <none> 5984:30984/TCP 25h
> > redis NodePort 10.43.163.123 <none> 6379:30379/TCP 25h
> > nuvolaris-minio NodePort 10.43.43.80 <none> 9000:32090/TCP,9090:32091/TCP 25h
> > nuvolaris-static-svc ClusterIP 10.43.170.115 <none> 8080/TCP 25h
> > kubegres-controller-manager-metrics-service ClusterIP 10.43.68.82 <none> 8443/TCP 25h
> > nuvolaris-postgres ClusterIP None <none> 5432/TCP 25h
> > nuvolaris-mongodb-svc ClusterIP None <none> 27017/TCP 25h
> > zookeeper ClusterIP None <none> 2181/TCP,2888/TCP,3888/TCP 25h
> > nuvolaris-postgres-replica ClusterIP None <none> 5432/TCP 25h
> > kafka ClusterIP None <none> 9092/TCP,9071/TCP,9888/TCP 25h
> > invoker ClusterIP 10.43.183.238 <none> 8080/TCP 25h
> > controller NodePort 10.43.183.175 <none> 3233:30233/TCP 25h
> > ```
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > I took the cluster ip of the nuvolaris-minio and I ran:
> > ```
> > export S3_API_URL=http://10.43.43.80:9000
> > ops ide deploy
> > /home/user/.ops/tmp/deploy.pid
> > PID 719534
> > > Scan:
> > >> Action: packages/test/test.go
> > > Deploying:
> > >> Package: test
> > $ $OPS package update test
> > ok: updated package test
> > >>> Action: packages/test/test.go
> > $ $OPS action update test/test packages/test/test.go
> > ok: updated action test/test
> > build process exited with code 0
> > UPLOAD ASSETS FROM web
> > ERROR: /home/user/path/packages/data/test/web is not a directory
> > URL: http://testuser.192.168.1.171.traefik.me
> > ```
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > So I created the web directory and then it worked. It's not clear to me why S3_API_URL is missing and why the web directory is mandatory. Now I can finally start using openserverless (I hope :) )
>
> Hello [@sgallizia](https://github.com/sgallizia)! Sorry I didn't noticed you're using golang.
>
> However:
>
> 1. the `ops ide deploy` will deploy the "application" as packages and web. So you have to create an empty "web" folder if you don't use it
> 2. currently the deployer supports only php, python and nodejs actions. Other languages may require some fix: you can eventually open a specific issue.
> 3. the message `required S3_API_URL environment variable is not set!` was coming from `ops util upload` that is used by the deployer to upload files to your web folder. Probably this part was resolved when minio was enabled. But then you needed to create the "web" folder. This is confirmed by the last part of your logs:
>
> ```
> UPLOAD ASSETS FROM web
> **required S3_API_URL environment variable is not set!**
> ops: Failed to run task "upload": exit status 1
> task execution error: ops: Failed to run task "upload": exit status 1
> ops: Failed to run task "deploy": exit status 1
> task execution error: ops: Failed to run task "deploy": exit status 1
> ```
>
> Let me know if you need further assistance, otherwise please close this issue.
>
> Regards
The message `required S3_API_URL environment variable is not set!` was resolved after I set the env variable as I wrote before:
export S3_API_URL=http://10.43.43.80:9000
I can close the ticket, but I think you should address the issue about the S3_API_URL env.
Thank you for your support!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] infinite loop "waiting for APIHOST ready" [openserverless]
Posted by "d4rkstar (via GitHub)" <gi...@apache.org>.
d4rkstar commented on issue #128:
URL: https://github.com/apache/openserverless/issues/128#issuecomment-2897678090
> I think I've solved it. I ran the command on the server:
>
> ```
> :~$ kubectl get svc -n nuvolaris
> NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
> couchdb ClusterIP 10.43.128.118 <none> 5984/TCP 25h
> couchdb-np NodePort 10.43.252.24 <none> 5984:30984/TCP 25h
> redis NodePort 10.43.163.123 <none> 6379:30379/TCP 25h
> nuvolaris-minio NodePort 10.43.43.80 <none> 9000:32090/TCP,9090:32091/TCP 25h
> nuvolaris-static-svc ClusterIP 10.43.170.115 <none> 8080/TCP 25h
> kubegres-controller-manager-metrics-service ClusterIP 10.43.68.82 <none> 8443/TCP 25h
> nuvolaris-postgres ClusterIP None <none> 5432/TCP 25h
> nuvolaris-mongodb-svc ClusterIP None <none> 27017/TCP 25h
> zookeeper ClusterIP None <none> 2181/TCP,2888/TCP,3888/TCP 25h
> nuvolaris-postgres-replica ClusterIP None <none> 5432/TCP 25h
> kafka ClusterIP None <none> 9092/TCP,9071/TCP,9888/TCP 25h
> invoker ClusterIP 10.43.183.238 <none> 8080/TCP 25h
> controller NodePort 10.43.183.175 <none> 3233:30233/TCP 25h
> ```
>
> I took the cluster ip of the nuvolaris-minio and I ran:
>
> ```
> export S3_API_URL=http://10.43.43.80:9000
> ops ide deploy
> /home/user/.ops/tmp/deploy.pid
> PID 719534
> > Scan:
> >> Action: packages/test/test.go
> > Deploying:
> >> Package: test
> $ $OPS package update test
> ok: updated package test
> >>> Action: packages/test/test.go
> $ $OPS action update test/test packages/test/test.go
> ok: updated action test/test
> build process exited with code 0
> UPLOAD ASSETS FROM web
> ERROR: /home/user/path/packages/data/test/web is not a directory
> URL: http://testuser.192.168.1.171.traefik.me
> ```
>
> So I created the web directory and then it worked. It's not clear to me why S3_API_URL is missing and why the web directory is mandatory. Now I can finally start using openserverless (I hope :) )
Hello @sgallizia!
Sorry I didn't noticed you're using golang.
However:
1. the `ops ide deploy` will deploy the "application" as packages and web. So you have to create an empty "web" folder if you don't use it
2. currently the deployer supports only php, python and nodejs actions. Other languages may require some fix: you can eventually open a specific issue.
3. the message `required S3_API_URL environment variable is not set!` was coming from `ops util upload` that is used by the deployer to upload files to your web folder. Probably this part was resolved when minio was enabled. But then you needed to create the "web" folder. This is confirmed by the last part of your logs:
```
UPLOAD ASSETS FROM web
**required S3_API_URL environment variable is not set!**
ops: Failed to run task "upload": exit status 1
task execution error: ops: Failed to run task "upload": exit status 1
ops: Failed to run task "deploy": exit status 1
task execution error: ops: Failed to run task "deploy": exit status 1
```
Let me know if you need further assistance, otherwise please close this issue.
Regards
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@openserverless.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org