On Fri, 21 Nov 2014, jdoe wrote: > Hello icinga-users, > > I'm trying to install icinga2 from wheezy-backports in my raspberry pi > running raspbian OS. At the end of the installation I got the following > issues: > > ===begin of output=== > pi@icinga-pi ~ $ sudo apt-get install icinga2 > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following extra packages will be installed: > icinga2-bin icinga2-common python-icinga2 > The following NEW packages will be installed: > icinga2 icinga2-bin icinga2-common python-icinga2 > 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. > Need to get 0 B/2.777 kB of archives. > After this operation, 8.300 kB of additional disk space will be used. > Do you want to continue [Y/n]? Y > WARNING: The following packages cannot be authenticated! > python-icinga2 icinga2-common icinga2-bin icinga2 > Install these packages without verification [y/N]? y > Selecting previously unselected package python-icinga2. > (Reading database ... 92596 files and directories currently installed.) > Unpacking python-icinga2 (from .../python-icinga2_2.1.1-1~bpo70+1_all.deb) > ... > Selecting previously unselected package icinga2-common. > Unpacking icinga2-common (from .../icinga2-common_2.1.1-1~bpo70+1_all.deb) > ... > Selecting previously unselected package icinga2-bin. > Unpacking icinga2-bin (from .../icinga2-bin_2.1.1-1~bpo70+1_armhf.deb) ... > Selecting previously unselected package icinga2. > Unpacking icinga2 (from .../icinga2_2.1.1-1~bpo70+1_armhf.deb) ... > Processing triggers for man-db ... > Setting up python-icinga2 (2.1.1-1~bpo70+1) ... > Setting up icinga2-common (2.1.1-1~bpo70+1) ... > enabling default icinga2 features > Module 'checker' has been enabled. > Module 'notification' has been enabled. > Module 'mainlog' has been enabled. > Make sure to restart Icinga 2 for these changes to take effect. > [....] checking Icinga2 configuration > [FAIL] checking Icinga2 configuration. Check '/var/log/icinga2/startup.log' > for details. ... failed!invoke-rc.d: initscript icinga2, action "start" > failed. > dpkg: error processing icinga2-common (--configure): > subprocess installed post-installation script returned error exit status 1 > dpkg: dependency problems prevent configuration of icinga2-bin: > icinga2-bin depends on icinga2-common (= 2.1.1-1~bpo70+1); however: > Package icinga2-common is not configured yet. > > dpkg: error processing icinga2-bin (--configure): > dependency problems - leaving unconfigured > dpkg: dependency problems prevent configuration of icinga2: > icinga2 depends on icinga2-bin (= 2.1.1-1~bpo70+1); however: > Package icinga2-bin is not configured yet. > icinga2 depends on icinga2-common (= 2.1.1-1~bpo70+1); however: > Package icinga2-common is not configured yet. > > dpkg: error processing icinga2 (--configure): > dependency problems - leaving unconfigured > Errors were encountered while processing: > icinga2-common > icinga2-bin > icinga2 > E: Sub-process /usr/bin/dpkg returned an error code (1) > pi@icinga-pi ~ $ > ===end of output=== > > Any hell on this is appreciated. As it seems, the answer is to use a real armhf device. The version works perfectly on my cubietruck, but it doesn't work on the raspberry pi.
I also can't recommend to run i2 on a raspberry pi, it is really low end and doesn't have much RAM. Maybe we can do something if you send us a gdb backtrace. Alex _______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
