re-xmyl opened a new issue, #5477:
URL: https://github.com/apache/openwhisk/issues/5477
I tried the methods of deployment on Ubuntu , ubuntu 18.04
When i run ansible-playbook -i environments/local openwhisk.yml
I deploy agagin but face the same problem,could you please help me find
what's wrong,thank you so much!
errors as follow:
TASK [controller : warm up activation path]
*********************************************************************************************************************************************************************************************
Saturday 20 April 2024 02:58:17 -0700 (0:00:10.731) 0:01:13.617
********
fatal: [controller0]: FAILED! => {"access_control_allow_headers":
"Authorization, Origin, X-Requested-With, Content-Type, Accept, User-Agent",
"access_control_allow_methods": "GET, DELETE, POST, PUT, HEAD",
"access_control_allow_origin": "*", "changed": false, "connection": "close",
"content": "{\"code\":\"FJgvfXLBQbxrTNajxJZ1gWexHd7VN8HI\",\"error\":\"The
requested resource does not exist.\"}", "content_length": "92", "content_type":
"application/json", "date": "Sat, 20 Apr 2024 09:58:18 GMT", "json": {"code":
"FJgvfXLBQbxrTNajxJZ1gWexHd7VN8HI", "error": "The requested resource does not
exist."}, "msg": "Status code was 404 and not [200]: HTTP Error 404: Not
Found", "redirected": false, "server": "akka-http/10.2.4", "status": 404,
"url":
"https://789c46b1-71f6-4ed5-8c54-816aa4f8c502:abczO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP@172.17.0.1:10001/api/v1/namespaces/_/actions/invokerHealthTestAction0?blocking=false&result=false",
"x_request_id": "FJgvfXLBQbxrTNajxJ
Z1gWexHd7VN8HI"}
...ignoring
Status code was 404 and not [200]: HTTP Error 404: Not Found
TASK [schedulers : wait until the Scheduler in this host is up and running]
****
Saturday 20 April 2024 03:17:31 -0700 (0:00:00.812) 0:01:54.732
********
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(12 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(11 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(10 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(9 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(8 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(7 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(6 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(5 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(4 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(3 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(2 retries left).
FAILED - RETRYING: wait until the Scheduler in this host is up and running
(1 retries left).
fatal: [scheduler0]: FAILED! => {"attempts": 12, "changed": false,
"content": "", "msg": "Status code was -1 and not [200]: Request failed:
<urlopen error [Errno 111] 拒绝连接>", "redirected": false, "status": -1, "url":
"http://172.17.0.1:14001/ping"}
Status code was -1 and not [200]: Request failed: <urlopen error [Errno
111] 拒绝连接>
the logs in container scheduler0 as follow:
[2024-04-20T08:24:39.305Z] [INFO] Cluster Node
[akka://[email protected]:25520] - Starting up, Akka version
[2.6.12] ...
[2024-04-20T08:24:39.336Z] [INFO] Cluster Node
[akka://[email protected]:25520] - Registered cluster JMX MBean
[akka:type=Cluster]
[2024-04-20T08:24:39.336Z] [INFO] Cluster Node
[akka://[email protected]:25520] - Started up successfully
[2024-04-20T08:24:39.350Z] [INFO] Cluster Node
[akka://[email protected]:25520] - No downing-provider-class
configured, manual cluster downing required, see
https://doc.akka.io/docs/akka/current/typed/cluster.html#downing
[2024-04-20T08:24:39.382Z] [INFO] Cluster Node
[akka://[email protected]:25520] - Node
[akka://[email protected]:25520] is JOINING itself (with roles
[dc-default], version [0.0.0]) and forming new cluster
[2024-04-20T08:24:39.383Z] [INFO] Cluster Node
[akka://[email protected]:25520] - is the new leader among
reachable nodes (more leaders may exist)
[2024-04-20T08:24:39.389Z] [INFO] Cluster Node
[akka://[email protected]:25520] - Leader is moving node
[akka://[email protected]:25520] to [Up]
[2024-04-20T08:24:39.769Z] [INFO] [#tid_sid_unknown] [Config] environment
set value for whisk.scheduler.endpoints.host
[2024-04-20T08:24:39.769Z] [INFO] [#tid_sid_unknown] [Config] environment
set value for limits.actions.invokes.concurrent
[2024-04-20T08:24:39.769Z] [INFO] [#tid_sid_unknown] [Config] environment
set value for whisk.scheduler.endpoints.rpcPort
[2024-04-20T08:24:39.770Z] [INFO] [#tid_sid_unknown] [Config] environment
set value for whisk.scheduler.endpoints.akkaPort
[2024-04-20T08:24:39.770Z] [INFO] [#tid_sid_unknown] [Config] environment
set value for runtimes.manifest
[2024-04-20T08:24:39.772Z] [INFO] [#tid_sid_unknown] [Config] environment
set value for kafka.hosts
[2024-04-20T08:24:39.772Z] [INFO] [#tid_sid_unknown] [Config] environment
set value for port
[2024-04-20T08:24:39.872Z] [WARN] Failed to attach the instrumentation
because the Kamon Bundle is not present on the classpath
[2024-04-20T08:24:39.959Z] [INFO] Started the Kamon StatsD reporter
[2024-04-20T08:24:40.571Z] [INFO] [#tid_sid_unknown]
[KafkaMessagingProvider] created topic scheduler0
[2024-04-20T08:24:40.690Z] [INFO] [#tid_sid_unknown]
[KafkaMessagingProvider] created topic creationAck0
[2024-04-20T08:24:41.809Z] [INFO] [#tid_sid_unknown] [LeaseKeepAliveService]
Granted a new lease Lease(7802925036371667984,10)
[2024-04-20T08:24:41.824Z] [INFO] [#tid_sid_unknown] [WatcherService] watch
endpoint:
WatchEndpoint(whisk/instance/scheduler0/lease,7802925036371667984,false,lease-service,Set(DeleteEvent))
Exception in thread "main" java.lang.ExceptionInInitializerError
at java.base/java.lang.J9VMInternals.ensureError(J9VMInternals.java:184)
at
java.base/java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:173)
at
org.apache.openwhisk.core.scheduler.queue.ElasticSearchDurationCheckerProvider$.instance(ElasticSearchDurationChecker.scala:121)
at
org.apache.openwhisk.core.scheduler.queue.ElasticSearchDurationCheckerProvider$.instance(ElasticSearchDurationChecker.scala:112)
at
org.apache.openwhisk.core.scheduler.Scheduler.<init>(Scheduler.scala:97)
at
org.apache.openwhisk.core.scheduler.Scheduler$.main(Scheduler.scala:350)
at org.apache.openwhisk.core.scheduler.Scheduler.main(Scheduler.scala)
Caused by: pureconfig.error.ConfigReaderException: Cannot convert
configuration to a
org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStoreConfig.
Failures are:
at 'whisk.activation-store.elasticsearch':
-
(jar:file:/scheduler/lib/openwhisk-common-1.0.1-SNAPSHOT.jar!/application.conf:368)
Key not found: 'protocol'.
-
(jar:file:/scheduler/lib/openwhisk-common-1.0.1-SNAPSHOT.jar!/application.conf:368)
Key not found: 'hosts'.
-
(jar:file:/scheduler/lib/openwhisk-common-1.0.1-SNAPSHOT.jar!/application.conf:368)
Key not found: 'index-pattern'.
-
(jar:file:/scheduler/lib/openwhisk-common-1.0.1-SNAPSHOT.jar!/application.conf:368)
Key not found: 'username'.
-
(jar:file:/scheduler/lib/openwhisk-common-1.0.1-SNAPSHOT.jar!/application.conf:368)
Key not found: 'password'.
at pureconfig.package$.getResultOrThrow(package.scala:139)
at pureconfig.package$.loadConfigOrThrow(package.scala:161)
at
org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore$.<init>(ElasticSearchActivationStore.scala:441)
at
org.apache.openwhisk.core.database.elasticsearch.ElasticSearchActivationStore$.<clinit>(ElasticSearchActivationStore.scala)
... 5 more
[2024-04-20T08:26:33.563Z] [WARN] Cluster Node
[akka://[email protected]:25520] - Scheduled sending of
heartbeat was delayed. Previous heartbeat was sent [7139] ms ago, expected
interval is [1000] ms. This may cause failure detection to mark members as
unreachable. The reason can be thread starvation, e.g. by running blocking
tasks on the default dispatcher, CPU overload, or GC.
bash-5.1$ S
root@ubuntu:/home/re/openwhisk/ansible# docker ps
CONTAINER ID IMAGE COMMAND
CREATED STATUS PORTS
NAMES
f5ce0ffc7d10 whisk/scheduler:latest "/bin/sh -c 'exec /i…" 8
minutes ago Up 8 minutes 0.0.0.0:13001->13001/tcp,
0.0.0.0:21000->21000/tcp, 0.0.0.0:22000->22000/tcp, 0.0.0.0:25520->3551/tcp,
0.0.0.0:14001->8080/tcp scheduler0
53e1e6089e0f whisk/controller:latest "/bin/sh -c 'exec /i…" 8
minutes ago Up 8 minutes 0.0.0.0:15000->15000/tcp,
0.0.0.0:16000->16000/tcp, 0.0.0.0:8000->2551/tcp, 0.0.0.0:10001->8080/tcp
controller0
349459c3d6ed wurstmeister/kafka:2.13-2.7.0 "start-kafka.sh" 8
minutes ago Up 8 minutes 0.0.0.0:9072->9072/tcp, 0.0.0.0:9093->9093/tcp
kafka0
10f1a16afad4 zookeeper:3.4 "/docker-entrypoint.…" 9
minutes ago Up 9 minutes 0.0.0.0:2181->2181/tcp, 0.0.0.0:2888->2888/tcp,
0.0.0.0:3888->3888/tcp
zookeeper0
0dbbe02d025d quay.io/coreos/etcd:v3.4.0 "/usr/local/bin/etcd…" 9
minutes ago Up 9 minutes 0.0.0.0:2379->2379/tcp, 0.0.0.0:2480->2480/tcp,
2380/tcp
etcd0
bdd6e9d4619a apache/couchdb:2.3 "tini -- /docker-ent…" 2
hours ago Up 2 hours 0.0.0.0:4369->4369/tcp, 0.0.0.0:5984->5984/tcp,
0.0.0.0:9100->9100/tcp
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]