Arch Linux User Repository

Hello @julianbrost, please correct the Upstream URL at least here and at icinga2-git package website to "https://icinga.com". Thank you.

(Atm, http://www.icinga.org does not work at all and http://icinga.org redirects).

I use a Vim3 to monitor my home IT. Could you please support aarch64. I can support if you need any help for testing.

@Luxii These packages are part of the base-devel package group, which is assumed to be installed when building packages.

I believe they should not be added as dependencies.

bison and flex are part of the base-devel group.

The group base-devel is assumed to be already installed when building with makepkg. Members of this group should not be included in makedepends array.

Source: https://wiki.archlinux.org/title/PKGBUILD

Hey,

I needed to install the packages bison and flex to get icinga2 to compile.

Maybe we should add this to the dependencies.

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
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -45,14 +45,14 @@ install='icinga2.install'
 changelog="icinga2.changelog"
 source=("https://github.com/Icinga/$pkgname/archive/v$pkgver.tar.gz"
         'https://patch-diff.githubusercontent.com/raw/Icinga/icinga2/pull/8184.patch'
-        'https://patch-diff.githubusercontent.com/raw/Icinga/icinga2/pull/8190.patch'
-        'https://patch-diff.githubusercontent.com/raw/Icinga/icinga2/pull/8191.patch'
+        'https://github.com/Icinga/icinga2/commit/7e62a68eadada58e762d3f4261750796adffd440.diff'
+        'https://github.com/Icinga/icinga2/commit/45dd71e0f9a93369e08d6cb26f97940f9c9594aa.diff'
         "$pkgname.tmpfiles"
         "$pkgname.sysusers")
 sha256sums=('56387d5e047df04fd91fdb8db3124eb09325c7377fbcaa11ef063147db816dfb'
             'dc1a2530d1c2c311826443cebaaa3c307f400e6a995414c654f4e6b94ec8b885'
-            '4f033a9a1bf74fe81eeda553e8d249ddc30fbb7c09a7edb37c3ce6dbad332958'
-            'ec60024196c381debb6caa759f5d8e1750f5039f5b3689d822009643da6fd6cb'
+            '52e50af7b10d75fcd6257fbf9b3c9043efb3cc497fac0970656fbffb1d328ee5'
+            '1fa4c67f2f1bbed9814441d370ed50484bf64e57d16fddbbf5a0be8da9c7f1a2'
             '1302b333f49ead14f8808a379535971501d3a0c1ba02a7bf7b4406b7d27c754c'
             '2f946a33ea50a3c4400a81acd778e6411ffe5e2257a98004288b84a64f382810')

@@ -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() {

@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 https://icinga.com/docs/icinga2/latest/doc/21-development/#build-optimization.

I noticed there are downloadable packages for other distributions.

https://icinga.com/download/

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?

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

Ping

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?

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.

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.

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?

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

Does not compile today:

% yay -S icinga2
:: There are 2 providers available for icinga2:
:: Repository AUR
    1) icinga2 2) icinga2-git 

Enter a number (default=1): 
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur: 1]  icinga2-2.11.2-1

  1 icinga2                                  (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
:: PKGBUILD up to date, Skipping (1/1): icinga2
  1 icinga2                                  (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
:: Parsing SRCINFO (1/1): icinga2
==> Making package: icinga2 2.11.2-1 (Tue Feb 11 15:12:14 2020)
==> Retrieving sources...
...
[ 21%] Building CXX object lib/base/CMakeFiles/base.dir/base_unity.cpp.o
{standard input}: Assembler messages:
{standard input}:98656: Warning: end of file not at end of a line; newline inserted
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [lib/base/CMakeFiles/base.dir/build.make:237: lib/base/CMakeFiles/base.dir/base_unity.cpp.o] Error 1
make[2]: *** Deleting file 'lib/base/CMakeFiles/base.dir/base_unity.cpp.o'
make[2]: Leaving directory '/home/stephane/.cache/yay/icinga2/src/icinga2-2.11.2/build'
make[1]: *** [CMakeFiles/Makefile2:1746: lib/base/CMakeFiles/base.dir/all] Error 2
make[1]: Leaving directory '/home/stephane/.cache/yay/icinga2/src/icinga2-2.11.2/build'
make: *** [Makefile:163: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
Error making: icinga2

workaround:

pacman -Rdd boost boost-libs
pacman -S boost1.69 boost1.69-libs
Edit PKGBUILD and change "boost"/"boost-libs" in "depends"/"makedepends" to "boost1.69"/"boost1.69-libs".
makepkg, etc

Build breaks again, but removing boost and boost-libs doesn't help:

/usr/include/boost/coroutine/asymmetric_coroutine.hpp: In Funktion »typename boost::coroutines::pull_coroutine<R>::iterator boost::coroutines::begin(boost::coroutines::pull_coroutine<Arg>&)«:
/usr/include/boost/coroutine/asymmetric_coroutine.hpp:2364:17: Fehler: »begin« ist kein Element von »boost«
 2364 | { return boost::begin( c); }
…
/usr/include/boost/coroutine/asymmetric_coroutine.hpp:2374:17: Fehler: »end« ist kein Element von »boost«
 2374 | { return boost::end( c); }

Please don't use flag out-of-date for reporting bugs with the package. This won't speed up anything.

@Ich875: You have to remove boost and boost-libs first pacman -Rdd boost boost-libs

Update: with the comment of freaknils it works. Thank you!

The solution with boost1.69 does not work on my system because I am not able to remove the old boost from the system.

:: Zu installierendes AUR-Paket:
 icinga2                               2.11.0-1             -> 2.11.0-2

:: Mit der Installation fortfahren? [J/n] 
:: [P]aketdetails anzeigen, Pakete [m]anuell auswählen
>> 
Suche nach in Konflikt stehenden AUR-Paketen...
:: Warnung: Diff für Paket icinga2 wird nicht angezeigt (already reviewed)
Editiere PKGBUILD für Paket icinga2? [j/N] j
Editiere icinga2.install für Paket icinga2? [j/N] n

:: Starte vollständige Systemaktualisierung...
 Es gibt nichts zu tun
Lese lokale Paketdatenbank...
:: Installiere Repository-Abhängigkeiten für icinga2:
Löse Abhängigkeiten auf...
Suche nach in Konflikt stehenden Paketen...
:: boost1.69 und boost stehen miteinander in Konflikt. boost entfernen? [j/N] j

Pakete (3) boost-1.71.0-2 [Entferne]  boost1.69-1.69.0-2  boost1.69-libs-1.69.0-2

Gesamtgröße der installierten Pakete:  178,29 MiB
Größendifferenz der Aktualisierung:    3,65 MiB

:: Installation fortsetzen? [J/n] J
(2/2) Prüfe Schlüssel im Schlüsselring                                                                       [################################################################] 100%(2/2) Überprüfe Paket-Integrität                                                                             [################################################################] 100%(2/2) Lade Paket-Dateien                                                                                     [################################################################] 100%(2/2) Prüfe auf Dateikonflikte                                                                               [################################################################] 100%Fehler: Konnte den Vorgang nicht durchführen (In Konflikt stehende Dateien)
boost1.69: /usr/lib/libboost_atomic.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_chrono.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_container.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_context.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_contract.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_coroutine.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_date_time.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_fiber.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_filesystem.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_graph.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_graph_parallel.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_iostreams.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_locale.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_log.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_log_setup.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_math_c99.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_math_c99f.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_math_c99l.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_math_tr1.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_math_tr1f.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_math_tr1l.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_mpi.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_numpy27.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_prg_exec_monitor.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_program_options.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_python27.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_random.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_regex.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_serialization.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_stacktrace_addr2line.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_stacktrace_basic.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_stacktrace_noop.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_system.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_thread.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_timer.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_type_erasure.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_unit_test_framework.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_wave.so existiert im Dateisystem (gehört zu boost-libs)
boost1.69: /usr/lib/libboost_wserialization.so existiert im Dateisystem (gehört zu boost-libs)
Fehler sind aufgetreten, keine Pakete wurden aktualisiert.

Current icinga version does not build with latest boost Update (1.71.0-2). CMake Error at third-party/cmake/BoostTestTargets.cmake:56 (message):
NOTE: boost::test-based targets and tests cannot be added: boost >= 1.34.0
required but not found. (found: '1.71.0' want >=103400) You may disable
BUILD_TESTING to continue without the tests.
Call Stack (most recent call first):
test/CMakeLists.txt:3 (include)

You should set extra/boost1.69 as dependencie.

diff --git a/PKGBUILD b/PKGBUILD
index 8be9478..5e41c99 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,16 +4,16 @@

 pkgname='icinga2'
 pkgver=2.11.0
-pkgrel=1
+pkgrel=2
 pkgdesc="An open source host, service and network monitoring program"
 license=('GPL')
 arch=('i686' 'x86_64')
 url="http://www.icinga.org"
-depends=('boost-libs' 'libedit' 'libsystemd' 'openssl' 'yajl')
+depends=('boost1.69-libs' 'libedit' 'libsystemd' 'openssl' 'yajl')
 optdepends=('monitoring-plugins: plugins needed for icinga checks'
             'libmariadbclient: for MySQL support'
             'postgresql-libs: for PostgreSQL support')
-makedepends=('boost' 'cmake' 'libmariadbclient' 'postgresql-libs' 'systemd')
+makedepends=('boost1.69' 'cmake' 'libmariadbclient' 'postgresql-libs' 'systemd')
 replaces=('icinga2-common')
 backup=(etc/default/icinga2
         etc/icinga2/features-available/api.conf

@zork bison and flex are members of the base-devel package group. As per https://wiki.archlinux.org/index.php/PKGBUILD#makedepends these should not be added to makedepends.

Missing build dependencies: bison, flex

I think you'd have to find a trusted user willing to maintain it in community. I'm not one of them.

Any chance this can be moved to community, so all of this compilation pain goes away for most of us?

I had to add additional swapfile on machine with 4GB ram and no services running. Compilation used about 400MB of swap.

I just set up a small VM according to your specs (2GB RAM + 2GB swap, but without any other services running in the background), and I could see some pretty large memory usage spikes of well over 1.5GB. Depending on your average memory load, this might be enough pressure to SIGKILL something, however it did build fine for me.

There's no functional difference between this PKGBUILD and the git version, so if you built the git package with the release commit, that should work just as well. Regardless, I suggest you setup a chroot for building on your main machine (or somewhere else with sufficient RAM) and then just upload the built package to your server.

@wuestengecko Thank you for the advices!

I would like to compile on a virtual machine with 2 processors and 2GB of memory, for which I have set a 2 GB swap. This is a simple Arch Linux server that I installed: powerdns, mysql55, apache, php, redmine, zabbix, postgresql.

Later (after icinga2 package), I tried to install the icinga2-git package, but it is also failed (on the same, 90%).

Answering your question: I just used the yaourt and I modified the PKGBUILD file as the yaourt offered.

I had an idea: Icinga latest version is 2.10.3 and Icinga developers use tags for versioning, but the last commit of 2.10.3 was not the same (in icinga2-git package is adf1549c2d6ce3ace0490122779290f6cf72071c), so I modified the source:

git + https: //github.com/Icinga/icinga2.git#commit=101783d7efe3050d68d2370db7b14a088bc1f413

The important thing: #commit=101783d7efe3050d68d2370db7b14a088bc1f413 , this is the last commit of version 2.10.3 (now)

The icinga2-git package uses the master branch, commit: adf1549c2d6ce3ace0490122779290f6cf72071c

101783d7efe3050d68d2370db7b14a088bc1f413 commit has worked, it was compiled. I haven't tried it yet, so I'm hoping it will work.

By the way, I don't understand the reason, I'm doing a diff between the two commit.

@malina: There should be a more specific error message from ld somewhere in the output stating why it exited with an error code.

@malina That 90% bit is a little strange, I can build it fine with -DICINGA2_UNITY_BUILD=OFF, and "Linking CXX executable ../Bin/Release/icinga2" is at 100% for me - no matter if on my "live system" or in a chroot.

Seeing how you had out-of-memory issues to begin with - might that be the case here too? Try adding a swapfile of 4 GB or so.

Generic troubleshooting questions, if that didn't work: Did you make any other change to the PKGBUILD? Did you make any changes to your makepkg.conf and/or create a $HOME/.makepkg.conf? How exactly do you build, do you use makepkg directly or any helper tool?

I can't compile the program, it always stops with the same error:

[ 90%] Linking CXX executable ../Bin/Release/icinga2 collect2: error: ld returned 1 exit status
make[2]: *** [icinga-app/CMakeFiles/icinga-app.dir/build.make:655: Bin/Release/icinga2] Error 1
make[1]: *** [CMakeFiles/Makefile2:2331: icinga-app/CMakeFiles/icinga-app.dir/all] Error 2
make: *** [Makefile:163: all] Error 2

Does anyone have an idea?

If you can't compile the program because of a memory issue, edit the PKGBUILD file (build function, 65. line) and insert the following line to cmake parameters:

-DICINGA2_UNITY_BUILD=OFF \

Here is the reason: https://icinga.com/docs/icinga2/latest/doc/21-development/#builds-unity-builds

The compile will be very slow, but at least it does.

@freaknils: None of my systems has termcap installed and I can build and run icinga2 just fine. Why do you think it is required?

termcap is needed for build and runnning Icinga.

Please add it to dependencies

@rixx: The packages should create the icinga user with /var/spool/icinga2 as its home directory (see https://aur.archlinux.org/cgit/aur.git/tree/icinga2.sysusers?h=icinga2#n1) which should work fine. Are you sure the user didn't already exist before?

Can you please give /var/lib/icinga as HOME to the icinga user at creation? Otherwise, mail(1) fails in the default notification script, since mail(1) relies on the executing user's home being present. If you set /dev/null as home, as you do currently, mail tries to create a file /dev/null/.rnd, and coredumps.

Diff for icinga2 2.10.0: https://gist.github.com/AnonFuncsAreAwesome/72f6ed3793601f4e31058afa2411294d

Hope you can use something. Builds for me in clean chroot.

I got this issue during the build-process:

[ 13%] Building CXX object lib/base/CMakeFiles/base.dir/base_unity.cpp.o
In file included from /home/USERNAME/.cache/pacaur/icinga2/src/icinga2-2.9.1/build/lib/base/base_unity.cpp:63:
/home/USERNAME/.cache/pacaur/icinga2/src/icinga2-2.9.1/lib/base/tlsutility.cpp: In Funktion »int icinga::MakeX509CSR(const icinga::String&, const icinga::String&, const icinga::String&, const icinga::String&, bool)«:
/home/USERNAME/.cache/pacaur/icinga2/src/icinga2-2.9.1/lib/base/tlsutility.cpp:329:60: Warnung: »RSA* RSA_generate_key(int, long unsigned int, void (*)(int, int, void*), void*)« ist veraltet [-Wdeprecated-declarations]
  RSA *rsa = RSA_generate_key(4096, RSA_F4, nullptr, nullptr);
                                                            ^
In file included from /usr/include/openssl/e_os2.h:13,
                 from /usr/include/openssl/bio.h:13,
                 from /home/USERNAME/.cache/pacaur/icinga2/src/icinga2-2.9.1/lib/base/base64.cpp:21,
                 from /home/USERNAME/.cache/pacaur/icinga2/src/icinga2-2.9.1/build/lib/base/base_unity.cpp:4:
/usr/include/openssl/rsa.h:234:1: Anmerkung: hier deklariert
 DEPRECATEDIN_0_9_8(RSA *RSA_generate_key(int bits, unsigned long e, void
 ^~~~~~~~~~~~~~~~~~
In file included from /home/USERNAME/.cache/pacaur/icinga2/src/icinga2-2.9.1/build/lib/base/base_unity.cpp:63:
/home/USERNAME/.cache/pacaur/icinga2/src/icinga2-2.9.1/lib/base/tlsutility.cpp:329:60: Warnung: »RSA* RSA_generate_key(int, long unsigned int, void (*)(int, int, void*), void*)« ist veraltet [-Wdeprecated-declarations]
  RSA *rsa = RSA_generate_key(4096, RSA_F4, nullptr, nullptr);
                                                            ^
In file included from /usr/include/openssl/e_os2.h:13,
                 from /usr/include/openssl/bio.h:13,
                 from /home/USERNAME/.cache/pacaur/icinga2/src/icinga2-2.9.1/lib/base/base64.cpp:21,
                 from /home/USERNAME/.cache/pacaur/icinga2/src/icinga2-2.9.1/build/lib/base/base_unity.cpp:4:
/usr/include/openssl/rsa.h:234:1: Anmerkung: hier deklariert
 DEPRECATEDIN_0_9_8(RSA *RSA_generate_key(int bits, unsigned long e, void
 ^~~~~~~~~~~~~~~~~~

Using aurman instead of pacaur for installation showed me the reason:

Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.7/threading.py", line 865, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3.7/site-packages/aurman/utilities.py", line 202, in sudo_loop
    if run(["sudo", "--non-interactive", "-v"]).returncode != 0:
  File "/usr/lib/python3.7/subprocess.py", line 453, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/usr/lib/python3.7/subprocess.py", line 756, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.7/subprocess.py", line 1430, in _execute_child
    restore_signals, start_new_session, preexec_fn)
OSError: [Errno 12] Nicht genügend Hauptspeicher verfügbar

So it seems theres to less RAM (at least 1.37G) on this device available.

After adding a swap file (https://wiki.archlinux.org/index.php/swap) with 4GB everything compiled fine (2GB failed).

I am not able to install Icinga on three of ten machines. On all three I got the folowing messages. Any ideas?

Scanning dependencies of target mkunity [ 12%] Building C object tools/mkunity/CMakeFiles/mkunity.dir/mkunity.c.o [ 12%] Linking C executable ../../Bin/Release/mkunity [ 12%] Built target mkunity [ 13%] Generating base_unity.cpp [ 13%] Generating application-ti.cpp, application-ti.hpp [ 14%] Generating configobject-ti.cpp, configobject-ti.hpp [ 15%] Generating datetime-ti.cpp, datetime-ti.hpp [ 16%] Generating filelogger-ti.cpp, filelogger-ti.hpp [ 17%] Generating function-ti.cpp, function-ti.hpp [ 17%] Generating logger-ti.cpp, logger-ti.hpp [ 18%] Generating perfdatavalue-ti.cpp, perfdatavalue-ti.hpp [ 19%] Generating streamlogger-ti.cpp, streamlogger-ti.hpp [ 20%] Generating sysloglogger-ti.cpp, sysloglogger-ti.hpp Scanning dependencies of target base [ 20%] Building CXX object lib/base/CMakeFiles/base.dir/application-version.cpp.o [ 21%] Building CXX object lib/base/CMakeFiles/base.dir/base_unity.cpp.o {standard input}: Assembler messages: {standard input}:1419706: Warning: end of file not at end of a line; newline inserted {standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive c++: fatal error: Killed signal terminated program cc1plus compilation terminated. make[2]: [lib/base/CMakeFiles/base.dir/build.make:223: lib/base/CMakeFiles/base.dir/base_unity.cpp.o] Error 1 make[1]: [CMakeFiles/Makefile2:1429: lib/base/CMakeFiles/base.dir/all] Error 2 make: *** [Makefile:163: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build icinga2. ==> Restart building icinga2 ? [y/N] ==> -------------------------------- ==>

Icinga 2 war running before and need to be recompiled because of the new boost binaires. Thanks.

the package cannot be installed. Could you please take a look into the error.

Sorry, I cannot reproduce it. Builds flawlessly on multiple systems. Even in a minimal arch docker container it's not reproducible. Please look forward to review your ssl packages

In Elementfunktion »void icinga::IdoMysqlConnection::Reconnect()«: /home/SomeUser/.cache/pacaur/icinga2/src/icinga2-2.9.1/lib/db_ido_mysql/idomysqlconnection.cpp:264:12: Fehler

Oh c'mon! Please do not paste german error messages in an international Forum. Before compiling the next time, please use LANG=C <command> for your generated output!

Also: AUR supports markdown. Fencing the code, would be great, as this preserves the line breaks.

the package cannot be installed. Could you please take a look into the error.

[ 67%] Building CXX object lib/db_ido_mysql/CMakeFiles/db_ido_mysql.dir/db_ido_mysql_unity.cpp.o In file included from /home/SomeUser/.cache/pacaur/icinga2/src/icinga2-2.9.1/lib/db_ido_mysql/idomysqlconnection.hpp:24, from /home/SomeUser/.cache/pacaur/icinga2/src/icinga2-2.9.1/lib/db_ido_mysql/idomysqlconnection.cpp:20, from /home/SomeUser/.cache/pacaur/icinga2/src/icinga2-2.9.1/build/lib/db_ido_mysql/db_ido_mysql_unity.cpp:1: /home/SomeUser/.cache/pacaur/icinga2/src/icinga2-2.9.1/lib/mysql_shim/mysqlinterface.hpp:55:10: Fehler: »my_bool« bezeichnet keinen Typ; meinten Sie »bool«? virtual my_bool ssl_set(MYSQL mysql, const char key, const char cert, const char ca, const char capath, const char cipher) const = 0; ^~~~~~~ bool In file included from /home/SomeUser/.cache/pacaur/icinga2/src/icinga2-2.9.1/build/lib/db_ido_mysql/db_ido_mysql_unity.cpp:1: /home/SomeUser/.cache/pacaur/icinga2/src/icinga2-2.9.1/lib/db_ido_mysql/idomysqlconnection.cpp: In Elementfunktion »void icinga::IdoMysqlConnection::Reconnect()«: /home/SomeUser/.cache/pacaur/icinga2/src/icinga2-2.9.1/lib/db_ido_mysql/idomysqlconnection.cpp:264:12: Fehler: »struct icinga::MysqlInterface« hat kein Element namens »ssl_set« m_Mysql->ssl_set(&m_Connection, sslKey, sslCert, sslCa, sslCaPath, sslCipher); ^~~~~~~ make[2]: [lib/db_ido_mysql/CMakeFiles/db_ido_mysql.dir/build.make:77: lib/db_ido_mysql/CMakeFiles/db_ido_mysql.dir/db_ido_mysql_unity.cpp.o] Fehler 1 make[1]: [CMakeFiles/Makefile2:1960: lib/db_ido_mysql/CMakeFiles/db_ido_mysql.dir/all] Fehler 2 make: *** [Makefile:163: all] Fehler 2 ==> FEHLER: Ein Fehler geschah in build(). Breche ab... :: Konnte icinga2-Paket(e) nicht erstellen

@Fightbackman Icinga2 doesn't require a specific version of boost, however the binaries are linked against whatever was installed at build time. Simply rebuild the package and you're fine.

It seems that icinga2 requires boost-libs 1.66 at the moment, but the version on arch was raised to version 1.67-04. Is it possible to upgrade the package to reflect these changes or is this a hard requirement from icinga2 upstream?

sr/lib/icinga2/sbin/icinga2: error while loading shared libraries: libboost_system.so.1.66.0: cannot open shared object file: No such file or directory Jun 13 10:47:07 firepulse systemd[1]: icinga2.service: Control process exited, code=exited status=127 Jun 13 10:47:07 firepulse systemd[1]: icinga2.service: Failed with result 'exit-code'. Jun 13 10:47:07 firepulse systemd[1]: Failed to start Icinga host/service/network monitoring system. -- Subject: Unit icinga2.service has failed

Hi, could you please add all ARM architectures to your PKGBUILD. Icinga works well on all of them. Thanks!

I'm copy-pasting my previous answer:

Yes and No.

Personally, I would stick to the Arch's package specifications of https://wiki.archlinux.org/index.php/PKGBUILD#arch :

If instead a package can be compiled for any architecture, but is architecture-specific once compiled, specify all architectures officially supported by Arch, i.e. arch=('i686' 'x86_64').

AFAIK Zearan does not use icinga2 on a Raspberry Pi. And I don't know how to assure support for other architectures, if you cannot test it as a maintainer.

Also It's a much cleaner way to use the AUR with an ARM-Based device while using makepkg with the option -A.

Hi, could you please add all ARM architectures to your PKGBUILD. Icinga works well on all of them. Thanks!

bison and flex are in the base-devel group which should be installed when you are building packages from AUR: https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages

Hi, could you please add bison and flex to the makedepends? Just built the package on my server and those packages were needed in order to pass the CMake setup. Thanks!

I'd be willing to co-maintain the package. Also for the icingaweb2 package, I'm using both actively an Arch.

I can add someone as co maintainer. I currently do not find the time for the update.

I'm also wondering - 2.8.1 is out.

Are you still maintaining this package? Do you need any help?