This is my first adventure with beaker. I downloaded the puppetlabs-mysql module. I ran bundle exec rspec spec/acceptance in the mysql folder and i get this error:
[vagrant@localhost mysql]$ bundle exec rspec spec/acceptance/
/home/vagrant/.gem/ruby/gems/beaker-rspec-5.3.0/lib/beaker-rspec/helpers/serverspec.rb:43: warning: already initialized constant Module::VALID_OPTIONS_KEYS
/home/vagrant/.gem/ruby/gems/specinfra-2.56.1/lib/specinfra/configuration.rb:4: warning: previous definition of VALID_OPTIONS_KEYS was here
Beaker::Hypervisor, found some vagrant boxes to create
/usr/share/ruby/open3.rb:211:in `spawn': No such file or directory - vagrant (Errno::ENOENT)
from /usr/share/ruby/open3.rb:211:in `popen_run'
from /usr/share/ruby/open3.rb:99:in `popen3'
from /home/vagrant/.gem/ruby/gems/beaker-2.39.0/lib/beaker/hypervisor/vagrant.rb:191:in `block in vagrant_cmd'
from /home/vagrant/.gem/ruby/gems/beaker-2.39.0/lib/beaker/hypervisor/vagrant.rb:189:in `chdir'
from /home/vagrant/.gem/ruby/gems/beaker-2.39.0/lib/beaker/hypervisor/vagrant.rb:189:in `vagrant_cmd'
from /home/vagrant/.gem/ruby/gems/beaker-2.39.0/lib/beaker/hypervisor/vagrant.rb:151:in `provision'
from /home/vagrant/.gem/ruby/gems/beaker-2.39.0/lib/beaker/hypervisor.rb:75:in `create'
from /home/vagrant/.gem/ruby/gems/beaker-2.39.0/lib/beaker/network_manager.rb:69:in `block in provision'
from /home/vagrant/.gem/ruby/gems/beaker-2.39.0/lib/beaker/network_manager.rb:68:in `each_key'
from /home/vagrant/.gem/ruby/gems/beaker-2.39.0/lib/beaker/network_manager.rb:68:in `provision'
from /home/vagrant/.gem/ruby/gems/beaker-rspec-5.3.0/lib/beaker-rspec/beaker_shim.rb:35:in `provision'
from /home/vagrant/.gem/ruby/gems/beaker-rspec-5.3.0/lib/beaker-rspec/spec_helper.rb:46:in `block in '
from /home/vagrant/.gem/ruby/gems/rspec-core-3.4.4/lib/rspec/core.rb:97:in `configure'
from /home/vagrant/.gem/ruby/gems/beaker-rspec-5.3.0/lib/beaker-rspec/spec_helper.rb:5:in `'
from /home/vagrant/.gem/ruby/gems/beaker-rspec-5.3.0/lib/beaker-rspec.rb:5:in `require'
from /home/vagrant/.gem/ruby/gems/beaker-rspec-5.3.0/lib/beaker-rspec.rb:5:in `'
from /home/vagrant/.gem/ruby/gems/beaker-rspec-5.3.0/lib/beaker-rspec.rb:1:in `'
from /home/vagrant/.puppet/modules/mysql/spec/spec_helper_acceptance.rb:1:in `require'
from /home/vagrant/.puppet/modules/mysql/spec/spec_helper_acceptance.rb:1:in `'
from /home/vagrant/.puppet/modules/mysql/spec/acceptance/mysql_backup_spec.rb:1:in `require'
from /home/vagrant/.puppet/modules/mysql/spec/acceptance/mysql_backup_spec.rb:1:in `'
from /home/vagrant/.gem/ruby/gems/rspec-core-3.4.4/lib/rspec/core/configuration.rb:1361:in `load'
from /home/vagrant/.gem/ruby/gems/rspec-core-3.4.4/lib/rspec/core/configuration.rb:1361:in `block in load_spec_files'
from /home/vagrant/.gem/ruby/gems/rspec-core-3.4.4/lib/rspec/core/configuration.rb:1359:in `each'
from /home/vagrant/.gem/ruby/gems/rspec-core-3.4.4/lib/rspec/core/configuration.rb:1359:in `load_spec_files'
from /home/vagrant/.gem/ruby/gems/rspec-core-3.4.4/lib/rspec/core/runner.rb:106:in `setup'
from /home/vagrant/.gem/ruby/gems/rspec-core-3.4.4/lib/rspec/core/runner.rb:92:in `run'
from /home/vagrant/.gem/ruby/gems/rspec-core-3.4.4/lib/rspec/core/runner.rb:78:in `run'
from /home/vagrant/.gem/ruby/gems/rspec-core-3.4.4/lib/rspec/core/runner.rb:45:in `invoke'
from /home/vagrant/.gem/ruby/gems/rspec-core-3.4.4/exe/rspec:4:in `'
from /home/vagrant/bin/rspec:23:in `load'
from /home/vagrant/bin/rspec:23:in `'
P.S: I have centos7 installed in my vagrant box. I have ruby 2.0.0.
Am I missing something very obvious for the vagrant hypervisor? Please clarify.
Thanks in advance.
↧
beaker No such file or directory - vagrant
↧
Agent stops working from time to time, requires restart. Error: Failed to apply catalog: no parameter named 'ensure'
We have a Puppet environment with a few hundred machines. Recently we started seeing agents that stopped working, which results in monitoring alerts. The agents spit out the error message:
Failed to apply catalog: no parameter named 'ensure'
That is the only notification. It does not output a filename in which the parameter is mentioned. Also, there isn't really anything wrong with the manifest. Restarting the puppet agent on the nodes resolves the issue. Sometimes it goes fine for weeks, sometimes it happens twice a day.
The report YAML file contains:
--- !ruby/object:Puppet::Transaction::Report
configuration_version:
logs:
- !ruby/object:Puppet::Util::Log
message: 'Failed to apply catalog: no parameter named ''ensure'''
source: Puppet
tags: !ruby/object:Puppet::Util::TagSet
hash:
err: true
time: 2016-06-02 07:04:56.572138275 +02:00
level: :err
host: X
kind: apply
time: 2016-06-02 07:04:50.366381982 +02:00
status: failed
metrics: {}
transaction_uuid: e9738442-864f-4ebe-81c1-775ef6e6ea35
puppet_version: 4.5.0
environment: production
report_format: 5
resource_statuses: {}
I have no clue what might cause this and I couldn't find anyone with the same problem. Any ideas?
↧
↧
Help! Get error while installing Puppet Master: /opt/puppetlabs/puppet/bin/bundle: No such file or directory
Help! Get error while installing Puppet Master: /opt/puppetlabs/puppet/bin/bundle: No such file or directory
on Linux Red Hat Enterprise Linux Server release 6.6 (Santiago)
with puppet-enterprise-2016.1.2-el-6-x86_64.tar
Please help me find the fix to this asap!
** rm -f /etc/yum.repos.d/puppet-enterprise-installer.repo
** mkdir -p '/opt/puppetlabs/puppet/share/installer/installer'
** cp -pR '/local/PuppetInstall/puppet-enterprise-2016.1.2-el-6-x86_64'/* '/opt/puppetlabs/puppet/share/installer/installer'
** RACK_ENV=production /opt/puppetlabs/puppet/bin/bundle exec thin start --debug -p 3000 -a 0.0.0.0 --ssl --ssl-disable-verify
./utilities: line 792: /opt/puppetlabs/puppet/bin/bundle: No such file or directory
** mkdir -p /var/log/puppetlabs/installer
** chmod 700 /var/log/puppetlabs/installer
** cp /tmp/PuppetInstall/puppet-enterprise-2016.1.2-el-6-x86_64/install_log.lastrun.d-eqx-t3-web02.svr.apac.jpmchase.net.log /var/log/puppetlabs/installer
↧
W2K8R2 puppet agent errors on second run - File exists - C:/ProgramData/PuppetLabs/puppet/var/facts.d
I consistently get the following on a second and all subsequent puppet agent runs after a puppet agent 3.6.2 install on a a Windows 2008R2 OS:
PS C:\Users\Administrator>& 'C:\Program Files (x86)\Puppet Labs\Puppet\bin\puppet.bat' agent -t
Error: Could not set 'directory' on ensure: File exists - C:/ProgramData/PuppetLabs/puppet/var/facts.d
Error: Could not set 'directory' on ensure: File exists - C:/ProgramData/PuppetLabs/puppet/var/facts.d
Wrapped exception:
File exists - C:/ProgramData/PuppetLabs/puppet/var/facts.d
Error: /File[C:/ProgramData/PuppetLabs/puppet/var/facts.d]/ensure: change from absent to directory failed: Could not set 'directory' on ensure: File exists - C:/ProgramData/PuppetLabs/puppet/var/facts.d
Error: Could not prepare for execution: Got 1 failure(s) while initializing: File[C:/ProgramData/PuppetLabs/puppet/var/facts.d]: change from absent to directory failed: Could not set 'directory' on ensure: File exists - C:/ProgramData/PuppetLabs/puppet/var/facts.d
↧
Syntax error at '}'; expected '}'
So the error message
Syntax error at '}'; expected '}'
is not helping me find my problem.
I'm trying to do something tricky, where I have this (shortened and anonymized) and the `$cron` variable set to `mon:12:0,wed:9:30`
class symantec
(
$version,
$style = "unmanaged",
$cron = '',
)
{
define createCronJob {
$lines = split ($name,',')
$lines[0] = split ($lines[0],':')
$lines[1] = split ($lines[1],':')
file { 'symantec.cron' :
ensure => file,
path => "/etc/cron.d/symantec.liveupdate.cron",
content =>
"#
# this file is managed by puppet.
#
${lines[0][2]} ${lines[0][1]} * * ${lines[0][0]} root /usr/local/bin/system_patch.pl
${lines[1][2]} ${lines[1][1]} * * ${lines[1][0]} root /usr/local/bin/system_patch.pl
"
}
}
if $style == "unmanaged"
{
createCronJob { [ $cron ] } /* <= <= <= line with the error */
}
}
It's supposed to create a file that looks like this:
#
# this file is managed by puppet.
#
0 12 * * mon root /usr/local/bin/system_patch.pl
30 9 * * wed root /usr/local/bin/system_patch.pl
I can take out the offending line and the catalog compiles and runs fine. I tested it separately with `puppet apply` and it was working and created the file. But I must be doing something different and I don't know what.
So I guess I have two questions.
Why does the error message seem to make no sense?
How can I properly call my defined function to create the file?
↧
↧
puppet-agent-el-7-x86_64.tar.gz Not Found
I am working to do an enterprise puppet install and I am getting a not found when trying to download a file from S3. It looks like the file doesnt exist.
One interesting thing I saw is that when you navigate to the link it redirects to S3 but it also changes the URI string. Not sure if that is intentional but when I change it back I get and error because the content can only be accessed through specified URLs.
I am working to install this on AWS. Outbound security groups are wide open.
2016-10-13 10:19:40,665 - [Error]: curl -f -L -o puppet-agent-el-7-x86_64.tar.gz https://pm.puppetlabs.com/puppet-agent/2016.2.1/1.7.0/repos/puppet-agent-el-7-x86_64.tar.gz returned 22 instead of one of [0]
2016-10-13 10:19:40,666 - [Error]: /Stage[main]/Pe_repo::Platform::El_7_x86_64/Pe_repo::El[el-7-x86_64]/Pe_repo::Repo[el-7-x86_64 2016.2.1]/Pe_staging::Deploy[puppet-agent-el-7-x86_64.tar.gz]/Pe_staging::File[puppet-agent-el-7-x86_64.tar.gz]/Exec[/opt/puppetlabs/server/data/staging/pe_repo-puppet-agent-1.7.0/puppet-agent-el-7-x86_64.tar.gz]/returns: change from notrun to 0 failed: curl -f -L -o puppet-agent-el-7-x86_64.tar.gz https://pm.puppetlabs.com/puppet-agent/2016.2.1/1.7.0/repos/puppet-agent-el-7-x86_64.tar.gz returned 22 instead of one of [0]
When I just run the curl command from the command line I get a similar result.
[root@ip-172-31-3-215 ~]# curl -f -L -o puppet-agent-el-7-x86_64.tar.gz https://pm.puppetlabs.com/puppet-agent/2016.2.1/1.7.0/repos/puppet-agent-el-7-x86_64.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 286 100 286 0 0 1228 0 --:--:-- --:--:-- --:--:-- 1232
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404 Not Found
Thanks for the help!
↧
Error 502 on SERVER: Incomplete response received from application
I am trying to run puppet agent on my own puppet master, which is using Passenger. All other agents can grab their catalogues without _any issues whatsoever_ however my master cannot get it's own catalogue. What's going on?
# puppet agent --test --server=puppet
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 502 on SERVER:
Incomplete response received from application
Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run I have tried rebooting the server, to no avail. I also have puppetdb installed. Versions: httpd-2.2.15-54.0.1.el6_8.x86_64 libselinux-ruby-2.0.94-5.8.el6.x86_64 mod_passenger-5.0.30-8.el6.x86_64 passenger-5.0.30-8.el6.x86_64 puppet-3.8.7-1.el6.noarch puppetdb-2.3.8-1.el6.noarch puppetdb-terminus-2.3.8-1.el6.noarch puppetlabs-release-6-12.noarch puppet-server-3.8.7-1.el6.noarch ruby-1.8.7.374-4.el6_6.x86_64 ruby-augeas-0.4.1-3.el6.x86_64 ruby-devel-1.8.7.374-4.el6_6.x86_64 rubygem-json-1.5.5-3.el6.x86_64 rubygem-rack-1.1.0-2.el6.noarch rubygem-rake-0.8.7-2.1.el6.noarch rubygems-1.3.7-5.el6.noarch ruby-irb-1.8.7.374-4.el6_6.x86_64 ruby-libs-1.8.7.374-4.el6_6.x86_64 ruby-rdoc-1.8.7.374-4.el6_6.x86_64 ruby-shadow-2.2.0-2.el6.x86_64 OS: Red Hat Enterprise Linux Server release 6.5 (Santiago)↧
How can I use a profile to include a class defined in hiera without getting dup class errors?
I want to use a profile to call a class that is already defined in a higher level in hiera and provide different data to that class. When I call the class in my profile puppet complains that the class is already defined. Is there anything I can do to avoid the dup definition? I want to leave the current implementation in place for other servers not included in this profile.
↧
Error: Syntax error at 'Boolean'; expected ')' in Artifactory OSS Puppet Module
Hi,
Trying to use [this](https://forge.puppet.com/autostructure/artifactory) module, it breaks with syntax error:
Error: Syntax error at 'Boolean'; expected ')' at /etc/puppet/modules/artifactory/manifests/init.pp:6 on node artifactoryserver.openstacklocal
This is how I'm including it in the pp file:
node default {
include '::artifactory'
}
The line it refers is this one:
https://github.com/autostructure/artifactory/blob/master/manifests/init.pp#L6
Any idea of what I'm doing wrong?
↧
↧
service start causes Beaker to show warnings as errors.
Here's a weird one: When running `bundle exec rake beaker` I get these deprecation warnings (via an older version of puppet/nodejs)
centos-7-x64 13:26:14$ puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest.pp.dSmdfP
Info: Loading facts
Warning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Bool. There is further documentation for validate_legacy function in the README.
(at /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')
Warning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::String. There is further documentation for validate_legacy function in the README.
(at /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')
Warning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Array. There is further documentation for validate_legacy function in the README.
(at /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')
Notice: Compiled catalog for centos-7-x64.thisIsABogusDomain.com in environment production in 0.35 seconds
Info: Applying configuration version '1486157175'
Notice: Applied catalog in 1.79 seconds
centos-7-x64 executed in 4.10 seconds
should work idempotently with no errors
Finished in 55.69 seconds (files took 1 minute 58.71 seconds to load)
1 example, 0 failures
Those warnings turn into this error
1) myClass::myMod class default parameters should work idempotently with no errors
Failure/Error: apply_manifest(pp, :catch_changes => true)
Beaker::Host::CommandFailure:
Host 'centos-7-x64' exited with 2 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest.pp.HaiSli
Last 10 lines of output were:
Warning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Bool. There is further documentation for validate_legacy function in the README.
(at /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')
Warning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::String. There is further documentation for validate_legacy function in the README.
(at /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')
Warning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Array. There is further documentation for validate_legacy function in the README.
(at /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:25:in `deprecation')
Notice: Compiled catalog for centos-7-x64.thisIsABogusDomain.com in environment production in 0.45 seconds
Info: Applying configuration version '1486157593'
Notice: /Stage[main]/myClass::myMod/Service[myModvc]/enable: enable changed 'false' to 'true'
Notice: Applied catalog in 2.03 seconds
# ./spec/acceptance/myClass_myMod_spec.rb:19:in `block (3 levels) in '
Finished in 1 minute 0.3 seconds (files took 1 minute 57.51 seconds to load)
1 example, 1 failure
when I added this service block.
service { 'myModvc':
ensure => running,
enable => true,
hasstatus => true,
hasrestart => true,
}
I can comment the service block out and the error goes away. The service starts with exit code 0 and behaves as expected.
I've removed all rake tests except the default from the garethr/puppet-module-skeleton:
apply_manifest(pp, :catch_failures => true)
apply_manifest(pp, :catch_changes => true)
↧
Trigger options minutes_interval and minutes_duration don't work in PE version 2016.1.1
Hi,
We are trialing out Puppet Enterprise (V2016.1.1) and despite being mentioned in the Puppet documentation (https://docs.puppet.com/puppet/4.9/type.html#scheduledtask), it looks like the below scheduled_task trigger options don't work.
minutes_interval
minutes_duration
Puppet agent run fails with error as seen below. Any advise on this would be great:
Error: Failed to apply catalog: Parameter trigger failed on Scheduled_task[SQL B
ackup Monitor]: Unknown trigger option(s): ['minutes_duration', 'minutes_interva
l'] at /etc/puppetlabs/code/environments/production/modules/sqlbackup_scheduler/
manifests/init.pp:6
Wrapped exception:
Unknown trigger option(s): ['minutes_duration', 'minutes_interval']
Thanks,
Karthik
↧
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Invalid relationship
Gettign follwing error when I run the command "puppet agent -t " any help would be appreciated.
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Invalid relationship: File[/etc/puppetlabs/puppet/autosign.rb] { notify => Service[pe-puppetserver] }, because Service[pe-puppetserver] doesn't seem to be in the catalog
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
↧
Puppet Enterprise Dashboard does not indicate a failure on some agent runs
Hi,
We're using PE on a very small scale. We noticed that sometimes the PE dashboard looks all "green", but when we drill down to the report itself we're seeing errors. This makes it very difficult for us to find issues.
Why is that and how we can notice these issues?
Thanks
↧
↧
Contribute to puppetlabs/facter
Hi there,
I am trying to make my first contribution to the puppet ecosystem. I've read the CONTRIBUTING.md but still I am not able to figure out the proper way to create a pull request. My first commit failed because of a wrong commit message format. After I fixed that it now fails with the following error message:
*Failures
- mingw-w64 (exited 1) - mingw-w64 not installed. An error occurred during installation:
Unable to read package from path 'mingw-w64.4.8.3.nupkg'.
Command exited with code 1*
The only thing that I have changed is the EC2\_CONNECTION\_TIMEOUT from 200 to 600, because I noticed that there appears a connection-timeout on a regular basis when working with auto-scaling groups.
I am creating a pull request from BramBauwens:ticket/master/fact-1268-ec2\_connection\_timeout into puppetlabs:master. I assumed from what I have read in the CONTRIBUTING.md that master is the correct branch to merge to.
Any help would be appreciated! :-)
Bram
↧
Error 500: pe_packages after 2017.2 install
Last week I tried to install PE 2017.2 over our working 2016.5 instance. I copied the tarball to our server, unpacked it, and ran puppet-enterprise-installer script. The install seemed to run without error and it told me to finish the install I should run puupet agent -t on the server. This is a monolithic install. The puppet run returns error 500 saying that is cannot get metadata for puppet:///pe\_packages/2017.2.1/el-7\_x86\_64-1.10.1.
This directory does not exist but I do have a similar directory at /opt/puppetlabs/server/data/packages/public that contains all of the packages. Also /etc/puppetlabs/puppet/fileserver.conf has a [pe\_packages] section with path set to /opt/puppetlabs/server/data/packages/public and allow *
Is it possible I have bad permissions or something on the /opt/puppetlabs/server/data/packages/public folders or is there somewhere else I can look. I have tried reinstalling several times with the same issue, I have also tried reinstalling using a new pe.conf file, the one I am using though only has password, dnsaltname, and hostname settings set.
↧
PE-console-services fail upon start
Good afternoon,
Having an issue where our pe-console-services fail upon start, and hoping someone can help lead me in the right direction. All other puppet services are running. We are running Puppet Enterprise 2015.2 on CentOS 7
The console-services log gives the following info:
>ERROR [p.t.internal] Error during service init!!!
>java.sql.SQLException: Unable to open a test connection to the given database. JDBC url = jdbc:postgresql://puppet-corp-02.domain.com:5432/pe-rbac?ssl=true&sslfactory=org.postgresql.ssl.jdbc4.LibPQFactory&sslmode=verify-full&sslrootcert=/etc/puppetlabs/puppet/ssl/certs/ca.pem&stringtype=unspecified&characterEncoding=UTF-8, username = pe-rbac. Terminating connection pool (set lazyInit to true if you expect to start your database after your app). Original Exception: ------
...followed by:
>Caused by: java.net.ConnectException: Connection refused
Am also seeing various SSL related errors:
mcollective.log:>ERROR -- : activemq.rb:149:in `on_ssl_connectfail' SSL session creation with stomp+ssl://mcollective@puppet-corp-02.domain.com:61613 failed: Connection refused - connect(2) for "puppet-corp-02.domain.com" port 61613
puppetdb.log:>2017-08-10 00:00:55,817 ERROR [c.j.b.h.AbstractConnectionHook] Failed to acquire connection Sleeping for 7000ms and trying again. Attempts left: 1. Exception: null>2017-08-10 00:01:02,817 ERROR [c.j.b.PoolWatchThread] Error in trying to obtain a connection. Retrying in 7000ms>org.postgresql.util.PSQLException: The server does not support SSL.
I know that this is a lot of scattered information, but I hope that it can at least start a conversation to lead to a solution. Currently no agents can talk to the puppet server. This all started happening Tuesday night after a reboot. However, we restored a snapshot of the server from July 5 and are seeing the same issue, so it's apparently been a problem for awhile, but didn't show up until the services had to be started again.
Any suggestions are welcome at this point, as we feel like we've exhausted our resources on our end with various troubleshooting.
Thanks, Mike
The console-services log gives the following info:
>ERROR [p.t.internal] Error during service init!!!
>java.sql.SQLException: Unable to open a test connection to the given database. JDBC url = jdbc:postgresql://puppet-corp-02.domain.com:5432/pe-rbac?ssl=true&sslfactory=org.postgresql.ssl.jdbc4.LibPQFactory&sslmode=verify-full&sslrootcert=/etc/puppetlabs/puppet/ssl/certs/ca.pem&stringtype=unspecified&characterEncoding=UTF-8, username = pe-rbac. Terminating connection pool (set lazyInit to true if you expect to start your database after your app). Original Exception: ------
...followed by:
>Caused by: java.net.ConnectException: Connection refused
Am also seeing various SSL related errors:
mcollective.log:>ERROR -- : activemq.rb:149:in `on_ssl_connectfail' SSL session creation with stomp+ssl://mcollective@puppet-corp-02.domain.com:61613 failed: Connection refused - connect(2) for "puppet-corp-02.domain.com" port 61613
puppetdb.log:>2017-08-10 00:00:55,817 ERROR [c.j.b.h.AbstractConnectionHook] Failed to acquire connection Sleeping for 7000ms and trying again. Attempts left: 1. Exception: null>2017-08-10 00:01:02,817 ERROR [c.j.b.PoolWatchThread] Error in trying to obtain a connection. Retrying in 7000ms>org.postgresql.util.PSQLException: The server does not support SSL.
I know that this is a lot of scattered information, but I hope that it can at least start a conversation to lead to a solution. Currently no agents can talk to the puppet server. This all started happening Tuesday night after a reboot. However, we restored a snapshot of the server from July 5 and are seeing the same issue, so it's apparently been a problem for awhile, but didn't show up until the services had to be started again.
Any suggestions are welcome at this point, as we feel like we've exhausted our resources on our end with various troubleshooting.
Thanks, Mike
↧
Can't delete user(s) from a Windows local group
Any ideas what the issue may be with deleting a user/member from a windows local group?
group {'remove from Administrators':
name => 'Administrators',
ensure => absent,
auth_membership => false,
members => $mymembers,
}
This is the result. Almost seems like it's trying to remove the actual group?
Error: Could not set 'absent' on ensure: (in OLE method `Delete': )
OLE error code:8007055B in Active Directory
Cannot perform this operation on built-in accounts.
HRESULT error code:0x80020009
Exception occurred. at 25:/etc/puppetlabs/code/environments/production/modules/localgroup/manifests/fallback.pp
Wrapped exception:
(in OLE method `Delete': )
OLE error code:8007055B in Active Directory
Cannot perform this operation on built-in accounts.
HRESULT error code:0x80020009
Exception occurred.
Error: /Stage[main]/localgroup::Fallback/Group[SPT Support remove from Administrators]/ensure: change from present to absent failed: Could not set 'absent' on ensure: (in OLE method `Delete': )
OLE error code:8007055B in Active Directory
Cannot perform this operation on built-in accounts.
HRESULT error code:0x80020009
Exception occurred. at 25:/etc/puppetlabs/code/environments/production/modules/localgroup/manifests/fallback.pp
↧
↧
error code 500 on master server and agents
Hi to all,
On Oracle Linux 7, I build a webserver and installed without errors Puppet Master server.
Running `puppet agent -t` or `puppet agent -t --debug` I receive an error. It is also not possible to download the agent MSI from the default URL.
What is going wrong?
Error is:
Debug: Caching connection for https://puppetserver.theben.lab:8140
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Class[Puppet_enterprise]: expects a value for parameter 'puppet_master_host' on node puppetserver.theben.lab
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Debug: Dynamically-bound server lookup failed, falling back to report_server setting
If someone has any idea, a tip will be appreciated. Kind regards, Ben
↧
Error 400 on SERVER: Error puppet master hostname, array size from puppet db is not 1
I come here because i'm blocked on a error since 5 days. As a novice on Puppet i've added my puppet agent to my puppet master (added and signed the certificate), after some tries i've start with a error in my hieradata, problem as been solved but no i've the following problem :
*Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Error puppet master hostname, array size from puppet db is not 1 : 0 on node mynewkvm.services.lan*
↧
2 classes defined in a manifest - getting evaluation error
Hi,
Still quite new to puppet and having problems with my NTP configuration manifest. Was hoping someone can point me in the right direction please...
The end goal is to make new servers CIS compliant so I have a number of manifests that carry out all the scored CIS requirements and configure and lock the servers down. Most of them work fine but I'm struggling with my NTP manifest.
Here's the current setup on the puppet master:
**site.pp**
node default {
include james_cis
}
**init.pp (located in my james_cis module)**
class james_cis {
include james_cis::el7::scored_1_1_17
include james_cis::el7::scored_3_6
}
(scored_3_6 is my NTP manifest)
**scored_3_6.pp**
class james_cis::el7::scored_3_6 {
class { 'ntp':
servers => ['62.73.128.137', '176.62.134.139'],
restrict => [
'default kod nomodify notrap nopeer noquery',
'-6 default kod nomodify notrap nopeer noquery',
'127.0.0.1',
'-6 ::1',
],
}
}
(Please excuse line spacing and blue section above - formatting is a bit skeewiff)
When I run on the puppet agent I get the following error:
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Could not find declared class ntp at /etc/puppetlabs/code/environments/production/modules/james_cis/manifests/el7/scored_3_6.pp:6:1 on node rhel7puppetclient2.tools.gov.xxxxxxxxxx.co.uk
I think the problem is I have class listed twice in the scored_3_6 manifest and it doesn't like it. I've trawled through the web but not sure how I can get around this - any ideas would be appreciated.
↧