Package Details: icinga2 2.9.1-1

Git Clone URL: (read-only)
Package Base: icinga2
Description: An open source host, service and network monitoring program
Upstream URL:
Licenses: GPL
Replaces: icinga2-common
Submitter: bebehei
Maintainer: julianbrost (bebehei)
Last Packager: julianbrost
Votes: 29
Popularity: 0.493624
First Submitted: 2014-06-23 01:10
Last Updated: 2018-08-03 16:35

Latest Comments

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

bebehei commented on 2018-09-14 14:23

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

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

@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

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: 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

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 :

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

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

bison and flex are in the base-devel group which should be installed when you are building packages from AUR:

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

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

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

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