Page 4 of 7 FirstFirst ... 23456 ... LastLast
Results 31 to 40 of 69

Thread: Daily call not working

  1. #31
    Join Date
    Feb 2007
    Location
    Melbourne. Vic
    Posts
    79
    This is all that's in the tclient.log, it seems to have deleted everything else, and it's randomly deleted shows that have been (manually) recorded over the last few weeks..

    Melissa.

    Jun 16 09:30:48 (none) tcphonehome[182]: Log file rotation complete.
    Jun 16 09:30:48 (none) tcphonehome[182]: TClient success
    Jun 16 09:30:48 (none) comm[182]: CallStatusReporter: Phase: Prepare_Data, Status Succeeded
    Jun 16 09:30:48 (none) comm[182]: CallStatusReporter: sending message "EX|49"
    Jun 16 09:30:48 (none) tcphonehome[182]: Sending dialup event, subtype 7, msg Succeeded
    Jun 16 09:30:48 (none) tcphonehome[182]: setCallStatus called with: Succeeded state 0
    Jun 16 09:30:48 (none) tcphonehome[182]: LastCallAttempt at -995453476
    Jun 16 09:30:48 (none) tcphonehome[182]: last attempt in future; set it to now: -995466552
    Jun 16 09:30:48 (none) tcphonehome[182]: status is 'Succeeded' == 'Succeeded'
    Jun 16 09:30:48 (none) tcphonehome[182]: setting last success time to -995466552
    Jun 16 09:30:48 (none) tcphonehome[182]: setting call status to: Succeeded
    Jun 16 09:30:48 (none) tcphonehome[182]: setting call in progress to 0 (second successCount)
    Jun 16 09:30:48 (none) tcphonehome[182]: setting LastSuccessPgdCall to -995466552
    Jun 16 09:30:48 (none) tcphonehome[182]: Setting callActive to 0
    Jun 16 09:30:48 (none) comm[182]: CallStatusReporter: sending data changed event 20
    Jun 16 09:30:48 (none) tcphonehome[182]: destroying CommGlobals!
    Jun 16 09:30:49 (none) tcphonehome[182]: pCommMempool empty
    Jun 16 09:30:49 (none) tcphonehome[182]: Setting MCP PhoneHome action: ENABLED

  2. #32
    Join Date
    Apr 2004
    Location
    Perth, Western Australia
    Posts
    3,037
    Well according to that log.

    Your last call home was a success. This is why it has been cleared.

    Try posting your otclient.log it will show the previous attempts.

    Also have you updated your TiVo recently? run oztivo_update -y.

    There have been updates to ntpdate which was also causing hanging issues.

    Peter.
    Please search this forum and our Website for your TiVo questions before starting a new thread. Thanks!

  3. #33
    Join Date
    Feb 2007
    Location
    Melbourne. Vic
    Posts
    79
    Hi Peter,
    Thanks for all your help so far, it is getting closer.... I've attached otclient.log and results of update_oztivo -y. Also, i now get 'upcoming' programs on the tivo, but no actual guide data and the upcoming program doesn't change..

    Melissa.
    Attached Files Attached Files

  4. #34
    Join Date
    Apr 2004
    Location
    Perth, Western Australia
    Posts
    3,037
    It seems like a proxy issue still, which is effecting slices.

    Are you still testing with the TiVo connected by cable, not wireless ?

    if yes, can you please post the content of your /var/hack/etc/emuProxyZA.conf

    Peter
    Please search this forum and our Website for your TiVo questions before starting a new thread. Thanks!

  5. #35
    Join Date
    Feb 2007
    Location
    Melbourne. Vic
    Posts
    79
    I've got it set up wireless. But here's /var/hack/etc/emuProxyZA.conf anyway.

    # emuProxyZA.conf

    # the serverip is specified in /etc/oztivo.conf
    # any serverip specified here will be ignored
    # modify rc.sysinit.author if you wish to change the emulator address
    # serverIP=131.244.9.101

    forceUpdate=0
    raw=1

    # all recognised parameters are listed below:
    # taken from http://tivoza.nanfo.com/forum/viewtopic.php?t=180#1268 2/7/06

    # debug: 0=No debug, 1=Debug info, 2=Detailed debug info
    # serverIP: Guide server DNS or IP address, default: 204.176.49.2 (TiVo Inc)
    # serverPort: Guide server port, default: 80
    # localPort: emuProxyZA IP address, default: 0.0.0.0
    # localIP: emuProxyZA port, default: 8000
    # DNSconf: File containing the DNS nameserver, default: '/etc/resolv.conf'
    # proxyIP: Proxy server IP or DNS address
    # proxyPort: Proxy server port
    # proxyUser: Username for proxy authentication
    # proxyPassword: Password for proxy authentication
    # raw: 1=Raw send, don't "clean" requests to mlog.cgi or HServer.cgi, 2=Raw send without making any unspecified changes to the requests
    # onScreen: Display the file being requested on screen via osd_cons
    # debugPath: Path to save request & response trace files
    # saveRequests: Save request trace files
    # saveResponses: Save response trace files
    # forceUpdate: 0=No change, 1=Force request to download all new guide slices, 2: Only download latest slices
    # timeOffset: Offset returned NTP time by OffsetAmount minutes
    # ntpIP: NTP (time server) to use
    # guideDays: Maximum guide days you would like to download (your provider needs to support this function for it to work)
    # weekDays: The days of the week you wish to download guide data, list each day from 0 to 6 (0 is Sunday). i.e. to download on Tuesdays and Fridays use: -w 25
    # locationID: Change your Postal Code
    # tcInfo: Fix the submitted TCINFO, so it sends the correct server connection settings not emuProxyZA settings
    # urlbase: Download slices direct from server, don't go via emuProxyZA
    proxyIP=210.15.254.253
    proxyPort=8080

  6. #36
    Join Date
    Feb 2007
    Location
    NSW
    Posts
    108
    It seems strange that there are so many problems. Is anyone else using the same ISP?
    (I suggested the proxy settings in the emuProxyZA.conf , which I found on the ISP website)

  7. #37
    Join Date
    Apr 2004
    Location
    Perth, Western Australia
    Posts
    3,037
    now that you have updated the TiVo, Comment out the 2 lines Matt suggested in /var/hack/etc/emuProxyZA.conf

    Reboot.

    run

    /bin/ntpdate -b 132.163.4.103 192.43.244.18 129.6.15.29

    to get your clock correct, then force a daily call. Once complete post your tclient.log if unsucessful or otclient.log if successful.

    Peter.
    Please search this forum and our Website for your TiVo questions before starting a new thread. Thanks!

  8. #38
    Join Date
    Feb 2007
    Location
    Melbourne. Vic
    Posts
    79
    I removed the 2 lines in /var/hack/etc/emuProxyZA.conf and rebooted It didn't work unfortunately, it went to 'Failed. Service unavailable' The tclient.log results are attached. The time/date is still incorrect also?

    Not sure what i was meant to see, but this was the result..
    [TiVo [p0] ~]# /bin/ntpdate -b 132.163.4.103 192.43.244.18 129.6.15.29
    [TiVo [p0] ~]#

    Cheers,
    Melissa.
    Attached Files Attached Files

  9. #39
    Join Date
    Apr 2004
    Location
    Perth, Western Australia
    Posts
    3,037
    Ok this proves that the newer emuproxyza still cannot get past your ISP's proxy on it's own.

    You shouldn't have seen any response to the ntpdate command, but it should have worked.

    Please return the two proxy lines, as least these are getting you closer.

    Reboot the TiVo.

    Now try ntpdate again as below, this adds -v so you will see what happens:
    /bin/ntpdate -b -v 132.163.4.103 192.43.244.18 129.6.15.29

    Clear all the current otclient log with:
    cat /dev/null > /var/log/otclient.log

    Now try a daily call again and post the tclient log again.

    Peter.

    PS who is your ISP?
    Please search this forum and our Website for your TiVo questions before starting a new thread. Thanks!

  10. #40
    Join Date
    Feb 2007
    Location
    NSW
    Posts
    108
    PS who is your ISP?
    A previous post says it's Netspace. That's how I found the proxy info.

    I've just been looking at the WiKi and came across this page: http://www.tuhs.org/twiki/bin/view/N...entProxyServer

    Maybe option 3 might work?

    Code:
    Modify /etc/tclient.conf so that instead of pointing to minnie:80 (The line is 127::131.244.9.101:80:::) it reads:
    
    127::202.63.38.134:8000:::
    But you are currently using emuproxyZA, so instead change the line
    Code:
    127::127.0.0.1:8000:::
    to
    Code:
    127::202.63.38.134:8000:::

Similar Threads

  1. S1 now failing to connect for daily call or test call
    By peter in forum Question and Answer Forum
    Replies: 7
    Last Post: 11-11-2009, 06:15 PM
  2. Daily Call Required but not working
    By raffi in forum Question and Answer Forum
    Replies: 2
    Last Post: 16-06-2009, 12:37 AM
  3. Daily call not working
    By MelissaH in forum Question and Answer Forum
    Replies: 40
    Last Post: 13-02-2008, 04:44 PM
  4. Daily Call no longer working
    By tatch76 in forum New Zealand TV Guide Issues
    Replies: 9
    Last Post: 09-10-2007, 07:37 PM
  5. Daily call: "Failed. Call Interrupted"
    By leanne in forum TV Guide Issues
    Replies: 4
    Last Post: 18-07-2005, 06:07 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •