-
Notifications
You must be signed in to change notification settings - Fork 582
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with Veeam monitoring #130
Comments
Veeam support confirmed the problem, haven't received an update yet, since march 2017. |
@jreynaert If you have a support case open, I would be glad to open another support case where I can reference you. If you could provide me a reference and the exact error you reported, I will gladly open a case too, to increase the pressure. We have 15+ Customers with Veeam + Zabbix who used this successfully in the past. |
Anybody having this issue still? I can't get this to work with Veeam 9.0/9.5 in combination with Zabbix 3.2/3.4. Anybody any ideas? |
We are on Zabbix 3.2.7 and Veeam 9.5 and everything works. Can you give more Details? |
I'm on Zabbix 3.2.7 and Veeam 9.5. It works fine except for the following errors (from zabbix_server logs) Zabbix agent item "vbr[VmCount,X]" on host "X" failed: first network error, wait for 15 seconds which happen every 10 minutes or so Any ideas? |
What happens if you collect the data via zabbix_get? For me it works only every seconde time. Seems like the underlying PowerShell query takes a lot of time. Something which Zabbix doesn't like. |
I'm on Zabbix 3.4.7 and Veeam 9.5. I was having the same trouble and I solved increasing the Timeout=30 on zabbix agent and server. |
I'm having trouble getting the Veeam monitoring to work. I'm using Zabbix 3.2 and Veeam Backup and Replication 9.5. On the veeam server I can run the zabbix_vbr_job.ps1 script manually ok (after signing it and running with appropriate permissions) and the zabbix agent also appears to run the discovery script ok, but the Running Job query is timing out. See an abridged excerpt of the zabbix_agentd.log file below (Server names redacted)
Note, it also takes a long time for the RunningJob query to complete manually ~50 seconds. I have the timeout set to its maximum of 30 seconds in the zabbix_agentd.win.conf file, but evidently this is not long enough.
When I look at the discovery rule in the zabbix web interface it has Not supported status "Value should be a JSON object"
And the Number of running jobs item has Not supported status "Timeout while executing a shell script".
In the zabbix server log it mentions a network error.
Any ideas whats going wrong? I'm fairly new to both Zabbix and Veeam so it may be something trivial I have missed.
The text was updated successfully, but these errors were encountered: