Oh, yeah, completely agreed. The 1.19.5_pre releases fix the LDAP issue, which is awesome - but not so great when you get logged in and there are no indices logged! 
Thanks for checking, I look forward to finding out what you discover. LMK if I can do anything on my end.
@cmh here is new build for you to test:
Indeed, there was an issue with _bulk request. Now should be ok.
1 Like
Thank you!
Applied on one cluster yesterday when I saw your message. Last night I logged in at 8:15 our time (just after midnight GMT) and I saw indices had been created for today. Checking again this morning, I see the logs are still coming in. I also logged in with my LDAP account - so at this point I would say that both of the issues I’ve seen are fixed. I will roll pre9 out to one or two other clusters this morning and continue to monitor.
Thanks!
2 Likes
Update - I’ve got 1.19.5_pre9 on several clusters and they’re working as expected. Thanks for the fix! Will hold off on putting it on prod clusters until 1.19.5 is released.
2 Likes
Glad to hear that, Chris. Yes, next release is going to be quite rich of fixes and enhancements in both ES and Kibana sides.
1 Like
Speaking of the next release, I’ve never received notification of a release, I think I’m supposed to be on a mailing list, but haven’t heard anything. I see there is an announcements category on the forums but the most recent thing I see is " ReadonlyREST 1.13.2 is here!" - so I guess that’s not regularly updated. Would it be possible to create a release announcements thread in there that could be followed so I get updates? Or some other way that I’ll actually receive the release notifications?
1 Like
Yeah you are right. We’ve experimented a bit and settled for the most difficult way to track: updating the download page with changelogs.
I created this poll as a result of this question. Please vote!
1 Like
Hi everyone, we have a two nodes cluster in our test environment. ES 7.17, using kibana plugin. I just received an email with similar massage to that of Chris H. But our cluster is up and running just fine. Not sure why the error. any idea on what what caused it and or what to do to avoid any potential issues. thanks.
This is the related log from ES logs: [2022-05-31T02:43:19,005][ERROR][t.b.r.a.b.d.l.i.UnboundidLdapAuthenticationService] [ol-tees-01] LDAP getting user operation failed.
[2022-05-31T02:43:19,001][ERROR][t.b.r.a.b.Block ] [ol-tees-01] KibanaAdmin: ldap_authentication rule matching got an error Task monix.execution.internal.InterceptRunnable@1d8fc822 rejected from java.util.concurrent.ThreadPoolExecutor@2b8202d0[Running, pool size = 50, active threads = 40, queued tasks = 0, completed tasks = 242893786]
java.util.concurrent.RejectedExecutionException: Task monix.execution.internal.InterceptRunnable@1d8fc822 rejected from java.util.concurrent.ThreadPoolExecutor@2b8202d0[Running, pool size = 50, active threads = 40, queued tasks = 0, completed tasks = 242893786]
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2065) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:833) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1365) ~[?:?]
this is the massage: > [2022-05-31T02:43:18,224][ERROR][t.b.r.a.b.d.l.i.UnboundidLdapAuthenticationService] [ol-tees-01] LDAP getting user operation failed.
[2022-05-31T02:43:18,224][ERROR][t.b.r.a.b.d.l.i.UnboundidLdapAuthenticationService] [ol-tees-01] LDAP getting user operation failed.
[2022-05-31T02:43:18,243][ERROR][t.b.r.a.b.Block ] [ol-tees-01] KibanaAdmin: ldap_authentication rule matching got an error Task monix.execution.internal.InterceptRunnable@414921c3 rejected from java.util.concurrent.ThreadPoolExecutor@2b8202d0[Running, pool size = 50, active threads = 33, queued tasks = 0, completed tasks = 242893370]
[2022-05-31T02:43:18,243][ERROR][t.b.r.a.b.Block ] [ol-tees-01] ROUsers: ldap_authentication rule matching got an error Task monix.execution.internal.InterceptRunnable@1fb6b893 rejected from