-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Heartbeat install issues on Ubuntu #3765
Comments
Additionally regular apt upgrade command would replace elastic heartbeat with the other clustering heartbeat tool, seen by apt as an upgradeable version to replace existing:
Marked it as held to prevent upgrade using:
|
Oh boy :( I knew that name is a mistake. |
We've discussed some potential options:
The last option currently seems the most appealing. We probably want to add the elastic- prefix to all beats, not only Heartbeat, to keep the packaging process consistent. Some potential issues that we need to investigate:
We plan to figure this out by 6.0. |
Also in the meanwhile apt pinning can mitigate the issue until we release a definitive fix. by editing
You get our repository pinned, so our heartbeat package (and any new one we release) has priority over Debian/Ubuntu repo
|
So we'll need to update the docs so users have ways to get around this
issue until it's solved in future releases. I can update the docs with this
info if someone wants to review my PR?
…On 29 Mar 2017 00:38, "Carlos Pérez-Aradros Herce" ***@***.***> wrote:
Also in the meanwhile apt pinning can mitigate the issue until we release
a definitive fix. by editing /etc/apt/preferences (or
/etc/apt/preferences.d/heartbeat):
Package: heartbeat
Pin: origin artifacts.elastic.co
Pin-Priority: 700
You get our repository pinned, so our heartbeat package (and any new one
we release) has priority over Debian/Ubuntu repo
***@***.***:/# apt-cache policy heartbeat
heartbeat:
Installed: (none)
Candidate: 5.3.0
Version table:
1:3.0.6-5 500
500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
5.3.0 700
500 https://artifacts.elastic.co/packages/5.x/apt stable/main amd64 Packages
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3765 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB-ZO7OOlLF0ZFBQdubq7YSucH5M-s-Aks5rqRuBgaJpZM4MgOnn>
.
|
@geekpete I can update the docs if you tell me what to add. Just offering because you'll need to conditionally code the info so that it doesn't appear in the docs for other Beats. We use a shared file with variables that resolve to the correct Beat name. |
Thanks for the help, @dedemorton :) The additional detail around pinning the repo with a higher priority provided by @exekias is the best/simplest solution to add to the Heartbeat docs. I can try to verify/test on Debian as well later today.
or similar to that,etc. |
Okay, after some initial hicup, the proposed (and I think correct) pinning works. Changing the package name still does make sense to allow co-installation of heartbeat cluster software and heartbeat Elastic Beat (although I think its unlikely that one would like to do that). |
Heartbeatbeat? |
Due to a naming conflict on Debian (see elastic#3765), we rename the name of the RPM and DEB packages to be `heartbeat-elastic`. The artifacts that we offer for download are still named `heartbeat`, only the package names in the repositories will be `heartbeat-elastic`. The init scripts and the service files are renamed, as well as the PID files and setting files (e.g. `/etc/default/heartbeat-elastic`). The binaries, config files, etc are not, so the changes are minimal. Fixes elastic#3765.
* Rename heartbeat packages Due to a naming conflict on Debian (see #3765), we rename the name of the RPM and DEB packages to be `heartbeat-elastic`. The artifacts that we offer for download are still named `heartbeat`, only the package names in the repositories will be `heartbeat-elastic`. The init scripts and the service files are renamed, as well as the PID files and setting files (e.g. `/etc/default/heartbeat-elastic`). The binaries, config files, etc are not, so the changes are minimal. Fixes #3765.
Issue installing on Ubuntu, the original "heartbeat" clustering tool package tries to install instead of the heartbeat beat.
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
stretch/sid
apt install heartbeat
should present installation of the original heartbeat (clustering tool) rather than the Elastic beat:The text was updated successfully, but these errors were encountered: