Tivo Time Problem

**sadrake** · 28-07-2005, 07:15 PM

I keep having to run Touch /var/hack/timestamp and then force_index.tcl to get my tivo to work with season passes and tivo suggestions.

This is due to the log error that keeps coming back:
Jul 28 20:58:12 (none) DbGc[165]: DbGc::HandleTriggerWhileIdle -- clock is warped -- re-marking in 300 seconds

Will running this command help and can i run it as a cron job if I put it in a script, which would bring me to the next question what type of script as im not a unix guru.

TiVo [p0] /hack/etc]# TZ=Pacific/Auckland rdate -vs 207.126.98.204
Offset 43200 for timezone NZST, daylight saving is off
Setting local time to Thu Jul 28 21:11:44 2005
[TiVo [p0] /hack/etc]#

**thomson** · 28-07-2005, 08:22 PM

You could create a bourne shell script called "Set_NZ_Time.sh" that contains the following:

Code:

#!/bin/sh

# Stop time warp messages
touch /var/timestamp

# Set the time to time server with appropriate timezone offset
TZ=Pacific/Auckland /hack/bin/rdate -vs 207.126.98.204

Once you have created the file, you will need to make it executable using the chmod command:

Code:

# chmod 755 Set_NZ_Time.sh

The it is just a matter of adding a line to your /hack/etc/crontab file:

Code:

# Synchronise the time on Monday mornings
17 01 * * 1 /hack/bin/Set_NZ_Time.sh > /dev/null 2>&1 &

**maddog** · 28-07-2005, 09:09 PM

I guess its possible that the clock skew could be due to the small battery on the motherboard running low and needing replacement. Im pretty sure I spotted one last time I opened my tivo - not sure if there are any gotchas to worry about in replacing it on a tivo as opposed to on a normal pc but I imagine it is straight forward.

**petestrash** · 29-07-2005, 12:37 AM

Which version of the image are you using?

If it a r1.4 version made before april 19 then there is a known bug.

From:KnownIssuesCurrentImageRelease

Originally Posted by From OzTiVo Twiki

The clock is warped after GS and will not index properly.
This issue has been fixed -- PetesTrash - 19 Apr 2005
wrong ntpdate binary snuck on there >

Ed

This may correct itself when it does its next daily call (I have been too impatient to wait that long).

You can correct this manually by telneting into your TiVo? and running the following commands:
[TiVo [p0] ~]# touch /var/timestamp
[TiVo [p0] ~]# /hack/bin/force_index.tcl

To correct this in older versions download ntpdate and replace the existing file in /bin

The battery is unused while power is applied to the unit and replacing the battery is almost unheard of (and a pain to do).

Peter

**sadrake** · 29-07-2005, 06:12 AM

-rwxr-xr-x 1 0 0 59473 Mar 30 03:09 ntpdate
-rwxr-xr-x 1 0 0 299512 May 24 03:37 ntpdate.orig

I setup my Tivo in June and looking at the bin directory on my Tivo it looks like it has the right one, I comparied the file size to the one in the link and it looks about right. (considering ntpdate.orig is massive in comparison)

Im going to put the script inplace as it will save me having to do it manually when it happens. Thanks Thomson.

**petestrash** · 29-07-2005, 01:35 PM

That is odd behavior since you are using the correct ntpdate.

Thompsons' workaround should work for you, but I would recommend running it more than once a week as some TiVo's do tend to drift.

I would like to find the real reason though, as most people no longer have this issue since the replacement ntpdate was used.

Before using thompsons scripts could you post your otclient log after a daily call and also advise what datestamp is on /var/timestamp before and after the call.

Peter.