Newbie trying install Zabbix 6.2 on RHEL 8

[scalyback]

I have tried a few different methods to do this, I got my RHEL 8 VM built and added the repos then updated if, but when I run this command: rpm -Uvh https://repo.zabbix.com/zabbix/6.2/r...el8.noarch.rpm
I get errors just errors basically peer certificate cannot be authenticated with given CA certificates.

I would follow how our previous Zabbix 4.0 was built but there is no documentation for it, which is nice.

So a little friendly help or poke in the right direction would be great many thanks peeps.

[LenR]

That installs the repos and keys, delete what you added and try again.

[scalyback]

As suggested I run a clean to clear everything, re-run the above command and receive this:
curl: (60) SSL certificate problem: self signed certificate in certificate chain. So now I am sort of stuck as my Linux\Zabbix knowledge is very limited

[simonl]

I can't help with the certificate issue, but you are better off using yum (or dnf on RHEL8+) than rpm to install packages, even if the documentation says to use rpm. Yum will pull in dependencies and keep track of what packages are installed.

[tim.mooney]

As suggested I run a clean to clear everything, re-run the above command and receive this:
curl: (60) SSL certificate problem: self signed certificate in certificate chain. So now I am sort of stuck as my Linux\Zabbix knowledge is very limited

This may not have anything to do with Zabbix. Do you have any repos enabled that might be using a self-signed cert? Sometimes a broken (or just offline) repo can mess up functionality with a completely unrelated repo.

[pyritejoe]

If your having a cert issue similar to the one I did I had to add the nogpgcheck to get past it. I would say that you need to be careful and make sure the repo is trusted.

yum install package --nogpgcheck

[scalyback]

Many thanks for the input funnily I did run sudo yum install on the various rpm files, the only one not to install was the zabbix-server-mysql, so lucky for me I have a snapshot of the VM i can revert back to that and try again from scratch. very strange one the only repo's are the Red Hat and the Zabbix but will look to see what is causing the problem.

So an update, reverted the snapshot, downloaded the zabbix-server-mysql 6.2-3 rpm, run sudo yum install that rpm name server does it's check to Red Hat then when trying to do the above rpm it gives this error:
Error:
Problem: conflicting requests - nothing provides fping needed the rpm above,

so now I am #annoyed. I am wondering if I need to clean my repos out.

[pyritejoe]

Yep had the same issue, had to manually install fping.

[tim.mooney]

the only repo's are the Red Hat and the Zabbix but will look to see what is causing the problem.

Ok, if those are the only repos you have enabled, then the trust error isn't coming from some 3rd party repo. Some people load some sketchy repos, so I thought I would check.

What version of the 'ca-certificates' package do you have installed on the RHEL 8 system where you're having this problem? There were some problems in 2021 with some clients not being able to verify the zabbix.com certificates, I think including the repo certificates, all related to an older cross-signed root certificate expiring, see: https://www.openssl.org/blog/blog/20...ootCertExpire/

I didn't think that problem impacted RHEL 8, but I'm not certain. Making sure you have the latest 'ca-certificates' from RHEL/CentOS would make sure you're not impacted by that problem.

As far as the 'fping' issue, that package is in the 'zabbix-non-supported' repo, which is enabled when you install the 'zabbix-release' package.

[scalyback]

Brilliant lots to do then, as I have not touched Linux for more than 30 years this is all new to me. I will search how to install the ca-certificates package and go from there.
Just annoyed that whoever did this previous to me left no documentation. But oh well. So I have reverted to my snapshot pre-everything I have just done and installing the ca-certificates package, I will tread careful I seem to hit a bit of confidence then wham something buggers the install.