Skip to content
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

zabbix class problems #28

Open
nobless opened this issue Jun 17, 2018 · 6 comments
Open

zabbix class problems #28

nobless opened this issue Jun 17, 2018 · 6 comments

Comments

@nobless
Copy link

nobless commented Jun 17, 2018

PHP message: PHP Notice: Trying to get property 'clock' of non-object in /public/inc/SMD/Backend/Zabbix.class.php on line 145

*2262 FastCGI sent in stderr: "PHP message: PHP Notice: Trying to get property 'acknowledged' of non-object in/public/inc/SMD/Backend/Zabbix.class.php on line 140

@nuxsmin
Copy link
Owner

nuxsmin commented Jun 19, 2018

Hello!

Which version of Zabbix are you running?. It seems that something went wrong when retrieving the lastEvent data from Zabbix

@nobless
Copy link
Author

nobless commented Jun 19, 2018

There are multiple zabbix versions from 2.2 - 4.0, mainly 3.4.7 versions

@nuxsmin
Copy link
Owner

nuxsmin commented Jun 19, 2018

Hmm, it might be the reason, since SMD has been tested from 2.0 to 3.0 but not on newer versions

@nobless
Copy link
Author

nobless commented Jun 19, 2018

okay, i will try to disable 4.0 zabbix backend and will report how it goes! if there will be a problem any chances on supporting 4.0 version ?

@nuxsmin
Copy link
Owner

nuxsmin commented Jun 19, 2018

I think it could be accomplished, but let me take look to the new Zabbix API, it seems that some data has changed.

Thanks for the feedback!

@nobless
Copy link
Author

nobless commented Jun 19, 2018

ok found it, i get these errors with one of zabbix 3.4.8 backend, but i have another backend with same version but no such errors.

also found it gets one trigger from somewhere which doesn't exist on that zabbix server, and this trigger have bad time sorting:
image

UPDATE: found an problem it was an host with bad triggered time, thats why it was parsed in wrong way. and got 'clock' and 'acknowledged' errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants