Summary

In the "All Complete Jobs" section of UI, the jobs listed are stale and paging through the records stops after the "3rd" next page.

However, if I go to an individual event and see job history, I can see the history. It could an issue with my file system storage but I'm not sure how to resolve.

I also have an issue where Cronicle stops running tasks with no seg fault or any errors. Looking over my log files, the scheduler tick never advances:

[1532069520.58][2018-07-19 23:52:00][xx][Cronicle][debug][4][Scheduler Minute Tick: Advancing time up to: 2018/07/19 23:52:00][]
[1532069580.636][2018-07-19 23:53:00][xx][Cronicle][debug][4][Scheduler Minute Tick: Advancing time up to: 2018/07/19 23:53:00][]
[1532100892.756][2018-07-20 08:34:52][xx][Cronicle][debug][5][Socket.io client disconnected: z9oTOzuFVLdvovZcAAAk (IP: ::ffff:127.0.
0.1)][]

Another example of scheduler not advancing:

[1534594740.949][2018-08-18 05:19:00][x][Cronicle][debug][4][Scheduler Minute Tick: Advancing time up to: 2018/08/18 05:19:00][]
[1534594800.036][2018-08-18 05:20:00][x][Cronicle][debug][4][Scheduler Minute Tick: Advancing time up to: 2018/08/18 05:20:00][]
[1534594860.126][2018-08-18 05:21:00][x][Cronicle][debug][4][Scheduler Minute Tick: Advancing time up to: 2018/08/18 05:21:00][]
[1535125990.188][2018-08-24 08:53:10][x][Cronicle][debug][5][New socket.io client connected: SiqNBvpfwntTJ1FgAAAQ (IP: ::ffff:127.0.0.1)][]

Steps to reproduce the problem

N/A

Your Setup

Vanilla Install

Operating system and version?

CentOS 6.10

Node.js version?

v10.9.0

Cronicle software version?

Version 0.8.24

Are you using a multi-server setup, or just a single server?

Single

Are you using the filesystem as back-end storage, or S3/Couchbase?

FS

Can you reproduce the crash consistently?

Yes

Log Excerpts