Package Details: icinga2 2.10.4-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
Last Packager: julianbrost
Votes: 31
Popularity: 0.650673
First Submitted: 2014-06-23 01:10
Last Updated: 2019-04-20 14:12

Required by (2)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

bebehei commented on 2016-12-29 22:03

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

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

Zearan commented on 2016-11-27 19:36

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

@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

@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

@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

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

> 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

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

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/