Clean installation - apache fails

Etzion_Bar-Noy · February 20, 2014, 6:00am

I am performing automated installations of Foreman. Through this, the base
system is always the same, and the amount of variability is almost nil.
Once every ten or so installation (on the same VMs, under the same
conditions exactly), the installation will fail as Apache fails to start.
The error in ssl_error_log shows:
[Wed Feb 19 11:14:40 2014] [error] Unable to configure RSA server private
key
[Wed Feb 19 11:14:40 2014] [error] SSL Library Error: 185073780
error:0B080074:x509 certificate routines:X509_check_private_key:key values
mismatch

Reinstallation of the system (and rerunning the same process) results in a
successful installation, meaning that the certificate creation, once a
while, fails. I attached the result of foreman-debug output, since this is
very awkward.

Any assistance would be greatly appreciated!

Thanks
Etzion

foreman-debug-tDNpm.tar.xz (12.3 KB)

dLobatog · February 20, 2014, 8:21pm

Hi Etzion,

From what I see on /var/log/messages (1430, : (/File[/var/lib/puppet/lib])
Failed to generate additional resources using 'eval_generate: The
certificate retrieved from the master does not match the agent's private
key.#012Certificate fingerprint:
7B:48:1A:49:ED:7C:BC:DB:B8:1B:C7:59:22:38:25:41#012To fix this, remove the
certificate from both the master and the agent and then start a puppet run,
which will automatically regenerate a certficate.#012On the master:#012
puppet cert clean mdw.mgmt#012On the agent:#012 rm -f
/var/lib/puppet/ssl/certs/mdw.mgmt.pem#012 puppet agent -t ),
it looks like your private key is somehow not being properly created or
moved to this machine, hence the SSL errors everywhere. I'd suggest to look
into how the private key is created or moved, and see if there are any
differences. I don't think Foreman is to blame here since you get errors
before then, are these hosts that you are creating through Foreman?

···

On Thu, Feb 20, 2014 at 7:00 AM, Etzion Bar-Noy wrote:

I am performing automated installations of Foreman. Through this, the base
system is always the same, and the amount of variability is almost nil.
Once every ten or so installation (on the same VMs, under the same
conditions exactly), the installation will fail as Apache fails to
start. The error in ssl_error_log shows:
[Wed Feb 19 11:14:40 2014] [error] Unable to configure RSA server private
key
[Wed Feb 19 11:14:40 2014] [error] SSL Library Error: 185073780
error:0B080074:x509 certificate routines:X509_check_private_key:key values
mismatch

Reinstallation of the system (and rerunning the same process) results in a
successful installation, meaning that the certificate creation, once a
while, fails. I attached the result of foreman-debug output, since this is
very awkward.

Any assistance would be greatly appreciated!

Thanks
Etzion

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.

–
Daniel Lobato

@elobatoss
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30

Michael_Hurn · February 24, 2014, 11:07pm

Hi Etzion,

One thing that has helped me in the past is to stop Foreman/Puppet, clean
out certs, start the puppet master, stop the puppetmaster them start
Foreman/Puppet.

As in:

service httpd stop

Clean out the certs. If this is your only system then this may work for

you. BUT Check it first as I am typing this from memory. rm -rf
/var/lib/puppet/ssl/

service puppetmaster start

That will generate new certs.

service puppetmaster stop

service httpd start.

Regards, Mike.

···

On Thursday, February 20, 2014 1:00:50 AM UTC-5, Etzion Bar-Noy wrote:

I am performing automated installations of Foreman. Through this, the base
system is always the same, and the amount of variability is almost nil.
Once every ten or so installation (on the same VMs, under the same
conditions exactly), the installation will fail as Apache fails to
start. The error in ssl_error_log shows:
[Wed Feb 19 11:14:40 2014] [error] Unable to configure RSA server private
key
[Wed Feb 19 11:14:40 2014] [error] SSL Library Error: 185073780
error:0B080074:x509 certificate routines:X509_check_private_key:key values
mismatch

Reinstallation of the system (and rerunning the same process) results in a
successful installation, meaning that the certificate creation, once a
while, fails. I attached the result of foreman-debug output, since this is
very awkward.

Any assistance would be greatly appreciated!

Thanks
Etzion

Etzion_Bar-Noy · February 21, 2014, 1:02am

Hi Daniel.
The certificates are created during the installation process of foreman. It
might be that there is some hidden bug with the way puppet generates these
certificates.
As said - the system (which is either physical or virtual) is installed
directly from Kickstart on a specifically authored DVD of RHEL.

The thing is that I do not use foreman as a one-time solution for my
internal IT or operations, but as a templating mechanism for some big-data
product, which will be deployed per customer (aka - each of my customers
will have a stand-alone system, using foreman to deploy all nodes and roles
in the system). The foreman's OS is always installed the same. It is
similar in any and every aspect, each time it's installed. The differences
usually come with the foreman's installation process. Either timeouts
(which seem to have been solved now that I do not use sqlite, but MySQL),
or incorrect certificate handling by the Apache server.

I wonder what will happen to Apache without a certificate at all. Assuming
that, will it start? If it does, than puppet would work with it as puppet
agent, however, without Apache (assuming it will not start without the
certificate in place), how do I get the puppet client to talk to the master
(same computer, however, not via https…)

Thanks!
Etzion

···

On Thursday, 20 February 2014 22:21:31 UTC+2, Daniel Lobato wrote: > > Hi Etzion, > > From what I see on /var/log/messages (1430, : (/File[/var/lib/puppet/lib]) > Failed to generate additional resources using 'eval_generate: The > certificate retrieved from the master does not match the agent's private > key.#012Certificate fingerprint: > 7B:48:1A:49:ED:7C:BC:DB:B8:1B:C7:59:22:38:25:41#012To fix this, remove the > certificate from both the master and the agent and then start a puppet run, > which will automatically regenerate a certficate.#012On the master:#012 > puppet cert clean mdw.mgmt#012On the agent:#012 rm -f > /var/lib/puppet/ssl/certs/mdw.mgmt.pem#012 puppet agent -t ), > it looks like your private key is somehow not being properly created or > moved to this machine, hence the SSL errors everywhere. I'd suggest to look > into how the private key is created or moved, and see if there are any > differences. I don't think Foreman is to blame here since you get errors > before then, are these hosts that you are creating through Foreman? > > > > > > On Thu, Feb 20, 2014 at 7:00 AM, Etzion Bar-Noy <etz...@barnoy.co.il > > wrote: > >> I am performing automated installations of Foreman. Through this, the >> base system is always the same, and the amount of variability is almost >> nil. Once every ten or so installation (on the same VMs, under the same >> conditions *exactly*), the installation will fail as Apache fails to >> start. The error in ssl_error_log shows: >> [Wed Feb 19 11:14:40 2014] [error] Unable to configure RSA server private >> key >> [Wed Feb 19 11:14:40 2014] [error] SSL Library Error: 185073780 >> error:0B080074:x509 certificate routines:X509_check_private_key:key values >> mismatch >> >> Reinstallation of the system (and rerunning the same process) results in >> a successful installation, meaning that the certificate creation, once a >> while, fails. I attached the result of foreman-debug output, since this is >> very awkward. >> >> Any assistance would be greatly appreciated! >> >> Thanks >> Etzion >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Daniel Lobato > > @elobatoss > blog.daniellobato.me > daniellobato.me > > GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 >

ohadlevy · February 21, 2014, 6:52am

> Hi Daniel.
> The certificates are created during the installation process of foreman.
> It might be that there is some hidden bug with the way puppet generates
> these certificates.
> As said - the system (which is either physical or virtual) is installed
> directly from Kickstart on a specifically authored DVD of RHEL.
>
> The thing is that I do not use foreman as a one-time solution for my
> internal IT or operations, but as a templating mechanism for some big-data
> product, which will be deployed per customer (aka - each of my customers
> will have a stand-alone system, using foreman to deploy all nodes and roles
> in the system). The foreman's OS is always installed the same. It is
> similar in any and every aspect, each time it's installed. The differences
> usually come with the foreman's installation process. Either timeouts
> (which seem to have been solved now that I do not use sqlite, but MySQL),
> or incorrect certificate handling by the Apache server.
>
> I wonder what will happen to Apache without a certificate at all. Assuming
> that, will it start? If it does, than puppet would work with it as puppet
> agent, however, without Apache (assuming it will not start without the
> certificate in place), how do I get the puppet client to talk to the master
> (same computer, however, not via https…)
>

what happens if you run the installer the second time, does it fix the
issue?

Ohad

···

On Fri, Feb 21, 2014 at 3:02 AM, Etzion Bar-Noy wrote:

Thanks!
Etzion

On Thursday, 20 February 2014 22:21:31 UTC+2, Daniel Lobato wrote:

Hi Etzion,

From what I see on /var/log/messages (1430, :
(/File[/var/lib/puppet/lib]) Failed to generate additional resources using
’eval_generate: The certificate retrieved from the master does not match
the agent’s private key.#012Certificate fingerprint:
7B:48:1A:49:ED:7C:BC:DB:B8:1B:C7:59:22:38:25:41#012To fix this, remove
the certificate from both the master and the agent and then start a puppet
run, which will automatically regenerate a certficate.#012On the
master:#012 puppet cert clean mdw.mgmt#012On the agent:#012 rm -f
/var/lib/puppet/ssl/certs/mdw.mgmt.pem#012 puppet agent -t ),
it looks like your private key is somehow not being properly created or
moved to this machine, hence the SSL errors everywhere. I’d suggest to look
into how the private key is created or moved, and see if there are any
differences. I don’t think Foreman is to blame here since you get errors
before then, are these hosts that you are creating through Foreman?

On Thu, Feb 20, 2014 at 7:00 AM, Etzion Bar-Noy etz...@barnoy.co.ilwrote:

I am performing automated installations of Foreman. Through this, the
base system is always the same, and the amount of variability is almost
nil. Once every ten or so installation (on the same VMs, under the same
conditions exactly), the installation will fail as Apache fails to
start. The error in ssl_error_log shows:
[Wed Feb 19 11:14:40 2014] [error] Unable to configure RSA server
private key
[Wed Feb 19 11:14:40 2014] [error] SSL Library Error: 185073780
error:0B080074:x509 certificate routines:X509_check_private_key:key
values mismatch

Reinstallation of the system (and rerunning the same process) results in
a successful installation, meaning that the certificate creation, once a
while, fails. I attached the result of foreman-debug output, since this is
very awkward.

Any assistance would be greatly appreciated!

Thanks
Etzion

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.

Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.

–
Daniel Lobato

@elobatoss
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.

Etzion_Bar-Noy · February 26, 2014, 12:13am

Hi Michael, and thanks for your help. I was able to work around the
problem by doing the following:

Identify that foreman installation failed (easy. Return code !=0 )
puppet cert clean hostname -f
rm -f /var/lib/puppet/ssl/certs/hostname -f.pem
rm /etc/httpd/conf.d/foreman.conf
service foreman-proxy stop
puppet agent -t
Attempt to reinstall foreman

This process was introduced to my automated deployment, and at least once
since (during my excessive tests) proven itself to work around the failure.

While I was able to find a workaround, I use this forum to bring the issue
to the attention of the developers. I am not a developer myself, so I
cannot really assist, except for testing.

Thanks!
Etzion

···

On Tuesday, 25 February 2014 01:07:18 UTC+2, Michael Hurn wrote: > > Hi Etzion, > > One thing that has helped me in the past is to stop Foreman/Puppet, clean > out certs, start the puppet master, stop the puppetmaster them start > Foreman/Puppet. > > As in: > > # service httpd stop > # Clean out the certs. If this is your only system then this may work for > you. BUT Check it first as I am typing this from memory. rm -rf > /var/lib/puppet/ssl/ > # service puppetmaster start > # That will generate new certs. > # service puppetmaster stop > # service httpd start. > > Regards, Mike. > > On Thursday, February 20, 2014 1:00:50 AM UTC-5, Etzion Bar-Noy wrote: > >> I am performing automated installations of Foreman. Through this, the >> base system is always the same, and the amount of variability is almost >> nil. Once every ten or so installation (on the same VMs, under the same >> conditions *exactly*), the installation will fail as Apache fails to >> start. The error in ssl_error_log shows: >> [Wed Feb 19 11:14:40 2014] [error] Unable to configure RSA server private >> key >> [Wed Feb 19 11:14:40 2014] [error] SSL Library Error: 185073780 >> error:0B080074:x509 certificate routines:X509_check_private_key:key values >> mismatch >> >> Reinstallation of the system (and rerunning the same process) results in >> a successful installation, meaning that the certificate creation, once a >> while, fails. I attached the result of foreman-debug output, since this is >> very awkward. >> >> Any assistance would be greatly appreciated! >> >> Thanks >> Etzion >> >

Etzion_Bar-Noy · February 23, 2014, 12:45am

If I remember correctly, then yes, it does. It works just fine on the next
installation attempt. I need to recreate the problem to be sure about it.
It happens once every many installations. I will try to reproduce this
state again, and see that my answer is correct.

Etzion

···

On Friday, 21 February 2014 08:52:53 UTC+2, ohad wrote: > > > > > On Fri, Feb 21, 2014 at 3:02 AM, Etzion Bar-Noy <etz...@barnoy.co.il > > wrote: > >> Hi Daniel. >> The certificates are created during the installation process of foreman. >> It might be that there is some hidden bug with the way puppet generates >> these certificates. >> As said - the system (which is either physical or virtual) is installed >> directly from Kickstart on a specifically authored DVD of RHEL. >> >> The thing is that I do not use foreman as a one-time solution for my >> internal IT or operations, but as a templating mechanism for some big-data >> product, which will be deployed per customer (aka - each of my customers >> will have a stand-alone system, using foreman to deploy all nodes and roles >> in the system). The foreman's OS is always installed the same. It is >> similar in any and every aspect, each time it's installed. The differences >> usually come with the foreman's installation process. Either timeouts >> (which seem to have been solved now that I do not use sqlite, but MySQL), >> or incorrect certificate handling by the Apache server. >> >> I wonder what will happen to Apache without a certificate at all. >> Assuming that, will it start? If it does, than puppet would work with it as >> puppet agent, however, without Apache (assuming it will not start without >> the certificate in place), how do I get the puppet client to talk to the >> master (same computer, however, not via https...) >> > > what happens if you run the installer the second time, does it fix the > issue? > > Ohad > >> >> Thanks! >> Etzion >> >> >> On Thursday, 20 February 2014 22:21:31 UTC+2, Daniel Lobato wrote: >> >>> Hi Etzion, >>> >>> From what I see on /var/log/messages (1430, : >>> (/File[/var/lib/puppet/lib]) Failed to generate additional resources using >>> 'eval_generate: The certificate retrieved from the master does not match >>> the agent's private key.#012Certificate fingerprint: >>> 7B:48:1A:49:ED:7C:BC:DB:B8:1B:C7:59:22:38:25:41#012To fix this, remove >>> the certificate from both the master and the agent and then start a puppet >>> run, which will automatically regenerate a certficate.#012On the >>> master:#012 puppet cert clean mdw.mgmt#012On the agent:#012 rm -f >>> /var/lib/puppet/ssl/certs/mdw.mgmt.pem#012 puppet agent -t ), >>> it looks like your private key is somehow not being properly created or >>> moved to this machine, hence the SSL errors everywhere. I'd suggest to look >>> into how the private key is created or moved, and see if there are any >>> differences. I don't think Foreman is to blame here since you get errors >>> before then, are these hosts that you are creating through Foreman? >>> >>> >>> >>> >>> >>> On Thu, Feb 20, 2014 at 7:00 AM, Etzion Bar-Noy wrote: >>> >>>> I am performing automated installations of Foreman. Through this, the >>>> base system is always the same, and the amount of variability is almost >>>> nil. Once every ten or so installation (on the same VMs, under the same >>>> conditions *exactly*), the installation will fail as Apache fails to >>>> start. The error in ssl_error_log shows: >>>> [Wed Feb 19 11:14:40 2014] [error] Unable to configure RSA server >>>> private key >>>> [Wed Feb 19 11:14:40 2014] [error] SSL Library Error: 185073780 >>>> error:0B080074:x509 certificate routines:X509_check_private_key:key >>>> values mismatch >>>> >>>> Reinstallation of the system (and rerunning the same process) results >>>> in a successful installation, meaning that the certificate creation, once a >>>> while, fails. I attached the result of foreman-debug output, since this is >>>> very awkward. >>>> >>>> Any assistance would be greatly appreciated! >>>> >>>> Thanks >>>> Etzion >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Foreman users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to foreman-user...@googlegroups.com. >>>> To post to this group, send email to forema...@googlegroups.com. >>>> >>>> Visit this group at http://groups.google.com/group/foreman-users. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> >>> >>> -- >>> Daniel Lobato >>> >>> @elobatoss >>> blog.daniellobato.me >>> daniellobato.me >>> >>> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> > >

Etzion_Bar-Noy · February 24, 2014, 9:07pm

I have been able to reproduce that at a lab. I cleanly installed a
(virtual) blank system and take a snapshot so I could revert back to
pre-foreman installation state. On my fourth or so revert->foreman-install
I hit this bug. I took another snapshot to be able to revert back to the
erroneous state, and attempting the following:

rm -f /var/lib/puppet/ssl/certs/mdw.mgmt.pem && puppet agent -t
err: Could not request certificate: Connection refused - connect(2)
Exiting; failed to retrieve certificate and waitforcert is disabled
(reverted back to the erroneous state and):
It doesn't fix the issue. I get the following error (snip):
debug: Puppet::Type::Service::ProviderRedhat: Exec: 98/134, 73%, 15.4/s,
elapsed: 00:00:09, ETA: 00:00:02
/Stage[main]/Apache::Service/Service[httpd]/ensure: change from stopped to
running failed: Could not start Service[httpd]: Execution of '/sbin/service
httpd start' returned 1: at
/usr/share/foreman-installer/modules/apache/manifests/service.pp:14
debug: Puppet::Type::Service::ProviderRedhat: Exec: 133/134, 99%, 21.2/s,
elapsed: 00:00:10
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[mdw.mgmt]: Could
not evaluate: Connection refused - connect(2)
Done : 134/134, 100%, 21.3/s,
elapsed: 00:00:11
Done : 134/134, 100%, 21.3/s,
elapsed: 00:00:11
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/foreman-installer/foreman-installer.log

I attached the output of foreman-debug.

Now that I have a snapshot of the broken status, I will see if I can devise
some method of recovery/reinstallation cleanly, so that in case of a
failure I can automatically recover from this problem without failing the
entire installation process.

Etzion

···

On Sunday, 23 February 2014 02:45:30 UTC+2, Etzion Bar-Noy wrote: > > If I remember correctly, then yes, it does. It works just fine on the next > installation attempt. I need to recreate the problem to be sure about it. > It happens once every many installations. I will try to reproduce this > state again, and see that my answer is correct. > > Etzion > > On Friday, 21 February 2014 08:52:53 UTC+2, ohad wrote: >> >> >> >> >> On Fri, Feb 21, 2014 at 3:02 AM, Etzion Bar-Noy wrote: >> >>> Hi Daniel. >>> The certificates are created during the installation process of foreman. >>> It might be that there is some hidden bug with the way puppet generates >>> these certificates. >>> As said - the system (which is either physical or virtual) is installed >>> directly from Kickstart on a specifically authored DVD of RHEL. >>> >>> The thing is that I do not use foreman as a one-time solution for my >>> internal IT or operations, but as a templating mechanism for some big-data >>> product, which will be deployed per customer (aka - each of my customers >>> will have a stand-alone system, using foreman to deploy all nodes and roles >>> in the system). The foreman's OS is always installed the same. It is >>> similar in any and every aspect, each time it's installed. The differences >>> usually come with the foreman's installation process. Either timeouts >>> (which seem to have been solved now that I do not use sqlite, but MySQL), >>> or incorrect certificate handling by the Apache server. >>> >>> I wonder what will happen to Apache without a certificate at all. >>> Assuming that, will it start? If it does, than puppet would work with it as >>> puppet agent, however, without Apache (assuming it will not start without >>> the certificate in place), how do I get the puppet client to talk to the >>> master (same computer, however, not via https...) >>> >> >> what happens if you run the installer the second time, does it fix the >> issue? >> >> Ohad >> >>> >>> Thanks! >>> Etzion >>> >>> >>> On Thursday, 20 February 2014 22:21:31 UTC+2, Daniel Lobato wrote: >>> >>>> Hi Etzion, >>>> >>>> From what I see on /var/log/messages (1430, : >>>> (/File[/var/lib/puppet/lib]) Failed to generate additional resources using >>>> 'eval_generate: The certificate retrieved from the master does not match >>>> the agent's private key.#012Certificate fingerprint: >>>> 7B:48:1A:49:ED:7C:BC:DB:B8:1B:C7:59:22:38:25:41#012To fix this, remove >>>> the certificate from both the master and the agent and then start a puppet >>>> run, which will automatically regenerate a certficate.#012On the >>>> master:#012 puppet cert clean mdw.mgmt#012On the agent:#012 rm -f >>>> /var/lib/puppet/ssl/certs/mdw.mgmt.pem#012 puppet agent -t ), >>>> it looks like your private key is somehow not being properly created or >>>> moved to this machine, hence the SSL errors everywhere. I'd suggest to look >>>> into how the private key is created or moved, and see if there are any >>>> differences. I don't think Foreman is to blame here since you get errors >>>> before then, are these hosts that you are creating through Foreman? >>>> >>>> >>>> >>>> >>>> >>>> On Thu, Feb 20, 2014 at 7:00 AM, Etzion Bar-Noy wrote: >>>> >>>>> I am performing automated installations of Foreman. Through this, the >>>>> base system is always the same, and the amount of variability is almost >>>>> nil. Once every ten or so installation (on the same VMs, under the same >>>>> conditions *exactly*), the installation will fail as Apache fails to >>>>> start. The error in ssl_error_log shows: >>>>> [Wed Feb 19 11:14:40 2014] [error] Unable to configure RSA server >>>>> private key >>>>> [Wed Feb 19 11:14:40 2014] [error] SSL Library Error: 185073780 >>>>> error:0B080074:x509 certificate routines:X509_check_private_key:key >>>>> values mismatch >>>>> >>>>> Reinstallation of the system (and rerunning the same process) results >>>>> in a successful installation, meaning that the certificate creation, once a >>>>> while, fails. I attached the result of foreman-debug output, since this is >>>>> very awkward. >>>>> >>>>> Any assistance would be greatly appreciated! >>>>> >>>>> Thanks >>>>> Etzion >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Foreman users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to foreman-user...@googlegroups.com. >>>>> To post to this group, send email to forema...@googlegroups.com. >>>>> >>>>> Visit this group at http://groups.google.com/group/foreman-users. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>> >>>> >>>> >>>> -- >>>> Daniel Lobato >>>> >>>> @elobatoss >>>> blog.daniellobato.me >>>> daniellobato.me >>>> >>>> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Foreman users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to foreman-user...@googlegroups.com. >>> To post to this group, send email to forema...@googlegroups.com. >>> Visit this group at http://groups.google.com/group/foreman-users. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >>