-
-
Notifications
You must be signed in to change notification settings - Fork 230
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_proxy.rb:7: syntax error #281
Comments
Hi, |
Yes, I'm sure. It's default ruby installation in Ubuntu 14.04.
|
I've tried to update ruby to 2.1 (the later version doesn't work with Puppet 3.x). And I'm getting the same issue:
|
This looks really strange. Is is possible that the ruby version used by puppet is not your system ruby? Is this a self-packaged puppet or installed as gem? |
No, the puppet uses system ruby:
The puppet installed from the PuppetLabs repo:
|
Moreover I'm getting the same error on the Cent OS 7.2:
|
Should I install something except the puppet modules (puppet-zabbix and it's dependencies)? I looked at the list of installed gems, there wasn't a zabbixapi gem. I've successfully installed it by hands and now I'm getting another one error message:
|
My Puppet server is running on CentOS 6 with ruby 1.8.7. If the Puppet run "types" on the server that might be a root cause of my issues. I'll install the new Puppet server using newer ruby and check this guess. |
My fault, the Puppet's types are executed on the server side where I had ruby-1.8.7. Thank you for help! |
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
There are some errors and puppet is unable to apply configuration.
What behaviour did you expect instead
I'm trying to setup zabbix server (without proxy) and agent using puppet-zabbix module.
Output log
The error disappears when I remove "manage_resources => true" in the server section. But I want to manage hosts using Zabbix API.
Can somebody tell me if I'm doing something wrong?
Thank you!
The text was updated successfully, but these errors were encountered: