Failed while preparing data.....AGAIN.

[DavidClarke]

Lets keep on it, can you do the same and post but use the -et flag on cat

cat -et /etc/postcodezones

[TiVo [p3] ~]# cat -et /etc/postcodezones
# A list of TiVo postcodes and the timezones that they represent$
# Two columns, separated by one tab only.$
#$
00800^IAustralia/Darwin$
02000^IAustralia/Sydney$
02600^IAustralia/Sydney$
03000^IAustralia/Melbourne$
04000^IAustralia/Brisbane$
05000^IAustralia/Adelaide$
06000^IAustralia/Perth$
07000^IAustralia/Hobart$
$
# New Zealand$
02112 Pacific/Auckland$
02113 Pacific/Auckland$
02114 Pacific/Auckland$
02115 Pacific/Auckland$
02116 Pacific/Auckland$
[TiVo [p3] ~]#


ARRRRGGGHHHH!!!!!! Memo to self to never cut and past into JOE...

[DavidClarke]

Now:

[TiVo [p3] ~]# cat -et /etc/postcodezones
# A list of TiVo postcodes and the timezones that they represent$
# Two columns, separated by one tab only.$
#$
00800^IAustralia/Darwin$
02000^IAustralia/Sydney$
02600^IAustralia/Sydney$
03000^IAustralia/Melbourne$
04000^IAustralia/Brisbane$
05000^IAustralia/Adelaide$
06000^IAustralia/Perth$
07000^IAustralia/Hobart$
$
# New Zealand$
02112^IPacific/Auckland$
02113^IPacific/Auckland$
02114^IPacific/Auckland$
02115^IPacific/Auckland$
02116^IPacific/Auckland$
[TiVo [p3] ~]#

AND... WAIT FOR IT>>>...

[TiVo [p3] ~]#
[TiVo [p3] ~]# /bin/ntpdate -v -v -v -s 210.48.107.133
/bin/ntpdate: invalid option -- s
Our postcode is 02113. Found matching timezone Pacific/Auckland
Offset 43200 for timezone NZST, daylight saving is 0
Connecting to time server 210.48.107.133
Setting the local time to Wed May 31 20:32:35 2006
gmtime gives 106/4/31 20:32:35 [3]
sending to clock 06/05/31 20:32:35 [3]
[TiVo [p3] ~]#

Where do I send the beer???????? Mate!

[Muzza]

I guess I just wait and see if the "warped clock" returns now over the next couple of days??

If not......thank you all so much for your help!!!!

Happiness is....a working TiVo!

[DJC]

Welcome.

Should be right I think. I've never had a warped clock.

Cheers/DJC

[DavidClarke]

Thanks guys, have #'d out the CRON file I wrote to :

00 06 * * * (touch /var/timestamp; /hack/bin/force_index.tcl) &

Shouldn't be required and was at best a work around to bandaid the problem but sometimes messed up the TiVo suggestions for a day.

Appreciate the help, the 1.4 image I used was quite early and obviously has some issues...

[DJC]

Appreciate the help, the 1.4 image I used was quite
early and obviously has some issues...

I don't think there was an image problem, ntpdate was the correct version.

It's been standard practise for NZ'ers to setup postcodezones on images prior to the release of the NZ specific images.

This is pointed out on the nztivo wiki, in the 'setting timesync up for New Zealand' section but, it is a bit (a lot) dated now.

[petestrash]

AKL being missing from the tz file is certainly an issue.

I would like to know how have the affected units been running for months, without this coming up earlier.

Peter.

[Muzza]

I got up this morning to find that TiVo had recorded one of my season passes and also 2 "TiVo Suggestions" during the night. It's been a long time since I've had that!!!

Hooray and thanks again for your help everyone!!!

[NZMarke]

Hi all,

I've been lurking on this thread waiting to see if any solutions emerged. And they have. Like the others, my problem was with the postcodes file. But unlike them I had actually added the AKL postcodes in - 'cause the link in the instructions that links to the Auckland postcode file is actually broken .. so I manually added it using vi.

What I hadn't done though was realise that there was a tab (not a space) between the code and the location. I'd used a space ... and it doesn't like it. Re-edited the file to introduce a tab, and ntpdate now works happily as.

In reply to PetesTrash question "why have affected units been running without problems?" A couple of thoughts/points spring to mind :
1) I thought that mostly the people who had incorrect Postcode files WERE actually experiencing the problem. So they haven't been running without problems ..
2) Perhaps some units are better than others at maintaining their time settings and not drifting?
3) Maybe - like me - some people had actually manually added the relevant entries to the postcodes file?

Anyway - thanks again to everyone for the trouble-shooting. And hopefully that's goodbye to the clock-warping saga!!??

I can see Muzza is a happy camper!

Cheers

Mark

[petestrash]

In reply to PetesTrash question "why have affected units been running without problems?" A couple of thoughts/points spring to mind :
1) I thought that mostly the people who had incorrect Postcode files WERE actually experiencing the problem. So they haven't been running without problems ..

According to Muzza's posts, both his and his in-law's TiVo were working fine, and only just started playing up.

2) Perhaps some units are better than others at maintaining their time settings and not drifting?

Not an issue, the timestamp file still needs to be updated to stop the TiVo recognising the timewarp and stopping the season passes from indexing. So, regardless of how well the TiVo actually keeps time, if you don't touch /var/timestamp the TiVo will recognise a timewarp.

3) Maybe - like me - some people had actually manually added the relevant entries to the postcodes file?

I imagine most people followed the NZ instructions , but looking though the old posts the timezone file has been missing from the nztivo site since before August last year. So it would be a good idea for it to be re-attached.

My guess is that a lot of people have just added the touch command to a cron job as others have recommended in different threads, without fixing the actual cause of the clock warp or stopping the TiVo's time from drifting.

Glad to hear it's working.

Peter.