With Zabbix Agent Active it works for sometime and then throws the error. Also make sure that your apache. The Name is the identifier for authenticating the agent to the Zabbix server and is the marker where the data are stored. Instead of spending time on the script detail, trimming the script down will reveal the faulty area sooner. The template mpm is mandatory. Code: :~ ps aux grep zabb root 9472 0.
If none of them worked, then your script doesn't have execute permissions or it is flawed. I am new to Zabbix and I am evaluating this package. Permissions A fairly common issue is permissions. Except that my general suggestion about them is: Never use the -t and -p parameters for the Zabbix agent. In the availability you should see if a certain host is monitored and if not why. I am trying to monitor a log file using Zabbix 1. If only the first script that ran as root worked, then your zabbix user does not have permissions to execute that script or parts of it.
As per the documentation they mentioned that the type should be Zabbix Agent Active. Filesystem permission issues are usually easy to test — try to run the command as the zabbix user. Have a question about this project? I have a cron job that runs a python script which uses pyelasticsearch to index some documents in an ElasticSearch instance. The default timeout on the agent is 3 seconds… and you should not change it. How to install Zabbix server you can find here: xxx. The fact is: zabbix is not executing the script, as I explained before. We figured out how they work in the article.
You can run agentd from init scripts or from command line. Is there anything I am missing here? But you are free to have even a more granular separation or to have just one host-group. While reading about the module I noticed a link to a webpage that took advantage of this status module and used rrdtool to create some nice graphics from the result. So, I think this is a bug of version 2. Be very careful with choosing the Name in other places also called Hostname. Very old versions of Zabbix agent did not support userparameters in the -t and -p flags at all, but there probably are few users with that old version of the agent. Ways to debug The above identifies the most common problems with userparameters.
Date: Nov 2015 Platform: Debian 8 Packages: zabbix-agent 1:2. It might have additional clues. Please if there are some errors in this documentation or if something is not described clearly! So only one way communication is possible! Today I got a few minutes over and I decided it was time to test it on one of my Virtual Private Servers. My script needed at least 5 seconds to run whereas the default timeout for either client or server was 3 seconds. The answer for me in the end was actually really simple: In my server-status I had this line: Uptime: 338982 ReqPerSec: 2. Can you please tell me what could be the reason? Saved me some time : I also had some issues getting it to work, so I share my experience. It could be bash, it could be dash, it could be ash or something else.
One way to start about that would be comparing the variables when the script is run manually and works, and when it is run by the Zabbix agent and fails. Then you have possibly forgotten to ad the mpm module template to the host you want to monitor. Please share that with us. Many, many users have been confused and spent a lot of time chasing the wrong things. So the name could be a bit miss-leading how we used it for our purposes. The item's becoming unsupported due to some bottleneck.
Available modules are: aria Module to monitor the Aria Storage Engine status variables. To look at your performance data go to the following web-site: and log in with the credentials we provide you. Guys, We've implemented an apache monitoring template based on this article:. Can you please tell me if anything I am doing wrong here? We adopted Method 3 to do that monitoring. So, the conclusion is: zabbix agent version 2. Possibly we will automatize these information in the future. All of our agents were zabbix version 1.
You can also choose root but for security reasons, this is not recommended. Conclusion Zabbix agent userparameters are very flexible and not that hard to debug. Now that is something all people love, graphs! Because of config and file location changed, check if scripts are corect etc. Please if you plan to run mpm or mpm MaaS on Windows. On the Monitoring Server only you and our engineers can see your performance data.
After upgrading all of then to 2. As I've choised to mantain the old configuration file for compatibility purposes , that path was maintened wrong in my config file. Zabbix agent is easy to extend for data collection with a feature called userparameters. Seen another issue with userparameters, or have some horror story about them? If the names do not match, the data cannot be delivered! I ran into this issue and spent several hours debugging it. Our philosophy is, that the Zabbix Agent and the Zabbix Server is running under the user mysql. Until you know your way around those two parameters, avoid them. So if you run the script from the command line, do it like this:.
Run the script manually Assuming you are using a script for the userparameter, try running that script manually as the zabbix user. Do filesystem permissions allow zabbix user to run the script? I began to investigate and later found out that, in my case, the error was due to processing timeouts. You might suspect it is some environment variable, but not know for sure which one. When we have these information we can create the service for you and provide you a configuration file. If not please get in contact with us for finding the problem. Keep in mind that permissions must allow access all along the path.