You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwhisk.apache.org by OpenWhisk Team Slack <ra...@apache.org> on 2021/10/07 12:13:32 UTC
[slack-digest] [2021-10-06] #general
2021-10-06 09:59:51 UTC - trungquan dao: Can everyone who help me to fix that bug, please? :(( I took over 6 hours for it and I don't actually understand it. That bug->Execution failed for task ':core:standalone:copyGWActions'. thanks for helping me :heart:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1633514391037400
----
2021-10-06 10:02:31 UTC - trungquan dao:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1633514551037500?thread_ts=1633514551.037500&cid=C3TPCAQG1
----
2021-10-06 10:47:17 UTC - Pavel Kravchenko: Hello, experiencing issue in my multinode cluster with zookeeper in `CrashLoopBackOff` and as a result kafka hangs in `init` state.
Zookeeper logs show no error:
```0
tickTime=2000
clientPort=2181
initLimit=5
syncLimit=2
dataDir=/data
dataLogDir=/datalog
server.0=owdev-zookeeper-0.owdev-zookeeper.openwhisk.svc.cluster.local:2888:3888
ZooKeeper JMX enabled by default
Using config: /conf/zoo.cfg
log4j:WARN No appenders could be found for logger (org.apache.zookeeper.server.quorum.QuorumPeerConfig).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See <http://logging.apache.org/log4j/1.2/faq.html#noconfig> for more info.```
And the pod has no error events:
```Tolerations: <http://node.kubernetes.io/not-ready:NoExecute|node.kubernetes.io/not-ready:NoExecute> for 300s
<http://node.kubernetes.io/unreachable:NoExecute|node.kubernetes.io/unreachable:NoExecute> for 300s
openwhisk-role=core:NoSchedule
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 3m46s default-scheduler Successfully assigned openwhisk/owdev-zookeeper-0 to vnode-1.localdomain
Normal Pulled 111s (x5 over 3m41s) kubelet, vnode-1.localdomain Container image "zookeeper:3.4" already present on machine
Normal Created 110s (x5 over 3m40s) kubelet, vnode-1.localdomain Created container zookeeper
Normal Started 110s (x5 over 3m39s) kubelet, vnode-1.localdomain Started container zookeeper
Warning BackOff 108s (x10 over 3m27s) kubelet, vnode-1.localdomain Back-off restarting failed container```
Please advice how to debug this error?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1633517237041800
----
2021-10-06 11:47:23 UTC - Pavel Kravchenko: Simulated "starting" zookeeper pod container and tried to run `zkServer.sh start-foreground` manually from inside. Appears that command finishes immediately with error code 1 without any meaningful messages
```root@owdev-zookeeper-0:/zookeeper-3.4.14# zkServer.sh start-foreground
ZooKeeper JMX enabled by default
Using config: /conf/zoo.cfg
log4j:WARN No appenders could be found for logger (org.apache.zookeeper.server.quorum.QuorumPeerConfig).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See <http://logging.apache.org/log4j/1.2/faq.html#noconfig> for more info.
root@owdev-zookeeper-0:/zookeeper-3.4.14# echo $?
1```
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1633520843045300?thread_ts=1633520843.045300&cid=C3TPCAQG1
----
2021-10-06 12:43:43 UTC - Pavel Kravchenko: Another question, what are the right steps to redeploy OpenWhisk on kubernetes while keeping couchdb state?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1633524223052800?thread_ts=1633524223.052800&cid=C3TPCAQG1
----