PDA

View Full Version : Guide data not being updated



sdb10_66
21-11-2006, 08:51 AM
Since last Sat, my guide data is not being updated. I have rebooted, done test calls - all OK, but when I make it do a daily call it downloads but fails during the indexing, often up to 40-50% completed before failing?? Please advise what I can do to fix the problem???? Thanks for your help

petestrash
21-11-2006, 02:46 PM
Force a dailycall then post a zipped version of your tclient log so we can see what is happening.

I know that there has been some issues with one of the external time servers for about the last week which can hang daily calls.

Peter.

sdb10_66
25-11-2006, 05:58 PM
Here is the tclient log zipped. Thanks for your help.

sdb10_66
25-11-2006, 06:07 PM
Sorry. forgot to foirce daily call in zip version today. So here is log after making a forced call:

Nov 25 17:59:03 (none) tcphonehome[156]: Log file rotation complete.
Nov 25 17:59:03 (none) comm[156]: CallStatusReporter: Phase: Prepare_Data, Status Failed
Nov 25 17:59:03 (none) comm[156]: CallStatusReporter: sending message "EX|18"
Nov 25 17:59:03 (none) tcphonehome[156]: TClient failed: EX|18
Nov 25 17:59:03 (none) tcphonehome[156]: Sending dialup event, subtype 8, msg EX|18
Nov 25 17:59:03 (none) tcphonehome[156]: setCallStatus called with: Failed state 0
Nov 25 17:59:06 (none) tcphonehome[156]: LastCallAttempt at 1164477018
Nov 25 17:59:06 (none) tcphonehome[156]: setting call status to: Failed
Nov 25 17:59:06 (none) tcphonehome[156]: setting call in progress to 0 (second successCount)
Nov 25 17:59:06 (none) tcphonehome[156]: Setting callActive to 0
Nov 25 17:59:06 (none) comm[156]: CallStatusReporter: sending data changed event 20
Nov 25 17:59:06 (none) tcphonehome[156]: destroying CommGlobals!
Nov 25 17:59:06 (none) tcphonehome[156]: pCommMempool empty
Nov 25 17:59:12 (none) tcphonehome[156]: Setting MCP PhoneHome action: ENABLED

petestrash
25-11-2006, 07:57 PM
Actually the daily call must have worked as the log has been rotated.

Post a zip of the otclient instead.

Peter.

sdb10_66
26-11-2006, 08:12 AM
otclient log as requested. Thanks for your help Peter.

petestrash
26-11-2006, 11:38 AM
The download is fine, but there appears to be corruptoin in your database.

try running mfscheck -fix from a telnet session. then once the TiVo reboots itself force a daily call. Nore: the TiVo will appear to freeze while mfscheck is running.

Peter.

sdb10_66
26-11-2006, 06:32 PM
where do I find mfscheck???

Darren King
26-11-2006, 07:43 PM
First you need to telnet into you TiVo. There is an explanation of how to achieve this here: http://minnie.tuhs.org/twiki/bin/view/Howto/TelnetToYourTiVo

Then once you have read that type the command Peter suggested.

sdb10_66
27-11-2006, 08:52 AM
[TiVo [p0] ~]# Couldn't CreateSharedMemoryFile() /var/tmp//fsmem.mpkey -- check permissions
> FsInit failed: 0x11001
> [TiVo [p0] ~]#
> [TiVo [p0] ~]#

sdb10_66
27-11-2006, 08:52 AM
Here is the response above

sdb10_66
27-11-2006, 09:13 AM
Rebooted tivo, forced to make update call, failed the first time at around 8%, then 5% on the second attempt, no change.....

petestrash
27-11-2006, 09:16 AM
the command you gave didn't work, because of the error you recieved.

Try it again now. If you still get the same message then delete the fsmem file by typing

rm /var/tmp//fsmem.mpkey

and run the mfscheck -fix command again.

Peter.

sdb10_66
27-11-2006, 11:08 AM
mfscheck scan ends
mfscheck: 0 fatal errors, 4 severe errors, 0 warnings.

You must manually restart the EventSwitcher

sdb10_66
27-11-2006, 11:09 AM
Here is the result? Do I reboot and force another daily call, or what do I do??

Thanks again for all your help.

sdb10_66
27-11-2006, 12:01 PM
Went back and read over initial advice, so after rebooting have forced daily call and succeeded 100% updated so thanks Peter for all your help. really appreciated. One last thing, should i do anything about the 4 severe errors reported back in the mfscheck above?? And how do I restart Eventswitcher?? or is that the daily call?? Thanks again.

petestrash
27-11-2006, 01:32 PM
mfscheck has fixed the errors and your reboot has restarted the eventswitcher.

Your good to go.

Peter

sdb10_66
27-11-2006, 07:02 PM
Thanks again, your efforts are most appreciated........cheers

Phil_C
01-12-2006, 05:04 PM
Hello All
I am having a similar problem to what sdb10_66 had except I cannot get past the "SettingUP" stage in the daily call. If I use "Make Test Call" then it works fine but "Make Daily Call Now" does not. I have tried the steps mentioned in this thread but had no effect. Does any one know what could be causing the problem?

Regards

Phil

petestrash
01-12-2006, 05:42 PM
Reboot, force a new daily call then post a zipped copy of either the otclient log or tclient log (whichever has the info from your call).

Also what revision of the OzTiVo software are you running ?

Peter.

Phil_C
01-12-2006, 06:38 PM
Hello Peter
The call and updates window says the software version is 3.0-01-1-000
But when the Tivo restarts it reports a software version 3.0 release 1.4.

I have uploaded todays contents of the tclient. If you need more of the file then let me know and I will upload the complete file which dates back to Nov 14.

Regards

Phil

petestrash
04-12-2006, 03:09 AM
Sorry for the delay, the forums didn't email me to say you have replied.

Turns out I have 24 posts waiting to be answered.

Telnet into your TiVo and execute the command /hack/bin/fixtivotime

I'm not positive it was included on r1.4, if not then execute these three lines:
touch /var/timestamp
ntpdate -v -b 129.6.15.29 132.163.4.103 192.43.244.18
/tvbin/settime -rtc

Then try a daily call again, and post the new tclient.log if it still doesn't work.

Phil_C
04-12-2006, 07:39 PM
Hello Pete
Thanks for the reply. I did as you said and it had no effect. The daily call still will not get past SettingUp.

Here is the trimmed text from the tclient. All I did was do a reboot and then attempt to make a daily call.

I am about ready to give up on this and reimage the drive. I will have to use the older image though as I don't have a working cd burner at the moment.

This all started when my LAN switch packed it in and the Tivo could not connect for a couple of days. It was working perfectly before the switch died.

Regards

Phil

Dec 4 20:32:09 (none) tcphonehome[129]: TCphonehome active
Dec 4 20:32:09 (none) tcphonehome[155]: cleaning /Setup
Dec 4 20:32:10 (none) tcphonehome[155]: Fetching /SwSystemACTIVE/Name
Dec 4 20:32:10 (none) tcphonehome[155]: Last Call Status Was: 'Succeeded' (size 9)
Dec 4 20:32:10 (none) tcphonehome[155]: Last Call Status Will Be: Succeeded
Dec 4 20:32:10 (none) tcphonehome[155]: setCallStatus called with: Succeeded state 0
Dec 4 20:32:10 (none) tcphonehome[155]: LastCallAttempt at 1165264069
Dec 4 20:32:10 (none) tcphonehome[155]: status is 'Succeeded' == 'Succeeded'
Dec 4 20:32:10 (none) tcphonehome[155]: setting last success time to 1165264069
Dec 4 20:32:10 (none) tcphonehome[155]: setting call status to: Succeeded
Dec 4 20:32:11 (none) tcphonehome[155]: setting call in progress to 0 (second successCount)
Dec 4 20:32:11 (none) tcphonehome[155]: Setting callActive to 0
Dec 4 20:32:11 (none) tcphonehome[155]: PhoneHome: statusValue = <0>, getResult = <0>
Dec 4 20:32:11 (none) tcphonehome[155]: /State/Avalanche LastStatus was <0> and getResult was <0>, changing to unknown
Dec 4 20:32:11 (none) tcphonehome[155]: finished cleaning /Setup
Dec 4 20:32:11 (none) tcphonehome[155]: About to execute: /sbin/ifconfig eth0 2>&1
Dec 4 20:32:11 (none) tcphonehome[155]: Command Output: eth0 Link encap:Ethernet HWaddr 00:0B:AD:10:10:10
Dec 4 20:32:11 (none) tcphonehome[155]: Command Output: inet addr:10.0.0.5 Bcast:10.0.0.255 Mask:255.255.255.0
Dec 4 20:32:11 (none) tcphonehome[155]: Command Output: UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Dec 4 20:32:11 (none) tcphonehome[155]: Command Output: RX packets:10 errors:0 dropped:0 overruns:0 frame:0
Dec 4 20:32:11 (none) tcphonehome[155]: Command Output: TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Dec 4 20:32:11 (none) tcphonehome[155]: Command Output: Interrupt:29
Dec 4 20:32:11 (none) tcphonehome[155]: Command Output:
Dec 4 20:32:11 (none) tcphonehome[155]: Command succeeded
Dec 4 20:32:11 (none) tcphonehome[155]: NOT Using debug ethernet
Dec 4 20:32:11 (none) tcphonehome[155]: Error statting file /var/log/http: No such file or directory (errno=2)
Dec 4 20:32:11 (none) tcphonehome[155]: Error statting file /var/log/Ohttp: No such file or directory (errno=2)
Dec 4 20:32:11 (none) tcphonehome[155]: Timesync is within the past 5 days... all is well
Dec 4 20:32:11 (none) tcphonehome[155]: getting LastSuccessfulCall
Dec 4 20:32:11 (none) tcphonehome[155]: ReschedCall: reason = 6, secSinceLast = 1764002, numFails = 0
Dec 4 20:32:11 (none) tcphonehome[155]: Last call was 1764002 secs. ago
Dec 4 20:32:11 (none) tcphonehome[155]: Adjusting secSinceLast within 24 hrs
Dec 4 20:32:11 (none) tcphonehome[155]: setting next attempt at 1165326251 (Tue Dec 5 13:44:11 2006 )
Dec 4 20:32:11 (none) tcphonehome[155]: ReschedCall(6, 36002) in 1032 min
Dec 4 20:32:11 (none) PhoneAction[155]: PhoneAction 2 register complete timeout 61920
Dec 4 20:32:11 (none) PhoneAction[155]: Register Complete: Next call should happen at Tue Dec 5 13:44:11 2006
Dec 4 20:32:11 (none) tcphonehome[155]: called getTZ
Dec 4 20:32:12 (none) WatchdogAction[155]: WatchdogAction register complete
Dec 4 20:33:43 (none) tcphonehome[155]: getting /State/GeneralConfig/Complete
Dec 4 20:33:43 (none) tcphonehome[155]: Setup not finished, skipping call

petestrash
04-12-2006, 08:51 PM
please zip and post the entire tclient log and confirm your TiVo's IP is 10.0.0.5

Peter

Phil_C
05-12-2006, 03:18 AM
Hello Pete
Sorry but that is the entire tclient log. The other file you mentioned the otclient log's last entry is the 14th November.

Yes 10.0.0.5 is the correct IP address for the Tivo.

I really don't want to waste any more of your time with this. There is nothing on the Tivo that really needs saving so I can simply re-image the drive unless you think there is some underlying problem there that will affect the new image:)

Regards

Phil

petestrash
05-12-2006, 11:59 AM
You could still try mfscheck -fix as suggested earlier in this thread.

If you get an error msg about fsmem, then just delete it.

rm /var/tmp//fsmem.mpkey

and run the mfscheck -fix command again.

Peter.

Phil_C
05-12-2006, 05:27 PM
Hello Peter
I did try the mfscheck earlier and it returned an error. Deleting the file as you suggested allowed mfscheck to complete but it did not change anything. I have since upgraded to the 1.6.2 image and everything is now working fine. (Except for the IR codes but thats another matter)

Thanks again for your help with this problem.

Regards

Phil

petestrash
05-12-2006, 10:19 PM
I'm glad it's working for you.

Peter.