Package Details: icinga2 2.10.1-1

Git Clone URL: https://aur.archlinux.org/icinga2.git (read-only)
Package Base: icinga2
Description: An open source host, service and network monitoring program
Upstream URL: http://www.icinga.org
Licenses: GPL
Replaces: icinga2-common
Submitter: bebehei
Maintainer: julianbrost (bebehei)
Last Packager: julianbrost
Votes: 30
Popularity: 0.670256
First Submitted: 2014-06-23 01:10
Last Updated: 2018-10-19 11:40

Latest Comments

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

julianbrost commented on 2018-10-19 11:15

@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

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.

IdleGandalf commented on 2018-10-13 03:31

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

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

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

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

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.