2019-07-15 00:30:18 UTC - Marty Wallace: Hey guys, is there a preferred channel for me to ask about some problems I've been having with OpenWhisk with IBM? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563150618433100 ---- 2019-07-15 01:03:06 UTC - Rodric Rabbah: Hi Marty. There are some ibmers in this channel. If the problem isn’t specific to ibm others might be able to help. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563152586434100 ---- 2019-07-15 01:05:14 UTC - Marty Wallace: Hard to say whether it’s specific to IBM but basically the problem we are experiencing using IBM’s OpenWhisk with MessageHub is it seems like for the last 6-8 weeks our OpenWhisk actions stop getting invoked indefinitely, at the moment this happens every weekend https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563152714435700?thread_ts=1563152714.435700&cid=C3TPCAQG1 ---- 2019-07-15 01:05:41 UTC - Marty Wallace: I basically have to go into the IBM dashboard and completely delete the topic and the action, then re-create them and it starts working again https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563152741436300 ---- 2019-07-15 01:06:18 UTC - Marty Wallace: When I look at bytes in and bytes out for the topic, I can validate that things are still going into the queue they just never come out and invoke the expected OpenWhisk action https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563152778437200?thread_ts=1563152778.437200&cid=C3TPCAQG1 ---- 2019-07-15 01:13:03 UTC - Rodric Rabbah: Might be specific to ibm. cc @Michael Behrendt https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563153183437900?thread_ts=1563152778.437200&cid=C3TPCAQG1 ---- 2019-07-15 01:13:30 UTC - Rodric Rabbah: i wonder if the trigger feed is still installed https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563153210438700?thread_ts=1563152778.437200&cid=C3TPCAQG1 ---- 2019-07-15 01:14:29 UTC - Marty Wallace: We’re most likely going to move to a system where we just deploy the action as a service that manually consumes from the queue instead, but wanted to make sure this wasn’t some known issue with a straightforward solution before we go ahead and do that https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563153269439900 ---- 2019-07-15 03:14:29 UTC - chris: @chetanm Dear chetanm, I am not sure if i bother u again :disappointed_relieved:
the openwhisk i installed by applying `apihost:localhost:3233`the solution u guys taught me last week. I am trying to run openwhisk on the jupyter. I can use `curl -I <http://172.17.0.1:9992>` `curl -I http://<ip>:9992` to call another container service i created and `reutrn 200 OK` on the jupyter platfrom. But, I tried `curl -I <http://172.17.0.1:3233>` or `curl -I <http://host.docker.internal:3233>` or `localhost:3233 ` to call openwhisk. All of them are failed. I surf the google like : how container connect to localhost... but still not it is not settled yet. :thinking_face: https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563160469440400?thread_ts=1562902316.394900&cid=C3TPCAQG1 ---- 2019-07-15 09:15:49 UTC - Pepi Paraskevoulakou: hello guys! i tried to install <https://github.com/apache/incubator-openwhisk-devtools/blob/master/docker-compose/README.md> in my virtual machine, i installed docker, docker compose and java8 but when i try to command “make quick start” i get an error like “make: *** No rule to make target ‘quick-start’. Stop.” can anyone help me? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563182149442800 ---- 2019-07-15 09:39:04 UTC - Pepi Paraskevoulakou: i followed these instructions and when i tried to do “make quick-start” i got the following message https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563183544443200?thread_ts=1563183544.443200&cid=C3TPCAQG1 ---- 2019-07-15 09:46:04 UTC - Roberto Diaz: it seems that you are not running docker in your computer https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563183964443700?thread_ts=1563183544.443200&cid=C3TPCAQG1 ---- 2019-07-15 09:46:30 UTC - Roberto Diaz: you need docker running before call `make quick-start` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563183990443900?thread_ts=1563183544.443200&cid=C3TPCAQG1 ---- 2019-07-15 09:46:45 UTC - Pepi Paraskevoulakou: actuall after https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563184005444300 ---- 2019-07-15 09:47:00 UTC - Pepi Paraskevoulakou: actually after git clone <https://github.com/apache/incubator-openwhisk-devtools.git> cd incubator-openwhisk-devtools/docker-compose, make quick-start https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563184020444600 ---- 2019-07-15 09:47:15 UTC - Pepi Paraskevoulakou: i put sudo before make quick start https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563184035444900 ---- 2019-07-15 09:48:52 UTC - Roberto Diaz: have you started docker before call `quick-start`? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563184132445400 ---- 2019-07-15 09:49:37 UTC - Pepi Paraskevoulakou: could you give instructions to make it run? i thought that when i run “hello world” the docker is running https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563184177446200 ---- 2019-07-15 10:29:31 UTC - Pepi Paraskevoulakou: anyone knows that? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563186571446400 ---- 2019-07-15 12:22:45 UTC - Michael Schmidt: If I am creating a secret for use with an ingress controller, what should the files for my private key and public certificate be? Where are the default cert files that openwhisk uses by default when it wakes up. If I know this, I can overwrite them with my k8s secret data. When I look at the values file I see `wsk.ingress.tls.crt` set to `crt` by default and `wsk.ingress.tls.key` set to `key` by default. Does this mean when I create my k8s secret that I should use files named key and crt? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563193365450100 ---- 2019-07-15 12:24:43 UTC - Michael Schmidt: This is still related to me trying to get the tls working so that I can use the kafka tirgger (which uses tls calls in the code itself, so I don't want to fork that) https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563193483451000 ---- 2019-07-15 12:33:24 UTC - Michael Schmidt: I got it!!!!!! Okay i will put together some documentation and then ask where things should go! clap : Rodric Rabbah +1 : Rodric Rabbah https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563194004451600 ---- 2019-07-15 12:33:51 UTC - Michael Schmidt: @Rodric Rabbah I got it! it expects the key file to be called `key` and the crt file to actually be called `crt` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563194031451700?thread_ts=1562949135.422900&cid=C3TPCAQG1 ---- 2019-07-15 12:33:54 UTC - Michael Schmidt: WOOT! https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563194034451900?thread_ts=1562949135.422900&cid=C3TPCAQG1 ---- 2019-07-15 13:05:54 UTC - Roberto Santiago: I am having a problem with openwhisk invoker pools. I am getting that the server is busy or overloaded when I do `wsk api list`. When I look at the controller it says it cannot find any invokers. When I look at the invokers I see that it cannot find the DockerDaemon (or its actually healthy... or at least appears to be). Anyone have ideas about this? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563195954454400?thread_ts=1563195954.454400&cid=C3TPCAQG1 ---- 2019-07-15 14:27:30 UTC - dubee: Have you tried doing a `wsk trigger get` on your MessageHub trigger? If your trigger is being disabled for some reason, a status should be shown when getting the trigger. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563200850454500?thread_ts=1563152714.435700&cid=C3TPCAQG1 ---- 2019-07-15 14:38:46 UTC - Michael Schmidt: If you kill the invoker, does it come back? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563201526454900 ---- 2019-07-15 14:47:10 UTC - Rodric Rabbah: it should https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563202030455100 ---- 2019-07-15 14:47:38 UTC - Rodric Rabbah: if the invoker cannot execute docker commands, it will marked unhealthy https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563202058455400?thread_ts=1563195954.454400&cid=C3TPCAQG1 ---- 2019-07-15 14:48:09 UTC - Michael Schmidt: Sorry that was to try and help @Roberto Santiago troubleshoot :stuck_out_tongue: yay : Rodric Rabbah, Michael Schmidt +1 : Rodric Rabbah https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563202089456000 ---- 2019-07-15 14:57:28 UTC - Roberto Santiago: Thanks @Michael Schmidt Yes. It does. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563202648456600 ---- 2019-07-15 14:58:05 UTC - Michael Schmidt: That is always my first troubleshooting step lol https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563202685456900 ---- 2019-07-15 15:29:41 UTC - Michael Schmidt: @Roberto Santiago try checking your permissions for docker https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1563204581457100?thread_ts=1563195954.454400&cid=C3TPCAQG1 ----
