Errors during foreman installation

Hi,
after Foreman installation my puppet doesn't work properly. i think, that
it because of errors during installation process.
echo "deb http://deb.theforeman.org/ jessie stable" > /etc/apt/sources.list.
d/foreman.list
wget -q http://deb.theforeman.org/pubkey.gpg -O- | apt-key add -
aptitude update
aptitude install foreman-installer

*foreman-*installer
Removing mount "files": /etc/puppet/files does not exist or is not a
directory
Installing -otice: /AddLanguage br .br
[28%] […
Execution of '/usr/bin/apt-get -q -y -o
DPkg::Options::=–force-confold install ruby-foreman-setup' returned 100:
Reading package lists…
/Stage[main]/Foreman::Plugin::Setup/Foreman::Plugin[setup]/Package[ruby-
foreman-setup]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get
-q -y -o DPkg::Options::=–force-confold install ruby-foreman-setup'
returned 100: Reading package lists…
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[puppet.company.
domain.com]: Failed to call refresh: Proxy puppet.company.domain.com cannot
be registered (ApipieBindings::MissingArgumentsError: id): N/A
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[puppet.company.
domain.com]: Proxy puppet.company.domain.com cannot be registered (
ApipieBindings::MissingArgumentsError: id): N/A
Installing Done [
100%]
[…]
Something went wrong! Check the log for ERROR-level output

full log is in attachment.

root@puppet:~# service puppet status
● puppet.service - Puppet agent
Loaded: loaded (/lib/systemd/system/puppet.service; enabled)
Active: active (running) since Tue 2016-01-19 18:56:41 CET; 13min ago
Main PID: 37702 (puppet)
CGroup: /system.slice/puppet.service
└─37702 /usr/bin/ruby /usr/bin/puppet agent

Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/facts.d])
Wrapped exception:
Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/facts.d])
Connection refused - connect(2) for "puppet.domain.company.com" port 8140
Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/lib])
Failed to generate additional resources using 'eval_generate':
Connectio…port 8140
Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/lib])
Could not evaluate: Could not retrieve file metadata for puppet://puppet…port
8140
Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/lib])
Wrapped exception:
Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/lib])
Connection refused - connect(2) for "puppet.domain.company.com" port 8140
Jan 19 19:08:17 puppet puppet-agent[37706]: Could not retrieve catalog from
remote server: Connection refused - connect(2) for "puppet.domain.co…port
8140
Jan 19 19:08:17 puppet puppet-agent[37706]: Using cached catalog
Jan 19 19:08:17 puppet puppet-agent[37706]: Could not retrieve catalog;
skipping run
Jan 19 19:08:17 puppet puppet-agent[37706]: Could not send report:
Connection refused - connect(2) for "puppet.domain.company.com" port 8140
Hint: Some lines were ellipsized, use -l to show in full.
root@puppet:~# service puppetmaster status
● puppetmaster.service - Puppet master
Loaded: loaded (/lib/systemd/system/puppetmaster.service; disabled)
Active: inactive (dead)

Jan 19 18:55:21 puppet puppet-master[2255]: puppet.domain.company.com has a
waiting certificate request
Jan 19 18:55:21 puppet puppet-master[2255]: Signed certificate request for
puppet.domain.company.com
Jan 19 18:55:21 puppet puppet-master[2255]: Removing file
Puppet::SSL::CertificateRequest puppet.domain.company.com at
'/var/lib/puppet/ssl/ca/requ…o.ch.pem'
Jan 19 18:55:21 puppet puppet-master[2255]: Removing file
Puppet::SSL::CertificateRequest puppet.domain.company.com at
'/var/lib/puppet/ssl/certifi…o.ch.pem'
Jan 19 18:55:21 puppet puppet-master[2265]: Reopening log files
Jan 19 18:55:21 puppet puppet-master[2265]: Starting Puppet master version
3.7.2
Jan 19 18:56:35 puppet puppet-master[2265]: Caught TERM; calling stop
Jan 19 18:56:37 puppet puppet-master[2313]: Reopening log files
Jan 19 18:56:37 puppet puppet-master[2313]: Starting Puppet master version
3.7.2
Jan 19 19:08:14 puppet puppet-master[2313]: Caught TERM; calling stop
Hint: Some lines were ellipsized, use -l to show in full.

what is going wrong?

Thank you!

Is looks like you have a firewall in place that is blocking the
communication with the port 8140 as per logs

Connection refused - connect(2) for "puppet.domain.company.com" port 8140

try to disable the firewall and check again :slight_smile:

··· On Wednesday, January 20, 2016 at 5:31:14 AM UTC+11, Alex M wrote: > > Hi, > after Foreman installation my puppet doesn't work properly. i think, that > it because of errors during installation process. > echo "deb http://deb.theforeman.org/ jessie stable" > /etc/apt/sources. > list.d/foreman.list > wget -q http://deb.theforeman.org/pubkey.gpg -O- | apt-key add - > aptitude update > aptitude install foreman-installer > > *foreman-**installer* > Removing mount "files": /etc/puppet/files does not exist or is not a > directory > Installing -otice: /AddLanguage br .br > [28%] [..................... > Execution of '/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install ruby-foreman-setup' returned 100: > Reading package lists... > /Stage[main]/Foreman::Plugin::Setup/Foreman::Plugin[setup]/Package[ruby- > foreman-setup]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get > -q -y -o DPkg::Options::=--force-confold install ruby-foreman-setup' > returned 100: Reading package lists... > /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[puppet.company. > domain.com]: Failed to call refresh: Proxy puppet.company.domain.com > cannot be registered (ApipieBindings::MissingArgumentsError: id): N/A > /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[puppet.company. > domain.com]: Proxy puppet.company.domain.com cannot be registered ( > ApipieBindings::MissingArgumentsError: id): N/A > Installing Done > [100%] > [.........................................................................] > Something went wrong! Check the log for ERROR-level output > * Foreman is running at https://puppet.company.domain.com > Initial credentials are admin / Daxcc64bhsNU7XBf > * Foreman Proxy is running at https://puppet.company.domain.com:8443 > * Puppetmaster is running at port 8140 > The full log is at */var/log/foreman-installer/foreman-installer.log* > > full log is in attachment. > > root@puppet:~# service puppet status > ● puppet.service - Puppet agent > Loaded: loaded (/lib/systemd/system/puppet.service; enabled) > Active: active (running) since Tue 2016-01-19 18:56:41 CET; 13min ago > Main PID: 37702 (puppet) > CGroup: /system.slice/puppet.service > └─37702 /usr/bin/ruby /usr/bin/puppet agent > > > Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/facts.d]) > Wrapped exception: > Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/facts.d > ]) Connection refused - connect(2) for "puppet.domain.company.com" port > 8140 > Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/lib]) > Failed to generate additional resources using 'eval_generate': > Connectio...port 8140 > Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/lib]) > Could not evaluate: Could not retrieve file metadata for puppet://puppet...port > 8140 > Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/lib]) > Wrapped exception: > Jan 19 19:08:17 puppet puppet-agent[37706]: (/File[/var/lib/puppet/lib]) > Connection refused - connect(2) for "puppet.domain.company.com" port 8140 > Jan 19 19:08:17 puppet puppet-agent[37706]: Could not retrieve catalog > from remote server: Connection refused - connect(2) for "puppet.domain.co...port > 8140 > Jan 19 19:08:17 puppet puppet-agent[37706]: Using cached catalog > Jan 19 19:08:17 puppet puppet-agent[37706]: Could not retrieve catalog; > skipping run > Jan 19 19:08:17 puppet puppet-agent[37706]: Could not send report: > Connection refused - connect(2) for "puppet.domain.company.com" port 8140 > Hint: Some lines were ellipsized, use -l to show in full. > root@puppet:~# service puppetmaster status > ● puppetmaster.service - Puppet master > Loaded: loaded (/lib/systemd/system/puppetmaster.service; disabled) > Active: inactive (dead) > > > Jan 19 18:55:21 puppet puppet-master[2255]: puppet.domain.company.com has > a waiting certificate request > Jan 19 18:55:21 puppet puppet-master[2255]: Signed certificate request for > puppet.domain.company.com > Jan 19 18:55:21 puppet puppet-master[2255]: Removing file > Puppet::SSL::CertificateRequest puppet.domain.company.com at > '/var/lib/puppet/ssl/ca/requ...o.ch.pem' > Jan 19 18:55:21 puppet puppet-master[2255]: Removing file > Puppet::SSL::CertificateRequest puppet.domain.company.com at > '/var/lib/puppet/ssl/certifi...o.ch.pem' > Jan 19 18:55:21 puppet puppet-master[2265]: Reopening log files > Jan 19 18:55:21 puppet puppet-master[2265]: Starting Puppet master version > 3.7.2 > Jan 19 18:56:35 puppet puppet-master[2265]: Caught TERM; calling stop > Jan 19 18:56:37 puppet puppet-master[2313]: Reopening log files > Jan 19 18:56:37 puppet puppet-master[2313]: Starting Puppet master version > 3.7.2 > Jan 19 19:08:14 puppet puppet-master[2313]: Caught TERM; calling stop > Hint: Some lines were ellipsized, use -l to show in full. > > > what is going wrong? > > Thank you! >

Check that you have the repositories configured correctly, especially
the plugin repo. This package should be available from it.

http://theforeman.org/manuals/latest/quickstart_guide.html

··· On 19/01/16 18:31, Alex M wrote: > [ERROR 2016-01-19 19:09:41 main] /Stage[main]/Foreman::Plugin::Setup/Foreman::Plugin[setup]/Package[ruby-foreman-setup]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install ruby-foreman-setup' returned 100: Reading package lists... > [ INFO 2016-01-19 19:09:41 main] Building dependency tree... > [ INFO 2016-01-19 19:09:41 main] Reading state information... > [ INFO 2016-01-19 19:09:41 main] E: Unable to locate package ruby-foreman-setup


Dominic Cleal
dominic@cleal.org

i added plugins repo. Now the error during installation is different:

Removing mount "files": /etc/puppet/files does not exist or is not a
directory
Installing -otice: /IndexIgnore .??* *~ *# RCS CVS *,v *,t
[59%] […

Installing Done
[100%]
[…]
Success!

but puppet services still crushes:

service puppetmaster status
● puppetmaster.service - Puppet master
Loaded: loaded (/lib/systemd/system/puppetmaster.service; disabled)
Active: inactive (dead)

Jan 20 09:45:48 puppet puppet-master[2235]: Signed certificate request for
ca
Jan 20 09:45:48 puppet puppet-master[2235]: puppet.domain.company.com has a
waiting certificate request
Jan 20 09:45:48 puppet puppet-master[2235]: Signed certificate request for
puppet.domain.company.com
Jan 20 09:45:48 puppet puppet-master[2235]: Removing file Puppet::SSL::
CertificateRequest puppet.domain.company.com at
'/var/lib/puppet/ssl/ca/requ…o.ch.pem'
Jan 20 09:45:48 puppet puppet-master[2235]: Removing file Puppet::SSL::
CertificateRequest puppet.domain.company.com at
'/var/lib/puppet/ssl/certifi…o.ch.pem'
Jan 20 09:45:48 puppet puppet-master[2245]: Reopening log files
Jan 20 09:45:48 puppet puppet-master[2245]: Starting Puppet master version
3.7.2
Jan 20 09:46:48 puppet puppet-master[2245]: Config file /etc/puppet/puppet.conf
changed; triggering re-parse of all config files.
Jan 20 09:46:59 puppet puppet-master[2245]: Caught TERM; calling stop
Jan 20 09:47:01 puppet puppet-master[2293]: Reopening log files
Jan 20 09:47:01 puppet puppet-master[2293]: Starting Puppet master version
3.7.2
Jan 20 09:48:46 puppet puppet-master[2293]: The environment must be purely
alphanumeric, not 'puppet-ca'
Jan 20 09:58:40 puppet puppet-master[2293]: Caught TERM; calling stop
Hint: Some lines were ellipsized, use -l to show in full.

service puppet status
● puppet.service - Puppet agent
Loaded: loaded (/lib/systemd/system/puppet.service; enabled)
Active: active (running) since Wed 2016-01-20 09:47:03 CET; 14min ago
Main PID: 37676 (puppet)
CGroup: /system.slice/puppet.service
└─37676 /usr/bin/ruby /usr/bin/puppet agent

Jan 20 09:58:43 puppet puppet-agent[37680]: (/File[/var/lib/puppet/facts.d])
Wrapped exception:
Jan 20 09:58:43 puppet puppet-agent[37680]: (/File[/var/lib/puppet/facts.d])
Connection refused - connect(2) for "puppet.domain.company.com" port 8140
Jan 20 09:58:43 puppet puppet-agent[37680]: (/File[/var/lib/puppet/lib])
Failed to generate additional resources using 'eval_generate':
Connectio…port 8140
Jan 20 09:58:43 puppet puppet-agent[37680]: (/File[/var/lib/puppet/lib])
Could not evaluate: Could not retrieve file metadata for puppet://puppet…port
8140
Jan 20 09:58:43 puppet puppet-agent[37680]: (/File[/var/lib/puppet/lib])
Wrapped exception:
Jan 20 09:58:43 puppet puppet-agent[37680]: (/File[/var/lib/puppet/lib])
Connection refused - connect(2) for "puppet.domain.company.com" port 8140
Jan 20 09:58:43 puppet puppet-agent[37680]: Could not retrieve catalog from
remote server: Connection refused - connect(2) for "puppet.company.do…port
8140
Jan 20 09:58:43 puppet puppet-agent[37680]: Using cached catalog
Jan 20 09:58:43 puppet puppet-agent[37680]: Could not retrieve catalog;
skipping run
Jan 20 09:58:43 puppet puppet-agent[37680]: Could not send report:
Connection refused - connect(2) for "puppet.domain.company.com" port 8140
Hint: Some lines were ellipsized, use -l to show in full.

all needed ports are open:

Starting Nmap 7.01 ( https://nmap.org ) at 2016-01-20 10:07
NSE: Loaded 132 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 10:07
Completed NSE at 10:07, 0.00s elapsed
Initiating NSE at 10:07
Completed NSE at 10:07, 0.00s elapsed
Initiating Ping Scan at 10:07
Scanning puppet.domain.company.com (192.168.0.18) [4 ports]
Completed Ping Scan at 10:07, 0.21s elapsed (1 total hosts)
Initiating SYN Stealth Scan at 10:07
Scanning puppet.domain.company.com (192.168.0.18) [65535 ports]
Discovered open port 22/tcp on 192.168.0.18
Discovered open port 111/tcp on 192.168.0.18
Discovered open port 80/tcp on 192.168.0.18
Discovered open port 443/tcp on 192.168.0.18
SYN Stealth Scan Timing: About 45.35% done; ETC: 10:08 (0:00:37 remaining)
Discovered open port 8140/tcp on 192.168.0.18
Discovered open port 8443/tcp on 192.168.0.18
Discovered open port 38054/tcp on 192.168.0.18

>>> puppet.domain.company.com has a waiting certificate request
looks like i have to generate some certificate for puppet?

··· среда, 20 января 2016 г., 9:11:23 UTC+1 пользователь Dominic Cleal написал: > > On 19/01/16 18:31, Alex M wrote: > > [ERROR 2016-01-19 19:09:41 main] > /Stage[main]/Foreman::Plugin::Setup/Foreman::Plugin[setup]/Package[ruby-foreman-setup]/ensure: > change from purged to present failed: Execution of '/usr/bin/apt-get -q -y > -o DPkg::Options::=--force-confold install ruby-foreman-setup' returned > 100: Reading package lists... > > [ INFO 2016-01-19 19:09:41 main] Building dependency tree... > > [ INFO 2016-01-19 19:09:41 main] Reading state information... > > [ INFO 2016-01-19 19:09:41 main] E: Unable to locate package > ruby-foreman-setup > > Check that you have the repositories configured correctly, especially > the plugin repo. This package should be available from it. > > http://theforeman.org/manuals/latest/quickstart_guide.html > > -- > Dominic Cleal > dom...@cleal.org >

> i added plugins repo. Now the error during installation is different:
>
> >
> Removingmount "files":/etc/puppet/files does notexist orisnota directory
> Installing -otice:/IndexIgnore .??* *~ *# RCS CVS *,v *,t
> [59%] […
>
> Installing Done
> [100%]
> […]
> Success!
> * Foreman is running at https://puppet.domain.company.com
> Initialcredentials are admin /redacted
> *ForemanProxyisrunning at https://puppet.domain.company.com:8443
> *Puppetmasterisrunning at port 8140
> Thefull log isat /var/log/foreman-installer/foreman-installer.log

This is a successful installation, the web UI should be working at least.

> but puppet services still crushes:
>
> >
> service puppetmaster status
> ●puppetmaster.service -Puppetmaster
> Loaded:loaded (/lib/systemd/system/puppetmaster.service;disabled)
> Active:inactive (dead)

This is the Puppet master service, it should be stopped as it's
configured to run under Apache 2. The log looks OK.

> Jan2009:58:43puppet puppet-agent[37680]:(/File[/var/lib/puppet/facts.d])
> Wrapped exception:
> Jan 20 09:58:43 puppet puppet-agent[37680]:
> (/File[/var/lib/puppet/facts.d])Connectionrefused
> -connect(2)for"puppet.domain.company.com"port 8140
> Jan2009:58:43puppet puppet-agent[37680]:(/File[/var/lib/puppet/lib])
> Failed to generate additional resources using 'eval_generate':
> Connectio…port 8140
> Jan 20 09:58:43 puppet puppet-agent[37680]:
> (/File[/var/lib/puppet/lib])Couldnotevaluate:Couldnotretrieve file
> metadata forpuppet://puppet…port 8140
> Jan2009:58:43puppet puppet-agent[37680]:(/File[/var/lib/puppet/lib])
> Wrapped exception:
> Jan 20 09:58:43 puppet puppet-agent[37680]:
> (/File[/var/lib/puppet/lib])Connectionrefused
> -connect(2)for"puppet.domain.company.com"port 8140
> Jan2009:58:43puppet puppet-agent[37680]:Couldnotretrieve catalog
> fromremote server:Connectionrefused
> -connect(2)for"puppet.company.do…port 8140
> Jan 20 09:58:43 puppet puppet-agent[37680]: Using cached catalog
> Jan 20 09:58:43 puppet puppet-agent[37680]: Could not retrieve catalog;
> skipping run
> Jan 20 09:58:43 puppet puppet-agent[37680]: Could not send report:
> Connection refused - connect(2) for "puppet.domain.company.com" port 8140

First try to restart it in case these logs are from before the installer
ran. Try telnetting to puppet.domain.company.com port 8140, see if it's
open.

Did you run nmap against a hostname or IP? My guess would be a DNS
resolution issue, that puppet.domain.company.com is resolving to
something else and the port indeed isn't open on that interface or IP.
You should be able to figure this out with some connectivity tests, as
if Apache is listening on 8140 then it's correctly configured.

> >>> puppet.domain.company.com has a waiting certificate request
> looks like i have to generate some certificate for puppet?

I don't think so, if you look at the context of the message it was
signed and set up immediately after.

··· On 20/01/16 09:19, Alex M wrote:


Dominic Cleal
dominic@cleal.org

so, puppetmaster is disables because of Apache2 was installed?
i restarted puppet - now it works:

service puppet status
● puppet.service - Puppet agent
Loaded: loaded (/lib/systemd/system/puppet.service; enabled)
Active: active (running) since Wed 2016-01-20 10:34:35 CET; 8s ago
Process: 39682 ExecStart=/usr/bin/puppet agent $DAEMON_OPTS (code=exited,
status=0/SUCCESS)
Main PID: 39689 (puppet)
CGroup: /system.slice/puppet.service
└─39689 /usr/bin/ruby /usr/bin/puppet agent

Jan 20 10:34:35 puppet puppet-agent[39689]: Reopening log files
Jan 20 10:34:35 puppet puppet-agent[39689]: Starting Puppet client version
3.7.2
Jan 20 10:34:39 puppet puppet-agent[39693]: Finished catalog run in 0.32
seconds

nmap was runned with DNS name, that was resolved in the correct IP address
of server.

right now i restarted server - now all works. Thank you very much.

··· среда, 20 января 2016 г., 10:25:58 UTC+1 пользователь Dominic Cleal написал: > > On 20/01/16 09:19, Alex M wrote: > > i added plugins repo. Now the error during installation is different: > > > > > > > Removingmount "files":/etc/puppet/files does notexist orisnota > directory > > Installing -otice:/IndexIgnore .??* *~ *# RCS CVS *,v *,t > > [59%] [........................................... > > > > Installing Done > > [100%] > > > [.........................................................................] > > Success! > > * Foreman is running at https://puppet.domain.company.com > > Initialcredentials are admin /redacted > > *ForemanProxyisrunning at https://puppet.domain.company.com:8443 > > *Puppetmasterisrunning at port 8140 > > Thefull log isat /var/log/foreman-installer/foreman-installer.log > > This is a successful installation, the web UI should be working at least. > > > but puppet services still crushes: > > > > > > > service puppetmaster status > > ●puppetmaster.service -Puppetmaster > > Loaded:loaded (/lib/systemd/system/puppetmaster.service;disabled) > > Active:inactive (dead) > > This is the Puppet master service, it should be stopped as it's > configured to run under Apache 2. The log looks OK. > > > Jan2009:58:43puppet puppet-agent[37680]:(/File[/var/lib/puppet/facts.d]) > > Wrapped exception: > > Jan 20 09:58:43 puppet puppet-agent[37680]: > > (/File[/var/lib/puppet/facts.d])Connectionrefused > > -connect(2)for"puppet.domain.company.com"port 8140 > > Jan2009:58:43puppet puppet-agent[37680]:(/File[/var/lib/puppet/lib]) > > Failed to generate additional resources using 'eval_generate': > > Connectio...port 8140 > > Jan 20 09:58:43 puppet puppet-agent[37680]: > > (/File[/var/lib/puppet/lib])Couldnotevaluate:Couldnotretrieve file > > metadata forpuppet://puppet...port 8140 > > Jan2009:58:43puppet puppet-agent[37680]:(/File[/var/lib/puppet/lib]) > > Wrapped exception: > > Jan 20 09:58:43 puppet puppet-agent[37680]: > > (/File[/var/lib/puppet/lib])Connectionrefused > > -connect(2)for"puppet.domain.company.com"port 8140 > > Jan2009:58:43puppet puppet-agent[37680]:Couldnotretrieve catalog > > fromremote server:Connectionrefused > > -connect(2)for"puppet.company.do...port 8140 > > Jan 20 09:58:43 puppet puppet-agent[37680]: Using cached catalog > > Jan 20 09:58:43 puppet puppet-agent[37680]: Could not retrieve catalog; > > skipping run > > Jan 20 09:58:43 puppet puppet-agent[37680]: Could not send report: > > Connection refused - connect(2) for "puppet.domain.company.com" port > 8140 > > First try to restart it in case these logs are from before the installer > ran. Try telnetting to puppet.domain.company.com port 8140, see if it's > open. > > Did you run nmap against a hostname or IP? My guess would be a DNS > resolution issue, that puppet.domain.company.com is resolving to > something else and the port indeed isn't open on that interface or IP. > You should be able to figure this out with some connectivity tests, as > if Apache is listening on 8140 then it's correctly configured. > > > *>>> puppet.domain.company.com has a waiting certificate request* > > looks like i have to generate some certificate for puppet? > > I don't think so, if you look at the context of the message it was > signed and set up immediately after. > > > -- > Dominic Cleal > dom...@cleal.org >