service unavailable message

[Donaldovitch]

Hi all
Just got my TiVo back from a most helpful Darren King who fixed a sound problem and installed the latest software (R1.6.2).
Although settings are unchanged, and I have the same ISP, I can now not make a daily call, receiving a "service unavailable"message after some time trying to connect.
I can open and use TiVowebplus, and can telnet into TiVo.
It appears the problem is between my ADSL modem and the TiVo server.
( I am really inexperienced in this area, and in linux)
I am attaching the (long!) log from tclient as suggested by Darren, who seems to have been successful in connecting on 21/22 March before returning the box to me.
Would really appreciate advice.
Don Mitchelmore

Batemans Bay (the land of no linux)

[Darren King]

Just for completeness (even though I have no experience in what Don's problem is) I made doubly sure that I noted down network IP/Subnet/Gateway settings before doing the update. I then changed the IP settings to DHCP to work with my network, completed all updates and tests which included a few automatic daily calls, and then used nic_config_tivo to put back the network settings exactly how they were when I originally got the TiVo in for repair (which BTW turned out to be a power supply of all things!). I verified the settings had "stuck" by rebooting and using a serial connection to review the settings via nic_config_tivo again using the menu option to view current settings.

The only thing I did not do was put the MAC address back as to what it originally was before the update, and the only thing I can think of is that the router/modem is somehow disallowing external communications as a result of this.... although I doubt this would be the root cause of the problem and I am not conversant with what the TiVo logs to provide the clues hence me advising Don that someone here should be able to assist.

If someone can help Don out that would be appreciated to get him up and running again and cure my red face in thinking I had been careful enough to prevent something like this happening :o

[petestrash]

Can you start by going through Configuration_and_Diagnostics (http://minnie.tuhs.org/twiki/bin/view/Network/NetworkingHowto#Configuration_and_Diagnostics) and run those tests and let us know the result.

Also what ISP are you with as there have been a couple that have added nasty proxies the last couple of weeks (also ADSL whether or ADSL2).

Peter.

[Donaldovitch]

Many thanks Peter
1. My ISP advises that I am on ADSL.
I am running TiVo and my box through a Netcomm NB5 plus4 ADSL2+ modem router.

2. My ISP is hotkey.net.au.

3. Attach the results of diagnostics tests.
Am a bit puzzled that I always get
[TiVo] [p0] ~]# as my first putty prompt and not [TiVo]#
If this is unimportant please disregard.

Really appreciate your assistance.
Regards
Don Mitchelmore.

[petestrash]

Well your TiVo passed all those tests ok, so it's probably not a problem your end.
Give hotkey a call and ask them what is the address of their proxy. I tried to find it on their website, but it's missing any technical info.

Peter

[Donaldovitch]

Hi Peter
I spoke to hotkey and they advise that they do NOT use a proxy as part of their normal web setup.
They do have a proxy, which is: proxy.hotkey.net.au, but it is not part of their normal setup.

Cheers

Don Mitchelmore

[petestrash]

Well we can prove either way, lets try the following.

Edit /var/hack/etc/emuProxyZA.conf and add the following 2 lines on the end:

proxyIP=proxy.hotkey.net.au
proxyPort=80

Save the file, reboot, then try a daily call again.

Peter

[Donaldovitch]

hi Peter
You are dealing with a real tyro here.
I have only a little experience of DOS, and no linux.

I used putty to get the prompt [TiVo [p0] ~0]#
then entered the string Edit/var/hack/etc/emuProxyZA.conf
and got "no such file or directory"
obiously i have got it wrong.
What do I do to enter the string and make the changes.
Also how do I save?

Thanks

Don

[Wibble]

I used putty to get the prompt [TiVo [p0] ~0]#
then entered the string Edit/var/hack/etc/emuProxyZA.conf
and got "no such file or directory"


Your best bet is to use pico (AKA nano)
as in:

pico /var/hack/etc/emuProxyZA.conf

(It's got onscreen help)

[petestrash]

Actually we can make it even easier.

Enter the following commands (in red) at the putty prompt:

[TiVo [p0] ~0]# echo " " >> /var/hack/etc/emuProxyZA.conf
[TiVo [p0] ~0]# echo "proxyIP=proxy.hotkey.net.au" >> /var/hack/etc/emuProxyZA.conf
[TiVo [p0] ~0]# echo "proxyPort=80" >> /var/hack/etc/emuProxyZA.conf
[TiVo [p0] ~0]# reboot

Once your tivo is rebooting, you can close putty.

Once ready force a daily call using TiVoWeb or TiVoWebPlus.

Though for the future it would be a good idea to learn how to use one of the editors. Either pico or joe is a good start, and vi once you get the hang of things. You can google for info on all of these.

Peter.

[Donaldovitch]

Used pico (thank you wibble) to add:
# proxyIP=proxy.hotkey.net.au
# proxyPort=80
to emuProxyZA.conf

saved, rebooted TiVo, and tried test call but got service unavailable again.

What should I try now?

Thanks
Don M

[petestrash]

You shouldn't have:

# proxyIP=proxy.hotkey.net.au
# proxyPort=80

You should have:

proxyIP=proxy.hotkey.net.au
proxyPort=80

Adding a '#' in the front tells the computer to ignore anything that comes after it. So in effect it has just ignored what you entered.

Try removing the #'s, reboot and try a daily call again (not test call).

Peter.

[Donaldovitch]

sorry about that.
presumed that all lines started with #
will get myself up to speed with linux!

Last few lines now read
# tcInfo: Fix the submitted TCINFO, so it sends the correct server connection s$
# urlbase: Download slices direct from server, don't go via emuProxyZA
proxyIP=proxy.hotkey.net.au
proxyPort=80

saved, rebooted TiVo and forced daily call
unfortunately still get the service unavailable message.

where now?

Don M

[petestrash]

Now you need to post the contents of your otclient.log, so we can see if it made any difference.

Peter

[Donaldovitch]

Have to close for tonight (5 30AM start)
really appreciate your assistance
will pick up again tomorrow

cheers

Don M

[Donaldovitch]

Where can I get the otclient log?
The otclient logs in TiVowebplus are old files from before my TiVo went to Darren.
Thanks

Don M

[petestrash]

Sorry, I meant the tclient.log it will contain your most recent attempts.

Peter.

[Donaldovitch]

Hi
Attach latest tclient.log for your comment.

Thanks

Don M

[petestrash]

Something is definately still blocking your calls. can you check with hotkey what port their proxy uses. It's commonly port 80, but may be different.

Or even better see if they can exclude minnie.tuhs.org (131.244.9.101)

Can you also try the following command and post your results.

traceroute 131.244.9.101

Peter.

[Donaldovitch]

Have discussed the problem with Hotkey.
They say they do not use a proxy for my internet account.
If they were to use a proxy it would be on port 80.

They can see no reason why I cannot connect to minnie.

They can connect to the URL and to 131.244.9.101

They were trying to be very helpful. Would it help for you to call their 1300 number, as you would probably ask better questions than I am able?

Attach the traceroute results.

Many thanks

Don M

[Donaldovitch]

Hi Peter
Dicussed problem with Hotkey who were most obliging.
They say they have no proxy on my account.
If they did it would be port 80.

They can see no reson why I cannot caontact Minnie
They can connect to the url and to 131.244.9.101

Would it be woth you speaking to them on their 1300 number, as you can certainly ask better question than I.

Attach the traceroute results.

regards
Don M
Having trouble submitting, so this reply may be a duplicate

[petestrash]

Did you give the traceroute some time to run? There are no results shown.

It can take about a minute to complete.

Peter.

[Donaldovitch]

Hi Peter
Attach the results of traceroute.
Each line took about 30 seconds.

Don

[T1voZA]

Hi Don

If you could enable the debug log and trace files in emuProxyZA, this should enable us to determine where the problem lies.

First thing that needs to be done is to kill the running instance of emuProxyZA, this is done as follows:

ps ax (look for the emuProxyZA pid in the list returned)
kill pid (replace pid with the emuProxyZA pid from above e.g. kill 154)

You can now start emuProxyZA with the debug and trace files enabled as follows:

/hack/bin/emuProxyZA -ds /var/log/ -dc /var/log/ -d2 > /var/log/emuProxyZA.log 2>&1 &
Once done, you can initiate a daily call and wait until if fails.

Your TiVo's '/var/log/' directory should now contain a file named 'emuProxyZA.log', this is the debug log. There should also be a number of files named 'epXRequest.log' and 'epXResponse.log' (X being a number), these are the trace files of all the requests made by your TiVo and the responses received from the server. If you could zip up both the debug log as well as all the trace files and post them here, we may be able to determine where things are failing.

[Donaldovitch]

Good morning
Thought I had worked out how to modify the files as suggeted.
However with my nearly zero knowledge of linux, I do not.

1. Found the emuProxy pid (161 in ps ax1, attached)

2. Kill 162 removed it ( ps ax2, attached)

How do I now add the required emuProxy with the debug?

I'm out of my depth I think.

Cheers
Don M

[petestrash]

once emuprozyZa has been killed, all you need to do is copy the line below:

/hack/bin/emuProxyZA -ds /var/log/ -dc /var/log/ -d2 > /var/log/emuProxyZA.log 2>&1 &

and paste it at your prompt in putty and press enter.

Then do a daily call and follow the rest of the instructions.

Peter.

[Donaldovitch]

Good afternoon all.
Added the line as indicated and made daily call.
emuProxyZA.log was there, but no epXResponse.logs

Attach the session.

Thanks

Don M

[T1voZA]

1. Found the emuProxy pid (161 in ps ax1, attached)

2. Kill 162 removed it ( ps ax2, attached)Out of interest, if the pid listed was 161 why did you type "kill 162"? Doing so should have led to a result of "bash: kill: (162) - No such pid" but I do see that emuProxyZA is no longer listed in your "ps ax" listing, not sure why though.



Added the line as indicated and made daily call.
emuProxyZA.log was there, but no epXResponse.logs
The reason no trace files (i.e. epXrequest.log & epXresponse.log) are being created is because the new instance of emuProxyZA is not running due to an existing instance already running. This is indicated by the below lines in the 'emuProxyZA.log' file:

Cannot bind port - are we already running?: Address already in useRun "ps ax | grep emu" to confirm that neither emuProxyZA nor emuProxy is running. If either are there then kill them, if not then reboot your TiVo and try killing them again and running emuProxyZA in debug mode.

[Donaldovitch]

Good morning.
I just cannot kill emuProxy!
Attach log of trying to remove line 162 (161 in my last post was typo).
Basically I
check to see if the line is there with ps ax | grep emu,
open with ps ax,
check the pid number,
command kill 162,
enter,
check that is gone with ps ax
and reboot TiVo

The line always reappears.

I am obviously doing something wrong here, and I do thank you for your persistence with a tyro.

Don M

[MattCallow]

When you reboot the TiVo, emuProxyzA will be restarted. If, after killing emuProxyZA you dont see it listed by the ps command, you can be pretty sure that you've stopped it. Therefore no need to reboot.

[petestrash]

correct, do not reboot at all.

once you have killed it enter the line:

/hack/bin/emuProxyZA -ds /var/log/ -dc /var/log/ -d2 > /var/log/emuProxyZA.log 2>&1 &

Then do a daily call.

Try not to reboot till someone here tells you to.

Peter.

[Donaldovitch]

Good evening.
Followed Peters instructions and added the emuProxy log line after killing the emuProxy line.'
[TiVo [p0] ~]# [TiVo [p0] ~]# ps ax
PID TTY STAT TIME COMMAND
1 ? SW 0:00 init
2 ? SW 0:00 (kflushd)
3 ? SW 0:01 (kswapd)
49 ? SW 0:00 /sbin/shondss.sh
51 S3 SW 0:00 /bin/bash --login
61 ? S 0:00 update (bdflush)
72 ? S 0:00 syslogd -p /var/dev/log -m 10000
74 ? SW 0:00 klogd
75 ? SW 0:00 bash /sbin/tnlited.sh
^@ 77 ? SW 0:00 /sbin/tnlited 23 /bin/bash -login
85 ? SW 0:00 /tvbin/switcherstart -m -F
86 ? S 0:02 /tvbin/mfsd
87 ? S 0:00 fancontrol
115 ? SW 0:00 /tvbin/mcp
121 ? SW 0:00 PipeListen
122 ? S 0:00 Mcp event
123 ? SW 0:00 /tvbin/tcphonehome
135 ? SW 0:00 tivoftpd
136 ? S 0:00 cron
144 ? SW 0:00 FsMpStream
145 ? SW 0:00 PipeListener
^@ 149 ? S 0:00 PhoneHome event hd
151 ? R 0:11 tivosh /hack/TivoWebPlus/httpd-tt.tcl
153 ? S 0:00 /var/hack/autospace/osdcons
156 ? S 0:00 /tvbin/dbgc-mcp
158 ? R 0:00 tivosh /var/hack/autospace/autospace.tcl BG
162 ? S 0:00 /hack/bin/emuProxyZA -s minnie.tuhs.org -p 80
164 ? S 0:00 trickey
182 ? SW 0:00 PipeListener
183 ? R 0:02 /tvbin/myworld
184 ? SW 0:00 FsMpStream
185 ? SW 0:00 PipeListener
^@ 186 ? SW 0:00 TmkSinkMixAud
189 ? SW 0:00 TmkClipCache0
190 ? S 0:00 TmkClipCache1
191 ? R 0:02 TvMomCs22Sink
192 ? SW 0:00 TvMomCs22Sink
196 ? R 0:00 Mediaswitch0
197 ? S 0:00 TvVideoManager
198 ? R 0:00 TvRecorder
199 ? S 0:00 TmkTaskManager
200 ? S 0:03 Scheduler
201 ? S 0:03 Prioritizer
202 ? S 0:00 EventLog event
203 ? S 0:00 PvrMain
^@ 204 ? SW 0:00 bus handler
^@ 205 ? S 0:02 ContextMgr eve
207 p0 SW 0:00 /bin/bash -login
209 p0 RW 0:00 ps ax
[TiVo [p0] ~]#
[TiVo [p0] ~]# kill 162
[TiVo [p0] ~]#
[TiVo [p0] ~]# /hack/bin/emuProxyZA -ds /var/log/ -dc /var/log/ -d2 > /var/log/emuProxyZA.log 2>&1 &
[1] 210
[TiVo [p0] ~]#
[TiVo [p0] ~]#


Then ran a daily call, but it stayed on "connecting"for two hours, so I rebooted and tried again with the same result.
The ps ax | grep emu command suggested by TivoZA gave:

[TiVo [p1] ~]# ps ax | grep emu
210 ? S 0:00 /hack/bin/emuProxyZA -ds /var/log/ -dc /var/log/ -d2
[TiVo [p1] ~]#
[TiVo [p1] ~]#

The complete emuProxy log line does not appear.

Have tried all of this several times

Where now?

Regards

Donaldovitch

[T1voZA]

Where now?Try running emuProxyZA as you did but instead of outputting the debug content to a file, output the content to your putty terminal. This is done by dropping everything after the "-d2" in the above line, i.e. type the following:

/hack/bin/emuProxyZA -ds /var/log/ -dc /var/log/ -d2

[Donaldovitch]

Good morning!

Opened ps ax, then Killed emuProxy file 62, pasted the shortened line and entered.
Results from putty:

[TiVo [p0] ~]# ps ax
PID TTY STAT TIME COMMAND
1 ? SW 0:00 init
2 ? SW 0:00 (kflushd)
3 ? SW 0:00 (kswapd)
49 ? SW 0:00 /sbin/shondss.sh
51 S3 SW 0:00 /bin/bash --login
61 ? S 0:00 update (bdflush)
72 ? S 0:00 syslogd -p /var/dev/log -m 10000
74 ? SW 0:00 klogd
75 ? SW 0:00 bash /sbin/tnlited.sh
77 ? SW 0:00 /sbin/tnlited 23 /bin/bash -login
85 ? SW 0:01 /tvbin/switcherstart -m -F
86 ? S 0:03 /tvbin/mfsd
87 ? S 0:00 fancontrol
115 ? SW 0:00 /tvbin/mcp
120 ? SW 0:00 PipeListen
121 ? S 0:00 Mcp event
122 ? SW 0:00 /tvbin/tcphonehome
135 ? SW 0:00 tivoftpd
136 ? S 0:00 cron
141 ? SW 0:00 FsMpStream
142 ? SW 0:00 PipeListener
145 ? S 0:00 PhoneHome event hd
153 ? R 0:11 tivosh /hack/TivoWebPlus/httpd-tt.tcl
155 ? S 0:00 /var/hack/autospace/osdcons
156 ? S 0:55 /tvbin/dbgc-mcp
158 ? R 0:00 tivosh /var/hack/autospace/autospace.tcl BG
162 ? S 0:00 /hack/bin/emuProxyZA -s minnie.tuhs.org -p 80
164 ? S 0:00 trickey
182 ? SW 0:00 PipeListener
183 ? S 0:02 /tvbin/myworld
184 ? SW 0:00 FsMpStream
185 ? SW 0:00 PipeListener
186 ? SW 0:00 TmkSinkMixAud
189 ? SW 0:00 TmkClipCache0
190 ? S 0:00 TmkClipCache1
191 ? R 0:00 TvMomCs22Sink
192 ? SW 0:00 TvMomCs22Sink
193 ? R 0:00 Mediaswitch0
194 ? R 0:00 TvVideoManager
195 ? R 0:00 TvRecorder
196 ? S 0:00 TmkTaskManager
197 ? S 0:04 Scheduler
198 ? S 0:02 Prioritizer
199 ? S 0:00 EventLog event
203 ? R 0:00 PvrMain
204 ? SW 0:00 bus handler
205 ? S 0:01 ContextMgr eve
212 p0 SW 0:00 /bin/bash -login
214 p0 RW 0:00 ps ax
[TiVo [p0] ~]#
[TiVo [p0] ~]# kill 162
[TiVo [p0] ~]#
[TiVo [p0] ~]# /hack/bin/emuProxyZA -ds /var/log/ -dc /var/log/ -d2
emuProxyZA (version 4.1.40)

Guide server listener created
Time offset listener created



Accepted connection on port: 80
Date/Time: Tue Apr 3 12:06:19 2007
timeWeekdayOverride: 0, Difference: 1175601979
Server socket created
DNS address detected (proxy.hotkey.net.au), attempting to resolve to an IP address
Failed to find server IP for given DNS!
: Resource temporarily unavailable
Function getIPAddress returned an empty IP address with value 0.0.0.0

Regards
Donaldovitch

[T1voZA]

DNS address detected (proxy.hotkey.net.au), attempting to resolve to an IP address
Failed to find server IP for given DNS!
: Resource temporarily unavailable
Function getIPAddress returned an empty IP address with value 0.0.0.0You need to edit the '/etc/resolv.conf' file and set the nameserver to the IP address of your router or the IP address of your ISP's DNS address. The edited file should look as follows (replace '192.168.1.1' with your router IP or ISP's DNS address):

# Example resolv.conf file
nameserver 192.168.1.1
# nameserver 192.168.14.1
# nameserver 192.168.14.2Once done, you need to restart emuProxyZA or reboot the TiVo after which you can try debugging the call-in again.

[Donaldovitch]

OK
Have got IP of my ISP (202.138.0.10) and of my modem (192.168.1.1)

However I canot figure out how to edit the IP
.................................................. ...........................
[TiVo [p0] ~]# cd /etc/
[TiVo [p0] /etc]#
[TiVo [p0] /etc]# dir
boot.expect nsswitch.conf rc.net.orig
build-version oztivo.conf resolv.conf
chap-secrets oztivo_version resolv.conf.backup
chat-script palmod.conf services
dflt_sysinit.conf pap-secrets syslog.conf
dhclient-script postcodezones tclient.conf
dhclient.conf ppp-options tclient.conf-oztivo
fstab ppp-options.cua3 tclient.conf.orig
fstab.hda4 ppp-options.orig tclientUK.conf
fstab.hda7 profile termcap
hosts protocols termcap.orig
inittab psdevtab tivoconfig
mtab rc.d update_exclude
[TiVo [p0] /etc]#
[TiVo [p0] /etc]# more resolv.conf



search
nameserver 192.168.1.254
resolv.conf lines 1-2/2 (END)
.................................................. ................................

This is simply due to my lack of understanding.
Should I bone up on linux before proceeding?
If so could you point me to a good tutorial?

Unfortunately I have been unable to find anyone fluent in linux in this area (South coast of NSW)

Really appreciate your forbearance and patience.

Regards
Donaldovitch

[Darren King]

OK
Have got IP of my ISP (202.138.0.10) and of my modem (192.168.1.1)
However I canot figure out how to edit the IP
This is simply due to my lack of understanding.
Should I bone up on linux before proceeding?
If so could you point me to a good tutorial?


Hi Don.

OK here's a little secret: You really don't need to know anything about linux to do what is requested of you. You have said that you can handle DOS without too much hassle and to be honest if you approach what you are doing pretty much the same as editing a config.sys or autoexec.bat file then you are almost home free. There's only a few little differences, namely:

use ls to list a directory
use cd to change directory
use ro to make the file system read only
use rw to make the file system read/write
use nano [filename] to text edit a file
use reboot to reboot the TiVo

That's about all you need to get you out of trouble with most basic things in addition to some of the commands given by Peter and TiVoZA in above posts.

The only gotcha you must remember is to issue a rw before starting otherwise no changes will be made, and after finishing issue a ro to put the file system back to read only.

So in your case this time do the following:

rw
cd /etc
nano resolv.conf
<do your editing and then save>
ro

[Donaldovitch]

Thank you Darren and al who are helping with ths problem.I will persist!
however will have to desist for a few days, as
1. we are having power outages (some planned) when I am able to work on the computer.
2. I am of to Melbourne to see my Daughter perform in the Comedy Festival over Easter.

Will be back on as soon as possible.
Regards

Donaldovitch

[Donaldovitch]

Good morning
I am back home and have worked out how to edit the IP address in resolv.conf

Changed it to my ISP's primary DNDS IP taken from their website

DNS IP Address:
Primary 202.138.0.10 (wallace.hotkey.net.au)
Secondary 202.138.0.11 (gromit.hotkey.net.au)

Killed emuProxy and ran trace

Results:
[TiVo [p0] ~]# ps ax
PID TTY STAT TIME COMMAND
1 ? SW 0:00 init
2 ? SW 0:00 (kflushd)
3 ? SW 0:00 (kswapd)
49 ? SW 0:00 /sbin/shondss.sh
51 S3 SW 0:00 /bin/bash --login
61 ? S 0:00 update (bdflush)
72 ? S 0:00 syslogd -p /var/dev/log -m 10000
74 ? SW 0:00 klogd
75 ? SW 0:00 bash /sbin/tnlited.sh
77 ? SW 0:00 /sbin/tnlited 23 /bin/bash -login
85 ? SW 0:00 /tvbin/switcherstart -m -F
86 ? S 0:02 /tvbin/mfsd
87 ? S 0:00 fancontrol
115 ? SW 0:00 /tvbin/mcp
121 ? SW 0:00 PipeListen
122 ? S 0:00 Mcp event
123 ? SW 0:00 /tvbin/tcphonehome
135 ? SW 0:00 tivoftpd
136 ? S 0:00 cron
143 ? SW 0:00 FsMpStream
144 ? SW 0:00 PipeListener
145 ? S 0:00 PhoneHome event hd
157 ? S 0:00 /var/hack/autospace/osdcons
159 ? S 0:00 /tvbin/dbgc-mcp
160 ? R 0:09 tivosh /hack/TivoWebPlus/httpd-tt.tcl
162 ? R 0:00 tivosh /var/hack/autospace/autospace.tcl BG
166 ? S 0:00 /hack/bin/emuProxyZA -s minnie.tuhs.org -p 80
168 ? S 0:00 trickey
186 ? SW 0:00 PipeListener
192 ? S 0:02 /tvbin/myworld
193 ? SW 0:00 FsMpStream
194 ? SW 0:00 PipeListener
196 ? SW 0:00 TmkSinkMixAud
197 ? SW 0:00 TmkClipCache0
198 ? S 0:00 TmkClipCache1
199 ? R 0:12 TvMomCs22Sink
200 ? SW 0:00 TvMomCs22Sink
201 ? R 0:00 Mediaswitch0
202 ? R 0:00 TvVideoManager
203 ? R 0:00 TvRecorder
204 ? S 0:00 TmkTaskManager
205 ? S 0:04 Scheduler
206 ? S 0:02 Prioritizer
207 ? S 0:00 EventLog event
208 ? R 0:01 PvrMain
209 ? SW 0:00 bus handler
210 ? R 0:01 ContextMgr eve
211 p0 SW 0:00 /bin/bash -login
213 p0 RW 0:00 ps ax
[TiVo [p0] ~]#
[TiVo [p0] ~]# kill 166
[TiVo [p0] ~]#
[TiVo [p0] ~]# /hack/bin/emuProxyZA -ds /var/log/ -dc /var/log/ -d2
emuProxyZA (version 4.1.40)

Guide server listener created
Time offset listener created

Accepted connection on port: 80
Date/Time: Fri Apr 13 10:50:58 2007
timeWeekdayOverride: 0, Difference: 1176461458
Server socket created
DNS address detected (proxy.hotkey.net.au), attempting to resolve to an IP address
Function getIPAddress returned a valid IP address
Could not connect to server: Connection timed out

[TiVo [p0] ~]#
[TiVo [p0] ~]#

Many Thanks

Donaldovitch

[Donaldovitch]

Hi
Just noticed that my ISP's port is listed as 8080, not 80 as advised by phone.

May be un important, but passed on anyway.

Donaldovitch

[MattCallow]

Then try editing emuProxyZA.conf and change

proxyPort=80
to

proxyPort=8080
then run

/hack/bin/emuProxyZA -ds /var/log/ -dc /var/log/ -d2

[Donaldovitch]

Good morning
Thanks for that
Tried to change port from 80 to 8080 using the pico command as previously
pico /var/hack/etc/emuProxyZA.conf
However got
.................................................. ......................
# 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'


# 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 sen$
# 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$
# 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$
# weekDays: The days of the week you wish to download guide data, list each day$
# locationID: Change your Postal Code
# tcInfo: Fix the submitted TCINFO, so it sends the correct server connection s$
# urlbase: Download slices direct from server, don't go via emuProxyZA


# tcInfo: Fix the submitted TCINFO, so it sends the correct server connection s$
# urlbase: Download slices direct from server, don't go via emuProxyZA
proxyIP=proxy.hotkey.net.au
proxyPort=80
.................................................. ..............................
Tried to change the port but the sequence ^X and Y does not save it.

Should I force this change using the =0 indicated?
If so when is the command issued?

many thanks

Donaldovitch.

[Donaldovitch]

Hi
Also could you lell me the directory in which I can find emeProxyZA.conf
The I can try to modify directly as suggested by Darren.
Thanks

Donaldovitch

[Donaldovitch]

Hi
Just to explain my conundrum.
When I edited the emuProxy file previously to add port and my ISP's IP, I used the command suggested Viz: pico/var/hack/etc/emuProxy.conf

Now when I try this I get the output in my 9.15 log today.

When I work thru the direcories /var, /hack, /etc and list using ls there is no emuProxyZA.conf file listed.

Do hope you can help.

Regards
Donaldovitch

[petestrash]

Sorry, I have been away from the boards for a few days.

You are now typing the wrong file name.

Should be:
pico /var/hack/etc/emuProxyZA.conf

Not:
pico /var/hack/etc/emuProxy.conf

If for some reason it has really disappeared and your post was a typo, then try the following:

[TiVo [p0] /var/hack/etc]# cd ~
[TiVo [p0] ~]# find . / -name emuProxyZA.conf

This will show where the file is located.

Peter.

[Donaldovitch]

Hi Peter
THank you for that

The omission of ZA in the post was a typo.
I have been copying/pasting to putty from the logs I receive, except for pico /var/hack/etc/emuProxyZA.conf
I realised after several tries that there must be a space after pico.

From your suggestions have found that emuProxyZA.conf is in /hack/etc/

[TiVo [p1] ~]# cd /var/hack/etc
[TiVo [p1] /var/hack/etc]#
[TiVo [p1] /var/hack/etc]# cd ~
[TiVo [p1] ~]#
[TiVo [p1] ~]# find . / -name emuProxyZA.conf
/hack/etc/emuProxyZA.conf
[TiVo [p1] ~]#
[TiVo [p1] ~]# cd /hack/etc
[TiVo [p1] /hack/etc]#
[TiVo [p1] /hack/etc]# ls
blocklist.txt crontab trickey.conf
blockpatt.txt emuProxyZA.conf trickey.conf.20050524
cron.d resolv.conf
[TiVo [p1] /hack/etc]#
.................................................. .....................................

But not apparently in /etc
.................................................. .....................................

[TiVo [p1] ~]# cd /etc
[TiVo [p1] /etc]#
[TiVo [p1] /etc]# ls -a
. mtab rc.net.orig
.. nsswitch.conf resolv.conf
boot.expect oztivo.conf resolv.conf.backup
build-version oztivo_version services
chap-secrets palmod.conf syslog.conf
chat-script pap-secrets tclient.conf
dflt_sysinit.conf postcodezones tclient.conf-oztivo
dhclient-script ppp-options tclient.conf.orig
dhclient.conf ppp-options.cua3 tclientUK.conf
fstab ppp-options.orig termcap
fstab.hda4 profile termcap.orig
fstab.hda7 protocols tivoconfig
hosts psdevtab update_exclude
inittab rc.d
[TiVo [p1] /etc]#
.................................................. ...........................................

Do not understand, but this is par for my course!
Then using the command [TiVo [p0] ~]# pico /var/hack/etc/emuProxyZA.conf
I get:
.................................................. .....................................


GNU nano 1.1.9 File: /var/hack/etc/emuProxyZA.conf Modified

# 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'

# 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 sen$
# 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$
# 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$
# weekDays: The days of the week you wish to download guide data, list each day$
# locationID: Change your Postal Code
# tcInfo: Fix the submitted TCINFO, so it sends the correct server connection s$
# urlbase: Download slices direct from server, don't go via emuProxyZA

# tcInfo: Fix the submitted TCINFO, so it sends the correct server connection s$
# urlbase: Download slices direct from server, don't go via emuProxyZA
proxyIP=proxy.hotkey.net.au
proxyPort=8080

proxyIP=proxy.hotkey.net.au
proxyPort=80

proxyIP=proxy.hotkey.net.au
proxyPort=8080

.................................................. .....................................
These last lines are from my recent attempts to edit the Proxy IP and the proxy port as per post of 13/04.

Is the place where these parameters should modified?

By the way, have spoken with my ISP again and they confirm that my "normal" browsing would NOT(default) be through a proxy, and would use port 80. A proxy would only be activated if my system requested it. Then it would be as previously advised (proxy.hotkey.net.au and port 8080

Many thanks
Donaldovitch

[MattCallow]

The file is in the correct place. You now have 3 values for proxyIP and proxy port in your config file. I've tested this on my TiVo, and it appears to take the last values in the file. The last values in your file are the ones we want. So can you try running


/hack/bin/emuProxyZA -ds /var/log/ -dc /var/log/ -d2 -s minnie.tuhs.org -p 80

and then force a daily call and see what happens?

[Donaldovitch]

Good afternoon
Killed emuProxyZA
Ran trace, and attach as Puttyfile 1

Cheers
Donaldovitch

[MattCallow]

It looks like you are now sending and receiving some data, we just need to know what.
There should be some log files in /var/log called ep*.log can you post these as well. On my Tivo, I have the following files after running a test:


[TiVo [p0] /var/log]# ls -l ep*.log
-rw-r--r-- 1 0 0 1058 Apr 16 12:44 ep1Request.log
-rw-r--r-- 1 0 0 150 Apr 16 12:44 ep1Response.log
-rw-r--r-- 1 0 0 1105 Apr 16 12:44 ep2Request.log
-rw-r--r-- 1 0 0 684 Apr 16 12:44 ep2Response.log
-rw-r--r-- 1 0 0 302 Apr 16 12:44 ep3Request.log
-rw-r--r-- 1 0 0 150 Apr 16 12:44 ep3Response.log

[Donaldovitch]

Good morning

Got these results from TiVo
[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 16 16:08 ep1Request.log
[TiVo [p0] /var/log]#
[TiVo [p0] /var/log]#

Thanks

Donaldovitch

[Donaldovitch]

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

[Donaldovitch]

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

Donaldovitch

[MattCallow]

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?

[Donaldovitch]

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

Thank you

Donaldovitch

[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

[MattCallow]

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

[Donaldovitch]

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

[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

[Donaldovitch]

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

Donaldovitch

[MattCallow]

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)

[Donaldovitch]

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

[MattCallow]

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.

[Darren King]

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.

[Donaldovitch]

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

[MattCallow]

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.

[Darren King]

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

[Donaldovitch]

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

Cheers

Don M (donaldovitch)

[Darren King]

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.

[Donaldovitch]

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

[Donaldovitch]

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.

[Darren King]

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 :) )

[Donaldovitch]

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.

[petestrash]

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.

[Donaldovitch]

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

[petestrash]

Run update_oztivo -y

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

Peter

[Donaldovitch]

Thanks Peter
Ran update_oztivo -y

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

Cheers
Don M

[MattCallow]

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

cat /var/hack/etc/emuProxyZA.conf
then copying everything from your terminal window from the the cat command to the next [TiVo [p0] ~]# prompt

[Donaldovitch]

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

[MattCallow]

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?

[Donaldovitch]

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

[Darren King]

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.

[Donaldovitch]

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)

[petestrash]

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.

[Donaldovitch]

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)

[petestrash]

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.