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

Filebeat is bundled with the RPM #211

Closed
ElvenSpellmaker opened this issue Dec 15, 2017 · 12 comments
Closed

Filebeat is bundled with the RPM #211

ElvenSpellmaker opened this issue Dec 15, 2017 · 12 comments
Assignees
Milestone

Comments

@ElvenSpellmaker
Copy link

Problem description

Bundling filebeat with the rpm causes problems if filebeat is already installed on the system, there's no way without rebundling the RPM to install sidecar on our machines which have filebeat already installed because they install to the same locations:

Execution of '/usr/bin/rpm -i /tmp/collector-sidecar.rpm' returned 1: file /usr/bin/filebeat from install of collector-sidecar-0.1.4-1.x86_64 conflicts with file from package filebeat-1.3.1-1.x86_64
@razvanphp
Copy link

The same with Debian, this should be a package dependancy, not included in the deb.

@michaeljoy
Copy link

I concur, this is a pretty annoying issue to have to deal with in larger environments. Filebeat should be a package dependency, not included directly

@michaeljoy
Copy link

An alternative would be to install filebeat in /usr/local/bin/filebeat or another location like in /opt/collector-sidecar/bin and specify in the collector config for binary location. This would allow side by side installs of both without forcing the use of older filebeat versions as well.

@mariussturm
Copy link
Contributor

The bundled filebeat binary will be installed in /usr/lib/graylog-sidecar from 3.0 on, see f15144a

mariussturm pushed a commit that referenced this issue Jul 23, 2018
* Install filebeat into /usr/lib/graylog-sidecar/filebeat

Fixes #211

* Use correct macro in deb/rpm recipe
@ElvenSpellmaker
Copy link
Author

@emarana FYI =)

@tjyang
Copy link

tjyang commented Dec 4, 2018

Hi @mariussturm
Is there a reason why sidecar can't use filebeat come with system rpm/deb package ?
Can newer 3.0 sidecar default to use system filebeat, if no filebeat installed then use sidecar bundle one ?

@mariussturm
Copy link
Contributor

@tjyang the reason for the bundling was to make it as simple as possible to get started with the Sidecar as well as the fact that the Sidecar was rendering the configuration. So we could never know if the installed version fits the configuration the Sidecar is generating. As people are more used to the Sidecar we can default to the official packages. With 3.0 the rendering of the configuration file changes so it's easier to use the official packages.

@tjyang
Copy link

tjyang commented Dec 4, 2018

@mariussturm Thanks for the reply.

Is it possible to release the collector-sidecar-0.1.8 that have bundled filebeat not using /usr/bin path ?

@sreerajkksd
Copy link

Is it possible to release the collector-sidecar-0.1.8 that have bundled filebeat not using /usr/bin path ?

Can someone respond back to this?

@mariussturm
Copy link
Contributor

@sreerajkksd since 1.0.0 is out there are no plans to have another 0.1.8/9 release.

@sreerajkksd
Copy link

@mariussturm Is there way, I can get a SRPM for this version ?

@mariussturm
Copy link
Contributor

@sreerajkksd sorry we don't provide SRPMs currently but you can simply checkout the source from the repository if that helps?

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

No branches or pull requests

7 participants