You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
by default, seems like operating system case can not find AMI even if based on redhat and ends up with the default database_schema_path file : $schema_path = '/usr/share/doc/zabbix-*-mysql'
However, this file doesn't exist.
Database schema file is well present as : $schema_path = "/usr/share/doc/zabbix-*-mysql-${zabbix_version}* but the case can not handle it .
Output log
initial error : Error: 'cd /usr/share/doc/zabbix--pgsql && if [ -f create.sql.gz ]; then gunzip -f create.sql.gz ; fi && psql -h 'localhost' -U 'zabbix_server' -d 'zabbix_server' -f create.sql && touch /etc/zabbix/.schema.done' returned 1 instead of one of [0]
==> aws-zabbix: Error: /Stage[main]/Zabbix::Database::Postgresql/Exec[zabbix_server_create.sql]/returns: change from notrun to 0 failed: 'cd /usr/share/doc/zabbix--pgsql && if [ -f create.sql.gz ]; then gunzip -f create.sql.gz ; fi && psql -h 'localhost' -U 'zabbix_server' -d 'zabbix_server' -f create.sql && touch /etc/zabbix/.schema.done' returned 1 instead of one of [0]
Error while trying to override database schema path :
Duplicate declaration: Class[Zabbix::Database] is already declared in file /tmp/vagrant-puppet/modules-764d2bc8e7b9b31e0bb0108d4568834b/zabbix/manifests/init.pp:279; cannot redeclare at /tmp/vagrant-puppet/manifests-846018e2aa141a5eb79a64b4015fc5f3/site.pp:42 at /tmp/vagrant-puppet/manifests-846018e2aa141a5eb79a64b4015fc5f3/site.pp:42:1 on node
What behaviour did you expect instead
how to force declaration of database_schema_path ?
how to properly have AMI machine caught by the case $::operatingsystem in zabbix::database classes
Any additional information you'd like to impart
puppet --verbose --debug :
...
Debug: Facter: fact "operatingsystem" has resolved to "Amazon".
...
The text was updated successfully, but these errors were encountered:
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
vagrant reload myvirtualmachine --provision
trying to force parameter in site.pp declaration
What are you seeing
by default, seems like operating system case can not find AMI even if based on redhat and ends up with the default database_schema_path file :
$schema_path = '/usr/share/doc/zabbix-*-mysql'
However, this file doesn't exist.
Database schema file is well present as :
$schema_path = "/usr/share/doc/zabbix-*-mysql-${zabbix_version}*
but the case can not handle it .Output log
initial error :
Error: 'cd /usr/share/doc/zabbix--pgsql && if [ -f create.sql.gz ]; then gunzip -f create.sql.gz ; fi && psql -h 'localhost' -U 'zabbix_server' -d 'zabbix_server' -f create.sql && touch /etc/zabbix/.schema.done' returned 1 instead of one of [0]
==> aws-zabbix: Error: /Stage[main]/Zabbix::Database::Postgresql/Exec[zabbix_server_create.sql]/returns: change from notrun to 0 failed: 'cd /usr/share/doc/zabbix--pgsql && if [ -f create.sql.gz ]; then gunzip -f create.sql.gz ; fi && psql -h 'localhost' -U 'zabbix_server' -d 'zabbix_server' -f create.sql && touch /etc/zabbix/.schema.done' returned 1 instead of one of [0]
Error while trying to override database schema path :
Duplicate declaration: Class[Zabbix::Database] is already declared in file /tmp/vagrant-puppet/modules-764d2bc8e7b9b31e0bb0108d4568834b/zabbix/manifests/init.pp:279; cannot redeclare at /tmp/vagrant-puppet/manifests-846018e2aa141a5eb79a64b4015fc5f3/site.pp:42 at /tmp/vagrant-puppet/manifests-846018e2aa141a5eb79a64b4015fc5f3/site.pp:42:1 on node
What behaviour did you expect instead
$::operatingsystem
inzabbix::database
classesAny additional information you'd like to impart
puppet --verbose --debug :
...
Debug: Facter: fact "operatingsystem" has resolved to "Amazon".
...
The text was updated successfully, but these errors were encountered: