Package Details: nagios 4.5.8-1

Git Clone URL: https://aur.archlinux.org/nagios.git (read-only, click to copy)
Package Base: nagios
Description: Nagios is an open source host, service and network monitoring program.
Upstream URL: http://www.nagios.org
Licenses: GPL
Submitter: Idares
Maintainer: Idares (Rhinoceros)
Last Packager: Rhinoceros
Votes: 114
Popularity: 0.000280
First Submitted: 2007-08-03 11:53 (UTC)
Last Updated: 2024-11-19 23:20 (UTC)

Latest Comments

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

Rhinoceros commented on 2022-11-24 09:03 (UTC)

Thanks for updating, @Idares. One minor issue, I get the warning when building

chown: warning: '.' should be ':': ‘nagios.nagios’

Looks like a typo in the PKGBUILD, which can be fixed with the following

diff --git a/PKGBUILD b/PKGBUILD
index 4371a24..5fa3bec 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -61,7 +61,7 @@ package() {
    install -D -m 644 startup/default-service $pkgdir/usr/lib/systemd/system/nagios.service

    mkdir $pkgdir/var/nagios/rw
-   chown $_nagios_user.$_nagios_group $pkgdir/var/nagios/rw
+   chown $_nagios_user:$_nagios_group $pkgdir/var/nagios/rw
    chmod 755 $pkgdir/var/nagios/rw

    chmod 755 $pkgdir/usr/bin

Rhinoceros commented on 2022-11-20 09:19 (UTC)

Thanks @Idares. That works perfectly.

Idares commented on 2022-11-20 08:40 (UTC)

@Rhinoceros, @nachfuellbar: the openssl package in core was changed from version 1.x to v3. Try to rebuild nagios package with latest openssl installed (without openssl-1.1).

Rhinoceros commented on 2022-11-20 06:54 (UTC)

As per the comment nine days ago, this also fails for me until I install openssl-1.1. @Idares could you please add this as a dependency?

Again, I can see that it's been a bit hard for you to keep updating this package regularly. Again, I'm happy to maintain this package if you like.

nachfuellbar commented on 2022-11-08 18:54 (UTC)

Seems like there were changes in Arch because after System Update today i got a error from nagios process about missing libssl.so.1.1. /usr/bin/nagios: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory After installing openssl-1.1 it's working again (should be made a dependency if it's really necessary)

Rhinoceros commented on 2022-09-08 23:33 (UTC)

@webdawg That user-side fix was also mentioned in my first link. Alternatively, adding the patch to this package will fix the actual upstream bug. Also, this will fix it for everyone, instead of every individual needing to manually apply the workaround.

@Idares can indeed comment as much as they want, but it is a bit spammy. I have never seen another AUR package contain comments for every update.

webdawg commented on 2022-09-08 21:04 (UTC)

Yo All, Set: check_for_updates=0

Here is the down low yo: https://support.nagios.com/forum/viewtopic.php?t=64845

@ldares you can comment on your own package as much as you want.

WebDawg out.

<mic drop>

Rhinoceros commented on 2022-08-14 09:28 (UTC) (edited on 2022-08-14 23:24 (UTC) by Rhinoceros)

@Idares. Thank you for updating the package. I'm happy to take over if it is difficult for you to update this regularly.

Also, there is no need to comment that it's been updated. You can have a look at the other packages in the AUR. If there are any specific messages that you think are important, including the changelog, you can always put this in the git commit message. Hope all is well.

EDIT

Nagios is failing to start on my system. The bug can be fixed with this patch. It would be helpful for @Idares to add this patch to the PKGBUILD.

Idares commented on 2022-08-14 09:15 (UTC)

Updated to 4.4.7-1 Nagios changelog: https://github.com/NagiosEnterprises/nagioscore/blob/master/Changelog

Rhinoceros commented on 2022-07-21 12:34 (UTC)

Is there an issue with the new version? It was released three months ago, and this package was flagged two months ago. For the last 14 releases (except for the major releases), you've just bumped the version number. Is it possible to do this for the current (minor) release as well? If you are no longer interested in maintaining this package, perhaps consider orphaning it and let someone else maintain it more regularly?