service unavailable message

Ran the test log sequence again, and got a response log this time
Viz:
[TiVo [p0] ~]#
[TiVo [p0] ~]# cd /var/log
[TiVo [p0] /var/log]#
[TiVo [p0] /var/log]# ls -l ep*.log
-rw-r--r-- 1 0 0 24576 Apr 17 17:42 ep1Request.log
-rw-r--r-- 1 0 0 0 Apr 17 08:23 ep1Response.log
[TiVo [p0] /var/log]#

Ran again and got:

[TiVo [p0] ~]# cd /var/log
[TiVo [p0] /var/log]#
[TiVo [p0] /var/log]# ls -l ep*.log
-rw-r--r-- 1 0 0 24576 Apr 17 17:55 ep1Request.log
-rw-r--r-- 1 0 0 0 Apr 17 08:23 ep1Response.log
[TiVo [p0] /var/log]#
[TiVo [p0] /var/log]#
[TiVo [p0] /var/log]#

Not sure if this has any significance but thought I should advise.

Regards
Donaldovitch

Just to advise that all three test log results reported were after the forced daily phone call had failed.

Donaldovitch

OK. Perhaps I should have been clearer. I need to see the contents of the ep*.log files. I was just showing a listing from my Tivo to give you an idea of the filenames.
Can you post contents of the files here?

Thanks Matt
How do I open the files?
Have tried a number of things to no avail

Thank you

Donaldovitch

Correction - can open the files by using the "more" command.
Files are very long (275 lines)
How can I select them all to copy and log?
Sorry for my ignorance, but I just cannot find the answer in any of the articles I have googled.

Regards

Donaldovitch

If you have tivoweb running, then I would suggest going to the logs page, then right clicking on each ep*.log file and saving it to your local machine. Then zip them all up and attach them to your post.
if you don't have TivoWeb running, then you'll have to FTP them

Thanks Matt.
Have TiVoweb running, and will do as you suggest, but have to go pick up my wife, so will do later this evening
Cheers Donaldovitch

Hi Matt
Home again!
Attach the Zipped ep1Request.log file
There was nothing in the ep1Response file. Tried opening it using TiVoweb and putty, but nothing there!
There were 3 other ep1Request.log files with extensions of swn, swo, & swp present, but opening them displayed hiroglyphics.

many thanks

Donaldovitch

Hi Matt
Just for clarity, there were only two ep*.log files present in the trace.

Donaldovitch

hmm, dont understand why the response file is empty. Can you run the test again and post your putty log file (as in port number 48) plus all the ep*.log files - All files from the same test run.

(p.s. the .swn, .swo, & .swp are probably temp files created by an editor)

Good morning
Ran the test again from rebooting TiVo (powere outage actually)
Also cleared contents of log files in TiVoweb.
Once again there were only two ep*.log files, and there was no content in ep1Response.log
Attach contents of ep1Request.log file.
Also attach the Putty log file, which I took from the Putty window.
Is this the "Port 48" log?
If not where do I find it?

many thanks

Donaldovitch

I don't know why our ep1Response.log is empty. The putty log indicates that emuproxyZA has recieved some data, so I don't know why it's not going into the response log.
I don't know what you mean by "Port 48" log.

Sorry, I can't think of what else to try at the moment.

OK I'll jump in at this point.

It may be "forgotten" over the course of this issue that the TiVo was sent to me for repairs and I upgraded the image from 1.4 to 1.6.2 via the methods described on Minnie rather than simply scrub the current 1.4 image and reimage with 1.6.2

I'm just wondering if there may be an issue with the upgrade that is causing anomalities in these tests and ultimately the issue of connection problems which may not show up under a fresh 1.6.2 install?

At everyone's approval I am prepared to express post a small 13 or 20GB test hard disk to Don freshly imaged with 1.6.2 and see if this is successful.

Don: If you can run nic_config_tivo and relay to me all your network setup information that would be good. I'm needing IP,Subnet,Gateway and MAC address information.

If people wish for me to take this path I can image tonight, post tomorrow and Don with have it (hopefully) Friday via Express Post.

Thanks Matt and Darren

Have run the test from scratch several times with the same result - no response log.

The "port 80" comment was only re re Matt's post asking for the putty log. I am not sure what "(as in port number 48) " refers to, as I run putty on port 22.

Thanks for that Darren
Will willingly try out a hard drive set up from scratch.
The info you requested from nic_config_tivo are:
IP address 192.168.1.10
MAC address 00: 0B:AD:80:14:20
Subnet 255.255.255.0
Gateway 192.168.1.1
Timing Optimal

Please let me know what testing I should do when installed,

regards
Donaldovitch

Quote:

---

Originally Posted by Donaldovitch

The "port 80" comment was only re re Matt's post asking for the putty log. I am not sure what "(as in port number 48) " refers to, as I run putty on port 22.

---

Sorry. My mistake (typo). I meant post 48 (as in post number 48 of this thread), not port 48. So yes, it was after the putty log I was after.

OK done. This way comparisons can be made and a final decision from the other contributors can be assessed.

Thanks Darren
That will define the problem area for the group.
Will await with bated breath!

Cheers

Don M (donaldovitch)

No problems.

Posted this morning via Express Post, however your area just falls outside the express network but fingers crossed regardless.

The hard drive is imaged with R1.6.2 plus the latest updates via the update_oztivo -y comand and has been set up with the networking options you provided and boots to the start of Guided Setup. I have also included a copy of 1.6.2 on CD which is the same CD I used to install the hard disk.

I guess the next step is to put it in the TiVo and see if you can connect to complete Guided Setup, tell us your results and go from there.

Thanks Darren
Yes, we live in one of the coastal "holes" in the delivery service industry!
Great place to live though!
Will get into it asap and advise results.

Regards

Don M

Good morning
The imaged hard drive ultimately arrived (thank you Darren), and I did a guided setup.
It all worked and I was able to connect both phonecalls, the TiVo downoaded programs, indexed and is up and running.
I guess my next step is to reimage my own harddrive and setup from scratch.
However before I do this, is there anything I can do that might contribute to the group's knowledge of this problem?
Please let me know.
Many thanks

Donaldovitch

BTW, I was unable to find an IR code that worked from the six available in setup.
I jumped the step to complete the setup and report the above results
Is there some way to enter the code for my austar box ?
The IR signal is OK, being visible to a digital camera.

Hmmmm... Just as I thought. There must be an update bug somewhere. I'll leave it up to the experts to answer this one if you can hold out for one of them to decide as I would not know what to look for, or if something else can be patched into your current hard disk to make it work without the need to reimage.


Regarding the IR codes I take it your original hard disk is working fine with your STB? If this is the case you can retrieve the current IR code number being used through TiVoWEB. Do the following:

Click on the "more" option
Click on the "MFS" option
Click on the "setup" option
Click on the number next to source (there may be more than one if you have two inputs)

You should see a list of info about that input come up. Note down the IR code number that begins with the line "CableBoxCodeNum = ". It will be a 5 digit number starting with a 3 (all OzTiVo generated IR codes start with a 3)

If you have two sources then note down the other one too. When you go back to do Guided Setup from scratch you can search for these numbers through the list and pick them.

(thanks to Peter who showed me how to do this a while ago :) )

Thanks Darren
I will await further comments and suggestions from the forum before going any further.

Thanks for the IR tip.
Will work through that when I get back to my own drive.

reagrds

donaldovitch.

I don't have any immediate suggestions, it appears re-imaging will fix the issue.

If you are interested in trying to get the old drive going again without re-imaging I'm happy to help.

I have a sneaking suspision that your ISP has fixed the proxy, but with the modifications we have made to your original drive this would stop it from working. So if we reset your dirve back to the original settings it would probably work.

Peter.

Thanks Peter
I if you have the patience, would like to have a go at getting my hard drive back without reimaging.
What should I do?

Cheers
Don M

Run update_oztivo -y

Then show us what you currently have in:
/var/hack/etc/emuProxyZA.conf
/etc/resolv.conf

Peter

Thanks Peter
Ran update_oztivo -y

Contents of emuProxyZA.conf and resolv.cof are attached.

Cheers
Don M

The emuProxyZA.conf is incomplete. The important bits are at the bottom of the file. I suggest trying

Code:

---

cat  /var/hack/etc/emuProxyZA.conf

---

then copying everything from your terminal window from the the cat command to the next [TiVo [p0] ~]# prompt

Ran cat /var/hack/etc/emuProxyZA.conf
Result attached.
Hope this helps.

The previous result was the full page after opening the directory /var/hack/etc
Then opening emuProxyZA.conf.

Entering the full line /var/hack/etc/emuProxyZA.conf gave a :"permission denied" result.

Thanks Peter

Don M

Sorry, my mistake. We had the end of the file, not the start.
Now it's all there and it looks like a stock emuProxyZA.conf to me.
resolv.conf also looks like the standard copy.

Just to be clear, are these files from your original drive, or the one posted by Darren?

Good afternoon
The files I sent today are from my own 320Gb hard drive.
I have
1. removed Darren's 20 Gb drive
2. reattached my 320 Gb drive
3. run update_oztivo -y
4. Opened and posted the emuProxyZA.conf and resolv.conf files you have.

Cheers
Don M

Have you tried forcing a daily call yet? I think what Peter eluded to is run the update script to load on a fresh copy of the files in question and see if that now restores a successful call or not.

It worked!
I had not realised that I did not have to make more adjustments to TiVo.
This morning I found that TiVo had made the daily call on its own, and that everything is back to normal!
As expected, I will have to fine tune channel 11 (win-nsw), but other than that everything appears to be back to normal.

I sincerely thank all who have had the patience to work through this with me.
I have personally learned a lot, and I admire your persistence in the face of ignorance
Not sure if this has helped your knowledge base, but it sure has mine!

Cheers
Do M (donaldovitch)

Sorry, have been away from here for a couple of days.

Glad to see it has been resolved. Looks like your ISP has finally excluded minnie from the proxy.

If only they would have done this at the end of March, would have saved a lot of hassles for you.

Peter.

Yes, I rang my ISP (Hotkey) again and the respose was again quite vague.
They seemed bemused that someone would ask about about a proxy, and could only give me the same standard reply, that they did not use a proxy, but if they did it would be on port=80 (althought the website quotes 8080).

In retrospect it would have been better if I had contacted them in (email) writing with a clear explanation of my requirements for connecting TiVo.

Maybe a standard statement of "ISP requirements for OzTiVo" would be a useful tool for us newbie / novices.

Again, many thanks.
Don M
(donaldovitch)

I used to have a quote in one of the transparent proxy wiki's explaining what to ask the ISP, but that seems to have disappeared.

I'll add something again.

Peter.