Arch Linux User Repository

I have just installed this package, not sure what the CONFLUENT_HOME is supposed to be but from what the confluent-cli is looking for, I assume it is the root directory.

So I did an export CONFLUENT_HOME=/, followed by "confluent local services start". It stopped after at the ksqlDB server with the same error message than jade: "Error: could not find share/java/confluent-common/common-config-*.jar in CONFLUENT_HOME"

I temporary created a link between /usr/share and /, far from ideal but I got it running. All services seem to be up and running, no problem with the control center etc...

What is the expected value for the CONFLUENT_HOME?

==> I fixed this by creating a symlink in /share/java as follows "ln -s /usr/share/java/confluent-common confluent-common". Not sure if this was the right thing to do?

I will have a look into it. That's not normal. I do not have this issue on my laptop, but it might be due to a past version or another tool.

==> Lastly, I don't see the "control center" service as being started. I can't access control center either from localhost:9021. Does this packaged version not have control center?

No problem from my side as well. Without further information, it's hard to understand the root cause. It's probably worth having a look at C3 logs, it should be explicit.

Thanks for the great work in making this available on Arch/Manjaro. Installation was painless.

It wasn't immediately apparent what I should set for CONFLUENT_HOME as it wasn't clear where it had been installed to. I eventually found out after looking round at the directories.

I had an issue when I first executed "confluent local services start". I got "Error: could not find share/java/confluent-common/common-config-*.jar in CONFLUENT_HOME". All the other services had been started apart from ksqlDB Server.

I fixed this by creating a symlink in /share/java as follows "ln -s /usr/share/java/confluent-common confluent-common". Not sure if this was the right thing to do?

Lastly, I don't see the "control center" service as being started. I can't access control center either from localhost:9021. Does this packaged version not have control center?

Thanks again for the good work.

@wolfjb, indeed you are right. I assume that the package has been modified at some point and I didn't notice it. I downloaded a fersh version of confluent-6.0.0 and updated the checksum. Thanks for the comment ;)

On building, getting this message:

==> Validating source files with sha256sums... confluent-6.0.0.tar.gz ... FAILED systemd_sysusers.d_confluent.conf ... Passed confluent_latest_linux_amd64.tar.gz ... Skipped ==> ERROR: One or more files did not pass the validity check!

sha256sum on a freshly downloaded confluent-6.0.0.tar.gz file is: ce1ba5754611f98028381c9b19309a3b42c43a359f45860fc860608507a81e7e

Using this value in the PKGBUILD resolved the problem for me.

Good point Noderat, I added the CLI as part of the package (committed on 5.3.0-2). Unfortunately, I just found a link to the latest version, I hope that an upgrade of the CLI would not break the package :/. For the moment, I put a SKIP on the checksum validation of the CLI.

Can the Confluent CLI also be re-added to this since they have now split it off into its own tarball? See: https://docs.confluent.io/current/cli/installing.html#cli-install

Thanks and sorry for missing this typos. I don't know how it was working on my environment (I use the schema registry every day). I fixed the typos and upgrade to Confluent 5.0.1.

Hey there, thanks for maintaining this package! It appears that there is a small typo preventing installation of the schema registry.

Line 17 in "install_confluent.sh" has the typo "cp-schema-resgistry", which causes the failure. Fixing this typo to read "cp-schema-registry" installs without error.

Once again thanks for the maintenance!

Indeed the confluent.conf shouldn't be in / ... Thanks @mikail.khan ;) Concerning the other issue, I didn't investigate much but it seems to be related to https://github.com/systemd/systemd/issues/661.

On my laptop, I was able to reproduce with: $> sudo systemctl start /usr/lib/systemd/system/confluent-zookeeper
Failed to start usr-lib-systemd-system-confluent\x2dzookeeper.mount: Unit usr-lib-systemd-system-confluent\x2dzookeeper.mount not found.

But, by using the standard unit syntax, it's working nicely: $> sudo systemctl start confluent-zookeeper