Package Details: icinga2 2.12.3-2

Git Clone URL: (read-only, click to copy)
Package Base: icinga2
Description: An open source host, service and network monitoring program
Upstream URL:
Licenses: GPL
Replaces: icinga2-common
Submitter: bebehei
Maintainer: julianbrost
Last Packager: julianbrost
Votes: 35
Popularity: 0.001925
First Submitted: 2014-06-23 01:10
Last Updated: 2020-12-24 10:49

Required by (0)

Sources (6)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

bldewolf commented on 2020-12-16 01:19

Hey, tried to build this today. Looks like the pull request authors for the boost build fixes force pushed their pull requests to be different. The checksums don't match and the new patches don't apply. I assume this means they'll be merged soon, but for the interim I had to update my PKGBUILD to use the raw commits of the old patches like so (pulled the commit ids from the pull request pages):

diff --git a/PKGBUILD b/PKGBUILD
index 5a10344..6d41c17 100644
@@ -45,14 +45,14 @@ install='icinga2.install'
-        ''
-        ''
+        ''
+        ''
-            '4f033a9a1bf74fe81eeda553e8d249ddc30fbb7c09a7edb37c3ce6dbad332958'
-            'ec60024196c381debb6caa759f5d8e1750f5039f5b3689d822009643da6fd6cb'
+            '52e50af7b10d75fcd6257fbf9b3c9043efb3cc497fac0970656fbffb1d328ee5'
+            '1fa4c67f2f1bbed9814441d370ed50484bf64e57d16fddbbf5a0be8da9c7f1a2'

@@ -60,8 +60,8 @@ prepare() {
   cd "$srcdir/$pkgname-$pkgver"

   patch -p1 < "$srcdir/8184.patch"
-  patch -p1 < "$srcdir/8190.patch"
-  patch -p1 < "$srcdir/8191.patch"
+  patch -p1 < "$srcdir/7e62a68eadada58e762d3f4261750796adffd440.diff"
+  patch -p1 < "$srcdir/45dd71e0f9a93369e08d6cb26f97940f9c9594aa.diff"

 build() {

wuestengecko commented on 2020-11-20 18:05

@ArthurBorsboom: If you have a machine with matching architecture and enough RAM, just build there and push over the binary package. Otherwise, take a look at

ArthurBorsboom commented on 2020-11-20 17:59

I noticed there are downloadable packages for other distributions.

Sometimes I see community or AUR packages which use these type of packages to create an Arch package.

Would that be an option? Or do you have a preference for the git repository?

julianbrost commented on 2020-11-20 17:38

If nobody replies, probably nobody knows. I can only tell you that I don't provide a repo with binary packages somewhere.

ArthurBorsboom commented on 2020-11-20 15:25


ArthurBorsboom commented on 2020-09-06 15:16

I'm using this package on several light weight servers, which usually have 512-2048 MB of RAM.

However, during the package upgrade (compilation) process, the earlyoom kicks in and kills the compilation process (+/- 10% of RAM left).

It seems Icinga2 agent runs well with little RAM; it is just the compilation which needs a lot of RAM (4GB+). Is there a way to reduce the memory hunger of the compilation process of this package?

Are there precompiled packages for Arch available?

julianbrost commented on 2020-02-23 22:04

I've just pushed yet another workaround which now allows compiling against the current boost version 1.72 from the extra repo and does not pull in any other AUR packages. It's a bit hacky unfortunately, and will likely need an update on the next boost update.

julianbrost commented on 2020-02-23 12:29

The conflict only exists for the boost and boost1.69 packages which contains the header files and are only needed at compile time. boost-libs and boost1.69-libs can be installed at the same time. I usually build the packages using extra-x86_64-build from the devtools package, which does the build in a systemd-nspawn container, where conflicting compile time dependencies are not an issue.

However, now that boost1.69 is gone from the repos, that workaround isn't that nice any more.

jhu commented on 2020-02-23 10:06

Since ":: boost1.69-libs is unmaintained!" now is a thing, I can tell you, that compiling still worked with boost 1.71, the reason I have configured

IgnorePkg   = boost
IgnorePkg   = boost-libs

with the result of

warning: boost: ignoring package upgrade (1.71.0-4 => 1.72.0-1)
warning: boost-libs: ignoring package upgrade (1.71.0-4 => 1.72.0-1)

during system updates. Ugly, but I can live with that and found it better than the forced boost downgrade to 1.69 that came with icinga2 2.11.2-2. Arch has no mechanism to have different library versions in slots like Gentoo, or does it?

bortzmeyer commented on 2020-02-12 13:33

OK, my previous report was just a problem of memory. Only (!!!) four gigabytes. With sixteen gigabytes, and adlerweb's workaround, it compiles and runs.