Failed. Service Unavailable Part 2

[Tuatara]

Obviously we're not all having this problem, and it would appear perhaps it's sporadic for some people. I wonder if those of us affected can find something in common that might indicate the cause of the problem.

For me, calls are failing on all three emulators (Ed's, which I've been using up till now, and both port 80 and 8000 on Orac). I don't think I've had a successful call all week.

I've tried it with emuProxy and, for the sake of completeness, without. I can load the Orac home page in a web browser. I haven't, however, tried looking at the traffic when TiVo attempts a daily call.

My ISP (Iconz) promises that nothing has changed with proxies, etc. My own router setup hasn't changed. My TiVo hasn't been tinkered with for several weeks. Although Telecom are apparently about to "grandfather" my particular Jetstream plan, Iconz says that hasn't happened yet.

I'm probably going to reimage anyway, because the beta image I used turned out to have a bug that created only a 64MB swap partition, which is a bit small for my TiVo, which has 240GB of disk space. But before I do that is there any debugging data I can share that might help pin down the problem?

Are others who are having this problem also using the beta image? I know Tony is using a beta image, but doesn't have the small-swapfile problem, because I helped him do the guided setup.

Cheers
Matt

(PS my home router has just dropped off the net so I can't try the new emulator on 8888, but I will when I get home this afternoon.)

[tonys]

Don't think I'll rush home and delete all my current guide data this afternoon then!

[DJC]

(PS my home router has just dropped off the net so I can't try the new emulator on 8888, but I will when I get home this afternoon.)

Excellent, I'm keen to see the result of this. Have deleted yesterdays slice so this emulator is still a one slicer. Which is what the majority who have not had network issues see on a daily basis from the main emulators.

[slangnz]

Hiya.

Mine has now dropped off as well. My ISP is Orcon

/etc/tclient config:
127::64.151.65.200:80:::

Software version: 3.0-01-1-000

Had been working fine until recently - not sure when the daily update started failing, but I've run out of guide info now.

Doing some low level tcp diagnostics yields:

Request going out:

POST /tivo-service/mlog.cgi HTTP/1.0
Content-Length: 2391

tclient_hangup TCD_ID=000134922972058 CALL_ID=1124832459 TIME=1124832566 CODE=0
tclient_ticket TCD_ID=000134922972058 CALL_ID=1124832459 TIME=1124832566 STATUS=None TICKET=None VALUE=None
tclient_result TCD_ID=000134922972058 CALL_ID=1124832459 TIME=1124832575 STATUS=Succeeded CODE=1
ird_id TCD_ID=000134922972058 CALL_ID=1124928792 TIME=1124928819 ID=53972058
tcd_driveid TCD_ID=000134922972058 CALL_ID=1124928792 TIME=1124928819 HDA=3LJ2JHVM HDB=Unknown
tclient_hangup TCD_ID=000134922972058 CALL_ID=1124928792 TIME=1124928822 CODE=65535
tclient_result TCD_ID=000134922972058 CALL_ID=1124928792 TIME=1124928822 STATUS=Failed CODE=14
ird_id TCD_ID=000134922972058 CALL_ID=1124936395 TIME=1124936427 ID=53972058
tcd_driveid TCD_ID=000134922972058 CALL_ID=1124936395 TIME=1124936427 HDA=3LJ2JHVM HDB=Unknown
tclient_hangup TCD_ID=000134922972058 CALL_ID=1124936395 TIME=1124936430 CODE=65535
tclient_result TCD_ID=000134922972058 CALL_ID=1124936395 TIME=1124936430 STATUS=Failed CODE=14
ird_id TCD_ID=000134922972058 CALL_ID=1124982301 TIME=1124982339 ID=53972058
tcd_driveid TCD_ID=000134922972058 CALL_ID=1124982301 TIME=1124982339 HDA=3LJ2JHVM HDB=Unknown
tclient_hangup TCD_ID=000134922972058 CALL_ID=1124982301 TIME=1124982342 CODE=65535
tclient_result TCD_ID=000134922972058 CALL_ID=1124982301 TIME=1124982343 STATUS=Failed CODE=14
ird_id TCD_ID=000134922972058 CALL_ID=1125037424 TIME=1125037444 ID=53972058
tcd_driveid TCD_ID=000134922972058 CALL_ID=1125037424 TIME=1125037444 HDA=3LJ2JHVM HDB=Unknown
tclient_hangup TCD_ID=000134922972058 CALL_ID=1125037424 TIME=1125037447 CODE=65535
tclient_result TCD_ID=000134922972058 CALL_ID=1125037424 TIME=1125037448 STATUS=Failed CODE=14
ird_id TCD_ID=000134922972058 CALL_ID=1125064491 TIME=1125064520 ID=53972058
tcd_driveid TCD_ID=000134922972058 CALL_ID=1125064491 TIME=1125064520 HDA=3LJ2JHVM HDB=Unknown
tclient_hangup TCD_ID=000134922972058 CALL_ID=1125064491 TIME=1125064523 CODE=65535
tclient_result TCD_ID=000134922972058 CALL_ID=1125064491 TIME=1125064524 STATUS=Failed CODE=14
ird_id TCD_ID=000134922972058 CALL_ID=1125064677 TIME=1125064697 ID=53972058
tcd_driveid TCD_ID=000134922972058 CALL_ID=1125064677 TIME=1125064697 HDA=3LJ2JHVM HDB=Unknown
tclient_hangup TCD_ID=000134922972058 CALL_ID=1125064677 TIME=1125064701 CODE=65535
tclient_result TCD_ID=000134922972058 CALL_ID=1125064677 TIME=1125064701 STATUS=Failed CODE=14

Reply:
HTTP/1.1 404 Not Found
Date: Fri, 26 Aug 2005 02:03:24 GMT
Server: Apache/1.3.33 (Unix) (Gentoo/Linux) PHP/4.3.11 mod_gzip/1.3.26.1a
Connection: close
Content-Type: text/html; ch****t=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>404 Not Found</TITLE>
</HEAD><BODY>
<H1>Not Found</H1>
The requested URL /tivo-service/mlog.cgi was not found on this server.<P>
<P>Additionally, a 404 Not Found
error was encountered while trying to use an ErrorDocument to handle the request.
<HR>
<ADDRESS>Apache/1.3.33 Server at www.pbp.net Port 80</ADDRESS>
</BODY></HTML>

Looks to me like a problem with the webserver?

I've got another tivo that is located in a different city that I look after that is likely to have the same problem, except I can't easily manage/change the config...

Hope this info helps someone track the problem down.

Cheers -

[DJC]

Yep. I'd agree, ed's emulator looks belly up for the moment.

The IP still looks right, his domain resolves to it.

We'll have to wait and see.

[Tuatara]

Yep. I'd agree, ed's emulator looks belly up for the moment.

In turn, pointing a browser at Orac:

http://210.48.107.133/tivo-service/mlog.cgi
http://210.48.107.133:8000/tivo-service/mlog.cgi

both simply return the word "done"

http://210.48.107.133:8888/tivo-service/mlog.cgi

gives no response at all; the browser times out.

Is that what's expected? Does the TiVo request differ in some way?

Cheers
Matt

[Edit: I see from the post below I was using port 8888 on the wrong server ;-). http://202.36.218.218:8888/tivo-service/mlog.cgi in a browser is just like Orac: the word "done".]

[wbeasley]

I have moved the ... lets call it ... bootstrap emulator to port 8888

So the address is 202.36.218.218:8888

That will eliminate any [transparent] proxy issues...

Just to confirm, port 8888 with no emuProxy did not work.

[DJC]

Try 202.36.218.218 for port 8888 (mlog)

[Edit... ok ignore, just saw your edit]

[DJC]

Just to confirm, port 8888 with no emuProxy did not work.

Please post your tclient.conf

[MrGadget]

Obviously we're not all having this problem, and it would appear perhaps it's sporadic for some people. I wonder if those of us affected can find something in common that might indicate the cause of the problem.

For what it's worth (having resolved the issue myself now), my details are as follows:
Emulator with issue: 210.48.107.133 Port 80 (Orac)
Verified no proxy in place (via ISP (Snap) and via http://www.lagado.com/proxy-test )
Image 1.3
My issue occured while I was away when my router dropped the connection on Aug 16 which I reset Aug 21st - all calls thereafter failed with a timeout (even after manually loading data). This apprears to be the theme with everyone - that is, no attemped guide downloads for a period, then failure on first attempt thereafter...

As noted I did resolve the issue (though not identify) with steps previously mentioned.

I post this only in the hope that it helps :-)