Can munin-nginx safely be installed on a DA server with apache?

[Richard G]

Formerly this was the exclude line in yum.conf which DA put in there:
exclude=apache* httpd* mod_* mysql* MySQL* mariadb* da_* *ftp* exim* sendmail* php* bind-chroot* dovecot*
this was also like this on my first Almalinux 8.x server which was converted from Centos 8 to Alma 8.

On newly installed Alma 8 and 9 servers, this is the exclude line:
exclude=apache* nginx* httpd* mod_* mysql* MySQL* mariadb* da_* *ftpd exim* sendmail* php* bind-chroot* dovecot*
as you can see nginx* is now added.

However I would like to install Munin again like I had on the Centos 7 server, but then the package munin-nginx will be installed too, because Munin requires this to run.
As far as I know Munin runs seperately on a different port.

But since DA added the nginx* exclusion now in Alma 8, I wonder if I can safely remove the nginx* restriction so Munin can be installed (and later updated if needed)?

I don't use nGinx on this server, only apache. So can I safely do this?

 

[Richard G]

Oh... additionally... it's not munin-nginx which is blocked but nginx* is blocking the nginx-filesystem package which Munin wants to install.
Can this give harmfull conflicts?

 

[Ohm J]

if your directadmin use only apache, you can. But you can't with Nginx.

because it will replace nginx file system

https://rhel.pkgs.org/8/epel-modular-x86_64/nginx-filesystem-1.23.1-2.module_el8+15017+873f21d4.noarch.rpm.html

 

[Richard G]

if your directadmin use only apache,

Oke thank you.
Maybe Munin has changed, I can't remember from several years ago they installed nGinx stuff. So this would mean nGinx users couldn't use Munin anymore on their systems. That's a pity. Don't know if that is the wisest decision of Munin then.

Thanks!