Package Details: icinga2 2.13.3-1

Git Clone URL: https://aur.archlinux.org/icinga2.git (read-only, click to copy)
Package Base: icinga2
Description: An open source host, service and network monitoring program
Upstream URL: https://icinga.com/
Licenses: GPL
Replaces: icinga2-common
Submitter: bebehei
Maintainer: julianbrost
Last Packager: julianbrost
Votes: 35
Popularity: 0.002897
First Submitted: 2014-06-23 01:10 (UTC)
Last Updated: 2022-04-17 11:37 (UTC)

Latest Comments

svlc commented on 2022-01-13 19:37 (UTC) (edited on 2022-01-13 19:38 (UTC) by svlc)

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).

Acema commented on 2021-08-04 12:24 (UTC)

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

julianbrost commented on 2021-06-07 19:55 (UTC)

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

ArthurBorsboom commented on 2021-06-07 19:55 (UTC)

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

Luxii commented on 2021-06-07 19:46 (UTC)

Hey,

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

Maybe we should add this to the dependencies.

bldewolf commented on 2020-12-16 01:19 (UTC) (edited on 2020-12-16 01:20 (UTC) by bldewolf)

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

wuestengecko commented on 2020-11-20 18:05 (UTC)

@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.

ArthurBorsboom commented on 2020-11-20 17:59 (UTC)

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?

julianbrost commented on 2020-11-20 17:38 (UTC)

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 (UTC)

Ping

ArthurBorsboom commented on 2020-09-06 15:16 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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

bortzmeyer commented on 2020-02-11 14:26 (UTC)

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

adlerweb commented on 2020-02-11 11:26 (UTC) (edited on 2020-02-11 11:28 (UTC) by adlerweb)

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

danieltetraquark commented on 2020-02-05 22:02 (UTC)

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); }

julianbrost commented on 2019-10-08 17:37 (UTC)

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

freaknils commented on 2019-10-08 05:44 (UTC) (edited on 2019-10-08 05:44 (UTC) by freaknils)

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

Ich875 commented on 2019-10-08 05:33 (UTC) (edited on 2019-10-08 05:54 (UTC) by Ich875)

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.

freaknils commented on 2019-10-06 14:56 (UTC) (edited on 2019-10-07 10:54 (UTC) by freaknils)

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

julianbrost commented on 2019-08-14 18:52 (UTC)

@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.

zork commented on 2019-08-14 18:48 (UTC)

Missing build dependencies: bison, flex

julianbrost commented on 2019-06-07 18:19 (UTC)

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

kbabioch commented on 2019-06-07 17:54 (UTC)

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

zork commented on 2019-05-08 11:46 (UTC)

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

wuestengecko commented on 2019-03-14 17:41 (UTC)

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.

malina commented on 2019-03-13 20:21 (UTC) (edited on 2019-03-13 20:24 (UTC) by malina)

@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.

julianbrost commented on 2019-03-13 18:02 (UTC)

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

wuestengecko commented on 2019-03-13 17:11 (UTC)

@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?

malina commented on 2019-03-13 00:24 (UTC) (edited on 2019-03-13 00:36 (UTC) by malina)

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?

malina commented on 2019-03-11 22:25 (UTC) (edited on 2019-03-11 22:40 (UTC) by malina)

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.

julianbrost commented on 2019-01-17 10:51 (UTC)

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

freaknils commented on 2019-01-17 08:23 (UTC)

termcap is needed for build and runnning Icinga.

Please add it to dependencies

julianbrost commented on 2018-10-19 11:15 (UTC)

@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?

rixx commented on 2018-10-18 17:33 (UTC)

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.

anonfunc commented on 2018-10-13 03:31 (UTC)

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

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

codiflow commented on 2018-10-02 12:07 (UTC) (edited on 2018-10-02 13:34 (UTC) by codiflow)

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).

Ich875 commented on 2018-10-01 10:02 (UTC) (edited on 2018-10-01 10:02 (UTC) by Ich875)

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.

bebehei commented on 2018-09-14 14:23 (UTC)

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.

frankenstein20 commented on 2018-09-14 10:54 (UTC)

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

wuestengecko commented on 2018-06-13 08:56 (UTC)

@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.

Fightbackman commented on 2018-06-13 08:49 (UTC)

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

bebehei commented on 2018-04-18 07:51 (UTC)

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.

freaknils commented on 2018-04-18 06:55 (UTC)

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

julianbrost commented on 2018-02-05 14:33 (UTC)

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

D.Cent commented on 2018-02-05 12:26 (UTC)

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!

julianbrost commented on 2018-01-20 12:56 (UTC)

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

Zearan commented on 2018-01-19 12:46 (UTC)

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

jhu commented on 2018-01-19 12:32 (UTC)

I'm also wondering - 2.8.1 is out.

julianbrost commented on 2018-01-09 16:45 (UTC)

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

aknarts commented on 2017-10-20 08:46 (UTC) (edited on 2017-10-20 08:47 (UTC) by aknarts)

Am I the only one having this issue? -- Unit icinga2.service has begun starting up. Oct 20 08:44:43 localhost kernel: traps: icinga2[4194] trap invalid opcode ip:7fb02f7d13b2 sp:7fff9567d060 error:0 in libconfig.so.2.7.1[7fb02f75e000+9a000] Oct 20 08:44:43 localhost systemd[1]: Started Process Core Dump (PID 4196/UID 0). -- Subject: Unit systemd-coredump@25-4196-0.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-coredump@25-4196-0.service has finished starting up. -- -- The start-up result is RESULT. Oct 20 08:44:43 localhost prepare-dirs[4193]: Could not fetch RunAsUser variable. Error ''. Exiting. Oct 20 08:44:43 localhost systemd[1]: icinga2.service: Control process exited, code=exited status=6 Oct 20 08:44:43 localhost systemd[1]: icinga2.service: Failed with result 'exit-code'. Oct 20 08:44:43 localhost systemd[1]: Failed to start Icinga host/service/network monitoring system. -- Subject: Unit icinga2.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit icinga2.service has failed. -- -- The result is RESULT. Oct 20 08:44:43 localhost systemd-coredump[4197]: Process 4194 (icinga2) of user 0 dumped core. Stack trace of thread 4194: #0 0x00007fb02f7d13b2 n/a (libconfig.so.2.7.1) #1 0x00007fb02f7abfe5 n/a (libconfig.so.2.7.1) #2 0x00007fb02f43a1e1 _ZN6icinga6Loader27ExecuteDeferredInitializersEv (libbase.so.2.7.1) #3 0x00007fb02f43e5a5 _ZN6icinga11Application14InitializeBaseEv (libbase.so.2.7.1) #4 0x000056260f9476f6 n/a (icinga2) #5 0x00007fb02e86af6a __libc_start_main (libc.so.6) #6 0x000056260f94789a n/a (icinga2) -- Subject: Process 4194 (icinga2) dumped core -- Defined-By: systemd

Zearan commented on 2017-10-06 22:34 (UTC)

Updated to 2.7.1, please report problems (with the PKGBUILD) as usual.

Zearan commented on 2017-10-06 18:01 (UTC)

The documentation states the following: "optional: Termcap (libtermcap-devel on RHEL, not necessary on Debian) - only required if libedit doesn't already link against termcap/ncurses". 'libedit' is already in dependecies and links against ncurses. So from what I have understood, there is no need for action. Preparing 2.7.1 this weekend, will incorporate all requests below as well.

commented on 2017-10-06 13:10 (UTC)

termcap should be a required package

bebehei commented on 2017-07-06 20:01 (UTC)

@Zearan: Could you please add a gitignore file? Only the content: /* See the Tip here: https://wiki.archlinux.org/index.php/Arch_User_Repository#Uploading_packages Thanks in advance.

jhu commented on 2017-05-16 07:54 (UTC)

Thanks for the quick and extensive answer. Much appreciated. I'm coming from years of Gentoo, so this is all quite new to me.

Zearan commented on 2017-05-15 20:12 (UTC)

wxgtk (and its dependencies) are required for icinga-studio. As icinga2 is a split package, they will be pulled when building the package. There is no need keeping the packages if you only want to have icinga2 on a headless VM. Either remove the makedependencies (e.g. via `makepkg -s -r`) or build the package(s) in a clean chroot from the start. You can read about... * dependencies in PKGBUILDs here: https://wiki.archlinux.org/index.php/PKGBUILD#Dependencies * split packages here: https://www.archlinux.org/pacman/PKGBUILD.5.html#_package_splitting * makepkg here: https://www.archlinux.org/pacman/makepkg.8.html * clean chroot here: https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot Hope that helps you out.

jhu commented on 2017-05-15 19:56 (UTC)

Why on earth does this need to pull in wxgtk and all the X stuff? I want to deploy on a rented, headless VM.. just curious.

disprofarma commented on 2017-04-26 18:54 (UTC)

The latest update increase the CPU usage to much, almost every 1min its running at 85% and only to check 12 hosts and 24 services (ping and esxi_hardware). Anyone see the same behavior?

julianbrost commented on 2017-04-23 11:00 (UTC)

backup misses etc/icinga2/features-available/influxdb.conf and etc/icinga2/features-available/opentsdb.conf

bebehei commented on 2017-02-20 12:16 (UTC)

@aknarts: read the thread. Thanks.

aknarts commented on 2017-02-20 11:56 (UTC)

Also requires bison and flex packages to compile Optionaly pkg-config

zork commented on 2017-02-14 12:53 (UTC) (edited on 2017-02-14 12:54 (UTC) by zork)

logrotate fails to rotate icinga2 logs due to permission problems. I had to change following lines in /etc/logrotate.d/icinga2: - su icinga icinga + su icinga icingacmd - create 644 icinga icinga + create 644 icinga icingacmd

Zearan commented on 2017-02-06 20:14 (UTC)

Icinga Studio is now available in AUR! Therefore this is now a split package. Please check out all the changes and help improving the package by providing feedback.

bebehei commented on 2016-12-29 22:03 (UTC)

Previous answer: @das_j install the base-devel package group. Base devel is included in no PKGBUILD, cause it's the arch-standard to install the base-devel package for compilation jobs.

svenihoney commented on 2016-12-29 21:19 (UTC)

bison and flex seem to be makedepends, perhaps you may add them to the PKGBUILD file.

Zearan commented on 2016-11-27 19:36 (UTC)

I would like to stick to arch=('i686' 'x86_64') as these are Arch Linux' officially supported architectures. If I had to build this package on ARM, I would follow bebehei's suggestion and use 'makepkg -A'.

bebehei commented on 2016-11-27 12:26 (UTC)

@q84fh: 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.

q84fh commented on 2016-11-27 10:00 (UTC)

@bebehei I finally managed to compile icinga2 on Rasberry Pi. So, I believe you can add armv7h to arch array. I used large swap external magnetic drive, and it took hours to complete, but it did not crashed this time. There was upgrade of boost libary in mean time, so I think they fixed this bug in upstream.

bebehei commented on 2016-10-16 18:45 (UTC)

@q84fh It seems like, something in /usr/include/boost/signals2/connection.hpp is broken. I don't know how to solve the problem exactly. Using my google foo, i can find exactly 0 related problems. Compiling on x86_64 with latest packages, everything works fine. So it may be caused by a bad combination of versions in boost/icinga2/gcc. It may help, to downgrade one of theses and test. I'm pretty unsure if any of these downgrades really will solve the problem, but personally I'd give it a shot. As I can see, boost got a small upgrade during the last month [1]. I would downgrade boost to 1.60.0-5 and give it a try. (Do not downgrade to 1.60.0-4, this version is known to fail! https://bugs.archlinux.org/task/49248) Also downgrading gcc may help. [2] Check for icinga2 changes at [3] [1] https://github.com/archlinuxarm/PKGBUILDs/commits/master/extra/boost [2] https://github.com/archlinuxarm/PKGBUILDs/commits/master/core/gcc [3] https://aur.archlinux.org/cgit/aur.git/log/PKGBUILD?h=icinga2 Completely off topic: Are you compiling with clang or gcc? I once had an issue while compiling a big project with clang. Memory consumption grew steadly, until everything had been eaten up. clang segfaulted, but it was a clear OOM issue and after segfault all memory was free. After upgrading the memory of the machine, everything went fine. You may also watch your memory-stats during compilation and double check the function of your swap. Also if your run your compilation in parallel, it causes obviously higher memory consumption.

q84fh commented on 2016-10-15 19:05 (UTC)

Hi, I also tried to compile it on Rasberry Pi 2 (I've added tons (10GB) of swap, because 1GB od RAM is way to little), it failed with segfault at some point. I'm using most recent, up to date Arch Linux. I will be more then happy to provide you additional details if you need to to solve this. PS. Many thanks for maintaining this package. [ 38%] Building CXX object lib/icinga/CMakeFiles/icinga.dir/icinga_unity.cpp.o In file included from /usr/include/boost/signals2/signal.hpp:22:0, from /usr/include/boost/signals2.hpp:19, from /tmp/packerbuild-1001/icinga2/icinga2/src/icinga2-2.5.4/build/lib/base/configobject.thpp:9, from /tmp/packerbuild-1001/icinga2/icinga2/src/icinga2-2.5.4/lib/base/configobject.hpp:24, from /tmp/packerbuild-1001/icinga2/icinga2/src/icinga2-2.5.4/lib/icinga/apiactions.hpp:24, from /tmp/packerbuild-1001/icinga2/icinga2/src/icinga2-2.5.4/lib/icinga/apiactions.cpp:20, from /tmp/packerbuild-1001/icinga2/icinga2/src/icinga2-2.5.4/build/lib/icinga/icinga_unity.cpp:1: /usr/include/boost/signals2/connection.hpp: In member function 'bool boost::signals2::detail::connection_body<GroupKey, SlotType, Mutex>::connected() const [with GroupKey = std::pair<boost::signals2::detail::slot_meta_group, boost::optional<int> >; SlotType = boost::signals2::slot<void(const boost::intrusive_ptr<icinga::Notification>&, const boost::intrusive_ptr<icinga::Checkable>&, const boost::intrusive_ptr<icinga::User>&, const icinga::NotificationType&, const boost::intrusive_ptr<icinga::CheckResult>&, const icinga::String&, const icinga::String&, const icinga::String&, const boost::intrusive_ptr<icinga::MessageOrigin>&), boost::function<void(const boost::intrusive_ptr<icinga::Notification>&, const boost::intrusive_ptr<icinga::Checkable>&, const boost::intrusive_ptr<icinga::User>&, const icinga::NotificationType&, const boost::intrusive_ptr<icinga::CheckResult>&, const icinga::String&, const icinga::String&, const icinga::String&, const boost::intrusive_ptr<icinga::MessageOrigin>&)> >; Mutex = boost::signals2::mutex]': /usr/include/boost/signals2/connection.hpp:149:22: internal compiler error: Segmentation fault virtual bool connected() const ^~~~~~~~~ Please submit a full bug report, with preprocessed source if appropriate. See <https://github.com/archlinuxarm/PKGBUILDs/issues> for instructions. make[2]: *** [lib/icinga/CMakeFiles/icinga.dir/build.make:330: lib/icinga/CMakeFiles/icinga.dir/icinga_unity.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:1665: lib/icinga/CMakeFiles/icinga.dir/all] Error 2 make: *** [Makefile:161: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... The build failed.

bebehei commented on 2016-07-27 12:39 (UTC)

> c++: internal compiler error: Killed (program cc1plus) You're lacking of RAM. icinga2 requires more than 1GB just for the compiler process to build. Use an apropriatly sized swapfile.

kbabioch commented on 2016-07-27 12:24 (UTC)

This package does currently not compile on a Raspberry Pi 2, failing with the following message (VERBOSE=1): [ 19%] Building CXX object lib/base/CMakeFiles/base.dir/application-version.cpp.o cd /tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/build/lib/base && /usr/bin/c++ -DI2_BASE_BUILD -Doverride="" -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10 -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/lib -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/build -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/build/lib -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/third-party/execvpe -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/third-party/mmatch -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/third-party/socketpair -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16 -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -g -pthread -std=c++11 -Wno-inconsistent-missing-override -O3 -DNDEBUG -fPIC -o CMakeFiles/base.dir/application-version.cpp.o -c /tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/lib/base/application-version.cpp [ 20%] Building CXX object lib/base/CMakeFiles/base.dir/base_unity.cpp.o cd /tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/build/lib/base && /usr/bin/c++ -DI2_BASE_BUILD -Doverride="" -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10 -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/lib -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/build -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/build/lib -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/third-party/execvpe -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/third-party/mmatch -I/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/third-party/socketpair -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16 -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -g -pthread -std=c++11 -Wno-inconsistent-missing-override -O3 -DNDEBUG -fPIC -o CMakeFiles/base.dir/base_unity.cpp.o -c /tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/build/lib/base/base_unity.cpp c++: internal compiler error: Killed (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See <https://github.com/archlinuxarm/PKGBUILDs/issues> for instructions. make[2]: *** [lib/base/CMakeFiles/base.dir/build.make:213: lib/base/CMakeFiles/base.dir/base_unity.cpp.o] Error 4 make[2]: *** Deleting file 'lib/base/CMakeFiles/base.dir/base_unity.cpp.o' make[2]: Leaving directory '/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/build' make[1]: *** [CMakeFiles/Makefile2:1421: lib/base/CMakeFiles/base.dir/all] Error 2 make[1]: Leaving directory '/tmp/yaourt-tmp-kbabioch/aur-icinga2/src/icinga2-2.4.10/build' make: *** [Makefile:161: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build icinga2.

Zearan commented on 2016-06-09 08:34 (UTC)

Well, you could try to completly clear your src/ and/or build/ directory to build from scratch. If this does not help, you could head to Arch BBS for support. If you believe you have encountered a bug within the Icinga 2 build process, please check out their issue tracker at https://dev.icinga.org/ or have a look at https://www.icinga.org/community/get-help/

dkaea353 commented on 2016-06-08 20:09 (UTC)

Can't compile on Raspberry Pi 2 (armv7h), Boost 1.60.0-5: [ 39%] Linking CXX executable ../Bin/Release/icinga2 ../Bin/Release/libcli.so: undefined reference to `boost::re_detail_106000::cpp_regex_traits_implementation<char>::transform_primary(char const*, char const*) const' ../Bin/Release/libcli.so: undefined reference to `boost::re_detail_106000::cpp_regex_traits_implementation<char>::transform(char const*, char const*) const' collect2: error: ld returned 1 exit status distcc[10066] ERROR: compile (null) on localhost failed icinga-app/CMakeFiles/icinga-app.dir/build.make:120: recipe for target 'Bin/Release/icinga2' failed make[2]: *** [Bin/Release/icinga2] Error 1 CMakeFiles/Makefile2:2227: recipe for target 'icinga-app/CMakeFiles/icinga-app.dir/all' failed make[1]: *** [icinga-app/CMakeFiles/icinga-app.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... [ 59%] Built target icinga Makefile:160: recipe for target 'all' failed make: *** [all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

bebehei commented on 2016-06-02 00:55 (UTC)

I've seen, since 2.4 there is also icinga2 studio [0] available. What about supporting this? [0] https://www.icinga.org/2015/09/02/icinga-2-api-updates/#clients

Zearan commented on 2016-05-20 10:17 (UTC)

I would like to wait a few days before updating to make sure that there are no severe bugs in 2.4.10 like there were in 2.4.8 and 2.4.9.

Zearan commented on 2016-05-15 15:21 (UTC)

Please see https://bugs.archlinux.org/task/49248, boost 1.60.0-4 will fail. @bebehei: Thank you for your quick answers and solutions. =)

bebehei commented on 2016-05-15 11:43 (UTC)

@MCL: Cannot reproduce with boost/boost-libs 1.60.0-5. PKGBUILD works like a charm. This bug may be either introduced by Arch-maintainer of boost or by icinga2 devs. But anyway: Please use LANG=C for your output before pasting it. Just because the maintainers are german and are able to understand it, is no reason to paste it in german.

WRMSR commented on 2016-05-14 11:25 (UTC) (edited on 2016-05-14 11:26 (UTC) by WRMSR)

Hi, can't compile this with boost 1.60.0-4: [ 95%] Linking CXX executable ../Bin/Release/icinga2 ../Bin/Release/libcli.so: undefined reference to `boost::re_detail_106000::cpp_regex_traits_implementation<char>::transform[abi:cxx11](char const*, char const*) const' ../Bin/Release/libcli.so: undefined reference to `boost::re_detail_106000::cpp_regex_traits_implementation<char>::transform_primary[abi:cxx11](char const*, char const*) const' collect2: Fehler: ld gab 1 als Ende-Status zurück icinga-app/CMakeFiles/icinga-app.dir/build.make:120: die Regel für Ziel „Bin/Release/icinga2“ scheiterte make[2]: *** [Bin/Release/icinga2] Fehler 1 CMakeFiles/Makefile2:2294: die Regel für Ziel „icinga-app/CMakeFiles/icinga-app.dir/all“ scheiterte make[1]: *** [icinga-app/CMakeFiles/icinga-app.dir/all] Fehler 2 Makefile:160: die Regel für Ziel „all“ scheiterte make: *** [all] Fehler 2 ==> FEHLER: Ein Fehler geschah in build(). Breche ab... ==> FEHLER:Makepkg konnte icinga2 nicht erstellen. ==> Erstellen von icinga2 neu starten?[j/N] Trying to compile the icinga2-git version fails also.

disprofarma commented on 2016-04-28 04:13 (UTC)

Hi, yajl is listed in depends= and makedepends=. Thanks.

bebehei commented on 2016-04-07 23:02 (UTC)

@valleedelisle: Read through the wiki's PKGBUILD arch section [0]. There had been also a discussion somewhere else, which elaborated these arguments and also applied them to the AUR. There is also in makepkg: -A, --ignorearch My personal opinion: Do you really want to push the pkgrel variable with the result of showing up on every persons AUR package-manager just for supporting a new architecture? Have a look at [1] and I found this annoying. This was just a small package, but what about a big one like this? [0] https://wiki.archlinux.org/index.php/PKGBUILD#arch [1] https://aur.archlinux.org/cgit/aur.git/diff/?h=package-query&id=47f9d99a1c42dcb50ed596725f6801807f6b3b0b&id2=699633619773f1373df8e721bd8448413ade5305

valleedelisle commented on 2016-04-07 21:16 (UTC)

works perfectly fine on my rasberry pi 3, just make sur you have a swap file and you add armv7h to the PKGBUILD file.

therisen06 commented on 2016-03-03 11:42 (UTC)

I cannot reproduce the problem with 2.4.3 (the problem might still occur at times if it's some kind of race condition). gcc 5.3.0 crashed while compiling 2.4.1 with "-j4" ("internal compiler error"). Just a heads up for anyone running into the same problem. As for "Please do not set settings that do not work on your system": No kidding...

bebehei commented on 2016-03-02 15:50 (UTC)

I'm running with MAKEFLAGS="-j4" and it's running perfectly fine, too. @therisen6 If you would give more details, it would bring us a step ahead.

Zearan commented on 2016-03-02 15:42 (UTC)

/etc/makepkg.conf does not set any makeflags by default. Please do not set settings that do not work on your system. Icinga2 builds with "-j4" on my system without any problems. If you believe you have encountered a bug within the Icinga 2 build process, please check the issue tracker at https://dev.icinga.org/

therisen06 commented on 2016-03-02 14:44 (UTC)

Please add something like options=('!makeflags') to your PKGBUILD. The build fails if you use -j4 by default in /etc/makepkg.conf.

bebehei commented on 2015-12-11 19:21 (UTC)

@das_j install the base-devel package group. Base devel is included in no PKGBUILD, cause it's the arch-standard to install the base-devel package for compilation jobs.

commented on 2015-12-11 19:19 (UTC)

Works great but bison and flex (build)dependencies seem to be missing.

bebehei commented on 2015-12-10 14:02 (UTC) (edited on 2015-12-10 16:09 (UTC) by bebehei)

@Zearan: Got this after executing makepkg on the current (2.4.1-1) PKGBUILD. [ 84%] Building CXX object lib/db_ido/CMakeFiles/db_ido.dir/db_ido_unity.cpp.o c++: internal compiler error: Killed (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See <https://bugs.archlinux.org/> for instructions. lib/compat/CMakeFiles/compat.dir/build.make:107: recipe for target 'lib/compat/CMakeFiles/compat.dir/compat_unity.cpp.o' failed make[2]: *** [lib/compat/CMakeFiles/compat.dir/compat_unity.cpp.o] Error 4 make[2]: *** Deleting file 'lib/compat/CMakeFiles/compat.dir/compat_unity.cpp.o' CMakeFiles/Makefile2:1852: recipe for target 'lib/compat/CMakeFiles/compat.dir/all' failed make[1]: *** [lib/compat/CMakeFiles/compat.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... Any hints? Update: 2015-12-10 17:06: Ok, this seems to be an OOM issue. Working with a 6GB RAM virtual machine and 8 cores. Using "-j 8" as makeflags will hit the issue, while "-j 1" won't. Sorry for the trouble.

commented on 2015-09-07 13:29 (UTC)

Hey, latest version is https://github.com/Icinga/icinga2/tree/v2.3.10 . Could you update the PGKBUILD please. regards

Zearan commented on 2015-05-27 06:48 (UTC)

Releasing 2.3.4-2: Cleaned up the PKGBUILD a bit and implemented djanos' suggestion.

Zearan commented on 2015-04-27 15:10 (UTC)

Updated package to 2.3.4! @djanos: Thank you! I will implement your suggestion with the next major release which will also include a PKGBUILD cleanup.

djanos commented on 2015-04-23 16:36 (UTC)

Thank you for your work on this package! I suggest to install $SRC/tools/syntax directory in /usr/share/icinga2/syntax.

Zearan commented on 2015-04-13 12:24 (UTC)

You need to have the group "base-devel" installed. The packages of this group are not listed in the makedepends array (see https://wiki.archlinux.org/index.php/PKGBUILD#makedepends).

simonsd commented on 2015-04-13 12:18 (UTC)

having some issues building the pkg: missing deps: - bison - flex - pkgconfig - make - gcc - binutils (strip) - fakeroot missing config for cmake: -DCMAKE_C_COMPILER=/usr/bin/gcc -DCMAKE_CXX_COMPILER=/usr/bin/g++ -DCMAKE_MAKE_PROGRAM=/usr/bin/make

Zearan commented on 2015-01-19 07:08 (UTC)

Updated package with the changes described below. A huge thank you to bebehei for spotting several issues in the new PKGBUILD and install script. Please check out the new release and report any problems in the comments.

bebehei commented on 2015-01-14 12:04 (UTC)

@Zearan thanks for the changes, i will check them this evening and reupload the PKGBUILD

Zearan commented on 2015-01-14 09:47 (UTC)

@issa: The error is in line 45 which tries to create folders in the root file system due to a missing "$pkgdir". I took some time yesterday and added some cmake options (to solve pacman 4.2 issues), fixed dependencies and change the way "/etc" and "/var" folders are handled. You can find my PKGBUILD at http://pastebin.com/xMXaGbDf and the install script at http://pastebin.com/LqFYnpuX. Feel free to adopt anything from these files if you think it is an improvement.

bebehei commented on 2015-01-13 06:51 (UTC)

It is updated!

issa commented on 2015-01-12 07:24 (UTC)

Ok I'm sorry but I couldn't built the aur nor the aur-dev version successfully on my pi. For the "mixed" version (added info from aur-dev PKGBUILD to aur PKGBUILD it returned: folder "usr" not found and terminated the built process without creating a {package-name}.tar.xz file. I don't know how to continue from here... could everyone else just built the package on x86?

issa commented on 2015-01-12 07:24 (UTC)

Ok I'm sorry but I couldn't built the aur nor the aur-dev version successfully on my pi. For the "mixed" version (added info from aur-dev PKGBUILD to aur PKGBUILD it returned: folder "usr" not found and terminated the built process without creating a {package-name}.tar.xz file. I don't know how to continue from here... could everyone else just built the package on x86?

issa commented on 2015-01-11 12:15 (UTC)

I downloaded and compiled the package provided at aur-dev.archlinux.org - unfortunately it seems that it didn't finish completely (it didn't built {package-name}.tar.xz) What I did then is to get the additional commands from the PKGBUILD from aur-dev and copied them into the PKGBUILD from aur (here). I just started compiling and will see tomorrow if that worked. Anyhow, some tips/hints where to learn more about building packages for archlinux (apart from the wiki I did start there but there are many questions left). cheers!

bebehei commented on 2015-01-10 11:31 (UTC)

pls search at aur-dev.archlinux.org foe the package it's fixed there

issa commented on 2015-01-10 10:33 (UTC)

Hey, I tried to built it on my raspberry pi. (needed ext. HDD + Swapfile) But sadly it seems to be one of packages that need special treatment as stated here: http://allanmcrae.com/2014/12/pacman-4-2-released/. Unfortunately I don't have sufficient knowledge to change the settings to rebuilt it myself and changing PKGBUILT and/or icinga2.install is not sufficient (as I can't find "/sbin" anywhere in those files). I tried extracting and manually changing "/usr/sbin/" to "/usr/bin" but as I can't update .MTREE pacman will not let me install it (and I think this is for a good reason). So maybe someone can help me out by telling me how to change the settings to rebuilt it (partially or completely).

bebehei commented on 2014-12-29 01:01 (UTC)

icinga updated to v2.2.2

bebehei commented on 2014-10-27 11:09 (UTC)

Sorry, the PKGBUILD has got an error. change the line _tmp_build_dir=`mktemp -dp $srcdir` to export _tmp_build_dir=`mktemp -dp $srcdir` then all should run fine. Sorry for the inconvenience, I can't fix this right now by uploading a new one, i'm on vacancies.

RubenKelevra commented on 2014-10-27 09:31 (UTC)

Sadly I can't build it on my machine: ==> Betrete fakeroot Umgebung... ==> Beginne package()... make: *** No rule to make target 'install'. Schluss. ==> FEHLER: Ein Fehler geschah in package(). Breche ab ... ==> FEHLER:Makepkg konnte icinga2 nicht erstellen.

nutz commented on 2014-09-16 09:06 (UTC)

I think you're right, icinga2 runs with boost-libs (and w/o boost) as well.

bebehei commented on 2014-09-12 19:47 (UTC)

... and pacman -Ss boost says: extra/boost 1.56.0-1 [installed] Free peer-reviewed portable C++ source libraries - development headers extra/boost-libs 1.56.0-1 [installed] Free peer-reviewed portable C++ source libraries - runtime libraries ... to be continued. Sry for maybe the incorrect dependency-handling. The next days I've got no time to test this. If you could investigate further, It would be great.

bebehei commented on 2014-09-12 19:38 (UTC)

The INSTALL-file says: * Boost library and header files (boost-devel on RHEL, libboost-all-dev on Debian) TBH. I've never heard a difference between boost and boost-libs.

msierks commented on 2014-09-12 19:10 (UTC)

Aren't the "boost-libs" package only required ? or is "boost" itself required as well ?

bebehei commented on 2014-09-11 19:03 (UTC)

Thanks for the info. It's updated. Sorry for the inconvenience.

nutz commented on 2014-09-11 15:40 (UTC)

boost is actually a runtime-dependency as well. otherwise, when trying to run icinga2, i get: /usr/sbin/icinga2: error while loading shared libraries: libboost_system.so.1.56.0: cannot open shared object file: No such file or directory

bebehei commented on 2014-09-10 17:56 (UTC)

Thanks for the improvement. I'll add the changes in a few minutes. After building it on my own machine.

msierks commented on 2014-09-10 17:14 (UTC)

Updated pkgbuild for 2.1.0 - http://pastebin.com/Yc9XuCXn Removed postgresql from depends. Added libmariadbclient and postgresql-libs to makedepends. This will build with support for both postgres and mysql databases. Though these libs are optional when running. Might want to add mariadb and postgresql to optdepends as well. Also added python-setuptools as makedepends as it would not build without.

bebehei commented on 2014-08-14 03:19 (UTC)

yeah, they should be dependencies.

azeotrope commented on 2014-08-14 03:17 (UTC)

yeah I've noticed that too, but with mysql. I didn't have mysql installed before and becuase of that it didn't compile and package the mysql ido library. In that case shouldn't both mysql and postgresql be dependencies?

bebehei commented on 2014-08-14 02:11 (UTC)

As I have seen in the source-code, cmake checks during build for postgresql/mysql and builds db_ido support if the necessary libs are available. If I put it into the opt-array, icinga2 will get built without postgresql/mysql support and you won't be able to change that later after installation. You have to rebuild the whole package. I think I have to add it to opt-array and make-array. But tbh idk what to do here. I'm not an experienced packager.

azeotrope commented on 2014-08-13 07:30 (UTC)

OK, fair enough. I don't think postgres should be a hard dependency, since you can choose to use mysql instead or to use neither. Shouldn't both be optional dependencies like the plugins?

bebehei commented on 2014-08-12 09:30 (UTC)

bison is included by the package-group base-devel, which you should have installed anyway if you want to compile and pack something

azeotrope commented on 2014-08-12 00:26 (UTC)

Thanks bebehei. Also looks like bison is a make dependancy.

bebehei commented on 2014-08-11 08:33 (UTC)

@azeotrope You're right! I will update the package and add the db-schemas.

azeotrope commented on 2014-08-11 06:59 (UTC)

Any reason why the DB schemas aren't being packaged?