You should not be reading this error message.
It means that an unforeseen error took place in /etc/rc.d/rcsysinit.d/S71pakfire, which exited with a return value of 2.
If you’re able to track this error down to a bug in one of the files provided by ipfire, please be so kind to inform us at https://bugzilla.ipfire.org.
[root@ipfire ~]# export GNUPGHOME="/opt/pakfire/etc/.gnupg" && gpg --import /opt/pakfire/pakfire-2007.key
gpg: can’t open `/opt/pakfire/pakfire-2007.key’: No such file or directory
gpg: Total number processed: 0
icinga complains sometimes… but installation is actual not really in use
Starting icinga: Can’t locate strict.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.12.3/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.12.3 /usr/lib/perl5/5.12.3/x86_64-linux-thread-multi /usr/lib/perl5/5.12.3 .) at /usr/lib/icinga/p1.pl line 5.
BEGIN failed–compilation aborted at /usr/lib/icinga/p1.pl line 5.
Starting icinga done.
More important is that after a power loss in about 90% of cases fs ( sda2 or sda3) is corrupted…
therefore i now haven an ups in use…
Could be a hard disk failing. If the manufacturer provides a checker program then it would be worth running that. Those generally run from USB stick which could be difficult to do while the disk is in an apu2c4 and you might need to move the disk temporarily to a conventional PC.