hi
Im new to zabbix, trying to see if it should replace our current commercial solution. Its a bit hard getting started with zabbix I think and we are probably way past saving money
but Im hoping the case will show better options of setting up monitors and so on once we get past the learning curve.
at the moment I simply took the appliance and installed on our Xen setup, installed the clients on some of our linux servers and selected them for the "linux template".
We get a lot of trigger action on the workload of some of the servers. Guessning that the tiggers should probably be different form server to server also based on what CPU they have each and so on.
the issue Im having most at the moment are with on of the 5 servers Im testing on. Its excaly the same as two others - they are mailscanners. One of them triggers the "unreachable" trigger all the time and SMTP down also. All the time Im happily online on the servers, running ssh connections, commands, checking mailflow and what have you. Our normal monitor system also dont report any problems.
I tried changing the timeout of the server.conf file (read in a thread that it might help) but its still doing this. As a result the graph of the network util. is also completly broken up. I dont see any problems with the server at all. It has no workload to mention or anything like this. The firewall setttings are all the same and nothing is really any different except the IP compared with the two other mailscanners running (that have also no real load but actually more load than the problem-server).
what might cause this? What might I look for?
Im new to zabbix, trying to see if it should replace our current commercial solution. Its a bit hard getting started with zabbix I think and we are probably way past saving money
but Im hoping the case will show better options of setting up monitors and so on once we get past the learning curve. at the moment I simply took the appliance and installed on our Xen setup, installed the clients on some of our linux servers and selected them for the "linux template".
We get a lot of trigger action on the workload of some of the servers. Guessning that the tiggers should probably be different form server to server also based on what CPU they have each and so on.
the issue Im having most at the moment are with on of the 5 servers Im testing on. Its excaly the same as two others - they are mailscanners. One of them triggers the "unreachable" trigger all the time and SMTP down also. All the time Im happily online on the servers, running ssh connections, commands, checking mailflow and what have you. Our normal monitor system also dont report any problems.
I tried changing the timeout of the server.conf file (read in a thread that it might help) but its still doing this. As a result the graph of the network util. is also completly broken up. I dont see any problems with the server at all. It has no workload to mention or anything like this. The firewall setttings are all the same and nothing is really any different except the IP compared with the two other mailscanners running (that have also no real load but actually more load than the problem-server).
what might cause this? What might I look for?
Comment