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.

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

Installing Logstash DEB file fails to run on Pi4+ with Buster #11428

fallenreaper opened this issue Dec 11, 2019 · 1 comment

Installing Logstash DEB file fails to run on Pi4+ with Buster #11428

fallenreaper opened this issue Dec 11, 2019 · 1 comment


Copy link

@fallenreaper fallenreaper commented Dec 11, 2019

Please post all product and debugging questions on our forum. Your questions will reach our wider community members there, and if we confirm that there is a bug, then we can open a new issue here.

For security vulnerabilities please only send reports to
See for more information.

Logstash Plugins are located in a different organization: For bugs on specific Logstash plugins, for example, if Redis Output has a defect, please open it in the respective Redis Output repository.

For all general issues, please provide the following details for fast resolution:

  • Version: 7.5.0
  • Operating System: Buster (Raspbian)
  • Config File (if you have sensitive info, please remove it):
  • Sample Data:
  • Steps to Reproduce:
    obtain a raspberry pi 4+, 4gb, (i have a 32gb sd card)
    apt-get update
    apt-get upgrade
    curl the deb file
    dpkg the deb
    try to run it, logs will show it stopping and not staying on.

I saw a gist that took the jar unzipped it, cp'd a file in there up a level, and then rejar'd it, and placed it back into place, and it worked correctly. i dont have the link to it at the moment.

Copy link

@fallenreaper fallenreaper commented Dec 13, 2019

I saw a reference to this:
when looking up the error: #10755

I must note that an error which i was getting which caused me to find this workaround was: LoadError ffi/ffi. When running that gist though it seems to resolve itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

1 participant