You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by "QWQyyy (via GitHub)" <gi...@apache.org> on 2023/05/12 10:01:34 UTC
[GitHub] [openwhisk-deploy-kube] QWQyyy opened a new issue, #764: get api error: Unable to obtain the API list
QWQyyy opened a new issue, #764:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/764
sometimes openwhisk-deploy-kube get error, but openwhisk system can run very well. I don't quite understand why such an error occurs when the function can be deployed, very confusing and requires a redeployment of the openwhisk system.
--
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: issues-unsubscribe@openwhisk.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk-deploy-kube] QWQyyy commented on issue #764: get api error: Unable to obtain the API list
Posted by "QWQyyy (via GitHub)" <gi...@apache.org>.
QWQyyy commented on issue #764:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/764#issuecomment-1545763400
@style95 Once I set the copy of Invoker to be greater than 1, this kind of error occurs, and when set to 1, I also face this problem at the beginning of creation, but, my resources are sufficient, and I lowered the container when setting Invoker to 2 The configuration of the pool, I'm confused what is the cause of this problem, and I can't find the correct log.
--
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: issues-unsubscribe@openwhisk.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk-deploy-kube] style95 commented on issue #764: get api error: Unable to obtain the API list
Posted by "style95 (via GitHub)" <gi...@apache.org>.
style95 commented on issue #764:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/764#issuecomment-1548843807
I believe the error is not related to invokers, you may find some logs on the controller side as it would generally happen when fetching data from CouchDB.
--
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: issues-unsubscribe@openwhisk.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk-deploy-kube] QWQyyy commented on issue #764: get api error: Unable to obtain the API list
Posted by "QWQyyy (via GitHub)" <gi...@apache.org>.
QWQyyy commented on issue #764:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/764#issuecomment-1545722014
I don't konw how to see this error logs, is schduler or invoker?
--
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: issues-unsubscribe@openwhisk.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [openwhisk-deploy-kube] QWQyyy commented on issue #764: get api error: Unable to obtain the API list
Posted by "QWQyyy (via GitHub)" <gi...@apache.org>.
QWQyyy commented on issue #764:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/764#issuecomment-1555875010
> I believe the error is not related to invokers, you may find some logs on the controller side as it would generally happen when fetching data from CouchDB.
Yes, CouchDB may not be as easy to use as ES
--
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: issues-unsubscribe@openwhisk.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org