As described in http://www.igniterealtime.org/community/message/180535 I’m getting a similar problem.
Below is my warn.log:
2008.10.29 08:13:00 Sample time of 1225296780 for statistic muc_outgoing is invalid.
2008.10.29 08:14:00 Sample time of 1225296840 for statistic muc_outgoing is invalid.
2008.10.29 08:15:00 Sample time of 1225296900 for statistic muc_outgoing is invalid.
2008.10.29 08:16:00 Sample time of 1225296960 for statistic muc_outgoing is invalid.
2008.10.29 08:17:00 Sample time of 1225297020 for statistic muc_outgoing is invalid.
2008.10.29 08:18:00 Sample time of 1225297080 for statistic muc_outgoing is invalid.
2008.10.29 08:19:00 Sample time of 1225297140 for statistic muc_outgoing is invalid.
2008.10.29 08:20:00 Sample time of 1225297200 for statistic muc_outgoing is invalid.
2008.10.29 08:21:00 Sample time of 1225297260 for statistic muc_outgoing is invalid.
2008.10.29 08:22:00 Sample time of 1225297320 for statistic muc_outgoing is invalid.
2008.10.29 08:23:00 Sample time of 1225297380 for statistic muc_outgoing is invalid.
2008.10.29 08:24:00 Sample time of 1225297440 for statistic muc_outgoing is invalid.
2008.10.29 08:25:00 Sample time of 1225297500 for statistic muc_outgoing is invalid.
2008.10.29 08:26:00 Sample time of 1225297560 for statistic muc_outgoing is invalid.
Here’s the corresponding error.log:
2008.10.29 08:24:00 [org.jivesoftware.openfire.reporting.stats.StatsEngine$SampleTask.run(StatsEngi ne.java:373)] Error sampling for statistic muc_outgoing
org.jrobin.core.RrdException: Bad sample timestamp 1225297440. Last update time was 1225300560, at least one second step is required
at org.jrobin.core.RrdDb.store(Unknown Source)
at org.jrobin.core.Sample.update(Unknown Source)
at org.jivesoftware.openfire.reporting.stats.StatsEngine$SampleTask.run(StatsEngin e.java:367)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
2008.10.29 08:25:00 [org.jivesoftware.openfire.reporting.stats.StatsEngine$SampleTask.run(StatsEngi ne.java:373)] Error sampling for statistic muc_outgoing
org.jrobin.core.RrdException: Bad sample timestamp 1225297500. Last update time was 1225300560, at least one second step is required
at org.jrobin.core.RrdDb.store(Unknown Source)
at org.jrobin.core.Sample.update(Unknown Source)
at org.jivesoftware.openfire.reporting.stats.StatsEngine$SampleTask.run(StatsEngin e.java:367)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
2008.10.29 08:26:00 [org.jivesoftware.openfire.reporting.stats.StatsEngine$SampleTask.run(StatsEngi ne.java:373)] Error sampling for statistic muc_outgoing
org.jrobin.core.RrdException: Bad sample timestamp 1225297560. Last update time was 1225300560, at least one second step is required
at org.jrobin.core.RrdDb.store(Unknown Source)
at org.jrobin.core.Sample.update(Unknown Source)
at org.jivesoftware.openfire.reporting.stats.StatsEngine$SampleTask.run(StatsEngin e.java:367)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
This is resulting in irregularities in the graphing, unreliable graphs, and ultimately useless reports as a result. I’m not sure why its barking so often about ‘at least one second step is required’ because all the times of the messages happen on the minute in the warn.log.
Are there fixes that I’m not finding or is this a database probelm with the way the field is set? Any help would be appreciated so we can stabilize the logs and reporting functions making them reliable.