PDA

View Full Version : Failed while preparing data



hh75
24-09-2010, 07:02 PM
Hi my tivo has run out of guide data. I can do wget http://210.48.107.133:8000 fine (log below) but when I manually force a phone call from tivo web it fails with failed while preparing data error. What's up?


[TiVo [p0] ~]# wget http://210.48.107.133:8000
--21:58:43-- http://210.48.107.133:8000/
=> `index.html'
Connecting to 210.48.107.133:8000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1,858 [text/html]

0% [ ] 1,858 0.00B/s ETA 00:00

Last-modified header invalid -- time-stamp ignored.
21:58:43 (0.00 GB/s) - `index.html' saved [1858/1858]

petestrash
25-09-2010, 03:04 PM
Have you tried a reboot?

If so, can you attach your tclient log

Peter.

hh75
25-09-2010, 08:25 PM
Tried a reboot and still failed while preparing when I forced new phone call. Here is tclient log
/var/log/tclient
Sep 25 23:25:22 (none) tcphonehome[159]: Log file rotation complete.
Sep 25 23:25:22 (none) comm[159]: CallStatusReporter: Phase: Prepare_Data, Status Failed
Sep 25 23:25:22 (none) comm[159]: CallStatusReporter: sending message "EX|18"
Sep 25 23:25:22 (none) tcphonehome[159]: TClient failed: EX|18
Sep 25 23:25:22 (none) tcphonehome[159]: Sending dialup event, subtype 8, msg EX|18
Sep 25 23:25:22 (none) tcphonehome[159]: setCallStatus called with: Failed state 0
Sep 25 23:25:27 (none) tcphonehome[159]: LastCallAttempt at 1285457084
Sep 25 23:25:27 (none) tcphonehome[159]: setting call status to: Failed
Sep 25 23:25:27 (none) tcphonehome[159]: setting call in progress to 0 (second successCount)
Sep 25 23:25:27 (none) tcphonehome[159]: Setting callActive to 0
Sep 25 23:25:27 (none) comm[159]: CallStatusReporter: sending data changed event 20
Sep 25 23:25:27 (none) tcphonehome[159]: destroying CommGlobals!
Sep 25 23:25:27 (none) tcphonehome[159]: pCommMempool empty
Sep 25 23:25:32 (none) tcphonehome[159]: Setting MCP PhoneHome action: ENABLED

petestrash
25-09-2010, 09:26 PM
The log was rotated, please attach the Otclient log (may need to zip it if it's large).

Peter.

hh75
26-09-2010, 06:42 AM
Yes - here's the Otclient file as attachment - hope not too big

petestrash
26-09-2010, 07:46 PM
You have a few issues. It is not setting the clock with is required for indexing and a successful call, but the download itself seemed to be fine. Then there appears to be some corruption of the existing data, but this may just be because it has not been indexed for a while.

When was the last successful call?
Has anything changed on your network or the TiVo?
How old is the Hard Drive?
can you make a time call manually?

/bin/ntpdate -vb 210.48.107.133

Peter.

hh75
27-09-2010, 03:42 AM
Thanks for helping. Nothing changed on network or Tivo that I know of recently. Last successful call was Sept. 11. Hard drives would be about 7-8 years old I guess. When I try to the ntpdate command I get timezone error


[TiVo [p0] ~]# /bin/ntpdate -vb 210.48.107.133
Our postcode is 02110. No matching timezone for postcode 02110

hh75
28-09-2010, 04:46 AM
Any further thoughts?

Skolink
28-09-2010, 07:55 AM
I know it has always worked until now, but maybe the advice regarding adding the postcode in this thread may be relevant?
http://forums.oztivo.net/showthread.php?2225-Daylight-savings-time-change

hh75
28-09-2010, 05:20 PM
Ok I followed instructions at http://forums.oztivo.net/showthread.php?2225-Daylight-savings-time-change/page3 and edited my postcodezones file to have line 02110 Pacific/Auckland and rebooted. Now when I issue /bin/ntpdate -b -v 132.163.4.103

I get
Our postcode is 02110. Found matching timezone Pacific/Auckland
Offset 46800 for timezone NZDT, daylight saving is 1
Connecting to time server 132.163.4.103
Setting the local time to Tue Sep 28 21:18:02 2010
gmtime gives 110/8/28 21:18:02 [2]
sending to clock 10/09/28 21:18:02 [2]


However, making a daily call still connects, downloads, hangsup and then fails at about 5% while preparing data.

Anyone else have ideas?

Skolink
29-09-2010, 06:07 AM
Failed at about 10% happens during initial Guided Setup if you change postcodes without reimaging. Not sure if that is relevant to your problem though, since it is not an initial call, nor have you changed postcodes.

petestrash
29-09-2010, 11:00 AM
Sorry, have been away.

As I mentioned there appears to be some corruption in the data which is why indexing is failing.

try manually indexing.


[TiVo [p0] ~]# touch /var/timestamp
[TiVo [p0] ~]# /hack/bin/force_index.tcl

Beyond that there are other things we can try to fix corruption, but they may kill the TiVo leaving you to re-image.

Peter.

petestrash
29-09-2010, 11:06 AM
Forgot to mention, leave it at least an hour before trying to make a call.

Peter.

hh75
29-09-2010, 12:10 PM
thanks - will try but do you mean force_index then wait an hour and make another call?

petestrash
29-09-2010, 12:50 PM
Yes, wait at least an hour after the index command before trying a daily call.

Peter.

hh75
29-09-2010, 06:09 PM
Hmm - not sure what cracked it but when i went to look again the phone call had succeeded overnight. Possibly after some time addition of the postcode finally worked - anyway all good now cheers for all the help.

petestrash
29-09-2010, 09:14 PM
Cool.

Peter.