Abhishek, are you running more than one scheduler instance at once? Max
On Mon, Oct 29, 2018 at 8:17 AM Abhishek Sinha <abhis...@infoworks.io> wrote: > The issue is happening more frequently now. Can someone please look into > this? > > > > > On 24 September 2018 at 12:42:49 PM, Abhishek Sinha (abhis...@infoworks.io > ) > wrote: > > Can someone please help in looking into this issue? It is critical since > this has come up in one of our production environment. Also, this issue has > appeared only once till now. > > > > > Regards, > > Abhishek > > On 20-Sep-2018, at 10:18 PM, Abhishek Sinha <abhis...@infoworks.io> wrote: > > Any update on this? > > > > > Regards, > > Abhishek > > On 18-Sep-2018, at 12:48 AM, Abhishek Sinha <abhis...@infoworks.io> wrote: > > Pastebin: https://pastebin.com/K6BMTb5K > > > > > Regards, > > Abhishek > > On 18-Sep-2018, at 12:31 AM, Stefan Seelmann <m...@stefan-seelmann.de> > wrote: > > On 9/17/18 8:19 PM, Abhishek Sinha wrote: > > Any update on this? > > Please find the scheduler error log attached. > > Can you share the full python stack trace? > > > Seems the mailing list doesn't allow attachments. Either post the > stacktrace inline, or post it somewhere at pastebin or so. >
