Let us know next week if this helped. I highly suggest upgrade to 1.15, it is a very solid release.
LZ On Wed, Oct 4, 2017 at 11:04 PM, 'Konstantin Orekhov' via Foreman users <[email protected]> wrote: > >> See the comment there, do you have this in your instance? If not git >> blame the commit and apply it. You have some older version I assume. > > > Yes, I'm running several 1.14.1 and 1.14.3 instances/clusters. Both had the > same issue with deadlocks. I've updated 2 of them with above patch and was > lucky enough to immediately observe a registration of at least 62 systems > went through w/o a single error. > I'll monitor things more, but so far this is huge steps forward. > > 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.
