Hosts out of sync

In my foreman-interface, 50% of the nodes are not reporting back and goes
out of sync. The interval is 30 min. What I don't understand is the
configuration on all nodes are same, so why some are reporting back on
every 30 min while other goes out of sync. Am I missing something? Thanks
in Advance

Most likely there is a module or class that is trying to be run, thats
failing in some way. Take a look at the reports for the nodes. Then hop on
a node and try a puppet run while tailing the logs.

··· On Thursday, July 17, 2014 7:10:59 AM UTC+8, huhm4n wrote: > > In my foreman-interface, 50% of the nodes are not reporting back and goes > out of sync. The interval is 30 min. What I don't understand is the > configuration on all nodes are same, so why some are reporting back on > every 30 min while other goes out of sync. Am I missing something? Thanks > in Advance >

Well start with basic tests, make sure the puppet agent service is running.
What OS, and versions are you running. Usually a 'service puppet status'
gets you the answer to this.

··· On Wednesday, July 16, 2014 7:10:59 PM UTC-4, huhm4n wrote: > > In my foreman-interface, 50% of the nodes are not reporting back and goes > out of sync. The interval is 30 min. What I don't understand is the > configuration on all nodes are same, so why some are reporting back on > every 30 min while other goes out of sync. Am I missing something? Thanks > in Advance >

I've not attached any modules to any host so far. But it is suppose to run
the agent on every 30 min and report it back to the foreman right? Half of
mine hosts are doing that without having any modules attached to them.
Also, If I go on each node and do " puppet run --test", the host will
immediately report back to the foreman server. But they are supposed to do
that automatically in every 30 min right? Thanks in advance. You've been
really good help.

··· On Wednesday, July 16, 2014 6:45:39 PM UTC-7, Robert Vernon wrote: > > Most likely there is a module or class that is trying to be run, thats > failing in some way. Take a look at the reports for the nodes. Then hop on > a node and try a puppet run while tailing the logs. > > On Thursday, July 17, 2014 7:10:59 AM UTC+8, huhm4n wrote: >> >> In my foreman-interface, 50% of the nodes are not reporting back and goes >> out of sync. The interval is 30 min. What I don't understand is the >> configuration on all nodes are same, so why some are reporting back on >> every 30 min while other goes out of sync. Am I missing something? Thanks >> in Advance >> >

check if the service puppet is running.

··· On Thu, Jul 17, 2014 at 6:45 PM, huhm4n wrote:

I’ve not attached any modules to any host so far. But it is suppose to run
the agent on every 30 min and report it back to the foreman right? Half of
mine hosts are doing that without having any modules attached to them.
Also, If I go on each node and do " puppet run --test", the host will
immediately report back to the foreman server. But they are supposed to do
that automatically in every 30 min right? Thanks in advance. You’ve been
really good help.

On Wednesday, July 16, 2014 6:45:39 PM UTC-7, Robert Vernon wrote:

Most likely there is a module or class that is trying to be run, thats
failing in some way. Take a look at the reports for the nodes. Then hop on
a node and try a puppet run while tailing the logs.

On Thursday, July 17, 2014 7:10:59 AM UTC+8, huhm4n wrote:

In my foreman-interface, 50% of the nodes are not reporting back and
goes out of sync. The interval is 30 min. What I don’t understand is the
configuration on all nodes are same, so why some are reporting back on
every 30 min while other goes out of sync. Am I missing something? Thanks
in Advance


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.