This message was deleted.
# general
s
This message was deleted.
a
I suppose you have authentication enabled, right? In that case, what
authenticationProviders
are registered in the
broker.conf
?
t
Yeah,
pulsar-admin
works just fine for example, without specifying the provider or token
I’ll just check whats registered
Copy code
# Authentication provider name list, which is comma separated list of class names
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderToken
a
Does it work using
pulsar-client produce
? The
pulsar-admin
goes against a different endpoint so it’s not comparable
Ah so it’s using token authentication. You should be able to make it work using the following:
Copy code
./bin/pulsar-perf produce \
--auth_plugin org.apache.pulsar.client.impl.auth.AuthenticationToken \
--auth-params token:<YOUR-TOKEN> \
test-topic
t
So
/pulsar-client produce test-topic -m "tesT"
this seemed to work as
test-topic
has been created
just trying your suggestion now
It still seems to hang, not sure how long its expected to take to start up?
a
Weird, it should start immediately giving some info logs about its config
t
Yeah i’m not sure what else to try
a
Is there still sufficient memory available on the broker?
t
i’ve got about 1gb free
i tried that
exit-on-failure
flag too but no luck there
a
Yeah that should only help if it’s already trying to produce, but it sounds like there is already an issue on startup
t
yeah it seems so
a
I think I’m out of ideas too. Can you try running the tool from your local machine instead?
t
Sure, should i just copy the script off of the instance?
a
You can just download the respective binaries from here
t
ah thanks
hmmm, works locally it seems 🤔
i think thats ok for my use case but just weird
👍 1
n
You could try running with
--debug
, might see some more output @Thomas Turner
t
Thanks both, think its in a pretty good spot now
🙌 1