Activity

30 days up to

User

Activity

From 10/07/2015 to 11/05/2015

11/05/2015

08:07 PM Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy): I see. Well, I think it is to always a good idea to ping an IP to be suggested to make sure it is not live on the net... Konstantin Orekhov
05:54 PM Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy): I need to find an ip that might be useable first. The choices I have atm is parsing the lease file or pinging the who... Anonymous
05:44 PM Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy): What will prevent you from using OMAPI instead of parsing the whole lease file to make sure the IP is not given away?... Konstantin Orekhov
05:17 PM Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy): Yeah, I was thinking I can use omapi for all calls except 'unused_ip' one, which will require parsing of the lease fi... Anonymous
04:57 PM Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy): Great! One thing though - if you read through my notes from 2 years ago, parsing a lease file is *not* the only probl... Konstantin Orekhov
03:46 PM Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy): It's an improvement, albeit a small one. The biggest improvement will come when we stop parsing the lease file on eve... Anonymous
03:39 PM Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy): Dmitri, do the changes from http://projects.theforeman.org/issues/11866 help here at all? Or are they even supposed to? Konstantin Orekhov
01:12 PM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: It's possible to manually assign an ip address to an interface during host creation. It's also possible that ip sugge... Anonymous
12:39 PM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: OK, this code is completely new to me so bound to be things I was missing. Presumably you could make dhcp_update_requ... Matt Jarvis
12:21 PM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: Keep in mind this is also used during host creation, for which it makes sense. I think your change breaks host creati... Anonymous
11:54 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: I may well be being dense, but why would you want to check this unless you know it's changed ? I can't think of a sce... Matt Jarvis
08:13 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: Look on the foreman side. I think the calls to smart-proxy are being triggered here, when save! is being called: http... Anonymous
04:44 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: I've had a poke around in the code but it's not obvious where that might be happening. Can you give me a steer where ... Matt Jarvis
09:14 AM Refactor #12402 (New): Configure proxy with syslog by default: Smart proxy already have new SYSLOG setting which logs via syslog socket instead of a file. The only limitation is th... Lukas Zapletal

11/04/2015

10:43 AM Bug #2687 (New): Performance issues with large ISC dataset (DHCP smart proxy): Anonymous
10:38 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: And as you know I also just raised an issue about importing network interfaces ;) Matt Jarvis
10:36 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: That would explain a lot if that is the case. We've been trying to debug puppet timeouts for weeks now, and have been... Matt Jarvis
10:33 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: Matt Jarvis wrote:
> Anecdotally it did seem like the DHCP records are being validated during puppet runs for some r... Dominic Cleal
10:32 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: In case it's useful, here's the dump using latest github code :
Starting thread dump for current Ruby process
===... Matt Jarvis
10:23 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: Yes, I've got DEBUG logging turned on at the minute. Matt Jarvis
10:22 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: Anecdotally it did seem like the DHCP records are being validated during puppet runs for some reason - is this the ca... Matt Jarvis
10:21 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: We have around 150 hosts, split across two environments with different proxies. Matt Jarvis
10:18 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: Our lease file is around 3MB, and the environment is currently completely static so there shouldn't be any add_record... Matt Jarvis
10:09 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: Smart-proxy is responding to three simultaneous calls to add a dhcp record, which is an expensive operation (and woul... Anonymous
10:02 AM Bug #12392 (New): 100% cpu usage on foreman-proxy DHCP calls: So it's DHCP-related, since Foreman's calling @/dhcp/:network/:record@ there. I have been suspecting that Foreman mi... Dominic Cleal
09:53 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: Starting thread dump for current Ruby process
=============================================
Thread TID-11812860
... Matt Jarvis
09:33 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: Here you go, this is the same patch designed for 1.9 - changing smart_proxy.rb instead:
https://github.com/thefore... Dominic Cleal
09:28 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: launcher.rb only exists in latest smart-proxy code - can I patch the trap code in somewhere else in 1.9.2 ? Matt Jarvis
09:19 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls: We don't have any smart proxy plugins installed. I'll try the debugging step. Matt Jarvis
06:42 AM Bug #12392 (Need more information): 100% cpu usage on foreman-proxy DHCP calls: Could you check the comment on #12359 and try the same debugging step that Lukas suggests there? It will help us nar... Dominic Cleal
06:40 AM Bug #12392 (Resolved): 100% cpu usage on foreman-proxy DHCP calls: At least since 1.8, the cpu usage on the foreman-proxy has been increasing massively. We now see it using 100% of cpu... Matt Jarvis
09:32 AM Bug #12359: 100% cpu usage foreman-proxy after upgrade to 1.9: https://github.com/theforeman/smart-proxy/compare/theforeman:1.9-stable...domcleal:1.9-stable-ttin.patch - equivalent... Dominic Cleal
09:23 AM Refactor #12394 (Resolved): Netsh Deprecated in Windows 2012R2: When installing the Foreman Smart-Proxy for DHCP on a Windows 2012R2 host there is a deprecation warning that netsh w... Chris Pisano

11/02/2015

11:21 AM Feature #12370 (Ready For Testing): Provide TTIN trap for stacktrace log output: The Foreman Bot
11:18 AM Feature #12370 (Closed): Provide TTIN trap for stacktrace log output: The same way we do this for Foreman Core. Lukas Zapletal
11:17 AM Bug #12359: 100% cpu usage foreman-proxy after upgrade to 1.9: Are you able to acquire stacktrace? Proxy does not provide signal trap, but if you modify launcher.rb with this code:... Lukas Zapletal
05:01 AM Bug #12319 (Closed): Proxy templates API breaks on concurrent requests: Applied in changeset commit:26aba8520d3d32ca27b9708cb98169bc31d43d7b. Anonymous
04:16 AM Revision 26aba852: Fixes #12319: fixed race condition in templates module: Multiple simultaneous requests to /unattended/template_type no longer fail. Dmitri Dolguikh

10/31/2015

05:59 AM Bug #12359 (Resolved): 100% cpu usage foreman-proxy after upgrade to 1.9: after upgrade from 1.8 to 1.9 at some point the ruby process of foreman-proxy starts consuming high amounts of mem an... Veaceslav Mindru

10/29/2015

12:11 PM Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy): I realize this is an old ticket but figured I would start here. We are seeing much higher load on our dhcp server / ... Andrew Cooper

10/28/2015

01:33 PM Bug #12319 (Ready For Testing): Proxy templates API breaks on concurrent requests: The Foreman Bot
10:21 AM Bug #12254 (Ready For Testing): Pin addressable for Ruby 1.8 compatibility: The Foreman Bot
10:12 AM Bug #8946 (Ready For Testing): Exception thrown when foreman-proxy restarts with SIGTERM: The Foreman Bot

10/27/2015

10:46 AM Bug #12319: Proxy templates API breaks on concurrent requests: After some time I see also:... Lukas Zapletal
10:44 AM Bug #12319: Proxy templates API breaks on concurrent requests: Here is one from latest development environment proxy running on Ruby 2.0:... Lukas Zapletal
06:41 AM Bug #12319: Proxy templates API breaks on concurrent requests: I assume this is under 1.8.7? Can you attach the backtrace? Anonymous
06:28 AM Bug #12319 (Closed): Proxy templates API breaks on concurrent requests: When trying to render templates concurrently, multiple (different) failures occurs.
Reproducer:... Lukas Zapletal
04:40 AM Feature #11676: Proxy cannot be configured with remote DHCP server: Yes, NFS I think. Lukas wrote up some documentation on the foreman-dev list, but it hasn't been submitted as part of... Dominic Cleal

10/26/2015

06:01 PM Feature #11676: Proxy cannot be configured with remote DHCP server: While this is certainly a useful thing to have, how does one go about the fact that *.conf files from ISC DHCP are ex... Konstantin Orekhov
04:01 AM Bug #12295 (Feedback): Smart proxy stops listening on HTTPS port after log rotate: Assuming this is Foreman 1.7, please try again with 1.10.0-RC1, the startup code has been refactored since. I can't ... Dominic Cleal

10/23/2015

11:14 AM Bug #12295 (Closed): Smart proxy stops listening on HTTPS port after log rotate: Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1273785
Description of problem:
The foreman-proxy stops l... Bryan Kearney
10:40 AM Bug #8946: Exception thrown when foreman-proxy restarts with SIGTERM: That looks like it's still there then, thanks for confirming. I'd guess it's also happening during service stop (on ... Dominic Cleal
10:38 AM Bug #8946: Exception thrown when foreman-proxy restarts with SIGTERM: After rebooting my foreman vm, I then get the following error messages:... Sher Chowdhury
10:36 AM Bug #8946: Exception thrown when foreman-proxy restarts with SIGTERM: I don't think that's related, it's a completely different process reporting an error - it's the Puppet agent, not the... Dominic Cleal
10:34 AM Bug #8946: Exception thrown when foreman-proxy restarts with SIGTERM: Ok I just built a new foreman 1.10.0 on Centos 7.1. ... Sher Chowdhury

10/22/2015

09:59 AM Feature #12209: Introduce support for dependency injection in dns module: Refactoring ticket without any description, PR has no description. All we have is one comment which mostly explains i... Lukas Zapletal
06:52 AM Bug #12254 (Closed): Pin addressable for Ruby 1.8 compatibility: addressable 2.4.0 is scheduled to drop Ruby 1.8.7 support, so it should be pinned to < 2.4. addressable is a test de... Dominic Cleal

10/20/2015

10:06 AM Bug #8946: Exception thrown when foreman-proxy restarts with SIGTERM: It looks like the handler originally came from #11098, which is also a 1.10.0 change. The thing is that both handler... Dominic Cleal
09:45 AM Bug #8946: Exception thrown when foreman-proxy restarts with SIGTERM: change introduced in 335a1610 (https://github.com/theforeman/smart-proxy/commit/335a1610fae8cd74720e2d9841d904deb8ff1... Anonymous
10:02 AM Bug #12217 (Closed): `ruby_21` is not a valid platform` with older versions of Bundler: Applied in changeset commit:00875b34eafe4993a7b0bcd93f7b238f86858b76. Anonymous
05:49 AM Bug #12217 (Ready For Testing): `ruby_21` is not a valid platform` with older versions of Bundler: The Foreman Bot
04:15 AM Bug #12217 (Closed): `ruby_21` is not a valid platform` with older versions of Bundler: Using :platforms in a Gemfile with newer Ruby versions is incompatible with older Bundler versions that we use on a n... Dominic Cleal
09:37 AM Revision 00875b34: Fixes #12217: support older versions of bundler: No longer rely on :platforms to install test-unit dependency Dmitri Dolguikh
08:09 AM Feature #12209: Introduce support for dependency injection in dns module: Also used in puppet_proxy (one of the examples: https://github.com/theforeman/smart-proxy/blob/develop/modules/puppet... Anonymous
07:35 AM Feature #12209: Introduce support for dependency injection in dns module: Ohad Levy wrote:
> whats the usage case? could you elaborate?
https://github.com/theforeman/smart_proxy_dns_power... Dominic Cleal
05:43 AM Feature #12211: Improve DHCP subnets parsing to get more informations from DHCP server: Pull request: https://github.com/theforeman/smart-proxy/pull/330 Baptiste Agasse
05:33 AM Feature #12211 (Ready For Testing): Improve DHCP subnets parsing to get more informations from DHCP server: The Foreman Bot
05:23 AM Bug #10581: UTF8 encoding error on realm update with freeipa: Probably should document the locale/character encoding we expect. Anonymous
03:35 AM Bug #10581: UTF8 encoding error on realm update with freeipa: I've encountered the same error several times with puppet, the cause was my system's locale wasn't set properly and d... Adam Ruzicka

10/19/2015

10:07 AM Feature #12211 (Closed): Improve DHCP subnets parsing to get more informations from DHCP server: At this time, only network and netmask are parsed from DHCP server configuration.
This patch add ability to retrieve... Baptiste Agasse
09:25 AM Feature #12209: Introduce support for dependency injection in dns module: whats the usage case? could you elaborate? Ohad Levy
09:21 AM Feature #12209 (Ready For Testing): Introduce support for dependency injection in dns module: The Foreman Bot
09:20 AM Feature #12209 (Assigned): Introduce support for dependency injection in dns module: Anonymous
09:19 AM Feature #12209 (Closed): Introduce support for dependency injection in dns module: Anonymous
08:01 AM Bug #12178 (Closed): Smart Proxy Plugins do not handle rc versions well: Applied in changeset smart-proxy:commit:26e7b2f2ac3fa215c22390941b2bad33f07d1d0a. Anonymous
07:36 AM Revision 26e7b2f2: fixes #12178 - Smart Proxy Plugins do not handle rc versions well: Timo Goebel
07:01 AM Feature #12152 (Closed): support for running of smart-proxy under ruby 2.2: Applied in changeset commit:b617b3f7cb898726226533bf4bc5e62e948be5d5. Anonymous
06:55 AM Revision b617b3f7: Fixes #12152: support for ruby 2.2.x: Dmitri Dolguikh

10/15/2015

11:45 AM Feature #6225 (Feedback): As an admin I would like to bind foreman-proxy service to a specific IP address for security reasons: You can use 'bind_host' setting to specify the interface to listen on. Anonymous
11:39 AM Bug #6526 (Feedback): Registering the smart-proxy service on windows fails.: This happens when you attempt to re-install the smart-proxy service using 'register-service' script. Rebooting the OS... Anonymous
11:36 AM Bug #6893: Class import tries to update the same classes over and over again.: Any chance you could verify this on a more up-to-date setup? Anonymous
11:25 AM Refactor #7010 (Feedback): Improve Error/Debug Log messaging: This has been addressed in puppet module already, and has been proposed for dhcp module (please see https://github.co... Anonymous
11:09 AM Feature #7839 (Feedback): Support IPv6: Try setting 'bind_host' config parameter to '::' or an ipv6 address -- it should bind to an ipv6 socket then. Anonymous
08:22 AM Bug #12178 (Ready For Testing): Smart Proxy Plugins do not handle rc versions well: The Foreman Bot
08:20 AM Bug #12178 (Closed): Smart Proxy Plugins do not handle rc versions well: Foreman 1.10.0-rc-1 smart proxy dns feature does not work.
In the Log you see the following error:
E, [2015-10-... Timo Goebel

Also available in: Atom

Project

General

Profile

Foreman » Smart Proxy

Activity

Activity

11/05/2015

11/04/2015

11/02/2015

10/31/2015

10/29/2015

10/28/2015

10/27/2015

10/26/2015

10/23/2015

10/22/2015

10/20/2015

10/19/2015

10/15/2015

10/14/2015

10/13/2015

10/12/2015

10/07/2015