Foreman shows all hosts out of sync

Support
#1

Dear all,
After upgrade to Foreman 1.7.5, all hosts show out of sync. All my hosts
appears with an orange "S", I can see that all my hosts are checking
configurations with my puppet master:

May 7 10:40:05 pptmaster puppet-master[3169]: Compiled catalog for
server1.com in environment production in 0.03 seconds
May 7 10:40:05 pptmaster puppet-master[3169]: Compiled catalog
for server2.com in environment production in 0.03 seconds
May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog for
server3.com in environment production in 0.14 seconds
May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog
for server4.com in environment production in 0.04 seconds
May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog
for server5.com in environment production in 0.04 seconds

rpm -qi foreman

Name : foreman Relocations: (not relocatable)
Version : 1.7.5 Vendor: Koji
Release : 1.el6 Build Date: mié 29 abr 2015
07:33:25 ART
Install Date: mié 06 may 2015 15:11:58 ART Build Host: koji.katello.org
Group : Applications/System Source RPM:
foreman-1.7.5-1.el6.src.rpm
Size : 17512322 License: GPLv3+ with
exceptions
Signature : RSA/SHA1, mié 29 abr 2015 09:52:12 ART, Key ID
4c258bd42d762e88
Packager : Koji
URL : http://theforeman.org
Summary : Systems Management web application
Description :
Foreman is aimed to be a Single Address For All Machines Life Cycle
Management.
Foreman is based on Ruby on Rails, and this package bundles Rails and all
plugins required for Foreman to work.

ps -ef | grep foreman

foreman 9911 1 0 May06 ? 00:00:04 Passenger RackApp:
/usr/share/foreman
postgres 16245 5816 0 10:08 ? 00:00:00 postgres: foreman foreman
[local] idle
root 17376 16602 0 10:33 pts/0 00:00:00 grep foreman
497 32169 1 0 03:17 ? 00:00:23 ruby
/usr/share/foreman-proxy/bin/smart-proxy

netstat -atun | grep 8443

tcp 0 0 0.0.0.0:8443 0.0.0.0:*
LISTEN

Is similar to this
issue, https://groups.google.com/forum/#!searchin/foreman-users/sync/foreman-users/SFzyWBuDMKY/M01BT0gOrbwJ
I tried all the steps on that and it wasn't work.

#2

Is the time on the foreman server correct?

··· On Thu, May 07, 2015 at 06:43:24AM -0700, gdurandvadas@technisys.com wrote: > Dear all, > After upgrade to Foreman 1.7.5, all hosts show out of sync. All my hosts > appears with an orange "S", I can see that all my hosts are checking > configurations with my puppet master: > > May 7 10:40:05 pptmaster puppet-master[3169]: Compiled catalog for > server1.com in environment production in 0.03 seconds > May 7 10:40:05 pptmaster puppet-master[3169]: Compiled catalog > for server2.com in environment production in 0.03 seconds > May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog for > server3.com in environment production in 0.14 seconds > May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog > for server4.com in environment production in 0.04 seconds > May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog > for server5.com in environment production in 0.04 seconds > > > # rpm -qi foreman > Name : foreman Relocations: (not relocatable) > Version : 1.7.5 Vendor: Koji > Release : 1.el6 Build Date: mié 29 abr 2015 > 07:33:25 ART > Install Date: mié 06 may 2015 15:11:58 ART Build Host: koji.katello.org > Group : Applications/System Source RPM: > foreman-1.7.5-1.el6.src.rpm > Size : 17512322 License: GPLv3+ with > exceptions > Signature : RSA/SHA1, mié 29 abr 2015 09:52:12 ART, Key ID > 4c258bd42d762e88 > Packager : Koji > URL : http://theforeman.org > Summary : Systems Management web application > Description : > Foreman is aimed to be a Single Address For All Machines Life Cycle > Management. > Foreman is based on Ruby on Rails, and this package bundles Rails and all > plugins required for Foreman to work. > > # ps -ef | grep foreman > foreman 9911 1 0 May06 ? 00:00:04 Passenger RackApp: > /usr/share/foreman > postgres 16245 5816 0 10:08 ? 00:00:00 postgres: foreman foreman > [local] idle > root 17376 16602 0 10:33 pts/0 00:00:00 grep foreman > 497 32169 1 0 03:17 ? 00:00:23 ruby > /usr/share/foreman-proxy/bin/smart-proxy > # netstat -atun | grep 8443 > tcp 0 0 0.0.0.0:8443 0.0.0.0:* > LISTEN > > Is similar to this > issue, https://groups.google.com/forum/#!searchin/foreman-users/sync/foreman-users/SFzyWBuDMKY/M01BT0gOrbwJ > I tried all the steps on that and it wasn't work. > > -- > 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/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

#3

Stephen,
Yes it is. I'll add that Foreman service's is on the same server as
puppetmaster.

··· On Thursday, May 7, 2015 at 12:47:20 PM UTC-3, Stephen Benjamin wrote: > > Is the time on the foreman server correct? > > On Thu, May 07, 2015 at 06:43:24AM -0700, gduran...@technisys.com > wrote: > > Dear all, > > After upgrade to Foreman 1.7.5, all hosts show out of sync. All my hosts > > appears with an orange "S", I can see that all my hosts are checking > > configurations with my puppet master: > > > > May 7 10:40:05 pptmaster puppet-master[3169]: Compiled catalog for > > server1.com in environment production in 0.03 seconds > > May 7 10:40:05 pptmaster puppet-master[3169]: Compiled catalog > > for server2.com in environment production in 0.03 seconds > > May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog for > > server3.com in environment production in 0.14 seconds > > May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog > > for server4.com in environment production in 0.04 seconds > > May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog > > for server5.com in environment production in 0.04 seconds > > > > > > # rpm -qi foreman > > Name : foreman Relocations: (not > relocatable) > > Version : 1.7.5 Vendor: Koji > > Release : 1.el6 Build Date: mié 29 abr 2015 > > 07:33:25 ART > > Install Date: mié 06 may 2015 15:11:58 ART Build Host: > koji.katello.org > > Group : Applications/System Source RPM: > > foreman-1.7.5-1.el6.src.rpm > > Size : 17512322 License: GPLv3+ with > > exceptions > > Signature : RSA/SHA1, mié 29 abr 2015 09:52:12 ART, Key ID > > 4c258bd42d762e88 > > Packager : Koji > > URL : http://theforeman.org > > Summary : Systems Management web application > > Description : > > Foreman is aimed to be a Single Address For All Machines Life Cycle > > Management. > > Foreman is based on Ruby on Rails, and this package bundles Rails and > all > > plugins required for Foreman to work. > > > > # ps -ef | grep foreman > > foreman 9911 1 0 May06 ? 00:00:04 Passenger RackApp: > > /usr/share/foreman > > postgres 16245 5816 0 10:08 ? 00:00:00 postgres: foreman > foreman > > [local] idle > > root 17376 16602 0 10:33 pts/0 00:00:00 grep foreman > > 497 32169 1 0 03:17 ? 00:00:23 ruby > > /usr/share/foreman-proxy/bin/smart-proxy > > # netstat -atun | grep 8443 > > tcp 0 0 0.0.0.0:8443 0.0.0.0:* > > LISTEN > > > > Is similar to this > > issue, > https://groups.google.com/forum/#!searchin/foreman-users/sync/foreman-users/SFzyWBuDMKY/M01BT0gOrbwJ > > I tried all the steps on that and it wasn't work. > > > > -- > > 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/d/optout. > > > -- > Best Regards, > > Stephen Benjamin > Red Hat Engineering >
#4

> Stephen,
> Yes it is. I'll add that Foreman service's is on the same server as
> puppetmaster.

AFAIK, The timestamp is included in the report from the client. This is
the most common reason all hosts would be out of sync even if puppet is
running.

Do any reports show up in Monitor / Reports after you run puppet apply
manaully on a host?

··· On Thu, May 07, 2015 at 10:53:10AM -0700, gdurandvadas@technisys.com wrote:

On Thursday, May 7, 2015 at 12:47:20 PM UTC-3, Stephen Benjamin wrote:

Is the time on the foreman server correct?

On Thu, May 07, 2015 at 06:43:24AM -0700, gduran...@technisys.com > > <javascript:> wrote:

Dear all,
After upgrade to Foreman 1.7.5, all hosts show out of sync. All my hosts
appears with an orange “S”, I can see that all my hosts are checking
configurations with my puppet master:

May 7 10:40:05 pptmaster puppet-master[3169]: Compiled catalog for
server1.com in environment production in 0.03 seconds
May 7 10:40:05 pptmaster puppet-master[3169]: Compiled catalog
for server2.com in environment production in 0.03 seconds
May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog for
server3.com in environment production in 0.14 seconds
May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog
for server4.com in environment production in 0.04 seconds
May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog
for server5.com in environment production in 0.04 seconds

rpm -qi foreman

Name : foreman Relocations: (not
relocatable)
Version : 1.7.5 Vendor: Koji
Release : 1.el6 Build Date: mié 29 abr 2015
07:33:25 ART
Install Date: mié 06 may 2015 15:11:58 ART Build Host:
koji.katello.org
Group : Applications/System Source RPM:
foreman-1.7.5-1.el6.src.rpm
Size : 17512322 License: GPLv3+ with
exceptions
Signature : RSA/SHA1, mié 29 abr 2015 09:52:12 ART, Key ID
4c258bd42d762e88
Packager : Koji
URL : http://theforeman.org
Summary : Systems Management web application
Description :
Foreman is aimed to be a Single Address For All Machines Life Cycle
Management.
Foreman is based on Ruby on Rails, and this package bundles Rails and
all
plugins required for Foreman to work.

ps -ef | grep foreman

foreman 9911 1 0 May06 ? 00:00:04 Passenger RackApp:
/usr/share/foreman
postgres 16245 5816 0 10:08 ? 00:00:00 postgres: foreman
foreman
[local] idle
root 17376 16602 0 10:33 pts/0 00:00:00 grep foreman
497 32169 1 0 03:17 ? 00:00:23 ruby
/usr/share/foreman-proxy/bin/smart-proxy

netstat -atun | grep 8443

tcp 0 0 0.0.0.0:8443 0.0.0.0:*
LISTEN

Is similar to this
issue,
https://groups.google.com/forum/#!searchin/foreman-users/sync/foreman-users/SFzyWBuDMKY/M01BT0gOrbwJ
I tried all the steps on that and it wasn’t work.

–
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 <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

–
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/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

#5

Stephen,
Thanks for the answer, the client is on sync with the same ntp server than
foreman/puppetmaster. Also, the last activity showed on Monitor / Reports
is 2 days ago (since I made the upgrade)

··· On Thursday, May 7, 2015 at 3:18:14 PM UTC-3, Stephen Benjamin wrote: > > On Thu, May 07, 2015 at 10:53:10AM -0700, gduran...@technisys.com > wrote: > > Stephen, > > Yes it is. I'll add that Foreman service's is on the same server as > > puppetmaster. > > AFAIK, The timestamp is included in the report from the client. This is > the most common reason all hosts would be out of sync even if puppet is > running. > > Do any reports show up in Monitor / Reports after you run puppet apply > manaully on a host? > > > > > On Thursday, May 7, 2015 at 12:47:20 PM UTC-3, Stephen Benjamin wrote: > > > > > > Is the time on the foreman server correct? > > > > > > On Thu, May 07, 2015 at 06:43:24AM -0700, gduran...@technisys.com > > > wrote: > > > > Dear all, > > > > After upgrade to Foreman 1.7.5, all hosts show out of sync. All my > hosts > > > > appears with an orange "S", I can see that all my hosts are checking > > > > configurations with my puppet master: > > > > > > > > May 7 10:40:05 pptmaster puppet-master[3169]: Compiled catalog for > > > > server1.com in environment production in 0.03 seconds > > > > May 7 10:40:05 pptmaster puppet-master[3169]: Compiled catalog > > > > for server2.com in environment production in 0.03 seconds > > > > May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog for > > > > server3.com in environment production in 0.14 seconds > > > > May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog > > > > for server4.com in environment production in 0.04 seconds > > > > May 7 10:40:06 pptmaster puppet-master[3169]: Compiled catalog > > > > for server5.com in environment production in 0.04 seconds > > > > > > > > > > > > # rpm -qi foreman > > > > Name : foreman Relocations: (not > > > relocatable) > > > > Version : 1.7.5 Vendor: Koji > > > > Release : 1.el6 Build Date: mié 29 abr > 2015 > > > > 07:33:25 ART > > > > Install Date: mié 06 may 2015 15:11:58 ART Build Host: > > > koji.katello.org > > > > Group : Applications/System Source RPM: > > > > foreman-1.7.5-1.el6.src.rpm > > > > Size : 17512322 License: GPLv3+ with > > > > exceptions > > > > Signature : RSA/SHA1, mié 29 abr 2015 09:52:12 ART, Key ID > > > > 4c258bd42d762e88 > > > > Packager : Koji > > > > URL : http://theforeman.org > > > > Summary : Systems Management web application > > > > Description : > > > > Foreman is aimed to be a Single Address For All Machines Life Cycle > > > > Management. > > > > Foreman is based on Ruby on Rails, and this package bundles Rails > and > > > all > > > > plugins required for Foreman to work. > > > > > > > > # ps -ef | grep foreman > > > > foreman 9911 1 0 May06 ? 00:00:04 Passenger RackApp: > > > > /usr/share/foreman > > > > postgres 16245 5816 0 10:08 ? 00:00:00 postgres: foreman > > > foreman > > > > [local] idle > > > > root 17376 16602 0 10:33 pts/0 00:00:00 grep foreman > > > > 497 32169 1 0 03:17 ? 00:00:23 ruby > > > > /usr/share/foreman-proxy/bin/smart-proxy > > > > # netstat -atun | grep 8443 > > > > tcp 0 0 0.0.0.0:8443 0.0.0.0:* > > > > LISTEN > > > > > > > > Is similar to this > > > > issue, > > > > https://groups.google.com/forum/#!searchin/foreman-users/sync/foreman-users/SFzyWBuDMKY/M01BT0gOrbwJ > > > > I tried all the steps on that and it wasn't work. > > > > > > > > -- > > > > 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/d/optout. > > > > > > > > > -- > > > Best Regards, > > > > > > Stephen Benjamin > > > Red Hat Engineering > > > > > > > -- > > 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/d/optout. > > > -- > Best Regards, > > Stephen Benjamin > Red Hat Engineering >
#6

Il giorno giovedì 7 maggio 2015 20:27:20 UTC+2, gduran...@technisys.com ha
scritto:
>
> Stephen,
> Thanks for the answer, the client is on sync with the same ntp server than
> foreman/puppetmaster. Also, the last activity showed on Monitor / Reports
> is 2 days ago (since I made the upgrade)
>
>

In the 'Puppet' section of the Foreman settings did you adjust the 'puppet
period' according the effective period?

PL

#7

Paolo,
Thanks for your reply, my puppet_interval is set on 15 minutes.

··· On Friday, May 8, 2015 at 8:48:53 AM UTC-3, Paolo Larcheri wrote: > > > > Il giorno giovedì 7 maggio 2015 20:27:20 UTC+2, gduran...@technisys.com > ha scritto: >> >> Stephen, >> Thanks for the answer, the client is on sync with the same ntp server >> than foreman/puppetmaster. Also, the last activity showed on Monitor / >> Reports is 2 days ago (since I made the upgrade) >> >> > > In the 'Puppet' section of the Foreman settings did you adjust the 'puppet > period' according the effective period? > > PL >
#8

In adition to this, I ran the following:

foreman-rake puppet:import:hosts_and_facts RAILS_ENV=production

Now I have the same hosts (with different FQDN) one says 'no reports' and
the old one still saying 'out of sync'

<https://lh3.googleusercontent.com/-EucLF1Q60Aw/VUzDn-Cb3pI/AAAAAAAAACU/45qiSbpJbIE/s1600/01.png>

#9

I fixed the problem.
In my puppet.conf I added
reports=log, foreman

Also I cleaned all reports with:
foreman-rake reports:expire days=1 status=0 RAILS_ENV="production"

Thanks for your help to all.
Regards

··· On Friday, May 8, 2015 at 11:09:59 AM UTC-3, gduran...@technisys.com wrote: > > In adition to this, I ran the following: > > foreman-rake puppet:import:hosts_and_facts RAILS_ENV=production > > Now I have the same hosts (with different FQDN) one says 'no reports' and > the old one still saying 'out of sync' > > > > >