Error In Logs: Unable to record samples: sql_stats.ee4c8acddba503005666f1431d9619e4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-05-2017 12:11 PM
Hi All,
After we updated to Jakarta, I started seeing this error message occur every minute in the System Logs:
Unable to record samples: sql_stats.ee4c8acddba503005666f1431d9619e4: org.jrobin.core.RrdException: Bad sample timestamp 1506760766. Last update time was 1506760766, at least one second step is required: org.jrobin.core.RrdDb.store(RrdDb.java:704)
org.jrobin.core.Sample.update(Sample.java:221)
com.glide.velocious.jrobin.backend.JRobinDB.recordSamples(JRobinDB.java:60)
com.glide.velocious.jrobin.da.JRobinWriter.recordSamples(JRobinWriter.java:56)
com.glide.monitor.db.MysqlStatsMonitor.flush(MysqlStatsMonitor.java:115)
com.glide.ui.monitor.InternalMonitor.flushSingletons(InternalMonitor.java:225)
com.glide.ui.monitor.InternalMonitor.run(InternalMonitor.java:195)
Does anyone know what this means? I'm not too sure what sql_stats is, but what follows appears to be a sys_id, and it's the same one every time. Is there anywhere else I can investigate to see what the issue seems to be?
My biggest concern is that it is marked as an error and is logged every minute, and that it appears to be a repeat sys_id.
Thanks so much!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2017 05:12 AM
I mentioned it earlier, it's jrobin_database. It contains records for each definition.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2017 05:13 AM
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-05-2018 07:56 AM
I encountered the same error...
Here is the fix for an on-premise implementation running two app servers.
The root cause is a timing difference in the application servers. I think mine were only 30 seconds off.
Use 'timedatectl' to set the time within a second or so of each other.
And the message should go away.