FireFly Media Server (formerly mtdaapd) › Firefly Media Server Forums › Firefly Media Server › General Discussion › Correction factor
This topic contains 1 reply, has 2 voices, and was last updated by rpedde 11 years, 4 months ago.

AuthorPosts

15th July 2007 at 3:00 pm #1565
Hey, I have a question on the FF log “correction factor”.
Is this a time adjustment… looking at the logs I noticed that it “corrected” 34 times an hour last night and the HDD was running this am instead of spun down and idle like it normally is. The log shows that it “corrected” on and off all day yesterday.
I am running svn 1586 on a Slug, unslung to flash on port 1 and Max HDD on port 2. Everything seems to be working fine, but I was curious if this is an issue and if it is connected to the HDD running this am. I have the DB and log files writing to the HDD.
Here is a sample from the log files:
20070714 21:16:29 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854809
20070714 21:16:29 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854813
20070714 21:45:47 (00000400): mDNSPlatformRawTime went backwards by 3 ticks; setting correction factor to 632854816
20070714 21:45:52 (00000400): mDNSPlatformRawTime went backwards by 6 ticks; setting correction factor to 632854822
20070714 22:01:58 (00000400): mDNSPlatformRawTime went backwards by 6 ticks; setting correction factor to 632854828
20070714 22:25:57 (00000400): mDNSPlatformRawTime went backwards by 3 ticks; setting correction factor to 632854831
20070714 22:32:50 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854836
20070714 23:37:14 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854841
20070715 00:41:37 (00000400): mDNSPlatformRawTime went backwards by 3 ticks; setting correction factor to 632854844
20070715 00:57:57 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854848
20070715 01:08:13 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854852
20070715 01:30:29 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854857
20070715 02:35:59 (00000400): mDNSPlatformRawTime went backwards by 2 ticks; setting correction factor to 632854859
20070715 02:55:49 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854863
20070715 03:08:45 (00000400): mDNSPlatformRawTime went backwards by 1 ticks; setting correction factor to 632854864
20070715 03:24:52 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854869
20070715 04:29:28 (00000400): mDNSPlatformRawTime went backwards by 7 ticks; setting correction factor to 632854876
20070715 04:29:29 (00000400): mDNSPlatformRawTime went backwards by 7 ticks; setting correction factor to 632854883
20070715 04:44:00 (00000400): mDNSPlatformRawTime went backwards by 2 ticks; setting correction factor to 632854885
20070715 05:01:40 (00000400): mDNSPlatformRawTime went backwards by 3 ticks; setting correction factor to 632854888
20070715 05:17:58 (00000400): mDNSPlatformRawTime went backwards by 6 ticks; setting correction factor to 632854894
20070715 05:38:19 (00000400): mDNSPlatformRawTime went backwards by 6 ticks; setting correction factor to 632854900
20070715 06:06:19 (00000400): mDNSPlatformRawTime went backwards by 2 ticks; setting correction factor to 632854902
20070715 06:22:31 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854907
20070715 06:32:11 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854911
20070715 06:38:37 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854916
20070715 07:11:03 (00000400): mDNSPlatformRawTime went backwards by 2 ticks; setting correction factor to 632854918
20070715 07:26:33 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854922
20070715 07:30:32 (00000400): mDNSPlatformRawTime went backwards by 1 ticks; setting correction factor to 632854923Dave
16th July 2007 at 5:50 am #11711@davesanti wrote:
Hey, I have a question on the FF log “correction factor”.
Is this a time adjustment… looking at the logs I noticed that it “corrected” 34 times an hour last night and the HDD was running this am instead of spun down and idle like it normally is. The log shows that it “corrected” on and off all day yesterday.
I am running svn 1586 on a Slug, unslung to flash on port 1 and Max HDD on port 2. Everything seems to be working fine, but I was curious if this is an issue and if it is connected to the HDD running this am. I have the DB and log files writing to the HDD.
Here is a sample from the log files:
20070714 21:16:29 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854809
20070714 21:16:29 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854813
20070714 21:45:47 (00000400): mDNSPlatformRawTime went backwards by 3 ticks; setting correction factor to 632854816
20070714 21:45:52 (00000400): mDNSPlatformRawTime went backwards by 6 ticks; setting correction factor to 632854822
20070714 22:01:58 (00000400): mDNSPlatformRawTime went backwards by 6 ticks; setting correction factor to 632854828
20070714 22:25:57 (00000400): mDNSPlatformRawTime went backwards by 3 ticks; setting correction factor to 632854831
20070714 22:32:50 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854836
20070714 23:37:14 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854841
20070715 00:41:37 (00000400): mDNSPlatformRawTime went backwards by 3 ticks; setting correction factor to 632854844
20070715 00:57:57 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854848
20070715 01:08:13 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854852
20070715 01:30:29 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854857
20070715 02:35:59 (00000400): mDNSPlatformRawTime went backwards by 2 ticks; setting correction factor to 632854859
20070715 02:55:49 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854863
20070715 03:08:45 (00000400): mDNSPlatformRawTime went backwards by 1 ticks; setting correction factor to 632854864
20070715 03:24:52 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854869
20070715 04:29:28 (00000400): mDNSPlatformRawTime went backwards by 7 ticks; setting correction factor to 632854876
20070715 04:29:29 (00000400): mDNSPlatformRawTime went backwards by 7 ticks; setting correction factor to 632854883
20070715 04:44:00 (00000400): mDNSPlatformRawTime went backwards by 2 ticks; setting correction factor to 632854885
20070715 05:01:40 (00000400): mDNSPlatformRawTime went backwards by 3 ticks; setting correction factor to 632854888
20070715 05:17:58 (00000400): mDNSPlatformRawTime went backwards by 6 ticks; setting correction factor to 632854894
20070715 05:38:19 (00000400): mDNSPlatformRawTime went backwards by 6 ticks; setting correction factor to 632854900
20070715 06:06:19 (00000400): mDNSPlatformRawTime went backwards by 2 ticks; setting correction factor to 632854902
20070715 06:22:31 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854907
20070715 06:32:11 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854911
20070715 06:38:37 (00000400): mDNSPlatformRawTime went backwards by 5 ticks; setting correction factor to 632854916
20070715 07:11:03 (00000400): mDNSPlatformRawTime went backwards by 2 ticks; setting correction factor to 632854918
20070715 07:26:33 (00000400): mDNSPlatformRawTime went backwards by 4 ticks; setting correction factor to 632854922
20070715 07:30:32 (00000400): mDNSPlatformRawTime went backwards by 1 ticks; setting correction factor to 632854923Dave
Ya, the RTC on the slug is notoriously bad. I need to tune down those error messages, as they are annoying. ðŸ™‚
— Ron

AuthorPosts
The forum ‘General Discussion’ is closed to new topics and replies.