You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/09/22 10:34:07 UTC
[GitHub] [pulsar] subhranil05 created a discussion: Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing
GitHub user subhranil05 created a discussion: Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing
pulsar image version = 2.9.3
initialize: true #set to true in values.yaml
Pulsar-broker and proxy pods are not coming up due to init containers
zookeeper and other pods are up and running
pulsar-broker-0 0/1 Init:1/2 0 5m40s
pulsar-proxy-0 0/1 Init:1/2 0 5m40s
logs : Defaulted container "pulsar-broker" out of: pulsar-broker, wait-zookeeper-ready (init), wait-bookkeeper-ready (init)
Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing
Please help me by providing solution if there any. Need real quick!!!!
GitHub link: https://github.com/apache/pulsar/discussions/17802
----
This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@pulsar.apache.org
Re: [D] Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing [pulsar]
Posted by "lhotari (via GitHub)" <gi...@apache.org>.
GitHub user lhotari added a comment to the discussion: Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing
There was on reply on Pulsar Slack to check the logs of the init jobs that initialize the cluster.
It's not very useful to do any analysis without the logs.
It's useful to check Kubernetes events and logs
Tips related to following k8s events in the console:
```
# events for ALL namespaces (fine for a local minikube or Docker Desktop k8s)
kubectl get events --sort-by=.lastTimestamp -A
# tailing all events
kubectl get events --sort-by=.lastTimestamp -A --watch
```
Getting logs, `pulsar-broker-0` in `pulsar` namespace as example:
```
kubectl -n pulsar logs pulsar-broker-0
# getting previous logs, for the previously crashed pod
kubectl -n pulsar logs pulsar-broker-0 -p
```
In this case, I'd check the init job logs (append `-n pulsar` to the command if you have a specific command, check the jobs with `kubectl get jobs` to see if they have different names).
```
kubectl logs job/pulsar-pulsar-init
kubectl logs job/pulsar-pulsar-init -p
kubectl logs job/pulsar-bookie-init
kubectl logs job/pulsar-bookie-init -p
```
You could use a k8s UI such as `k9s` on command line or [OpenLens](https://github.com/MuhammedKalkan/OpenLens)/[Lens](https://k8slens.dev/) for the desktop. That makes things a lot users to begin with.
GitHub link: https://github.com/apache/pulsar/discussions/17802#discussioncomment-8702647
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org
Re: [D] Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing [pulsar]
Posted by "subhranil05 (via GitHub)" <gi...@apache.org>.
GitHub user subhranil05 added a comment to the discussion: Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing
Try it by disabling anti affinity
`anti_affinity: false`
GitHub link: https://github.com/apache/pulsar/discussions/17802#discussioncomment-8707019
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org
Re: [D] Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing [pulsar]
Posted by "rahuldstk (via GitHub)" <gi...@apache.org>.
GitHub user rahuldstk added a comment to the discussion: Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing
i faced something similar to this, and for me it solved when i deleted the namespace and created again along with the installation steps.
i had initially installed another version of pulsar in the same namespace, and when i tried this later version, the secrets might have been in conflict.
i deleted the old namespace and created again, and installed pulsar. now all the pods are in running state
GitHub link: https://github.com/apache/pulsar/discussions/17802#discussioncomment-8704983
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org
Re: [D] Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing [pulsar]
Posted by "asafm (via GitHub)" <gi...@apache.org>.
GitHub user asafm added a comment to the discussion: Error from server (BadRequest): container "pulsar-broker" in pod "pulsar-broker-0" is waiting to start: PodInitializing
@hangc0276 Maybe you know?
GitHub link: https://github.com/apache/pulsar/discussions/17802#discussioncomment-8695826
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org