Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

pods for broker/bookkeeper init failed - Could not find or load main class "-Xms1g error #26

Closed
rvashishth opened this issue Jun 25, 2020 · 8 comments
Closed

pods for broker/bookkeeper init failed - Could not find or load main class "-Xms1g error #26

rvashishth opened this issue Jun 25, 2020 · 8 comments

Comments

@rvashishth
Copy link
Contributor

Describe the bug
Init container pulsar-bookkeeper-verify-clusterid fail fails to start with following stack trace

[conf/bookkeeper.conf] Applying config ledgerDirectories = /pulsar/data/bookkeeper/ledgers
[conf/bookkeeper.conf] Applying config statsProviderClass = org.apache.bookkeeper.stats.prometheus.PrometheusMetricsProvider
[conf/bookkeeper.conf] Applying config useHostNameAsBookieID = true
[conf/bookkeeper.conf] Applying config zkLedgersRootPath = /ledgers
[conf/bookkeeper.conf] Applying config zkServers = pulsar-zookeeper:2181
[conf/bookkeeper.conf] Adding config journalDirectories = /pulsar/data/bookkeeper/journal
JMX enabled by default
Error: Could not find or load main class "-Xms1g
JMX enabled by default
Error: Could not find or load main class "-Xms1g
JMX enabled by default
Error: Could not find or load main class "-Xms1g
.
.

To Reproduce
Steps to reproduce the behavior:

  1. Package a chart with this repo(no change in config)
  2. broker, recovery, proxy, bookkeeper pod creation fails
  3. check init container logs kubectl logs pulsar-bookkeeper-0 -c pulsar-bookkeeper-verify-clusterid -n pulsar

Env
Azure AKS
@rvashishth rvashishth changed the title pods for broker/bookkeeper fails to create with Could not find or load main class "-Xms1g error pods for broker/bookkeeper init failed - Could not find or load main class "-Xms1g error Jun 25, 2020
@sijie
Copy link
Member

sijie commented Jun 26, 2020

@rvashishth Are you running with the latest master?

@sijie
Copy link
Member

sijie commented Jun 26, 2020

I don't see -Xms1g in the default vaules.ymal file. Can you share your values file?

@rvashishth
Copy link
Contributor Author

@sijie I used this Values.yml file from from the previous commit after PR #22 merged. I didn't make any changes in this values file.

looks like some config issue at bkEnv.sh

This error looks somewhat similar to these two issues - apache/pulsar#7243, or apache/pulsar#6355

@sijie
Copy link
Member

sijie commented Jun 26, 2020

@rvashishth please use the latest master to include #24

@sijie sijie mentioned this issue Jun 26, 2020
Closed
@rvashishth
Copy link
Contributor Author

@sijie I have tested with the latest master with #28, still the same error with init containers.

@rvashishth
Copy link
Contributor Author

this time zookeeper also going in CrashLoopBackOff status with the below error.

$ kubectl logs pulsar-zookeeper-0  -n pulsar
[conf/zookeeper.conf] Applying config dataDir = /pulsar/data/zookeeper
[conf/zookeeper.conf] Adding config serverCnxnFactory = org.apache.zookeeper.server.NettyServerCnxnFactory
Current server id 1
Error: Could not find or load main class "-Xms1g

@lukestephenson-zendesk
Copy link

Similar, I'm trying the latest master and my bookies are now failing to start with:

Error: Could not find or load main class "
JMX enabled by default

@rvashishth
Copy link
Contributor Author

all pods started successfully. the previous issue was due to chart being cached.

@Syphixs Syphixs mentioned this issue Aug 13, 2020
Closed
Joshhw pushed a commit to Joshhw/pulsar-helm-chart that referenced this issue Mar 10, 2021
Fix condition on grafana ingress (apache#26)
8877f61 
* fix tls condition for grafana engress

* lint is working for this version in local

* 3.2.4 is not available on helm mixin
pgier pushed a commit to pgier/pulsar-helm-chart that referenced this issue Apr 22, 2022
@lhotari
Fix ct config and lint errors (apache#26)
2998646 
* Fix ct config

* Fix lint errors in Chart.yaml

* Fix lint errors in values.yaml

* Remove trailing whitespace in yaml files

* Change no -> false, yes -> true in yaml files since linting requires it

* Replace 2 or more blank lines with 1 blank line to pass linter

* Add maintainers since linting requires that

- use github id as name. similar convention is used in
  kube-prometheus-stack

* Set apiVersion to v2 in Chart.yaml

- error message was:
  dependencies are not valid in the Chart file with apiVersion 'v1'. They are valid in apiVersion 'v2'
rdhabalia added a commit to rdhabalia/pulsar-helm-chart that referenced this issue Feb 2, 2023
@rdhabalia
Apply Journal directories change from values.yaml (apache#26)
8b2eadc 
Co-authored-by: rajan <rdhabalia@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sijie @rvashishth @lukestephenson-zendesk