Sorry for the delay in replying. This is our Foreman server setup:
The four ENC/fact/report servers are CentOS 7.2 running
kernel 3.10.0-327.el7.x86_64.
The following ruby*, tfm* and foreman* packages are installed:
foreman-1.12.3-1.el7.noarch
foreman-cli-1.12.3-1.el7.noarch
foreman-compute-1.12
The second one:
1 SIMPLE hosts ALL index_hosts_on_type NULL NULL NULL 1625 75.02 Using where
1 SIMPLE host_status ref index_host_status_on_host_id
index_host_status_on_host_id 4 foreman.hosts.id 1 100.00 Using index
1 SIMPLE compute_resources eq_ref PRIMARY PRIMARY 4
foreman.hosts.compute_resour
OK, the first query returns this:
1 SIMPLE hosts ALL
PRIMARY,index_hosts_on_name,index_hosts_on_last_report,index_hosts_on_installed_at,host_arch_id_ix,host_os_id_ix,host_env_id_ix,host_medium_id_ix,host_group_id_ix,index_hosts_on_certname,index_hosts_on_type,hosts_compute_resource_id_fk,hosts_i
Oh, sorry, forgot that mysql doesn't have ANALYZE - please replace it with
EXTENDED.
It doesn't look like the issue from the other thread affected something
that requires a reindex, so I doubt it is the issue - more likely one of
the related tables has a lot of rows causing the join result to be
Hmm, MySQL DB complains about the syntax of those queries:
You have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version for the right syntax to use near 'ANALYZE SELECT DISTINCT
`hosts`.`id` FROM `hosts` LEFT OUTER JOIN `host_status` ' at line 1
You have a
On 10/12, Ben Hart wrote:
> I know its possible and there are plugins for Foreman for Ansible but I'm
> unable to get them talking. I have setup identical CentOS 7 vm's, one
> running Foreman the other Ansible. I've set the config as described
> here: https://theforeman.org/plugins/foreman_ansibl
That's expected, the tracer is topped to prevent eating lot of memory,
so it rather crash than consume more. I have slightly increased the
limit, can you update the script and run once again, now for the last
time:
rails objects-total app 100
and
rails calls all 100
Please set minimum font size
Hi all,
I like to set up a foreman in our environment to realize a new provisioning
structure. Therefore I like to use the following smart proxies: tftp,dns,
dhcp and realm.
Right now, the dns and realm proxy works great, but I have some trouble
with the dhcp proxy.
I am using isc dhcpd in vers
Hey,
I think you nailed it :)
rails calls all probe failed at some point though.
*rails calls all*
FILENAME LINE METHOD CALLS
gems/gems/activerecord-4.2.5.1/lib/active_record/associations/join_depe
Were you running the "foreman-trace rails calls" utility when you
searched the problematic "puppet" query? Because the output looks like
sane output, I can see one hundred of NIC models allocated, but this
should not take 6 Gbs at all.
I've slightly enhanced the foreman-tracer, can you also try to
Thank you Greg, the funny part of this is I found that same link late last
night also.
I appreciate the help.
On Wednesday, November 2, 2016 at 4:38:37 AM UTC-5, Greg Sutcliffe wrote:
>
> I don't do Windows myself, but https://github.com/kireevco/wimaging seems
> to be the route people have th
Glad you solved it out. Thank you so much for the input data, we will
work on the performance improvements in this area. The 20k dup calls
do not seem right, there will be a snag.
On Tue, Nov 1, 2016 at 7:42 PM, Justin Foreman wrote:
> I set it to ignore the offending interface names, but the iss
This is the problem, it's seems like running a query without any field is
causing this problem, it became more aggressive now probably because i am
running it under the "Classes" dashboard which now have much much more
objects than before.
Running a query without a specific field: "puppet", mem
I don't do Windows myself, but https://github.com/kireevco/wimaging seems
to be the route people have the most success with. I'd give that a try.
Greg
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop rece
On 10/31/2016 06:14 PM, Lukas Zapletal wrote:
> We recently found a bug in 1.13 when NICs aren't validated correctly,
> which causes built call to fail to save. Symtoms are similar, return
> value is 201 not 409.
>
> Can you check the host and edit it submitting it back without any
> chances? D
Looks like there are two queries that are extremely slow for some reason,
could you please run the following commands in the psql console:
EXPLAIN ANALYZE SELECT DISTINCT `hosts`.`id` FROM `hosts` LEFT OUTER JOIN
`host_status` ON `host_status`.`host_id` = `hosts`.`id` LEFT OUTER JOIN
`compute_reso
16 matches
Mail list logo
