Arch Linux User Repository

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.