Hello, please use git to find out which branches it landed in, I believe the MySQL facter patch is 1.15+ only.
For 1.15.5 you need to talk with release engineer of this version which is Daniel, if the changes are small enough I see no reason not to include them. I think it's too late for 1.15.5 tho, maybe .6. For smart proxy, there was a patch done by Dmitri who redesigned DHCP parser, it's much more capable and faster now. I think this landed in 1.16 RC1, yeah: http://projects.theforeman.org/issues/19441 (https://github.com/theforeman/smart-proxy/commit/21813c6cde0d2be10747682f1a001a7c0bd3ffb9) I did not hear about unresponsive smart-proxy processes, can you check system limits (open handles etc)? SELinux? Firewall. Any proxy plugins enable? Then file a redmine bug, haven't seen that. On Fri, Oct 6, 2017 at 3:35 AM, 'Konstantin Orekhov' via Foreman users <[email protected]> wrote: > >> Let us know next week if this helped. I highly suggest upgrade to >> 1.15, it is a very solid release. > > > Are there any performance improvements for Smart-Proxy in 1.15, BTW? > > Lately, in one of my busiest locations, we've started seeing a strange issue > when SmP stops responding on 8443 for API calls. The process itself is > running, logs messages are logged, just no response from it: > > [root@spc01 ~]# systemctl start foreman-proxy > > [root@spc01 ~]# date; curl --connect-timeout 30 -kSs > https://localhost:8443/bmc; date > Thu Oct 5 17:53:36 MST 2017 > curl: (7) Failed connect to localhost:8443; Connection refused > Thu Oct 5 17:53:36 MST 2017 > > It does take ~30 seconds to start up in our env because of large DHCP > dataset, during which the connection would be refused. > > > [root@spc01 ~]# date; curl --connect-timeout 30 -kSs > https://localhost:8443/bmc; date > Thu Oct 5 17:53:49 MST 2017 > curl: (28) NSS: client certificate not found (nickname not specified) > Thu Oct 5 17:54:19 MST 2017 > > Then it starts working for a very short period of time (above) and then > stops (below). > > [root@spc01 ~]# date; curl --connect-timeout 30 -kSs > https://localhost:8443/bmc; date > Thu Oct 5 17:54:24 MST 2017 > curl: (28) Operation timed out after 30001 milliseconds with 0 out of 0 > bytes received > Thu Oct 5 17:54:54 MST 2017 > > So far there's nothing in proxy.log that helps me identify the issue. I > can't replicate it at will no matter what I do - had a bunch clients hitting > different APIs for a couple of days, nothing. > Then today the above happens and the only thing that helped me is to move > SmP from one node to another (I really wish DHCP SmP would allow for > active/active horizontal scaling instead of just being limited to a single > node). > Strace is useless as it only give this on tracing "ruby foreman-proxy" > process: > > [root@spc03 ~]# strace -p 12526 > strace: Process 12526 attached > futex(0x184e634, FUTEX_WAIT_PRIVATE, 1, NULL^Cstrace: Process 12526 detached > <detached ...> > > I tried https://github.com/tmm1/rbtrace, but it is so heavy that it actually > pretty much kills SmP by itself. > > Do you have any suggestions on ways to troubleshoot this? I have DEBUG > enabled with these values: > > :log_buffer: 4000 > :log_buffer_errors: 2000 > > Also, is a way to move SmP from WebBrick to Apache/Passenger if that makes > sense at all? If so, any docs? Any other ways to increase the performance as > it does feel like a performance issue to me. > > Thanks! > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. -- Later, Lukas @lzap Zapletal -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
