This is the only reference I have found to a similar issue as yours.
You could try the 3rd post suggestions there and see if that works. We will take it from there..
http://archive.tivocommunity.com/tiv...threadid=74036
Printable View
This is the only reference I have found to a similar issue as yours.
You could try the 3rd post suggestions there and see if that works. We will take it from there..
http://archive.tivocommunity.com/tiv...threadid=74036
Sounded a similar situation in that I have three tivos here, only one misbehaving.
OK have done:
cd /var/log
touch xxxx
cp xxxx tivoLog.prv
cp xxxx tivoLog.prv.gz
tivoLog.prv.gz.bfg does not exist so could not do. Might be a proprietary encryted file bypassed in our units?
Make Daily Call failed again with same basic message of Failed...
Make Test Call Now worked fine
Make Daily Call Now seemed to work, it spent ages setting the clock as it does......and it still is, seems like it is downloading the whole lot of data again. Bed time! I hope that helps?
8 hours later it is still setting the clock! ok Reboot.
Using Remote Test EPG OK
Using Remote EPG Download EPG OK (Wahoo!)
I think there could be two bugs here.
1) The main problem whatever that is!
2) Possible confounding time server not responding. This was considered around the new year, however I can't find the references. I didn't hurry to apply the fix as I was not convinced the NZ architecture was fully compatible and I did not get around to test it - not being an easy thing to test! Anyone got the thread link?
Incidentally it seems the xxxx exercise is merely one in clearing the logs. I now see one can also do this using TWP from the log page! (Quicker and easier!)
can you look through the tclient or otclient log to find the lines which mention ntpdate as this is where the clock is being set and post here.
Peter.
tclient is now empty.
from current otclient:
02/06:10:47:15: /tvbin/TClient: timeService: /bin/ntpdate -b 210.48.107.133
02/06:10:47:15: /tvbin/TClient: sequenceCookie: 12345678
02/06:10:47:15: /tvbin/TClient: inventoryFile:
02/06:10:47:15: /tvbin/TClient: noPrivBackhaul: 1
02/06:10:47:15: /tvbin/TClient: serviceState: 3
02/06:10:47:15: /tvbin/TClient: stateExpiration: 0
02/06:10:47:15: /tvbin/TClient: swSystemName: 2.5.5-01-1-023
02/06:10:47:15: /tvbin/TClient: infoCode:
02/06:10:47:15: /tvbin/TClient: tcdMessage:
02/06:10:47:15: /tvbin/TClient: globalMessages:
02/06:10:47:15: /tvbin/TClient: keyServer:
02/06:10:47:15: /tvbin/TClient: forceBackhaul: 0
02/06:10:47:15: /tvbin/TClient: publicLogFilter:
02/06:10:47:15: /tvbin/TClient: dbLoadOrder: PG.*
02/06:10:47:15: /tvbin/TClient: regenToken: 0
02/06:10:47:15: /tvbin/TClient: backhaulDataOn: 0
02/06:10:47:15: /tvbin/TClient: personalDataOn: 0
02/06:10:47:15: /tvbin/TClient: dataGroupList:
02/06:10:47:15: /tvbin/TClient: End SvrResp =======================
02/06:10:47:15: /tvbin/TClient: Connect/POST(s) succeeded
02/06:10:47:15: /tvbin/TClient: Executing HTTP GET: /tvbin/http_get -U http://210.48.107.133:8000/static/He...C-678-v1.slice -D /var/packages -T 02300006023E322 -C 1170758794 -d
02/06:10:47:15: /tvbin/TClient: TFA is 0
02/06:10:47:15: /tvbin/TClient: Not overwriting 1 with 0
02/06:10:47:15: /tvbin/TClient: process411 returned: 0
02/06:10:47:16: /tvbin/TClient: updateStatus: In Progress ST| 34 26
02/06:10:47:16: /tvbin/TClient: SendDialupEvent 30 9 ST|34
02/06:10:47:16: /tvbin/TClient: ServiceInfo DataGroupList attribute was not sent by the service
02/06:10:47:16: /tvbin/TClient: ServiceInfo PublicLogFilter attribute was not sent by the service
02/06:10:47:16: /tvbin/TClient: updateStatus: In Progress ST| 34 26
02/06:10:47:16: /tvbin/TClient: SendDialupEvent 30 9 ST|34
02/06:10:47:16: /tvbin/TClient: Setting NoPrivateBackhaul to 1
02/06:10:47:16: /tvbin/TClient: starting backhaul: 1
02/06:10:47:16: /tvbin/TClient: Setting ServiceInfo ForceBackhaul attribute to 0
02/06:10:47:16: /tvbin/TClient: starting backhaul2
02/06:10:47:16: /tvbin/TClient: starting backhaul3
02/06:10:47:16: /tvbin/TClient: Executing HTTP POST: /tvbin/http_post /var/tmp/syslog.gz http://210.48.107.133:8000/tivo-service/acceptfile.cgi OFF ON
02/06:10:47:16: /tvbin/TClient: updateStatus: In Progress ST| 35 21
02/06:10:47:16: /tvbin/TClient: SendDialupEvent 30 9 ST|35
02/06:10:47:16: /tvbin/TClient: processing timeService: /bin/ntpdate -b 210.48.107.133
02/06:10:47:16: /tvbin/TClient: parsed ntpdate args of -b 210.48.107.133
02/06:10:47:16: /tvbin/TClient: about to run: /bin/ntpdate -b 210.48.107.133
02/06:10:54:50: /tvbin/TClient: updateStatus: In Progress DL| 36 23
02/06:10:54:50: /tvbin/TClient: SendDialupEvent 30 9 DL|36
02/06:10:54:50: /tvbin/TClient: updateStatus: In Progress DL| 38 16
02/06:10:54:50: /tvbin/TClient: SendDialupEvent 30 9 DL|38
The previous otclients are already posted if that helps at all?
This doesn't appear to be the one which got stuck on setting the time. But it is correctly contacting orac for the time update.
You might want to check with DJC if anyone else is having time issues. We (OzTiVo) are using a newer version of ntpdate which handles timeout better. it may be worth trying as a workaround.
This still doesn't find the cause of your problem, but with both these issues being timeouts from the emulator it looks like a networking issue. You also appear to be the only one with this problem since Dec. It may be worth changing your turbonet setting to failsafe using nic_config_tivo.
Peter.