Installing Zabbix on Centos 7
-
Are you using the Zabbix Repos?
Make sure you are using the RHEL7 repo.
-
Fixed it, I think. The YUM Repo file was incorrect and there was no Zabbix repo. I changed it from doing a basesearch to just going to the correct architecture. Installed Zabbix packages immediately.
-
Here is what the error was:
zabbix/x86_64/filelists | 46 kB 00:00:00 http://repo.zabbix.com/zabbix/2.4/rhel/7/x86_64/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum Trying other mirror. One of the configured repositories failed (Zabbix Official Repository - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable zabbix 4. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=zabbix.skip_if_unavailable=true failure: repodata/filelists.xml.gz from zabbix: [Errno 256] No more mirrors to try. http://repo.zabbix.com/zabbix/2.4/rhel/7/x86_64/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum -
Check now, looks like it will install without a complaint.
-
OK, guys... Now that I have the install and good and dandy, I am trying to connect Zabbix to an external database. Alas, it is giving me issues and the documentation doesn't show what needs to be done to connect to an external database. Any advise would be appreciated
-
@antonit What database?
-
Use the mysql client on the Zabbix server manually to connect to the MariaDB on the remote server. Make sure that doing so manually works before you try to troubleshoot Zabbix itself. Port is 3306.
-
I started doing some more digging and found that there is a descrepency with the version of gnutls on Centos 7. It seems to crash the "zabbix_server" service. Because it's an unoficial release of Zabbix on Centos 7, the problem will be there till I downgrade the version of gnutls. So my question is this.... Isn't this a security issue since there has been a vulnerability in the previous versioning of gnutls?
-
What version of Zabbix?
-
@antonit said:
It seems to crash the "zabbix_server" service. Because it's an unoficial release of Zabbix on Centos 7,
Unofficial? What do you mean? Zabbix lists it as their first OS and it is the matching version for their LTS product.
-
@scottalanmiller You're right Scott, but this post suggests otherwise
-
@antonit said:
@scottalanmiller You're right Scott, but this post suggests otherwise
In what way do you feel that that thread suggests otherwise?
-
@antonit said:
@scottalanmiller You're right Scott, but this post suggests otherwise
This begs the question..... what Zabbix are you installing? Zabbix 3.0 is the current LTS version. It released today, believe it or not, and is the only one you should be considering. Zabbix 2.4 is 12 years old and not what should be being run.
That thread is from the Zabbix 2 era and is thirteen months old. Unless it is 13 minutes old, it's totally outdated.
-
@scottalanmiller I've installed 2.4 and the installation was done last week... Guess I'll start over
Keep you posted. -
This adds to the excitement.
-
@scottalanmiller said:
Zabbix 3.0 is the current LTS version. It released today,
Great time to delete my VM and start again with latest version lol
-
I am excited to see the new interface. The old one was SO dated.
-
@scottalanmiller said:
I am excited to see the new interface. The old one was SO dated.
Indeed! I didn't realize 3.0 had dropped already, so I'm planning an upgrade
-
@dafyre said:
@scottalanmiller said:
I am excited to see the new interface. The old one was SO dated.
Indeed! I didn't realize 3.0 had dropped already, so I'm planning an upgrade
Well, it WAS only a couple of hours ago
You'd have to be watching like a hawk. -
@scottalanmiller said:
@dafyre said:
@scottalanmiller said:
I am excited to see the new interface. The old one was SO dated.
Indeed! I didn't realize 3.0 had dropped already, so I'm planning an upgrade
Well, it WAS only a couple of hours ago
You'd have to be watching like a hawk.Oh, ha ha ha. i feel slightly better then.
